Skip to content

release-train-issue-template.md

Latest commit

 

History

History
77 lines (60 loc) · 4.92 KB

release-train-issue-template.md

File metadata and controls

77 lines (60 loc) · 4.92 KB
Raw

Release Akka $VERSION$

Cutting the release

  • Check that open PRs and issues assigned to the milestone are reasonable
  • If PRs related to clustering were merged after the previous multi-node test run, trigger the multi-node tests and see that they are green.
  • If PRs were merged after EU midnight, trigger the native-image tests and see that they are green.
  • If PRs were merged after the last nightly, trigger nightlies nightly-builds and see that they are green.
  • Run the release-prep script to update LICENSE (version, copyright year, change date + 3y) and bump the akka version in every sample build file. With --commit-and-pr it pushes a wip-release-prep-$VERSION$ branch and opens a PR: ./scripts/release-prep.sh --commit-and-pr $VERSION$
  • Create a new milestone for the next version
  • Close the $VERSION$ milestone
  • Make sure all important PRs have been merged
  • Wait until main build finished after merging the latest PR
  • Create the draft release, click Generate release notes to get a title and release description. Use the Publish release button, which will create the tag.
  • Check that GitHub Actions release build has executed successfully (GitHub Actions will start a CI build for the new tag and publish artifacts to https://repo.akka.io/TOKEN/secure)

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 warning).
  • Check the release mvn dependency:get -Dartifact=com.typesafe.akka:akka-actor_2.13:$VERSION$

When everything is on https://repo.akka.io/TOKEN/secure

  • Log into gustav.akka.io as akkarepo
    • If this updates the current version, run ./update-akka-current-version.sh $VERSION$
    • otherwise check changes and commit the new version to the local git repository 
      cd ~/www
git status
git add libraries/akka-core/current libraries/akka-core/$VERSION$
git add api/akka-core/current api/akka-core/$VERSION$
git add japi/akka-core/current japi/akka-core/$VERSION$
git commit -m "Akka core $VERSION$"
    • push changes to the remote git repository 
      cd ~/www
git push origin master
  • If this updated 'current' docs - trigger a re-index of the docs for search through Run workflow for the scraper

Announcements

For minor or major releases:

  • Include noteworthy features and improvements in Akka umbrella release announcement at akka.io. Coordinate with PM and marketing.

Afterwards