[wp-hackers] 2.3 Dev Cycle

Alex Günsche ag.ml2007 at zirona.com
Wed May 16 22:00:03 GMT 2007

On Wed, 2007-05-16 at 22:55 +0100, Geoffrey Sneddon 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.

I absolutely agree. There should be a feature freeze at least one month
before the scheduled release.


Alex Günsche, Zirona OpenSource-Consulting
http://www.zirona.com/ | Hilfe für das HQ AC: http://www.prohq.de
PubKey for this address: http://www.zirona.com/misc/ag.ml2007.asc

More information about the wp-hackers mailing list