Release Play 2.8.15

[mkurz]

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
  • Akka Team
• Triage issues

Do the Release (Full document)

• Release projects that Play depends on

  • release play-json
    • Look for PRs that should be merged.
    • Look at status:needs-backport, status:needs-forwardport issues/PRs (including closed ones).
    • Look at issues/PRs tagged milestone version (including closed ones).
    • Update any dependencies that are needed. (e.g JDK, Scala)
  • release play-ws
    • Look for PRs that should be merged.
    • Look at status:needs-backport, status:needs-forwardport issues/PRs (including closed ones).
    • Look at issues/PRs tagged milestone version (including closed ones).
    • Update any dependencies that are needed. (e.g JDK, Scala)
    • Make sure play-ws uses new play-json
  • release twirl
    • Look for PRs that should be merged.
    • Look at status:needs-backport, status:needs-forwardport, status:needs-backport-1.3 issues/PRs (including closed ones).
    • Look at issues/PRs tagged milestone version (including closed ones).
    • Update any dependencies that are needed. (e.g JDK, Scala)

• Release Play itself

  • Look for PRs that should be merged.
  • Look at status:needs-backport, status:needs-forwardport, status:needs-backport-2.6 issues/PRs (including closed ones).
  • Look at issues/PRs tagged milestone version (including closed ones).
  • Update any dependencies that are needed. (e.g JDK, Scala)
  • Make sure play uses new play-json, play-ws, twirl

• Release external modules

  • release play-slick
  • release scalatestplus-play
  • release play-grpc

• Release omnidoc

• Update the supported modules page

• Update playframework templates and seeds

• Update Example Code Service

• Update playframework.com

  • Update .version in play-generated-docs
  • Update playReleases.json and changelog.md
  • Update versions for Example Code Service
  • Deploy the website changes

• Announce

  • Write a topic on https://discuss.lightbend.com/
  • Write a release on https://github.com/playframework/playframework/releases
  • Send an internal email to eng-updates
  • Tweet about the new release.

• Post release tasks

[gokhanoner]

following up the release.

[mkurz]

@gokhanoner Sorry I was busy, I will start the release today.

[mkurz]

Out on maven central, regarding partial Java 17 support see: playframework/playframework#11206

[mkurz]

Changed title to "Release Play 2.8.15", since there was playframework/playframework#11214 meanwhile.

[mkurz]

Done.

• https://github.com/playframework/playframework/releases/2.8.15
• Play 2.8.15 (Spring4Shell / Experimental support for Java 17) playframework#11216
• https://twitter.com/playframework/status/1510068300302233603
• Announced on Discord.