ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: ant ReleaseInstructions
Date Mon, 18 Aug 2003 10:22:17 GMT
bodewig     2003/08/18 03:22:17

  Modified:    .        ReleaseInstructions
  revise Release Instructions
  Revision  Changes    Path
  1.14      +24 -15    ant/ReleaseInstructions
  Index: ReleaseInstructions
  RCS file: /home/cvs/ant/ReleaseInstructions,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- ReleaseInstructions	13 Aug 2003 06:47:41 -0000	1.13
  +++ ReleaseInstructions	18 Aug 2003 10:22:17 -0000	1.14
  @@ -85,6 +85,10 @@
       The files should go to /www/
       on daedalus.
  +    [[ FIXME: The above URL is definitively wrong, but I can't
  +       remember whether we've put the betas to or some
  +       subdirectory under ]]
   11. Address the available release tags in BugZilla. Create a new tag 1.5Beta1 
       and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these release 
  @@ -95,7 +99,7 @@
         text/plain.  Fix it by using some .htaccess magic (AddEncoding stuff)
       * Your gz.asc files are not being displayed properly (RemoveEncoing stuff)
  -    If it looks OK, announce it on ant-dev and ant-user. After a few
  +    If it looks OK, announce it on dev@ant and user@ant. After a few
       days pass and there are no major problems, a wider announcement is
       made (main jakarta website,,
  @@ -103,8 +107,8 @@
       Also ensure you:
       * Update antnews.xml (Announcement)
       * Update faq.xml (Ant's history details - not for betas)
  -    * Update index.xml (Announcement, latest release details)
  -    * Update problems.xml (Debug Output details - not for betas IMHO -SB)
  +    * 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
  @@ -126,7 +130,7 @@
       To monitor the number of downloads, look at the access_log
       file under /usr/local/apache2/logs
  -15. When the final beta is considered OK, propose a vote on ant-dev to 
  +15. When the final beta is considered OK, propose a vote on dev@ant to 
       officially adopt the latest beta as the Ant 1.5 release. If it is passed, 
       (it usually does,) this would be labelled ANT_15 and built in a similar 
       fashion to the above process.
  @@ -136,20 +140,11 @@
       This time the directory you upload the files to is different and
       you'll have to do some house-keeping for the old release:
  -    * create a directory for the old release in 
  -      /www/ on daedalus.
  -    * Move the release notes, .zip files and corresponding signatures
  -      and md5 hashes of the old release from /www/
  -      to a matching directory structure in
  -      /www/
  -    * remove the remaining files except for the KEYS file from
  -      /www/
       * upload the new release files to 
  +    * remove the symbolic links from /www/
       * Create proper -current symlinks in /www/
   17. Change the links in /xdocs/bindownload.xml and /xdocs/srcdownload.xml,
  @@ -159,10 +154,24 @@
       may want to add a note to that effect to the pages and remove it a few
       days later.
  +18. Clean up.
  +    * remove the remaining files of the previous release from
  +      /www/[source|binary].
  +    * rename the README.html of the old release to
  +      RELAEASE-NOTES-1.4.1.html in
  +      /www/[source|binary] on minotaur,
  +    * remove all *tar* files of the old release from
  +      /www/[source|binary] on minotaur,
  +      leave the *zip* files alone.
   18. Now and perhaps during previous betas any changes on the branch must 
       be merged back into the tree.
   19. At this point in time, the release is done and announcements are made. 
  +    PGP-sign your announcement posts.
       [[TODO: Identify the mailing lists where announcements are to be made.
         Also identify the webpages to which the announcements must go. ]]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message