Release 5.1.0

[patriknw]

Release Akka Persistence JDBC 5.1.0

~ 1 week before the release

• Check that open PRs and issues assigned to the milestone are reasonable
• Create a new milestone for the next version
• Check closed issues without a milestone and either assign them the 'upcoming' release milestone or invalid/not release-bound
• Close the 5.1.0 milestone

1 day before the release

• Make sure all important / big PRs have been merged by now
• Communicate that a new version is about to be released in Gitter Akka Dev Channel

Preparing release notes in the documentation / announcement

• For non-patch releases: rename the 'akka-persistence-jdbc-x.x-stable' reporting projects in WhiteSource accordingly
• Review the draft release notes
• For non-patch releases: Create a news item draft PR on akka.github.com, using the milestone

Cutting the release

• Wait until master build finished after merging the latest PR
• Update the draft release with the next tag version v5.1.0, title and release description linking to announcement and milestone
• Check that GitHub Actions release build has executed successfully (GitHub Actions will start a CI build for the new tag and publish artifacts to Sonatype)

Check availability

• Check API documentation
• Check reference documentation. Check that the reference docs were deployed and show a version warning (see section below on how to fix the version warnning).
• Check the release on Maven central

When everything is on maven central

• Log into gustav.akka.io as akkarepo
  • If this updates the current version, run ./update-akka-persistence-jdbc.sh 5.1.0
  • otherwise check changes and commit the new version to the local git repository

    cd ~/www
    git status
    git add docs/akka-persistence-jdbc/current docs/akka-persistence-jdbc/5.1.0
    git add api/akka-persistence-jdbc/current api/akka-persistence-jdbc/5.1.0
    git commit -m "Akka Persistence JDBC 5.1.0"
    

Announcements

• For non-patch releases: Merge draft news item for akka.io
• Send a release notification to Lightbend discuss
• Tweet using the @akkateam account (or ask someone to) about the new release
• Announce on Gitter akka/akka
• Announce internally (with links to Tweet, blog, discuss)

Afterwards

• Update version for Lightbend Supported Modules in private project
• Close this issue