I guess we need to consider how to handle 2.0 versus 2.2 stuff. things like auth providers bring with them new constants, header files, etc - stuff we will be expected to support going forward.
--Geoff
-------- Original Message --------
Subject: Re: Time for 2.2?
Date: Mon, 1 Sep 2003 17:47:54 -0700 (PDT)
From: Justin Erenkrantz <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
David Reid wrote:
Seems like a plan.
Do we then migrate from 2.0 to 2.2 for our *stable* tree? Some extra clarification might be nice...
Well, as Cliff pointed out, we would start issuing releases under the 2.1 moniker. Then, when we're all feeling warm and fuzzy about 2.1, we'll call it 2.2, and open APACHE_2_2_BRANCH. HEAD would then become 2.3. APACHE_2_0_BRANCH would still be open.
Ideally, we'd recommend that 2.0 users migrate to 2.2 because it's 'stable' and has more feature, blah, blah, blah.
And, to re-iterate, I forsee this process taking a few months. -- justin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
