Skip to content

Latest commit

 

History

History
69 lines (51 loc) · 4.08 KB

release-train-issue-template.md

File metadata and controls

69 lines (51 loc) · 4.08 KB

Release Akka Management $VERSION$

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

Preparing release notes in the documentation / announcement

  • For non-patch releases:
    • rename the 'akka-management-x.x-stable' reporting projects in WhiteSource accordingly (unfortunately this requires permissions that cannot be shared outside of Lightbend)
    • Create a news item draft PR on akka.github.com, based on the draft release and sbt-authors (eg. ./scripts/authors.scala v1.0.9 HEAD).
  • Move all unclosed issues for this milestone to the next milestone
  • Close the $VERSION$ milestone

Cutting the release

  • Wait until master build finished on GH Actions after the last merge
  • git tag -a v$VERSION$ -m "Release version $VERSION$"; git push --tags
  • Check that GitHub Actions release build has executed successfully (it should publish artifacts to Sonatype and documentation to Gustav)

Check availability

When everything is on maven central

  • ssh [email protected]
    • update the current links on repo.akka.io to point to the latest version 
      ln -nsf $VERSION$ www/docs/akka-management/current
ln -nsf $VERSION$ www/api/akka-management/current
    • check changes and commit the new version to the local git repository 
      cd ~/www
git add docs/akka-management/ api/akka-management/
git commit -m "Akka Management $VERSION$"

Announcements

  • Update the draft release, either with the content from the news item, or by revising and adding the sbt-authors (eg. ./scripts/authors.scala v1.0.9 HEAD) to the generated text. Attach to the tag created earlier, and publish.
  • For non-patch releases: Merge draft news item for akka.io
  • For non-patch releases or for a particularly interesting patch release:
    • 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

Afterwards