diff options
Diffstat (limited to 'src/documentation/content/xdocs/dev/release.xml')
| -rw-r--r-- | src/documentation/content/xdocs/dev/release.xml | 44 |
1 files changed, 22 insertions, 22 deletions
diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml index 8785d8789..fa4dbfa37 100644 --- a/src/documentation/content/xdocs/dev/release.xml +++ b/src/documentation/content/xdocs/dev/release.xml @@ -37,18 +37,18 @@ The purpose of documenting it here is to facilitate consistency, ensure that the <li>Determine whether this is a Release Candidate or a Release.</li> <li>Determine whether further testing is required.</li> <li>Commit any outstanding changes</li> - <li>Create a branch called <code>branches/fop-v_vv</code></li> - <li>Edit release notes (README and status.xml in the root).</li> - <li>Update the index.xml and site.xml for the new version.</li> + <li>Create a branch called <code>branches/fop-v_vv</code></li> + <li>Edit release notes (<code>README</code> and <code>status.xml</code> in the root).</li> + <li>Update the <code>index.xml</code> and <code>site.xml</code> for the new version.</li> <li>Update the version numbers in the release column on the - compliance page; update the compliance in the release column + compliance page (<code>compliance.xml</code>); update the compliance in the release column to the current state (development column).</li> - <li>Update version number in build.xml (not to be merged back + <li>Update version number in <code>build.xml</code> (not to be merged back into trunk).</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>Copy <code>test/fotree/disabled-testcases.xml</code> and + <li>Copy <code>test/fotree/disabled-testcases.xml</code> and <code>test/layoutengine/disabled-testcases.xml</code> to the new version directory <code><version>/fotree/disabled-testcases.xml</code> and @@ -56,40 +56,40 @@ The purpose of documenting it here is to facilitate consistency, ensure that the Copy <code>known-issues.xml</code> to the new version directory. Copy <code>knownissues-overview.xml</code> from the previous to the new version directory.</li> - <li>Delete the previous version directory.</li> - <li>Build the dist files (<code>build[.sh] dist</code>) + <li>Delete the previous version directory.</li> + <li>Build the dist files (<code>build[.sh] dist</code>) and upload them to your web directory on <code>people.apache.org</code></li> - <li>Ask on fop-dev to check the branch and the generated dist + <li>Ask on fop-dev to check the branch and the generated dist files for errors.</li> - <li>Tag the source tree with the release ID. For example, if the release is 0.93: - <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_93 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93</code></li> + <li>Tag the source tree with the release ID. For example, if the release is 0.94: + <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_94 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94</code></li> <li>Make a fresh checkout with the just created tag: - <code>svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93</code></li> + <code>svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94</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>Copy the hyphenation patterns jar file + <li>Copy the hyphenation patterns jar file <code>fop-hyph.jar</code> to lib/ (e.g. from <code>http://sourceforge.net/projects/offo</code></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.93-src.tar.gz</code> etc.</li> + <code>gpg -a -b --force-v3-sigs fop-0.94-src.tar.gz</code> etc.</li> <li>Upload the dist and signature files to your web directory on people.apache.org (An account on minotaur is needed): - <code>scp fop-0.93*.tar.gz* + <code>scp fop-0.94*.tar.gz* chrisg@people.apache.org:public_html/</code></li> <li>Check permissions: <code>chmod 664 ... ; chgrp xmlgraphics ...</code></li> - <li>Add MD5 sums: <code>md5 fop-0.93-src.tar.gz > - fop-0.93-src.tar.gz.md5</code> etc.</li> + <li>Add MD5 sums: <code>md5 fop-0.94-src.tar.gz > + fop-0.94-src.tar.gz.md5</code> etc.</li> <li>Make a test download.</li> - <li>Start a vote for the release on + <li>Start a vote for the release on <code>general@xmlgraphics.a.o</code>. The message should point to the release files and list the MD5 sums (<code>cat *.md5</code>). The vote is open for 72hrs.</li> - <li>When the release is accepted, copy the release files, + <li>When the release is accepted, copy the release files, their md5 sum files and the signature files to /www/www.apache.org/dist/xmlgraphics/fop/ in the subdirectories <code>source</code> and @@ -98,10 +98,10 @@ The purpose of documenting it here is to facilitate consistency, ensure that the the previous version.</li> <li>Update HEADER.html and README.html in people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/</li> <li>Wait 24 hours (for the mirrors to catch up).</li> - <li>Merge the changes of the subversion release branch back + <li>Merge the changes of the subversion release branch back into trunk (not the version number in the build file) and delete the branch.</li> - <li>Deploy the updated documentation to the FOP website.</li> + <li>Deploy the updated documentation to the FOP website.</li> <li>Post announcements on fop-dev and fop-user and other related mailing lists.</li> <li>Ask a Bugzilla admin (Christian Geisert) to add a bugzilla entry for the new release id, or create an issue at @@ -131,7 +131,7 @@ The purpose of documenting it here is to facilitate consistency, ensure that the <li>general@xmlgraphics.apache.org</li> <li>general@xml.apache.org</li> <li>announce@apache.org (from your apache.org address)</li> - <li>xsl-list@lists.mulberrytech.com (subscriber-only)</li> + <li>xsl-list@lists.mulberrytech.com (subscriber-only)</li> <li>XSL-FO@yahoogroups.com (subscriber-only)</li> <li>www-xsl-fo@w3.org</li> <li>docbook-apps@lists.oasis-open.org (subscriber-only)</li> |