Skip to content

Release Checklist

Nicolas Mervaillie edited this page Mar 29, 2017 · 21 revisions
  • 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.
  • 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
  • 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, then update OGM sub-module POMS on any respective branches (micro, minor or major) to declare a new version. Also update OGM README with new versions.
  • 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
  • Announce the release on slack channels
Clone this wiki locally