[wp-hackers] 2.3 Dev Cycle

[Robin Adrianse]

I'm +1 for the concept, but maybe, say, 60 days (~ 2 months) for new
features? Keep in mind that also includes debating the feature, how it will
be implemented, and so on. I like the idea of feature-freezing for QA,
though.

On 5/16/07, Geoffrey Sneddon <foolistbar at googlemail.com> wrote:
>
> Can I just please say that we should (if we're on a 120 day release
> cycle) have every major code change within the first 40 days? Then
> after 80 days enter a feature freeze? That thereby leaves another 40
> days purely of QA, and would hopefully avoid any chaos like we had
> with tagging in 2.2.
>
>
> - Geoffrey Sneddon
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>