On Apr 13, 2008, at 3:32 AM, Justin Erenkrantz wrote:
On Sat, Apr 12, 2008 at 9:52 PM, Ruediger Pluem <[EMAIL PROTECTED]>
wrote:
My proposal is for every 2 months, we do a release of the main
stable
branch, which at this time is 2.2.x.
I would like to go for 3 month, so four times per year or once each
quarter.
I think it's a good idea - except I think 2 months is a little too
frequent as well. That means 1 week out of every 8 that we're
spending checking and testing the release. 1 out of 12 weeks eases it
a bit...so +1 for every three months. -- justin
Plus, every 3 months would coincide with the report-to-board cycle,
making it easier for everyone to follow :) Next is due in May, so
if we release this month, then we can follow a "Release before
the board report" or else "Release at board report" cycle (with
the caveat I noted before ;) )
As noted (and as I pinged a few people about in Amsterdam), I'm
looking to push for a 2.2.9 soon. We have enough for sure
warrant it... There is the "ship 1.3.0 with 2.2.9" thread going on,
but I do not want 2.2.9 to hold off too long for that...
So I'd like to propose 2.2.9 for the end of this month.
