Page History

...

• Go to https://github.com/fcrepo4/$REPO/releases/tag/$REPO-$CURR

• Click Edit tag, and update title to "Release $CURR"
• If appropriate, attach binaries and checksums that have been published to Maven Central
  • e.g. http://repo1.maven.org/maven2/org/fcrepo/fcrepo-webapp/45.50.12/
  • Note: The Maven artifact for fcrepo-webapp-<version>-jetty-console needs to be renamed from war to jar.
  • Note: The checksum files should be of the format "[checksum] [filename]" (MacOSX's md5 requires the use of the -r argument to produce the correct format. I.e. md5 -r fcrepo-webapp-45.70.42.war >> fcrepo-webapp-45.70.42.war.md5).
• Click Publish Release

...

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.

...