+1, I agree with using Lazy Consensus(CTR) for non-API changes in a
2.2.x branch, until it reaches GA.
-Paul
Justin Erenkrantz wrote:
Assuming that we can get a beta approved to eventually become 2.2.x, I'd
like to propose the following policy that tries to balance the need for
review with the
Assuming that we can get a beta approved to eventually become 2.2.x, I'd like
to propose the following policy that tries to balance the need for review with
the need for stability:
Any code changes can be backported to a release candidate branch from trunk
via lazy consensus (CTR) if it does
+1
[EMAIL PROTECTED] Wednesday, February 23, 2005 9:03:48 AM
Assuming that we can get a beta approved to eventually become 2.2.x,
I'd like
to propose the following policy that tries to balance the need for
review with
the need for stability:
Any code changes can be backported to a release
