Update release checklist.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_91@358806 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 23 insertions, 19 deletions

diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml
index e67daeb7f..e71463ed9 100644
--- a/src/documentation/content/xdocs/dev/release.xml
+++ b/src/documentation/content/xdocs/dev/release.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!--
-  Copyright 1999-2004 The Apache Software Foundation
+  Copyright 1999-2005 The Apache Software Foundation
 
   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
@@ -35,29 +35,33 @@ The purpose of documenting it here is to facilitate consistency, ensure that the
       <ul>
         <li>Determine whether this is a Release Candidate or a Release.</li>
         <li>Determine whether further testing is required.</li>
-        <li>Edit release notes, and commit any changes.</li>
+        <li>Commit any outstanding changes</li>
+        <li>Edit release notes (relnotes.xml, README, status.xml in the root and in xdocs).</li>
         <li>Update version number in build.xml, and commit the change.</li>
-        <li>Tag the source tree with the release ID. For example, if the release is 0.20.5rc3:
-          <code>cvs tag fop-0_20_5rc3</code></li>
+        <li>Copy trunk documentation directory to a new directory with the version number and update any links and the .htaccess file for redirections.</li>
+        <li>Update the index.xml for the new version.</li>
+        <li>Update the version numbers on the compliance page.</li>
+        <li>Tag the source tree with the release ID. For example, if the release is 0.91beta:
+          <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_91beta</code></li>
         <li>Make a fresh checkout with the just created tag:
-          <code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co -r 
-fop-0_20_5rc3 xml-fop</code></li>
+          <code>https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_91beta</code></li>
         <li>Copy jimi and jai to lib/ (jimi-1.0.jar, jai_core.jar, jai_codec.jar)</li>
         <li>Copy jce-jdk13-119.jar from <link href="http://www.bouncycastle.org/latest_releases.html">
           from http://www.bouncycastle.org/latest_releases.html</link> to lib/</li>
-        <li>Run build[.sh] dist. Use jdk1.3. A Forrest installation is needed.</li>
+        <li>Alternatively, create a build-local.properties file that points to the above libs.</li>
+        <li>Run build[.sh] dist. Do this once using Sun JDK 1.3.1_15 or later and once with Sun JDK 1.4.2_08 or later. A Forrest installation is needed.</li>
         <li>Create signatures. Don't forget to upload your KEY:
-          <code>gpg -a -b --force-v3-sigs fop-0.20.5rc3-bin.tar.gz etc.</code></li>
-        <li>Upload to www.apache.org. (An account on daedalus is needed):
-          <code>scp fop-0.20.5rc3*.tar.gz* 
-chrisg@www.apache.org:/www/www.apache.org/dist/xml/fop/</code></li>
+          <code>gpg -a -b --force-v3-sigs fop-0.91beta.tar.gz etc.</code></li>
+        <li>Upload to people.apache.org. (An account on minotaur is needed):
+          <code>scp fop-0.91beta*.tar.gz* 
+chrisg@www.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/</code></li>
         <li>Check permissions:
-          <code>chmod 664 ... ; chgrp xml ...</code></li>
-        <li>Add MD5 sums: <code>md5 fop-0.20.5rc3-bin.tar.gz &gt;
-          fop-0.20.5rc3-bin.tar.gz.md5</code></li>
+          <code>chmod 664 ... ; chgrp xmlgraphics ...</code></li>
+        <li>Add MD5 sums: <code>md5 fop-0.91beta-bin.tar.gz &gt;
+          fop-0.91beta-bin.tar.gz.md5</code></li>
         <li>Make a test download.</li>
         <li>Wait 24 hours (for the mirrors to catch up).</li>
-        <li>Post announcements on fop-dev and fop-user mailing lists.</li>
+        <li>Post announcements on fop-dev and fop-user and other related mailing lists.</li>
         <li>Add bugzilla entry for the new release id.</li>
       </ul>
     </section>
@@ -65,14 +69,14 @@ chrisg@www.apache.org:/www/www.apache.org/dist/xml/fop/</code></li>
       <title>Resources</title>
       <p>The following is a sample of some other project release checlists, which might be consulted for ideas:</p>
       <ul>
-        <li><jump href="http://cvs.apache.org/viewcvs.cgi/xml-batik/MAINTAIN?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">Batik</jump></li>
-        <li><jump href="http://cvs.apache.org/viewcvs.cgi/ant/ReleaseInstructions?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">Ant</jump></li>
-        <li><jump href="http://jakarta.apache.org/cactus/participating/release_checklist.html">Cactus</jump></li>
+        <li><jump href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/MAINTAIN">Apache Batik</jump></li>
+        <li><jump href="http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions">Apache Ant</jump></li>
+        <li><jump href="http://jakarta.apache.org/cactus/participating/release_checklist.html">Apache Cactus</jump></li>
       </ul>
       <p>Following are links with information about mirroring:</p>
       <ul>
         <li><jump href="http://www.apache.org/dev/mirrors.html">Apache Mirroring</jump></li>
-        <li>Stefan Bodewig's <jump href="http://cvs.apache.org/~bodewig/mirror.html">Making your Downloads Mirrorable</jump></li>
+        <li>Stefan Bodewig's <jump href="http://people.apache.org/~bodewig/mirror.html">Making your Downloads Mirrorable</jump></li>
       </ul>
     </section>
     <section id="announcements">