This document is intended to be used and kept up to date by the Release Manger. It details the technical steps necessary to perform an official release of Fedora. PrerequisitesBefore attempting to perform a release, ensure that:
Release StepsSnapshot previous documentationThis step should be done before major changes are made to the documentation wiki for the new release.
Copy license and javadocs to static area on websiteTODO: Describe this Tag the releaseTag the trunk based on the version of the release (svn copy to tags/release-VERSION) Build the final distributionTODO: We need a maven target, or targets for this. The distribution should consist of:
Each filename should include the version number of the Fedora release. Upload and verify the distributionUpload all files to the fedora-commons project at sourceforge.net. Follow the pattern established for previous releases, where all files associated with the release reside in a single "release" folder. In the release notes box, paste the URL to the appropriate release notes page in the documentation wiki. After uploading, download each file and verify the md5 checksums locally (e.g., using md5sum). Change the primary download page on sourceforge so it points to the new fedora-repository installer jar, and change the additional downloads to include the other (non-md5) files. Archive the distributionFor disaster recovery purposes, we keep an archive of files we release to sourceforge. To do this:
Complete wiki documentation updates... Update high-level pages on fedora-commons.org websiteIn the Software section:
On the homepage:
Announce releaseSend a short summary of this release, and a link to the release notes, to Carol Minton Morris (clt6 at cornell dot edu) and work with her to send out the release announcement. Depending on the significance of the release, the announcement will be disseminated in various forms to:
|