On Thu, Nov 01, 2012 at 11:07:12PM -0400, Chip Childers wrote: > Following up on the previous thread about this topic, I'd like to > propose the following release calendar for our next feature release.
Thanks for taking lead on this! > First, note the subject tag of "[ASFCS41]". I'm making 2 assumptions > right now. First, that we should adopt semantic versioning for our > versioning scheme. Second, that our next feature release will be > backward compatible with 4.0.0-incubating. Note that I'm NOT > discussing bug fix releases below. Shout if you disagree with either > assumption! Both of these assumptions seem reasonable to me. > * Docs contributors, does this give us enough time (assuming > concurrent development of docs for new features as much as possible)? I think this is enough time, but I'm curious to hear what other folks think. One "rule" I'd like to propose, though: We shouldn't be landing any features without at least rudimentary documentation. > Here's the proposed schedule: > > 2012-11-01 through 2012-12-30 > Feature and documentation development (obviously ongoing, but > continued during this period) In terms of length of feature/doc development, I think this is in line with other projects and (at least for me) sufficient time for development of the docs work I plan to work on in this cycle. In terms of actually landing on the calendar, though, I have some concerns. I suspect we'll lose at least one week, maybe two, at the end of the cycle due to holidays. We also have the collab conference which will be at the end of November/early December. I suspect we'll lose at least three or four days for many of the contributors who are attending, and more for those of us who are managing the conference. Having a dev cycle that ends between Christmas and New Year's is a little rough. Can we extend this so that (if we keep to the release dates) our feature development cycle is ending at the end of January instead? We'd end up with releases in early April, August, and December 2013 if all works according to plan. Best, Joe -- Joe Brockmeier Twitter: @jzb http://dissociatedpress.net/