Geoffrey De Smet píše v Pá 24. 06. 2011 v 12:25 +0200: > Here's what I propose: > - For the next 4 weeks, until 22-JUL, we focus on big, risky features. > - The 2 weeks after that, until 5-AUG, we focus on bugfixing and avoid > risky changes. > On 5-AUG, I release 5.3.0.Beta1 directly from master. > If needed, we can call it 5.3.0.Alpha1 instead.
+1 for a time-based fixed-length release cycle. It's quite popular these days - Kernel, X.org, Fedora, Eclipse, recently Firefox... With Git, it's very easy to keep stabilization branches and when Final is out, you just merge all the changes back into master. If it's done well, it makes the project more predictable and looks real good. -- Lukáš Petrovický QA Engineer, JBoss Enterprise BRMS Phone: +420 532 294 123 irc: lpetrovi, triceo Red Hat Czech, s. r. o. Purkyňova 99, 612 00 Brno, Czech Republic _______________________________________________ rules-dev mailing list rules-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev
