Release Play 2.8.0-M6

[dwijnand]

Preparing the release

Better to do this in advance:

• Make sure that other teams inside Lightbend are aware of the upcoming release, even if it is a minor/patch one
  • Lightbend Telemetry Team
  • Lightbend Platform Team
  • Akka Team
• Triage issues

Do the Release (Full document)

• Release projects that Play depends on

  • release play-json 2.8.0-M7
    • playframework/play-json@2.8.0-M6...master
    • Look for PRs that should be merged.
    • Look at status:needs-backport issues/PRs (including closed ones).
    • Look at issues/PRs tagged milestone version (including closed ones).
    • Update any dependencies that are needed.
    • Update any upstream projects (e.g make sure new play-ws is using new play-json)
    • pushing to GitHub asked for my username/password, changed the remote to the git/ssh protocol, added the key as a deploy key, and added the play-json ssh key to the ssh agent
  • release play-ws
    • playframework/play-ws@v2.1.0-M5...master
    • Look for PRs that should be merged.
    • Look at status:needs-backport issues/PRs (including closed ones).
    • Look at issues/PRs tagged milestone version (including closed ones).
    • Update any dependencies that are needed.
    • Update any upstream projects (e.g make sure new play-ws is using new play-json)
      • Akka 2.6.0-M8 #408
      • Play JSON 2.8.0-M7 #409
  • release twirl
    • playframework/twirl@1.5.0-M4...master
    • Look for PRs that should be merged.
    • Look at status:needs-backport issues/PRs (including closed ones).
    • Look at issues/PRs tagged milestone version (including closed ones).
    • Update any dependencies that are needed.
    • Update any upstream projects (e.g make sure new play-ws is using new play-json)

• Release Play itself

  • Look for PRs that should be merged.
  • Look at status:needs-backport issues/PRs (including closed ones).
  • Look at issues/PRs tagged milestone version (including closed ones).
  • Update any dependencies that are needed.
  • Update any upstream projects (e.g make sure new play-ws is using new play-json)
    • upstream #9731
    • sbt (and mima) #9732

• Release external modules

  • release play-slick 5.0.0-M7
  • release scalatestplus-play 5.0.0-M6
  • release play-grpc

• Release omnidoc

• Update the supported modules page

• Update playframework templates and seeds

  • Upgrade to Play 2.8.0-M6 play-samples#56

• Update Example Code Service

• Update playframework.com

  • New Play 2.8.0-M6 release playframework.com#339

• Announce

  • Write a blog post on https://playframework.ghost.io/ghost/24 about the release.
  • Write a topic on https://discuss.lightbend.com/
    • https://discuss.lightbend.com/t/play-2-8-0-m6-released/5248
  • Write a release on https://github.com/playframework/playframework/releases
    • https://github.com/playframework/playframework/releases/2.8.0-M6
  • Send an internal email to eng-updates
  • Tweet about the new release.

• Post release tasks

  • Close the milestone for the release (for example 2.7.1)
    • https://github.com/playframework/playframework/milestone/96
  • Create a new milestone for the next release (for example 2.7.2)
    • https://github.com/playframework/playframework/milestone/97
  • Move issues and pull requests from the old milestone to the new one if necessary