[x] Check that open PRs and issues assigned to the milestone are reasonable
[x] Triage tickets that should be ready for this release, add "pick next" label and release milestone
[x] Triage open PRs and apply "pick next" label and maybe add to release milestone. Some PRs might be explicitly scheduled for this release, others might be ready enough to bring them over the finish line
Wind down PR queue. There has to be enough time after the last (non-trivial) PR is merged and the next phase. The core of the eco-system needs time to prepare for the final!
[x] Decide on planned release date
[x] Notify depending projects (notably Play + cinnamon) about upcoming release
1 day before the release
[x] Make sure all important / big PRs have been merged by now
[x] Check that latest nightly (once we have that) / master still works with depending projects (notably Play + cinnamon)
[x] Communicate that a release is about to be released in Gitter Akka Dev Channel, so that no new Pull Requests are merged
Preparing release notes in the documentation / announcement
[x] If this is a new minor (not patch) release, rename the 'akka-http-x.x-stable' reporting project in WhiteSource accordingly
[x] Add a release notes entry in docs/src/main/paradox/release-notes/. As a helper run scripts/commits-for-release-notes.sh <last-version-tag> which will output a list of commits grouped by submodule, and the closed issues for this milestone.
[x] Create a PR on https://github.com/akka/akka.github.com with a news item draft, using the milestones and scripts/authors.scala previousVersion thisVersion
[x] Go to the Maven Central tab and sync with Sonatype
[x] Log in to Sonatype to Close the staging repository (optional, should happen automatically if selected in Bintray)
[x] Notify Telemetry / Play team to check against staged artifacts
[x] Run a test against the staging repository to make sure the release went well, for example by using https://github.com/akka/akka-http-scala-seed.g8 and adding the sonatype staging repo with resolvers += "Staging Repo" at "https://oss.sonatype.org/content/repositories/comtypesafe-xxx"
[x] Release the staging repository to Maven Central.
[x] Checkout the newly created tag and run sbt -Dakka.genjavadoc.enabled=true ++2.12.8 "deployRsync akkarepo@gustav.akka.io" to deploy API and reference documentation.
~ 1 week before the release
1 day before the release
Preparing release notes in the documentation / announcement
scripts/commits-for-release-notes.sh <last-version-tag>
which will output a list of commits grouped by submodule, and the closed issues for this milestone.scripts/authors.scala previousVersion thisVersion
Cutting the release
v13.3.7
), title and release description linking to announcement, release notes and milestone.resolvers += "Staging Repo" at "https://oss.sonatype.org/content/repositories/comtypesafe-xxx"
sbt -Dakka.genjavadoc.enabled=true ++2.12.8 "deployRsync akkarepo@gustav.akka.io"
to deploy API and reference documentation.Check availability
When everything is on maven central
gustav.akka.io
asakkarepo
10.1
andcurrent
links onrepo.akka.io
to point to the latest version with (replace the minor appropriately)Announcements
Afterwards
project/MiMa.scala
to themimaPreviousArtifacts
key of all current compatible branches.