+0, I'm not a big fan of the extra work but I understand the need. On Mon, May 21, 2012 at 9:22 PM, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
Given that each development cycle usually starts with bigger changes and ends with a couple of stabilization releases, IMHO it makes sense to keep the last branch of a cycle maintained for a while longer.
Our current strategy is to only support two branches at a time, the one being developed, and the one before it. This means that as soon as [N].0 is released, [N-1].5.x is dropped. However, the [N-1].5.x branch is much more stable and polished than the fresh new start of the cycle, so more people would be interested in using that stable version, especially in enterprise situations. Thus, I propose to amend our support rule to keep the end-of-cycle branch active for, let's say, 6 months. Still, this means only that we backport major or critical issues, which would improve the stability of that branch, without any new features. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne