Browse Source

Document keyserver stuff, possible gotchas while downloading, xml files to update.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@272490 13f79535-47bb-0310-9956-ffa450edef68
master
Magesh Umasankar 23 years ago
parent
commit
3746afe1ab
1 changed files with 26 additions and 5 deletions
  1. +26
    -5
      ReleaseInstructions

+ 26
- 5
ReleaseInstructions View File

@@ -1,6 +1,8 @@
Instructions for making a Release: Instructions for making a Release:


Author: Conor MacNeill
Authors: Conor MacNeill
Stefan Bodewig
Magesh Umasankar


Note: This document was created in the context of releasing Ant 1.5. Note: This document was created in the context of releasing Ant 1.5.
Please interpret the branch names, tags, etc. according to Please interpret the branch names, tags, etc. according to
@@ -60,6 +62,9 @@ Note: This document was created in the context of releasing Ant 1.5.
Before you do that, ensure that the key you use is inside the KEYS Before you do that, ensure that the key you use is inside the KEYS
file in Ant's CVS repository - and that you perform a cvs update on file in Ant's CVS repository - and that you perform a cvs update on
the KEYS file in /www/jakarta.apache.org/builds/jakarta-ant/release/ the KEYS file in /www/jakarta.apache.org/builds/jakarta-ant/release/
Also make sure you have sent the key that you use to a public
keyserver.


8. The beta distribution is now ready to go. Bundle it up into a tar.gz file and 8. The beta distribution is now ready to go. Bundle it up into a tar.gz file and
scp to your apache account. scp to your apache account.
@@ -81,10 +86,26 @@ Note: This document was created in the context of releasing Ant 1.5.
and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these release and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these release
labels. labels.
12. Once that is done, do a test download to make sure everything is OK. If it
looks OK, announce it on ant-dev and ant-user. After a few days pass and
there are no major problems, a wider announcement is made (main jakarta
website, general and announce lists, etc).
12. Once that is done, do a test download to make sure everything is OK. A
common problem may be:
* the file's mime type is not recognized and is interpreted as
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 days pass
and there are no major problems, a wider announcement is made (main jakarta
website, announcements@jakarta.apache.org, etc).
Also ensure you:
* Update antnews.xml (Announcement)
* Update faq.xml (Ant's history details)
* Update index.xml (Announcement, latest release details)
* Update problems.xml (Debug Output details)
Generate the html files by invoking ant on docs.xml - you need jakarta-site2
checked out for this and velocity.jar somewhere in your classpath -
you might choose to put it under lib/optional for auto pick-up.
Commit the modified/generated files and also perform a
cvs update on files in daedalus' www/jakarta.apache.org/ant.


13. As problems in the beta are discovered, there may be a need for one or more 13. As problems in the beta are discovered, there may be a need for one or more
subsequent betas. The release manager makes this call. Each time, the subsequent betas. The release manager makes this call. Each time, the


Loading…
Cancel
Save