...

1. Edit the Release associated with the tag in GitHub
   1. Add release notes
   2. Upload the binaries
      
      
2. Go to https://oss.sonatype.org and release the staging repository
   1. Navigate to "Staging Repositories"
   2. Select the same project you "Closed" above and hit Release.
3. Update Jira
   1. Mark the version released, moving remaining open issues to the next version.
   2. Do a query for all unresolved issues that affect the previous release and release candidates. Add the new release version as an affected version for each issue in the results.
   3. Batch transition all resolved issues for the version to closed (Don't do this?  It's really annoying in preventing updates to those issues to improve their metadata.)
4. Create Public Release Notes on http://www.apereo.org/uportal
   1. Go to https://www.apereo.org and log in
   2. Create a Product Release
   3. Give the page a title of uPortal X.Y.Z
   4. Add the magic tag uPortal product release
   5. Add a link to the GitHub release page's hosting of the binary releases
   6. Add a short release note, linking to the wiki page and to the GitHub release page
   7. Under the URL path settings section set a URL of: uportal/download/uportal-X-Y-Z
   8. Under Publishing options check Published, Promoted to front page, and Sticky at top of lists
   9. Click Save
   10. Then go and edit the page for the previous release and under Publishing options uncheck Promoted to front page, and Sticky at top of lists
5. Create a news entry on http://www.apereo.org/uportal
   
   1. Add a news entry (type=Article; tag="uPortal news") so that news of the release surfaces to the /uPortal page.
   2. Give it a URL path of uportal-news/uportal-x-y-x
6. Send Email
   1. For a Milestone or RC release, email to uportal-dev is needed.  Be sure to acknowledge those who contributed to the release.
   2. For a GA release also email uportal-user .  Be sure to put the release into context for an existing adopter to understand.
   3. For a GA release also email jasig-announce , announcing the release to a general public audience.  (Do we still do this?  Haven't done this for a couple releases?)
7. Update release notes link to link latest
   1. Update the parent page(s) of the Release Notes page you created for your release to highlight and link your release as the latest.

Cutting a Milestone release

Milestone releases are special in that they're essentially just a tag-and-release of an arbitrary point on an in-flight branch (typically, master, towards the next release).  They are not represented in JIRA.  Consequently, while auditing the state of JIRA as regards the future release is a fine idea, cutting a Milestone release doesn't involve tagging or moving any issues in JIRA.