On Wed, Oct 31, 2012 at 08:26:05PM -0400, Chip Childers wrote: > Digging this out of the past, IIRC, we never got around to resolving > the time period for releases. We should come to a conclusion on this > topic! I'd like to propose that we follow a 4 month release cycle for > non-bug fix releases.
Sounds reasonable. > Generally, it would mean a schedule that would look something like > this (M=Month and W=Week): > M1 through M2 - Features are being developed in branches, and merged > into master over the course of these two months > M2 W4 - Feature freeze (and release branch is cut). > M3 W1 through M4 W1 - Doc Updates and Testing > M4 W1 - Docs Freeze > M4 W2 - Final regression testing / bug fixes / doc fixes > M4 W3 - First RC cut and opened for voting... Wash rince repeat until > an RC is voted to be released Though we don't yet have a big translation community, we should probably plan for translations in here somewhere after docs freeze. 3-4 weeks should give time for translations. Ideally, though - docs should be updated through the process. (i.e., let's not wait until M3W1 to start doc updates, please.) I assume M4 W3 is also code freeze? Do we plan milestone releases between M2 W4 and M4 W3, or are we assuming folks will just use builds out of Jenkins or ...? > If we can reach a consensus on this, I'll be happy to draft up a > schedule with specific dates for our 4.1.0 release. > > Thoughts, comments, flames? Looks reasonable to me. Best, Joe -- Joe Brockmeier Twitter: @jzb http://dissociatedpress.net/
