On Wed, Jan 11, 2012 at 2:41 PM, Yonik Seeley <[email protected]> wrote:
> From the other comments in this thread, it feels like an actual 4.0 > would be months off. I'd think we could cut a 4.0 alpha today, after branching. Sure it'd have caveats (certain issues are in progress, APIs may change, etc.), but that's all par-for-the-course for an alpha release. > Branching so soon would just cause that much more merging work, which > would quickly get difficult if people made meaningful changes to 5x. Merging is low-cost when the branches haven't diverged much, as will be the case during 4.0's release process. It does take discipline though, on the committers' parts, to remember/choose/decide on each commit whether/where it should be back ported. > Are there really any large 5x changes that people want to start > working on *now* rather than working on 4.0? That question is by definition unanswerable in open-source. You can never know who suddenly wants to work on something crazy... and trunk should never be frozen to such changes. Trunk should always be open for the next major release, no restrictions. By having a bug-fix only 3.6 branch, a stable 4.x branch, and an "anything goes" trunk, we don't have to answer this question. Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
