I agree with both and also vote for a 6 month cadence for majors. What I would like for majors is to put some effort in defining a realistic roadmap (not just a wish list) and work together to complete it. We have some roadmap definitions in the wiki fruit of the meetups, etc, but I think we need to have a real plan, for it and work together in its tasks (and use better the "fixVersion" field in JIRA).
This is not about the cadence but about the predictability of the releases. Users should know in advance (when possible) what's going to be in the next major. Anyway, I think a 6 month cadence is an appropriate one that could meet most user needs. El 20/06/2014 00:20, "Andrew Phillips" <aphill...@qrmedia.com> escribió: > I propose four potential major release cadences: 6 weeks, i.e., no minor >> releases, 3 months, 6 months, and 1 year. From my experience 3 or 6 >> months seems about right, >> > > Given the time it's taken us to pick up some of the larger candidate > changes for 2.0 (de-asyncing), I'd say 6 months seems more realistic for > now. > > I'd love to propose 3 months, but that's basically once every 2 minor > releases, which seems a pretty tall order at present. > > ap >
