diff options
Diffstat (limited to 'src/documentation/content/xdocs/dev/release.xml')
| -rw-r--r-- | src/documentation/content/xdocs/dev/release.xml | 36 |
1 files changed, 24 insertions, 12 deletions
diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml index ef9b34b1c..8b82c9111 100644 --- a/src/documentation/content/xdocs/dev/release.xml +++ b/src/documentation/content/xdocs/dev/release.xml @@ -37,16 +37,26 @@ The purpose of documenting it here is to facilitate consistency, ensure that the <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 (<code>README</code> and <code>status.xml</code> in the root).</li> - <li>Update the <code>index.xml</code>, <code>site.xml</code> and <code>download.xml</code> for the new version.</li> + <li>Edit release notes (<code>README</code> and + <code>status.xml</code> in the root).</li> + <li>Add the release to <code>news-data.xml</code>; + remove links to release notes of older versions from this file.</li> + <li>Update the FAQ (<code>faq.xml</code>) to the new release.</li> + <li>Check and update the copyright year in NOTICE and build.xml.</li> + <li>Update the file <code>doap.rdf</code>, and the files + <code>index.xml</code>, <code>site.xml</code>, + <code>download.xml</code>, <code>fo.xml</code>, + <code>maillist.xml</code>, <code>quickstartguide.xml</code>, + <code>faq.xml</code> and <code>status.xml</code> + in directory <code>xdocs</code> for the new version.</li> <li>Update the version numbers in the release column on the 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 <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> + the new version number, and update the .htaccess file for + redirections.</li> <li>Copy <code>test/fotree/disabled-testcases.xml</code> and <code>test/layoutengine/disabled-testcases.xml</code> to the new version directory @@ -54,17 +64,19 @@ The purpose of documenting it here is to facilitate consistency, ensure that the <code><version>/layoutengine/disabled-testcases.xml</code>. 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> + current to the new version directory, and update the <code>xi:include</code> + links in it.</li> + <li>Update the tab names and directories in tabs.xml</li> <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 files for errors.</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>Tag the source tree with the release ID. For example, if the release is 1.0: + <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-1_0 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0</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_94</code></li> + <code>svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0</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> @@ -74,15 +86,15 @@ The purpose of documenting it here is to facilitate consistency, ensure that the <li>Alternatively, create a build-local.properties file that points to the above libs.</li> <li>Run build[.sh] dist. Do this using 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.94-src.tar.gz</code> etc.</li> + <code>gpg -a -b --force-v3-sigs fop-1.0-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.94*.tar.gz* + <code>scp fop-1.0*.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.94-src.tar.gz > - fop-0.94-src.tar.gz.md5</code> etc.</li> + <li>Add MD5 sums: <code>md5 fop-1.0-src.tar.gz > + fop-1.0-src.tar.gz.md5</code> etc.</li> <li>Make a test download.</li> <li>Start a vote for the release on <code>general@xmlgraphics.a.o</code>. The message should point |