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.

Prerequisites

Before Release Day

Verify release privileges

To make sure release day goes smoothly, you should Before attempting to perform a release, ensure that:

• The test cycle for this release is complete.
• You have an account with commit and release privileges for the fedora-commons project on sourceforge.net. As a committer, you should already have this level of access.
• You have the login details for the fcrelman account at fedora-commons.org.  If you don't have this information yet, you can get it from the previous release manager.

Release Steps

Snapshot previous documentation

...

1. Go to the documentation space's homepage: http://fedora-commons.org/go/fcr30
2. Select Browse -> Advanced
3. Select HTML Export
4. De-select _inclusionsLibrary and everything beneath it
5. Click Export
6. sftp the zip file to the appropriate directory at fedora-commons.org
   1. Login using the fcrelman account
   2. Follow the symlink at ~/documentation/
   3. Create a subdirectory based on the previous version number, e.g., 3.2.1
   4. Unpack the zip file into the version subdirectory

Prepare and distribute test plan

The test plan should be ready prior to code freeze.

It should include:

• Which platform/database combinations will be tested
• Which automated tests will be run, and by whom
• Which manual tests will be run, and by whom
• Which service tests will be run, and by whom
• Instructions on how testers will report on test results

Announce code freeze

Approximately a week before release, the trunk should be frozen for code updates.  Announce this to the dev mailing list.

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

Copy license and javadocs to static area on website

...