This document is intended to be used and kept up to date by the Fedora Release Manager. It details the steps necessary to perform an official release of Fedora.
The Fedora release process is split into:
Steps to be taken at any time before a release
Verify release privileges
To make sure release day goes smoothly, you should ensure that:
- You have an account with commit access for the fedora project on github. As a committer, you should already have this level of access.
- You have an account with edit privileges on the wiki.lyrassis.org Confluence wiki.
- You have an s01.oss.sonatype.org account and have an existing committer to have requested to be given permission to publish to the org.fcrepo groupId by adding a comment to the Fedora Sonatype Hosting Ticket
Your maven settings (
~/.m2/settings.xml) includes the following:
<settings>
...
<servers>
...
<server>
<id>sonatype-nexus-snapshots</id>
<username>your-sonatype-id</username>
<password>your-sonatype-pwd</password>
</server>
<server>
<id>sonatype-nexus-staging</id>
<username>your-sonatype-id</username>
<password>your-sonatyp-pwd</password>
</server>
<server>
<id>github</id>
<username>your-github-id</username>
<password>your-github-token</password>
</server>
</servers>
...
</settings>
Note about encrypted passwords
Encrypted passwords work for the plugin that references the sonatype-nexus passwords, but NOT the one that uses github. To avoid a cryptic error, enter your github token in plaintext.
Ensure you have a trusted code signing key
- create one if you haven't before
- ensure that it's listed within the committer keys
Steps to be taken for a release candidate
See Release Candidates - Fedora Release Process
