...

• 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 manager privileges on the Fedora Repository Drupal site.
• You have an account with edit privileges on the duraspace.org Confluence wiki.
• You have an oss.sonatype.com account and have requested to be given permission to publish to the org.fcrepo groupId by adding a comment to the Fedora Sonatype Hosting Ticket
• You have project configuration privileges on JIRA (you'll see an error here if you don't)
• Your maven settings.xml includes the following:

...

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

Close the release in Jira, and create the next one

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

...