...
If any online resources have been modified or added to during the release, these must be updated. Particularly XSD schema files served at http://www.fedora-commons.org/definitions/1/0/
must be verified. todo: process for doing this
Release Day
Tag the release
The source must be updated to the release version identifier, and a tag created in subversion for the release.
#Ensure all committers know that the release process is in progress and that no commits to trunk must be made.
#Check out a clean copy of trunk.
#Update all pom.xml files with the release version
#Update the README file in the root directory with the release version
#Update /resources/doc/licence/licence.html with the release version
#Rename /fcrepo-webapp/fcrepo-webapp-fedora/src/main/webapp/admin/fcrepo-client-webadmin-A.B.swf to fcrepo-client-webadmin-X.Y.swf
#Update /fcrepo-webapp/fcrepo-webapp-fedora/src/main/webapp/admin/index.html to point to the renamed file
Do a full build, installation and run ConfigQ tests, verify the name of the installation jar file and check that the web admin client operates correctly from the /fedora/admin URL
When you are satisifed that the release is correctly identified, commit these changes to trunk
Tag the trunk based on the version of the release (e.g. svn copy to tags/release-X.Y)
Prepare static documentation area on website
...
For *nix systems use the following command to add a missing key to the KEYS file: (gpg --list-sigs AB76196 && gpg -a --export AB76196) >> KEYS
Tag the release
Tag the trunk based on the version of the release (e.g. svn copy to tags/release-X.Y)
Build the final distribution
...
- sftp fcrelman@fedora-commons.org
- cd release-archive
- Create a subdirectory based on the release date, e.g. 2009/12-07/fedora-
X.Y/ - Upload all released files to this directory.
Update trunk with a new release identifier
#Update all pom.xml files with a version for the new release. For a point release, this is eg 3.5-SNAPSHOT if the current release is 3.4 (and similarly 4.0-SNAPSHOT for a major release)
#Update the README file in the root directory with the version
#Update /resources/doc/licence/licence.html with the version
#Rename /fcrepo-webapp/fcrepo-webapp-fedora/src/main/webapp/admin/fcrepo-client-webadmin-X.Y.swf to fcrepo-client-webadmin-version.swf
#Update /fcrepo-webapp/fcrepo-webapp-fedora/src/main/webapp/admin/index.html to point to the renamed file
Do a full build, installation and run ConfigQ tests, verify the name of the installation jar file and check that the web admin client operates correctly from the /fedora/admin URL
When you are satisifed that the release is correctly identified, commit these changes to trunk
Complete wiki documentation updates
...