I would like to point out that if we go with option 1 then the lifespan
of 2.1.x will almost certainly be very short.
Stephen Connolly wrote:
can we hurry up and make a decision?
call a vote with the two options:
1. make 2.1.x be the replacement for 2.0.10... we're making no
promises that there'll be a 2.0.10... the new features will now be in
2.2.x
2. spin a 2.1.0-m1 to get the 2.0.10-tc stuff "out there" and push for
2.1.0 in the next 4 weeks... any features not in 2.1 by then will have
to wait for 2.2... after 4 weeks we start stabilizing until we have a
2.1.0 released
Sent from my iPod
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
