...

At this stage, the only updates that may occur in trunk are non-code related or any problem discovered during testing that is considered a show-stopper.  As release manager, you will need to make judgements on a case-by-case basis on what kind of problem constitutes a show-stopper for the release, and whether the release date should be pushed to allow for additional testing.

Release Day

Prepare static documentation area on website

For each Fedora release, there is a permanent documentation URL on the fedora-commons.org website.

For example, http://fedora-commons.org/documentation/3.2^{Image Added}

This URL will always resolve to the appropriate copy of the documentation for that version of Fedora.  For old releases, it will contain a browsable archive of the documentation for that release.  For the current release, it will automatically forward to the live documentation wiki: http://fedora-commons.org/go/fcr30^{Image Added}

In addition, this area is a convenient place to hold static documentation that doesn't naturally fit in the wiki, such as generated documentation (javadocs) and third-party license information for the release.

To prepare this area for the new release:

1. Build the aggregate javadocs for all of trunk
   1. mvn javadoc:javadoc (this will build them in target/site/apidocs)
   2. mv target/site/apidocs target/site/javadocs
2. Copy

...

1. the license information to target/site
   1. cp -r resources/doc/license target/site
2. Create a jar file to upload
   1. cd target/site
   2. jar -cMf static.jar javadocs license
3. Upload the jar to fedora-commons.org
   1. sftp fcrelman@fedora-commons.org
   2. cd documentation
   3. mkdir 3.3
   4. cd 3.3
   5. put static.jar
   6. exit
4. Unpack the jar and ensure the static documentation is viewable on the web
   1. ssh fcrelman@fedora-commons.org
   2. cd documentation/3.3
   3. jar -xf static.jar
   4. rm static.jar
   5. Point your browser to http://fedora-commons.org/documentation/3.3/javadocs^{Image Added} and /license/license.html (these are the full URLs that should be referenced from the documentation in the wiki)
5. Ensure the documentation URL forwards to the wiki
   1. cp ../index.html .
   2. Point your browser to http://fedora-commons.org/documentation/3.3^{Image Added} (it should redirect to the FCR30 wiki space)

Tag the release

Tag the trunk based on the version of the release (e.g. svn copy to tags/release-VERSION3.3)

Build the final distribution

...