robert burrell donkin wrote:
i would strongly suggest that you add the creation of at least one release candidate to the plan. a release candidate has a lot of advantages: not only does it allow a wider range of users to test it (a good way to save blushes) but it can be announced in the news section of the jakarta site (a good way to drum up interest) and you get a chance to try out the release procedure (before the real thing).
Why not...
it's very important to remember that the final approval for the full release needs to come from jakarta pmc. (this is for legal reasons.) the current procedure is to copy the pmc with final result of the final release vote and then wait a day or two too allow the pmc time to veto the release. (please subscribe to general at jakarta since this process may change in the future.)
Understood.
one thing that you should decide is whether you're going to do everything (including the upload) or whether you'd prefer to manage the release but have someone else perform the release build and upload. if you do want to do everything, you'd be well advised to read carefully the links about signing releases and then install and configure a signing tool (for example http://www.gnupg.org).
I really like to hand over to as much as possible to other volunteers. Is there anyone volunteering for this? Would you like to help, Robert?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
