Jetty Releases 9.4.47

[joakime]

Jetty Versions:
This release process will produce releases: 9.4.47

Target Date:
June 6, 2022

Tasks:

• Create the release(s) issue.
• Update the target Jetty version(s) in the issue.
• Update the target release date in the issue.
• Link this issue to the target GitHub Project(s).
• Assign this issue to a "release manager". (Taken by @joakime)
• Review draft security advisories. Ensure that issues are created and assigned to GitHub Projects to capture any advisories that will be announced.
• Create the GitHub Project(s) for the next releases.
• Review the issues/PRs assigned to the target GitHub Project(s). Any PRs that are moved to next releases should be commented on so their authors are informed.
• Freeze the target GitHub Project(s) by editing their names to "Jetty X.Y.Z FROZEN"
• Wait 24 hours from last change to the issues/PRs included in FROZEN GitHub Project(s).
• Verify target project(s) are complete.
• Assign issue to "build manager", who will stage the releases.
  • Ensure VERSION.txt additions for each release will be meaningful, descriptive, correct text.
  • Stage 9.4 release with Java 11.
  • Edit a draft release (for each Jetty release) in GitHub (https://github.com/eclipse/jetty.project/releases). Content is generated with the "changelog tool".
• Assign issue to "test manager", who will oversee the testing of the staged releases.
  • Test CometD.
  • Test Reactive HttpClient.
  • Test Load Generator.
  • Test Jetty Docker images.
  • Test other Jetty OSS integrations.
  • Check TCK CI.
  • Test sponsored integrations.
  • Check CI for performance regressions.
  • Notify interested parties and invite testing of the staged release(s).
  • Assign issue back to "release manager".
• Collect release votes from committers.
• Promote staged releases.
• Merge release branches back to main branches and delete release branches.
• Verify release existence in Maven Central by triggering the Jenkins builds of CometD.
• Update Jetty versions on the web sites.
  • Update (or check) Download page is updated.
  • Update (or check) documentation page(s) are updated.
• Publish GitHub Releases.
• Prepare release announcement for mailing lists.
• Publish any security advisories.
  • Edit VERSION.txt to include any actual CVE number next to correspondent issue.
  • Edit any issues for CVEs in github with their CVE number
• Notify downstream maintainers.
  • Eclipse p2 maintainer.
  • Docker maintainer.
  • Jenkins maintainer.
  • Other maintainers.

[joakime]

I'm taking Release Manager role for this release.

[joakime]

I'm taking the Build Manager role for this release.

[joakime]

Version 9.4.47.v20220610 is now staged.

[joakime]

The 9.4.47.v20220610 tests fine on dropwizard branch release/2.1.x locally.

[joakime]

PR to merge release branch to mainline branch opened.

• Merge Release 9.4.47 back into jetty-9.4.x #8179

[antonmos]

since 9.4.48.v20220622 is out, should this issue be closed?

[joakime]

We are waiting on Eclipse Foundation on a review of this release.
9.4.48 was small enough it got a quick review.
9.4.47 is larger and taking more time.

[joakime]

The CVEs for this release are now public.
Appropriate issues, VERSION.txt, and security advisories page on github now reflect the up to date information for this release.