Don't worry - as usual theres plenty going on. I've just done a quick check in the sourcecode repository, and there have been 253 source code checkins since 4.3.5's release (most of these also have to be applied to the 3.3.5 branch also). Not all checkin's have public gemini items (e.g. security fixes/partially complete features).

In addition we've been very busy setting up the corporation, and dealing with the backlog of modules now the module release process has gone live. As the process is more formalised now, it involves a lot more people e.g. I've had to audit 5 module's in the past fortnight (including a few that failed, and had to go through the process again), normally I'd probably only have 1 every month or so, so this will definately impact on lots of other people including people from the QA, release manager, security & localization teams. This backlog will clear soon, as it only built up due to us wanting to finalise the release process.

FYI: We're also looking at tweaking our release process. Typically the codebase is always in a state of flux due to chunks of new functionality being checked in. This makes life difficult if we have to get a release out quickly i.e. if a showstopper/security issue is found. We've been discussing changing to twin tracks, a "maintenance" release which solely deals with bug's and is released on a regular fixed schedule, and a "feature" release which has longer periods between releases but allows for integraton of new features (obviously we merge all the fixes from the maintenance track into the feature track before we test and release it). To do this we would need to get a lot of things in place (seperate managers, dedicated people on each version, someone to synchronise when necessary, infrastructure changes etc.), but IMO if we do it would perhaps give us the best of both worlds.

Cathal