Does a template for such a release plan exist from previous releases?
Peter's issues were expressed in his original post:
http://www.mail-archive.com/james-dev@jakarta.apache.org/msg03100.html,
which kicked off this round of discussion. Other folks have added their
viewpoints, which can be found in the archives. Now that we've updated the
Milestone build, I'd amend some of my earlier points.
This is a case where a Wiki would be a useful tool as the details of the
release plan are hashed out.
--- Noel
-----Original Message-----
From: Danny Angus [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 19, 2002 11:43
To: James Developers List
Subject: What do we need to release 2.1
Ok,
1/ we need a release plan, circulated to this list or put into cvs then put
to a vote.
Should include all steps needed to make a release, including..
issue management, fix, close or defer all open bugs.
build & test, make a release candidate available to canvas widest testing
audience
Vote on progress to the next step after completion of issue management.
update all documentation
update website
build, upload, announce
d.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
