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.

...

Note the version of Java against which the release was built.

New Wiki Space

1. If this is a new major or minor point release, copy the current, in-progress documentation to create the release wiki, then update accordingly. Mark the new pages as current, and update the pages in the previous documentation to indicate they are out-of-date.

   1. Add the following header to the previous major release wiki space (see: Space

...

1. 1. Tools ->

...

1. 1. Look and Feel ->

...

1. 1. Sidebar, header and footer)

      No Format
      {note:title=Old Release} This documentation covers an old version of Fedora. Looking for another version? [See all documentation|FF:Documentation]. {note}

If this is a maintenance point release, create separate child release note pages for each release covered by the documentation.
Otherwise, post the release notes in the Release Notes page (see Fedora 4.0.0 Release Notes for an example).

Update any other documentation as needed, per changes/features added with this release.

...

1. 1. 
      

   2. Add the following header to the new release wiki space

      No Format
      {tip:title=Current Release} This documentation covers the current version of Fedora. Looking for another version? [See all documentation|FF:Documentation]. {tip}

      Make sure the license and copyright information is up-to-date with this release.

2. Update permissions on new wiki space to be like the previous space
3. Add "fedora" category to new wiki space
   1. Space Tools → Overview
4. Add logo
   1. Sidebar → Space Details
5. Remove default space pages
6. Set space "Home Page"
   1. Space Tools → Space Details
7. Ensure `noformat` and `code` macros were copied successfully (this is a bug in the Confluence "copy space" utility)
   1. e.g: First Steps
8. Update Documentation wiki page

Close the release in Jira, and create the next one

...