Skip to content

Latest commit

 

History

History
80 lines (61 loc) · 4.95 KB

release-train-issue-template.md

File metadata and controls

80 lines (61 loc) · 4.95 KB
Raw

Release Akka HTTP $VERSION$

Cutting the release

  • Check that open PRs and issues assigned to the milestone are reasonable
  • If PRs were merged after EU midnight, trigger the native-image tests and see that they are gr
  • Update the Change date in the LICENSE file.
  • Update the Akka HTTP version in the samples to $VERSION$, otherwise the published zip files of the samples will have the old version.
  • For minor or major versions, add a release notes entry in docs/src/main/paradox/release-notes/.
  • Create a new milestone for the next version
  • Close the $VERSION$ milestone
  • Make sure all important PRs have been merged
  • For recent dependency updates or changes on a minor release branch the Fossa validation can be triggered from the GitHub actions "Dependency License Scanning" (Manually choosing the release branch)
  • Update the revision in Fossa in the Akka Group for the Akka umbrella version, e.g. 22.10. Note that the revisions for the release is udpated by Akka Group > Projects > Edit. For recent dependency updates the Fossa validation can be triggered from the GitHub actions "Dependency License Scanning".
  • Wait until main build finished after merging the latest PR
  • Update the draft release with the next tag version v$VERSION$, 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/maven)

Check availability

When everything is on https://repo.akka.io/maven

  • Log into gustav.akka.io as akkarepo

    • If this updates the current version, run ./update-akka-http-current-version.sh $VERSION$
    • otherwise check changes and commit the new version to the local git repository 
      cd ~/www
git status
git add docs/akka-http/current docs/akka-http/$VERSION$
git add api/akka-http/current api/akka-http/$VERSION$
git add japi/akka-http/current japi/akka-http/$VERSION$
git commit -m "Akka HTTP $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

  • Update version in _config.yml in https://github.com/akka/akka.io

Announcements

For important patch releases, and only if critical issues have been fixed:

  • Send a release notification to Lightbend discuss
  • Tweet using the @akkateam account (or ask someone to) about the new release
  • Announce internally (with links to Tweet, discuss)

For minor or major releases:

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

Afterwards