On 11/2/12 8:48 AM, "Joe Brockmeier" <j...@zonker.net> wrote:
> > >One "rule" I'd like to propose, though: We shouldn't be landing any >features without at least rudimentary documentation. > +1. Also a Jira ticket so QA can close it as verified. I think we need criteria as to when is a feature "ready"? We don't want half-baked features thrown in because of the rush to meet the Freeze. > >> 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. I agree. December is rough (at least in the U.S).
