From f1a69a352e5c7af5b0f08257d17aca2142c01e45 Mon Sep 17 00:00:00 2001 From: Simon Pepping Date: Wed, 10 Jan 2007 20:59:54 +0000 Subject: [PATCH] Updates after release 0.93, a.o. the new approval procedure git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@494979 13f79535-47bb-0310-9956-ffa450edef68 --- .../content/xdocs/dev/release.xml | 78 ++++++++++++++----- 1 file changed, 59 insertions(+), 19 deletions(-) diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml index ed5069026..bde915824 100644 --- a/src/documentation/content/xdocs/dev/release.xml +++ b/src/documentation/content/xdocs/dev/release.xml @@ -37,39 +37,78 @@ The purpose of documenting it here is to facilitate consistency, ensure that the
  • Determine whether this is a Release Candidate or a Release.
  • Determine whether further testing is required.
  • Commit any outstanding changes
    • -
  • Edit release notes (relnotes.xml, README, status.xml in the root and in xdocs).
    • -
  • Update version number in build.xml, and commit the change.
    • -
  • Copy trunk documentation directory to a new directory with the version number and update any links and the .htaccess file for redirections.
    • -
  • Update the index.xml for the new version.
    • +
  • Create a branch called branches/fop-v_vv
    • +
  • Edit release notes (README and status.xml in the root).
    • +
  • Update the index.xml and site.xml for the new version.
  • Update the version numbers on the compliance page.
    • -
  • Tag the source tree with the release ID. For example, if the release is 0.92beta: - svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_92beta
    • +
  • Update version number in build.xml (not to be merged back + into trunk).
    • +
  • Copy trunk documentation directory to a new directory with + the version number, and update any links and the .htaccess + file for redirections.
    • +
  • Copy test/fotree/disabled-testcases.xml and + test/layoutengine/disabled-testcases.xml to the + new version directory + <version>/fotree/disabled-testcases.xml and + <version>/layoutengine/disabled-testcases.xml. + Copy known-issues.xml to the new version + directory. Copy knownissues-overview.xml from the + previous to the new version directory.
    • +
  • Delete the previous version directory.
    • +
  • Build the dist files (build[.sh] dist) + and upload them to your web directory on + people.apache.org
    • +
  • Ask on fop-dev to check the branch and the generated dist + files for errors.
    • +
  • Tag the source tree with the release ID. For example, if the release is 0.93: + 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
  • Make a fresh checkout with the just created tag: - https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_92beta
    • + svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93
  • Copy jimi and jai to lib/ (jimi-1.0.jar, jai_core.jar, jai_codec.jar)
  • Copy jce-jdk13-119.jar from from http://www.bouncycastle.org/latest_releases.html to lib/
    • +
  • Copy the hyphenation patterns jar file + fop-hyph.jar to lib/ (e.g. from + http://sourceforge.net/projects/offo
  • Alternatively, create a build-local.properties file that points to the above libs.
  • 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.
  • Create signatures. Don't forget to upload your KEY: - gpg -a -b --force-v3-sigs fop-0.92beta.tar.gz etc.
    • -
  • Upload to people.apache.org. (An account on minotaur is needed): - scp fop-0.92beta*.tar.gz* -chrisg@people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/
    • + gpg -a -b --force-v3-sigs fop-0.93-src.tar.gz etc. +
  • Upload the dist and signature files to your web directory + on people.apache.org (An account on minotaur is needed): + scp fop-0.93*.tar.gz* + chrisg@people.apache.org:public_html/
  • Check permissions: chmod 664 ... ; chgrp xmlgraphics ...
    • -
  • Add MD5 sums: md5 fop-0.92beta-bin.tar.gz > - fop-0.92beta-bin.tar.gz.md5
    • +
  • Add MD5 sums: md5 fop-0.93-src.tar.gz > + fop-0.93-src.tar.gz.md5 etc.
  • Make a test download.
    • +
  • Start a vote for the release on + general@xmlgraphics.a.o. The message should point + to the release files and list the MD5 sums (cat + *.md5). The vote is open for 72hrs.
    • +
  • 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 source and + binaries. Create links to all files in the + fop directory. Remove the links to the files of + the previous version.
  • Update HEADER.html and README.html in people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/
  • Wait 24 hours (for the mirrors to catch up).
    • +
  • Merge the changes of the subversion release branch back + into trunk (not the version number in the build file) and + delete the branch.
    • +
  • Deploy the updated documentation to the FOP website.
  • Post announcements on fop-dev and fop-user and other related mailing lists.
    • -
  • Add bugzilla entry for the new release id.
    • +
  • Ask a Bugzilla admin (Christian Geisert) to add a bugzilla + entry for the new release id, or create an issue at + https://issues.apache.org/jira/browse/INFRA.
    • Resources -

    The following is a sample of some other project release checlists, which might be consulted for ideas:

    +

    The following is a sample of some other project release checklists, which might be consulted for ideas: