Closed mkurz closed 2 years ago
Looks like we should actualize the issue template of Play Release 😄
A good portion of the first half doesn't apply, because it was a very minor release for CVEs. We can follow-up if we want to release some fixes for the other sub-projects. But, we skipped releases for play-json, play-ws, twirl, play-slick, scalatestplus-play, and play-grpc.
What do you think to add play-ebean into the external modules
checklist as well?
Most Java developers use it as a project dependency.
@felipebonezi Please provide a pull request to add play-ebean, thanks!
Closing, I already also posted to the security mailing list (https://groups.google.com/g/play-framework-security, however I want to retire that list as soon it is possible to subscribe to GHSA notifications on GitHub, see https://github.com/github-community/community/discussions/12226#discussioncomment-2489025 )
(Also yes this issue template needs update, we'll do that next release :wink: )
Preparing the release
Better to do this in advance:
Do the Release (Full document)
x[]
status:needs-backport
,status:needs-forwardport
issues/PRs (including closed ones).status:needs-backport
,status:needs-forwardport
issues/PRs (including closed ones).status:needs-backport
,status:needs-forwardport
,status:needs-backport-1.3
issues/PRs (including closed ones).x[]
status:needs-backport
,status:needs-forwardport
,status:needs-backport-2.6
issues/PRs (including closed ones).x[]
x[]
[]
x[]
[]
x[]
x[]
x[]