[Jakarta Lucene Wiki] Updated: ReleaseTodo

[lu...@jakarta.apache.org]

   Date: 2004-11-29T09:49:34
   Editor: ChristophGoller <go...@apache.org>
   Wiki: Jakarta Lucene Wiki
   Page: ReleaseTodo
   URL: http://wiki.apache.org/jakarta-lucene/ReleaseTodo

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,48 +1,105 @@
 Things that should be done when a new release is made:
 
- 1. See [http://nagoya.apache.org/wiki/apachewiki.cgi?ReleaseManager the Apache instructions]
+ 1. See [http://jakarta.apache.org/site/convert-to-mirror.html?Step-By-Step Guide To Distributing Existing Releases Through The ASF Mirrors]
+    and the links that are there.
  2. Announce the release on [http://www.freshmeat.net]
  3. Add the version of the new release to Bugzilla
 
 --------------
 
-We also need to describe how to make a release.  The best notes I can find are at:
+We also need to describe how to make a release.
 
-http://www.mail-archive.com/lucene-dev@jakarta.apache.org/msg01002.html
 
-This is missing a few things, namely:
+ 1. Run unit tests.
 
- run unit tests
+ 2. Update the CHANGES.txt file.
 
- updating the docs
+ Check the email archives, and make sure that there's an entry in this file for every significant CVS commit message.
 
-   (cd ../jakarta-site2; cvs update -d)
+ 3. Update the docs
 
-   edit xdocs/index.html ../jakarta-site2/xdocs/index.xml ../jakarta-site2/xdocs/news/
+ (cd ../jakarta-site2; cvs update -d)
 
-   ant docs
-   cvs commit -m "updating for release XX" docs
+ edit xdocs/index.html ../jakarta-site2/xdocs/index.xml ../jakarta-site2/xdocs/news/
 
- updating the website
+ ant docs
 
-   ssh www.apache.org
+ 4. Commit these changes.
 
-   cd /www/jakarta.apache.org/lucene
+ 5. Start with a clean CVS tree.  The surest way to do this is to check out a new copy from CVS, with the command:
 
-   cvs update
+ cvs -d :ext:$[EMAIL PROTECTED]:/home/cvs co jakarta-lucene
 
- updating the javadocs on the website
+ If you don't do this, at least do:
 
-   ssh www.apache.org
+  ant clean
 
-   cd /www/jakarta.apache.org/lucene
+  cvs update -d
 
-   cd docs
+ The latter should confirm that everything is up to date, and that you don't have any extraneous files lying around.
 
-   tar xzf /www/cvs.apache.org/dist/jakarta/lucene/vXX.XX/lucene-XX.XX.tar.gz lucene-XX.XX/docs/api
+ 6. Build the release with a command like:
 
-   mv api api.old ; mv lucene-XX.XX/docs/api api
+ ant -Dversion=1.2-rc5 dist dist-src
 
-   rm -rf api.old lucene-XX.XX
+ (The version here should be formatted as in default.properties.)
+
+ 7. Examine the results.  Did it build without errors?  Unpack the release somewhere, examine the files, run some simple tests.  Do not proceed further until you are confident that this release is of appropriate quality.
+
+ 8. Tag the files in CVS with the release name.
+
+ The release is tagged with a command like:
+
+ cvs tag lucene_1_2_rc4
+
+ (Note the use of underscores instead of dots or dashes.)
+
+ 9. Sign and create md5 sums for each release file. Release files are:
+
+ lucene-1.2-rc5-src.tar.gz
+
+ lucene-1.2-rc5-src.zip
+
+ lucene-1.2-rc5.jar
+
+ lucene-1.2-rc5.tar.gz
+
+ lucene-1.2-rc5.zip
+
+ 10. Copy the files to the release directory
+   
+  /www/www.apache.org/dist/jakarta/lucene
+   
+  on minotaur.apache.org
+
+ 11. Update the symlinks in the release directory. If this is your first release, add your key to the KEYS file.
+
+ 12. Wait 24 hours to give the mirrors a chance to get the new release.
+
+ 13. Update the website.
+
+  ssh www.apache.org
+
+  cd /www/jakarta.apache.org/lucene
+
+  cvs update
+
+ 14. Update the javadoc on the website.
+
+ This is done by unpacking it from the release that you've just made, moving it into place, then deleting the old version.
+
+  ssh www.apache.org
+
+  cd /www/jakarta.apache.org/lucene/docs
+
+  tar xzf ../../builds/jakarta-lucene/release/v1.2-rc5/lucene-1.2-rc5-tar.gz
+
+  lucene-1.2-rc5/docs/api
+
+  mv api api.old ; mv lucene-1.2-rc5/docs/api api
+
+  rm -rf api.old lucene-1.2-rc5
+
+ 15. Start a new, empty section in CHANGES.txt for the next release.
 
 Ideally we could automate much of this.

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org