http://jakarta.apache.org/site/decisions.html
"Release Plan
"A release plan is used to keep all volunteers aware of when a release is desired, who will be the release manager, when the repository will be frozen to create a release, and other assorted information to keep volunteers from tripping over each other. Lazy majority decides each issue in a release plan. "
Personally, I'd like to try and lock this down so that next milestone can be a release candidate, but everything depends on what comes in "over the transom" once its released =:(
-Ted.
Eddie Bush wrote:
I don't really think we need a revote, but if others do you can count in my +1. At this stage, I'm all for marking new bugs as LATER for the "next release" (whether that be a beta or final). By all means, let's try to knock out the bugs we can between now and the time the beta is cut, but let's cut it none-the-less.
(What is the next milestone we're aiming for? 1.1-final? 1.1-beta-4?)
Peace
Martin Cooper wrote:
On Thu, 26 Dec 2002, Ted Husted wrote:Ok, I'll update the Roadmap and the B3 plan with the appropriate queries, and add a box next to the bugs we are swatting to indicate their status. This will at least make the static list easier to maintain =:0)I just updated the site with your updated release plan. Given that the plan has changed from what people voted on, do we need to ((re-)re-)vote on the updated release plan? <sigh/> I hope not, but I fear so. FYI, we had 9 +1/+0 responses and no -1/-0 responses, so 9 committers responding out of 14 currently listed. -- Martin Cooper
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
