Release Checklist

• Verify changes.txt, update version being released in changes.txt
• Don't need to change the versions in the POMs, they are automatically updated to release by the build.
• Authorized person (Lasse) releases. Specify branch and version to be released
• Wait for new version artifacts to become available in Maven Central, verify here (takes a few hours).
• Once the release process is complete, tag the release (named vx.x.x)

git tag -a vX.Y.Z -m "Released as vX.Y.Z"

• Create the Github release, associating it with the created tag
• Update sample applications SDN University and OGM University to use new OGM version. (check the different branches)
• Verify that SDN builds correctly against new the new version of OGM in Maven Central
• Update OGM sub-module POMS on any respective branches (micro, minor or major) to declare a new version.

mvn versions:set -DgenerateBackupPoms=false -DnewVersion=X.Y.Z-SNAPSHOT

Use commit message "Update version to X.Y.Z-SNAPSHOT". Also update OGM README with new versions.

• Update The latest OGM version README.md
• When the TeamCity build is done, collaborate with the authorized person (Lasse) to get the new snapshot version published at https://m2.neo4j.org/content/repositories/snapshots/org/neo4j/neo4j-ogm-core/
• Update SDN poms to use the new OGM snapshot if required
• Update the issue templates
• Announce the release on slack channels