At least until someone else comes along and wants to do a
better job at it :-).
May be you'll need to find someone to do that job to help
you be more on 4.0 ? Someone as proposed to do that some time ago.
PS: What's the status of the RPM packaging for jakarta and xml projects ?
At this point of time, I would suggest that we (committers) go
ahead and apply
patches as you receive and test them. When we've accumulated
enough for another
point release (3.2.2), we can go ahead and propose a temporary
freeze on patches
until the release is prepared, then open it up again.
There have recently been a couple of security-related BugRat
reports on 3.2.
Any volunteers to look into these issues and prepare patches for them?
Craig
"Pour la plupart des hommes, se corriger consiste à changer
de défauts."
-- Voltaire
-Original Message-
From: Dan Milstein [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 25, 2000 11:44 PM
To: [EMAIL PROTECTED]
Subject: 3.2 Branch Release Management
Does anyone have any opinions on a process for making commits
to the 3.2 branch? Now that I've got my new fancy committer
status, I'd like to check in some bug fixes there (to mod_jk /
ajp13). However, before I do that, I wanted to check if there
is anyone who is functioning as a Release Manager or anything
like that.
I'm only planning on checking in some tested bug fixes, just
to be clear.
-Dan
--
Dan Milstein // [EMAIL PROTECTED]