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.

• 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.
• Update the version numbers on the compliance page.
• Tag the source tree with the release ID. For example, if the release is 0.91beta: svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_91beta
• Make a fresh checkout with the just created tag: https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_91beta
• 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/
• 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.91beta.tar.gz etc.
• Upload to people.apache.org. (An account on minotaur is needed): scp fop-0.91beta*.tar.gz* chrisg@people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/
• Check permissions: chmod 664 ... ; chgrp xmlgraphics ...
• Add MD5 sums: md5 fop-0.91beta-bin.tar.gz > fop-0.91beta-bin.tar.gz.md5
• Make a test download.
• 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).
• Post announcements on fop-dev and fop-user and other related mailing lists.
• Add bugzilla entry for the new release id.

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

• Apache Batik
• Apache Ant
• Apache Cactus

Following are links with information about mirroring:

• Apache Mirroring
• Stefan Bodewig's Making your Downloads Mirrorable

Here's a collected list of places where to announce new FOP releases:

• fop-dev@xmlgraphics.apache.org
• fop-users@xmlgraphics.apache.org
• general@xmlgraphics.apache.org
• general@xml.apache.org
• announce@apache.org
• XSL-FO@yahoogroups.com
• www-xsl-fo@w3.org
• docbook-apps@lists.oasis-open.org
• dita-users@yahoogroups.com (http://dita-ot.sourceforge.net/)
• http://xslfo-zone.com/news/index.jsp
• http://www.w3.org/Style/XSL/
• http://freshmeat.net/projects/fop/
• any others?