Page History

...

Push Release Branch to Maintenance

The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.

...

Ensure that your commit history matches the release branch's commit history, except for the two additional commits.
 

1. Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
2. Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration

...

If this appears correct, you can push your release branch on to the maintenance branch.

...

1. Go to the release management page.
2. For the release you just made (there should be an open package icon to the left of it)
   
   1. click the gear icon on the left and choose "release"
   2. enter the date you finished the release
   3. the package should be closed
   4. if you are not already listed as the release manager in the description, enter "Release Manager: your-name-here"
3. Create the next release
   1. enter a name (ie, Fedora 4.x.y) in the form at the top, and click Add.  If the release manager is known, enter that in the note.

Update the Fedora Repository site

Fedora Repository site (Drupal): http://www.fedorarepository.org/

• Update Download page based on Downloads page in wiki
• Update News on front page with release information
• Update Features page with current version number
• Update Documentation page with link to current release documentationNo need to perform this step until the website refactor has been performed.

Announce release

Let Carol Minton Morris know that the release is complete and can be announced.

...