antoine 2003/12/20 08:33:20
Modified: . Tag: ANT_16_BRANCH ReleaseInstructions
Log:
Merge from HEAD
Improve ReleaseInstructions to deliver a doc with a welcome page showing
the version number being delivered.
PR: 25652
Revision Changes Path
No revision
No revision
1.17.2.5 +48 -24 ant/ReleaseInstructions
Index: ReleaseInstructions
===================================================================
RCS file: /home/cvs/ant/ReleaseInstructions,v
retrieving revision 1.17.2.4
retrieving revision 1.17.2.5
diff -u -r1.17.2.4 -r1.17.2.5
--- ReleaseInstructions 16 Dec 2003 14:48:10 -0000 1.17.2.4
+++ ReleaseInstructions 20 Dec 2003 16:33:20 -0000 1.17.2.5
@@ -3,6 +3,7 @@
Authors: Conor MacNeill
Stefan Bodewig
Magesh Umasankar
+ Antoine Levy-Lambert
Note: This document was updated in the context of releasing Ant 1.6.
Please interpret the branch names, tags, etc. according to
@@ -39,17 +40,35 @@
to the right areas of Ant's website. ]]
5. Before a build :
- Update the following files for version number, and commit your changes.
-
- * docs/manual/cover.html
- * docs/manual/credits.html
- * build.xml (version property)
the first beta on the 1.6 branch should be called 1.6Beta1, ...
the version property in build.xml governs the output of ant -version and
the naming of the distribution files.
+ Update the following files for version number:
+
+ On the branch only :
+
+ * docs/manual/cover.html
+ * docs/manual/credits.html
+ * build.xml (version property & manifest-version property)
+
+ Commit your changes.
+
+ On the branch and on the main trunk (*):
+
+ * xdocs/antnews.xml (Announcement)
+ * xdocs/faq.xml (Ant's history details - not for betas)
+ * xdocs/index.xml (Announcement, latest release details, link to
+ manual under "Documentation")
+ * xdocs/srcdownload.xml
+ * xdocs/bindownload.xml
+
+ Generate the html files by invoking ant on docs.xml - you need
+ jakarta-site2 checked out for this. Commit the modified/generated
+ files
+
6. Ensure you have all the external libraries that Ant uses in your
lib/optional directory. To find out what libraries you need, execute
the build with -verbose option and scan for lines beginning with
@@ -101,7 +120,9 @@
12. Address the available release tags in BugZilla. Create a new tag 1.6Beta1
and a 1.7Alpha. Assign all existing 1.6 alpha bugs to one of these
release
- labels.
+ labels. Note that such massive changes can be done at once by choosing
the
+ link "Change several bugs at once" at the bottom of the bug list
+ displaying the 1.6alpha bugs.
13. Once that is done, do a test download to make sure everything is OK. A
common problem may be:
@@ -114,15 +135,7 @@
made (ant website, main jakarta website,
[email protected],
etc).
- Also ensure you:
- * Update antnews.xml (Announcement)
- * Update faq.xml (Ant's history details - not for betas)
- * Update index.xml (Announcement, latest release details, link to
- manual under "Documentation")
-
- Generate the html files by invoking ant on docs.xml - you need
- jakarta-site2 checked out for this. Commit the modified/generated
- files and also perform a cvs update on files in minotaur's
+ and also perform a cvs update on files in minotaur's
/www/ant.apache.org/
Announce beta releases at freshmeat.net (Stefan Bodewig is the
@@ -141,8 +154,8 @@
file under /usr/local/apache2/logs
16. When the final beta is considered OK, propose a vote on [EMAIL
PROTECTED] to
- officially adopt the latest beta as the Ant 1.6.0 release. If it is
passed,
- (it usually does,) this would be labelled ANT_160 and built in a similar
+ officially adopt the latest beta as the Ant 1.6 release. If it is passed,
+ (it usually does,) this would be labelled ANT_16 and built in a similar
fashion to the above process.
17. BUT
@@ -160,15 +173,15 @@
* Make sure that the symbolic link README.html points to the new
RELEASE-NOTES.
-18. Change the links in /xdocs/bindownload.xml and /xdocs/srcdownload.xml,
- regenerate the HTML files, commit and update the site.
+ (**)
+
+18. Update the ant.apache.org site :
- Updating the site includes updating the online manual which should
display
- the manual of ant 1.6.0 instead of 1.5.4
+ running cvs update *.html under /www/ant.apache.org should update the
+ files regenerated and committed in point 5 above (index.html, faq.html,
+ antnews.html, srcdownload.html, bindownload.html).
- As the mirrors may need some days to pick up the new release, you
- may want to add a note to that effect to the pages and remove it a few
- days later.
+ Update the online manual too.
19. Clean up.
@@ -200,3 +213,14 @@
22. You can now reacquaint yourself with your family and friends.
+(*) the xdocs need to be updated on both the branch and the HEAD revision
+ because traditionally the ant.apache.org web site reflects the HEAD
+ revision of the xdocs, but the users downloading a distribution will get
+ the xdocs and the generated html from the branch and will complain if
there
+ are discrepancies in version numbers.
+
+(**) Mirrors : the srcdownload.html and bindownload.html each list a number
of
+ mirrors. For ant 1.6.0 the mirrors picked up the new version in 8 hours
+ or less, the release having been done at midnight on Dec 18th, the
+ mirrors had it on Dec 19th at 8 am. The srcdownload/bindownload pages
both
+ contain a note advising users to be patient immediately after the
release.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
