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 ------------------------------------------------------------------------------ = Vote Mail = - Again, email to the developer mailing list, as {{{[VOTE] Release 3.1-beta-2}}}. + Again, email to the developer mailing list, as {{{[VOTE] Release 4.0-beta-2176}}}. Try to be specific in the email about the timetable, who would do the vote, how long it will last, the rationale, etc. Don't forget to include your +1 vote. @@ -23, +23 @@ {{{ To: tapestry-dev@jakarta.apache.org - Subject: [VOTE] Release 4.0-beta-13 + Subject: [VOTE] Release 4.0-beta-2176 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 4.0-beta-13. + 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-2176. I'll be able to generate the release over the weekend following the vote. Howard M. Lewis Ship: +1 (binding) @@ -63, +63 @@ 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 the {{{version.properties}}} in the file {{project.properties}} as well. + Make sure to update the {{{version.properties}}} value 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. @@ -86, +86 @@ * tapestry-''version''.zip -- larger, zip version of above * tapestry-''version''-docs.tar.gz -- documentation as a web site + In addition, MD5 hash files are created for each of the three files (these are the .md5 files in target/dist). + + Recent change: a large file named target/tapestry-examples-''version''.tar.gz is now created, and must be uploaded to Howard's home page (which is why Howard usually does the builds). It doesn't hurt to give these files a once over to make sure they built correctly (occasionally, build file errors cause erronous files to be included in the distribution). The build scripts should end with a reminder to sign the release. - = Label The Release in CVS = + = Label The Release in SVN = 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-4-0-beta-13}}} (adjust for the correct release). CVS labels can't include periods, so translate those to dashes. + Use SVN to create a copy of trunk to a new folder under tags with the same name as the release. + + This can be done from the IDE, and generates a SVN command like: + + {{{copy -rHEAD https://svn.apache.org/repos/asf/jakarta/tapestry/trunk https://svn.apache.org/repos/asf/jakarta/tapestry/tags/4.0-beta-12}}} = Sign the release = @@ -153, +160 @@ = Update jakarta-site2 = - This is a whole process onto itself; you need Subversion to get the jakarta-site2 stuff. It's yet-another XML-like limited HTML syntax (related to Forrest markup, but not quite). Once you check it out, there are directions on how to proceeed. + This is a whole process onto itself; you need Subversion to get the jakarta-site2 stuff. It's yet-another XML-like limited HTML syntax (related to Forrest markup, but not quite). Once you check it out, there are directions on how to proceeed. The url of the jakarta-site2 svn repository is: {{{https://svn.apache.org/repos/asf/jakarta/site}}} You would need to use the build scripts to rebuild the documentation, then check in the ''derived HTML files'' as well as the XML source files. Yes, I cringe. You need to do three things: + * Add a <release> stanza to the news.xml file. - * Update the correct files in news. It will likely be {{{xdocs/site/news/news-2005-q3.xml}}} or somesuch. - * Update {{{xdocs/index.xml}}} and add an entry pointing to your new news item. * Update {{{xdocs/downloads/downloads.xml}}}. + The <release>s inside <news> are inside <group> elements; if you are the first person to update news.xml in a given calendar quarter, you may need to create a new <group>. - Each news file covers one quarter of one year; there will be many examples (Tapestry and other projects) to copy and paste. Here's your - chance to be creative when describing what's changed and why anyone should care. Don't forget the marketting (but don't overdue it either). About {{{downloads.xml}}} ... mostly you just put the correct release number into the XML entities defined at the top. For interim releases, simply update the release numbers within the relevant {{{<download>}}} entries. For the very infrequent stable releases (i.e., for a 3.1 or 3.2 final release, a rare event) update the download {{{<group>}}} as well. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
