Release Akka HTTP 10.2.0-RC2

[jrudolph]

1 day before the release

• Make sure all important / big PRs have been merged by now
• Check that latest nightly (once we have that) / master still works with depending projects (notably Play + cinnamon)
• [ ] 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

• If this is a new minor (not patch) release, rename the 'akka-http-x.x-stable' reporting project in WhiteSource accordingly
• Create a PR to 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. -> docs: release notes for 10.2.0-RC2 #3387
• Create a PR on https://github.com/akka/akka.io with a news item draft, using the milestones and scripts/authors.scala previousVersion master -> https://github.com/akka/akka.io/pull/732
• Create a PR on https://github.com/akka/akka.io updating Akka HTTP dependency for akka.io website: https://github.com/akka/akka.io/blob/master/_config.yml
• Release notes PR has been merged
• Create a new milestone for the next version at https://github.com/akka/akka-http/milestones
• Move all unclosed issues to the newly created milestone (or remove milestone) and close the version you're releasing

Cutting the release

• Make sure there are no stray staging repos on sonatype
• Wait until master build finished after merging the release notes
• Create a tag for the release (e.g. v13.3.7) and push it.
• Check that the Travis CI 10.2.0 release build has executed successfully
• Go to https://bintray.com/akka/maven/akka-http and select the just released version
• Go to the Maven Central tab and sync with Sonatype. You may need to log in and switch to the 'Old Look' for this.
• Log in to Sonatype to Close the staging repository (optional, should happen automatically if selected in Bintray)
• Notify Telemetry / Play team to check against released RC artifacts -> https://github.com/lightbend/cinnamon/issues/2491
• Run a test against the staging repository to make sure the release went well, for example by using https://github.com/akka/akka-http-quickstart-scala.g8 and adding the sonatype staging repo with resolvers += "Staging Repo" at "https://oss.sonatype.org/content/repositories/staging"
• Release the staging repository to Maven Central.

Check availability

• Check the release on maven central: https://repo1.maven.org/maven2/com/typesafe/akka/akka-http-core_2.13/

When everything is on maven central

• Log into gustav.akka.io as akkarepo
  • update the 10.1 and current links on repo.akka.io to point to the latest version with (replace the minor appropriately)

    ln -nsf 10.2.0-RC2 www/docs/akka-http/10.2
    ln -nsf 10.2.0-RC2 www/api/akka-http/10.2
    ln -nsf 10.2.0-RC2 www/japi/akka-http/10.2
    ln -nsf 10.2.0-RC2 www/docs/akka-http/current
    ln -nsf 10.2.0-RC2 www/api/akka-http/current
    ln -nsf 10.2.0-RC2 www/japi/akka-http/current
    

  • check changes and commit the new version to the local git repository

    cd ~/www
    git add docs/akka-http/ api/akka-http/ japi/akka-http/
    git commit -m "Akka HTTP 10.2.0-RC2"
    

• Merge draft news item at https://github.com/akka/akka.io
• Wait until the release page is published
• Create the GitHub release with the tag, title and release description linking to announcement, release notes and milestone.

Announcements

• Send a release notification to https://discuss.akka.io
• Tweet using the akka account (or ask someone to) about the new release
• Announce on Gitter at https://gitter.im/akka/akka

Afterwards

- [ ] Add the released version to project/MiMa.scala to the mimaPreviousArtifacts key of all current compatible branches.
- [ ] Forward port release notes from old releases to master
- [ ] Update Akka HTTP reference in lightbend-platform-docs

• Close this issue