--On Thursday, August 12, 2004 2:10 AM +0200 André Malo [EMAIL PROTECTED] wrote:
There are also some showstoppers in 2.1 which I don't see resolved until
Oct 1 or Nov 1. IIRC Nick had also a kind of roadmap (?) posted some weeks
ago.This one should also reviewed.
Well, progress isn't going to
I really think the mod_auth stuff makes it so much easier to write
aaa backends, that we're doing a great disservice to our module writers
by holding back on 2.2 even by a single day.
indeed :)
so, can someone comment on what 2.2 (and the subsequent 2.3) mean for 2.0?
that is, if
Geoffrey Young wrote:
so, can someone comment on what 2.2 (and the subsequent 2.3) mean for 2.0?
that is, if everyday hacking is against 2.3 and we propose a new feature to
backport, do we backport to both 2.2 and 2.0? or does it mean that 2.0 has
reached end-of-life and we backport only to
On Thu, 12 Aug 2004, Jim Jagielski wrote:
Geoffrey Young wrote:
so, can someone comment on what 2.2 (and the subsequent 2.3) mean for 2.0?
that is, if everyday hacking is against 2.3 and we propose a new feature to
backport, do we backport to both 2.2 and 2.0? or does it mean that 2.0 has
reached
--On Thursday, August 12, 2004 4:20 PM -0400 Joshua Slive [EMAIL PROTECTED]
wrote:
I would hope we could make a statement like: Major security issues will be
addressed in 2.0 until at least [2.2 release date + 1 year].
If someone volunteers to be a 2.0 security RM, that'll happen. Otherwise, it
At 03:15 PM 8/12/2004, Jim Jagielski wrote:
Geoffrey Young wrote:
so, can someone comment on what 2.2 (and the subsequent 2.3) mean for 2.0?
that is, if everyday hacking is against 2.3 and we propose a new feature to
backport, do we backport to both 2.2 and 2.0? or does it mean that 2.0 has
I would hope that 2.0 is EOLed as soon as possible after 2.2 ships.
Being basically the NetWare platform maintainer of two versions of
Apache (1.3, 2.0) with a development version on top of that, has been
bad enough. Three would be a nightmare and when would it stop? Even
for all but the most
Working backwards and allowing a little time for slip:
Nov 1: Planned final RC tarball for release of 2.2.0
Oct 1: Code freeze of all new features in 2.1-dev (for a month till we
branch head to 2.2.0 and bless HEAD as 2.3-dev)
Thoughts?
Bill
* William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
Working backwards and allowing a little time for slip:
Nov 1: Planned final RC tarball for release of 2.2.0
Oct 1: Code freeze of all new features in 2.1-dev (for a month till we
branch head to 2.2.0 and bless HEAD as 2.3-dev)
