Jetty Releases 10.0.10 and 11.0.10

[joakime]

Jetty Versions:
This release process will produce releases: 10.0.10 and 11.0.10

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". (take 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.
• Verify that branch jetty-10.0.x is merged to branch jetty-11.0.x.
• Assign issue to "build manager", who will stage the releases.
  • Ensure VERSION.txt additions for each release will be meaningful, descriptive, correct text.
  • Stage 10 release with Java 17.
  • Stage 11 release with Java 17.
  • 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 Build Manager role for this release.

[joakime]

Version 10.0.10 is now staged.

[joakime]

Version 11.0.10 is now staged.

[joakime]

Updates: Jun 16

• Old staged version 10.0.10 (take 1) has been dropped.
• Old staged version 11.0.10 (take 1) has been dropped.
• New staged version 10.0.10 (take 2) has been staged.
• New staged version 11.0.10 (take 2) has been staged.

[joakime]

Dropwizard on branch release/4.0.x works with Jetty 11.0.10

[joakime]

PR to merge release branches to mainline branches opened.

• Merge Release 10.0.10 back into jetty-10.0.x #8180
• Merge Release 11.0.10 back into jetty-11.0.x #8181

[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.