ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From umag...@apache.org
Subject cvs commit: jakarta-ant ReleaseInstructions
Date Wed, 17 Apr 2002 15:14:15 GMT
umagesh     02/04/17 08:14:15

  Modified:    .        ReleaseInstructions
  Log:
  Document keyserver stuff, possible gotchas while downloading, xml files to update.
  
  Revision  Changes    Path
  1.7       +26 -5     jakarta-ant/ReleaseInstructions
  
  Index: ReleaseInstructions
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/ReleaseInstructions,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- ReleaseInstructions	11 Apr 2002 15:53:42 -0000	1.6
  +++ ReleaseInstructions	17 Apr 2002 15:14:15 -0000	1.7
  @@ -1,6 +1,8 @@
   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.
         Please interpret the branch names, tags, etc. according to
  @@ -60,6 +62,9 @@
       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
       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 
       scp to your apache account.
  @@ -81,10 +86,26 @@
       and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these release 
       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 
       subsequent betas. The release manager makes this call. Each time, the 
  
  
  

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message