Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change notification.
The following page has been changed by HowardLewisShip: http://wiki.apache.org/jakarta-tapestry/ReleaseChecklist ------------------------------------------------------------------------------ There are several steps between a consensus forming about a new release, and actually delivering the release. This has been an area of confusion, and the Tapestry team has certainly trodded on a few Jakarta PMC toes. Let's try and get this right in the future! - * Note: certain aspects of this discussion apply to 3.1 and above (such as running the build and packaging the results). + * Note: certain aspects of this discussion apply to 4.0 and above (such as running the build and packaging the results). = Discuss = - This isn't necessarily a step, but should be considered. Before initiating a vote, generate a discussion. Send mail to the developer mailing list with the subject {{{[DISCUSS] Release 3.1-beta-2}}} (adjust for the actual release being proposed). + This isn't necessarily a step, but should be considered. Before initiating a vote, generate a discussion. Send mail to the developer mailing list with the subject {{{[DISCUSS] Release 4.0-beta-13}}} (adjust for the actual release being proposed). Generally speaking, we shouldn't go forward to a vote unless we're pretty sure of the outcome ahead of time. @@ -23, +23 @@ {{{ To: tapestry-dev@jakarta.apache.org - Subject: [VOTE] Release 3.1-beta-2 + Subject: [VOTE] Release 4.0-beta-13 The latest bug fixes really seem to be kicking things into high gear. We should get a release out the door to spot - more problems and see if people can follow the new documentation. This vote will run for a week, a +1 is to release Tapestry 3.1-beta-2. + more problems and see if people can follow the new documentation. This vote will run for a week, a +1 is to release Tapestry 4.0-beta-13. I'll be able to generate the release over the weekend following the vote. Howard M. Lewis Ship: +1 (binding) @@ -61, +61 @@ * Record the vote in a <vote> stanza * Update the {{{version}}} and {{{date}}} attributes of the property <release> stanza - In some cases, the version may need to be updated; it may change from, say, "3.1-alpha-3-snapshot" to "3.1-beta-1" if we decide to follow 3.1-alpha-2 with 3.1-beta-1. + In some cases, the version may need to be updated; it may change from, say, "4.0-alpha-3" to "4.0-beta-1" if we decide to follow 4.0-alpha-2 with 4.0-beta-1. - Make sure to update {{{version.properties}}} as well. + Make sure to update the {{{version.properties}}} in the file {{project.properties}} as well. Finally, take a peek at the {{{KEYS}}} file. You'll sign the KEYS file using your GnuPG or PGP key. Instructions are inside the file itself. This KEYS file is how diligent users validate that the final release is, in fact, authenticated and valid. @@ -96, +96 @@ If the release files are all set, then it's time to lock down the versions in CVS. - Use CVS to label HEAD as {{{release-3-1-beta-2}}} (adjust for the correct release). CVS labels can't include periods, so translate those to dashes. + Use CVS to label HEAD as {{{release-4-0-beta-13}}} (adjust for the correct release). CVS labels can't include periods, so translate those to dashes. = Sign the release = @@ -122, +122 @@ You need to provide your Jakarta login user id (you can also update {{{project.properties}}} for this). - You will be prompted for your password ... in cleartext yet. Sorry! Have to do it. Ant's ssh support doesn't seem to know from ssh-agent. + You will be prompted for your pass phrase ... in cleartext yet. Sorry! Have to do it. Ant's ssh support doesn't seem to know from ssh-agent. The {{{install-dist}}} target installs the main distribution files (plus md5 sums and PGP signatures, and KEYS) into /www/www.apache.org/dist/jakarta/tapestry. This directory is mirrored to all the Apache download mirrors. @@ -137, +137 @@ Send mail to the developer mailing list ... the the checkins begin! - '''Note:''' The first checking should increment the {{{project.version}}} release number, and add "-snapshot" ... i.e., {{{3.1-beta-4-snapshot}}}. + '''Note:''' The first checkin should increment the {{{project.version}}} release number, and add "-snapshot" ... i.e., {{{3.1-beta-4-snapshot}}}. Also, don't forget to create a '''new''' <release> stanza! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
