Proposal: New refined release cycle [WAS: Re: release plan for 2.2.2]

[Nikolaj Hald Nielsen]

I share much the same thoughts as Dan on this one.

- Nikolaj

> As we discussed on IRC, I disagree with this, and heres why:
>
> 1) Much of the new feature development already happens outside of
> trunk, and therefore is ongoing during freezes anyways, this allows
> features to be dumped  in early in the release cycle and already gives
> them more time for testing.
>
> 2) We could roll a beta @ string freeze, which gives us three weeks
> for testing anyways in a 6 week cycle.
>
> 3)  The longer we take between releases, the longer it takes to get
> fixes out.  One of the appeals of such a short cycle is that we don't
> have to feel obligated to make each one absolutely perfect, and be
> tempted to delay a release for a OMGMUSTHAVE feature, because we will
> soon be releasing another version.  The longer we take between
> versions, the more tempting it is to delay a version to get another
> cool new feature in.