Page History

...

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 the license information to target/site
   1. cp -r resources/doc/license target/site
3. Create a jar file to upload
   1. cd target/site
   2. jar -cMf static.jar javadocs license
4. 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
5. 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 and http://fedora-commons.org/documentation/3.3/license/license.html (these are the full URLs that should be referenced from the documentation in the wiki)
6. Ensure the main documentation URL for this version forwards to the wiki
   1. cp ../index.html . (the parent directory already contains an index.html that forwards to the right place in the wiki)
   2. Point your browser to http://fedora-commons.org/documentation/3.3 (it should redirect to the FCR30 wiki space)

Update the KEYS file

Make sure the KEYS file in subversion is up-to-date with the latest, exported public keys of the committers (and most importantly, the release manager).  For more information on this file, see this page.

Tag the release

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

...