From cbe508833d226377bd9eedf018a11c4eb9e84e57 Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Sat, 14 Jun 2003 05:41:18 +0000 Subject: [PATCH] Add release notes (from Christian Geisert's notes). git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196499 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/dev/book.xml | 1 + .../content/xdocs/dev/release.xml | 59 +++++++++++++++++++ 2 files changed, 60 insertions(+) create mode 100644 src/documentation/content/xdocs/dev/release.xml diff --git a/src/documentation/content/xdocs/dev/book.xml b/src/documentation/content/xdocs/dev/book.xml index be3f1829d..10322781a 100644 --- a/src/documentation/content/xdocs/dev/book.xml +++ b/src/documentation/content/xdocs/dev/book.xml @@ -27,6 +27,7 @@ + diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml new file mode 100644 index 000000000..bbfa6ee1d --- /dev/null +++ b/src/documentation/content/xdocs/dev/release.xml @@ -0,0 +1,59 @@ + + + +
+ FOP Development: Release Mechanics +
+ +
+ Introduction +

This page documents the process of creating a FOP release. +FOP releases are coordinated by one member of the team (currently Christian Geisert), so others do not ordinarily need to use this information. +The purpose of documenting it here is to facilitate consistency, ensure that the process is captured, and to allow others to comment on the process.

+

The checklist below was assembled from Christian Geisert's notes. It will be expanded in the future as he has time.

+
+
+ Checklist +
    +
  • Determine whether this is a Release Candidate or a Release.
    • +
  • Determine whether further testing is required.
    • +
  • Edit release notes, and commit any changes.
    • +
  • Update version number in build.xml, and commit the change.
    • +
  • Tag the source tree with the release ID. For example, if the release is 0.20.5rc3: + cvs tag fop-0_20_5rc3
    • +
  • Make a fresh checkout with the just created tag: + cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co -r +fop-0_20_5rc3 xml-fop
    • +
  • Copy jimi and jai to lib/ (jimi-1.0.jar, jai_core.jar, jai_codec.jar)
    • +
  • Run build[.sh] dist. Use jdk1.3. A Forrest installation is needed.
    • +
  • Create signatures. Don't forget to upload your KEY: + gpg -a -b --force-v3-sigs fop-0.20.5rc3-bin.tar.gz etc.
    • +
  • [md5?]
    • +
  • Upload to www.apache.org. (An account on daedalus is needed): + scp fop-0.20.5rc3*.tar.gz* +chrisg@www.apache.org:/www/www.apache.org/dist/xml/fop/
    • +
  • Check permissions: + chmod 664 ... ; chgrp xml ...
    • +
  • Make a test download.
    • +
  • Wait 24 hours (for the mirrors to catch up).
    • +
  • Post announcements on fop-dev and fop-user mailing lists.
    • +
  • Add bugzilla entry for the new release id.
    • +
+
+
+ Resources +

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

+
    +
  • Batik
    • +
  • Ant
    • +
  • Cactus
    • +
+

Following are links with information about mirroring:

+
    +
  • Apache Mirroring
    • +
  • Stefan Bodewig's Making your Downloads Mirrorable
    • +
+
+ + -- 2.39.5