Jetty Releases 9.4.43, 10.0.6, 11.0.6

[gregw]

Jetty Versions:
This release process will produce releases: 9.4.43, 10.0.6, 11.0.6

Target Date:
2021-06-28

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 project(s).
• Assign this issue to a "release manager".
• Review draft security advisories. Ensure that issues are created and assigned to GitHub Projects to capture any advisories that will be announced.
• Review the issues/PRs assigned to the target project(s). Any PRs that are moved to subsequent releases should be commented on so their authors are informed.
• Freeze the target project(s) by editing their names to "Jetty X.Y.Z FROZEN"
• Wait 24 hours from last change to the issues/PRs included in a FROZEN GitHub Project.
• 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 9.4 release with Java 11.
    • Staged 9.4.43.v20210629 at https://oss.sonatype.org/content/repositories/jetty-1684/
  • Stage 10 release with Java 16.
    • Staged 10.0.6 at https://oss.sonatype.org/content/repositories/jetty-1682/
  • Stage 11 release with Java 16.
    • Staged 11.0.6 at https://oss.sonatype.org/content/repositories/jetty-1683/
  • 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.
  • Add testing tick list to the target project(s).
  • Testing tick lists complete in all target project(s).
  • 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.
• Notify downstream maintainers.
  • Eclipse p2 maintainer.
  • Docker maintainer.
  • Jenkins maintainer.
  • Other maintainers.

[lachlan-roberts]

@joakime can you build and stage the releases for testing.

[joakime]

@lachlan-roberts the releases for 9.4.43, 10.0.6, and 11.0.6 are staged.

[joakime]

@lachlan-roberts Testing as shown that we broke a few things.
I've dropped the staged releases, as we need to reroll now.

[joakime]

Accidentally closed.