[wp-hackers] 120-day release cycle

Stefano steagl at people.it
Tue Oct 3 09:01:45 GMT 2006

On Mon, 02 Oct 2006 05:36:49 +0200, Matt Mullenweg <m at mullenweg.com>

>I think as an experiment after 2.1, we should aim to do a release 
>exactly 120 days after when 2.1 comes out.

Having a scheduled realeases would be great, I think that a 4 month
cycle it's a bit short thinking to have 3 major version per year sound
a bit inrealistic, moving to a 6 month cycle can be a better choice,
tha 2 additional month can be used to:

>2.5 months of crazy fun wild development where anything goes
>1.5 month of polishing things a little bit, and performance
>Feature freeze.
>1 month of testing, with a public beta release at the beginning
1 month to see first ueser feedbacks and pallnning what to include
into next release... a peace period of no development but just brani
storming for next release could help to concentrate to have new
features well determined on "paper" with less chanche we shoudl revise
them after a large base of end users used them.

>What do you folks think about trying this type of release schedule out?

The 1 month test period with a beta would be a greta time for plugind
devs to upgrade theyr plugins and for we translators to have the new
locale ready with less rush than in the past.


Stefano Aglietti - StallonIt on IRCnet - ICQ#: 2078431
Email: steve at 40annibuttati.it steagl at people.it
Sites: http://www.40annibuttati.it (personal blog)
       http://www.wordpress-it.it (WordPress Italia)

More information about the wp-hackers mailing list