Jetty Releases 10.0.24 / 11.0.24 (EOL)

[joakime]

Jetty Versions: This release process will produce releases: 10.0.24 (EOL) 11.0.24 (EOL)

Target Date: Aug 29, 2024

Tasks:

• [x] Create the release(s) issue.
• [x] Update the target Jetty version(s) in the issue.
• [x] Update the target release date in the issue.
• [x] Link this issue to the target GitHub Project(s).
• [x] Assign this issue to a "release manager".
• [x] Review draft security advisories. Ensure that issues are created and assigned to GitHub Projects to capture any advisories that will be announced.
• [x] Update GitHub Project(s)
  • [x] Create new project for the next releases (not this release).
  • [x] Ensure new project is public (not private)
  • [x] Freeze the target GitHub Project(s) by editing their names to "Jetty X.Y.Z FROZEN"
  • [x] Review the issues/PRs assigned to the target GitHub Project(s). Any tasks that are not-yet-started are moved to next releases.
• [x] Review dependabot status. Manually run dependabot if needed and review resulting PRs for inclusion. Such updates should only be included in the week before a release if there is a compelling security or stability reason to do so.
• [x] Wait 24 hours from last change to the issues/PRs included in FROZEN GitHub Project(s).
• [x] Verify target project(s) are complete.
• [x] 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.
  • [x] Create and use branches release/<ver> to perform version specific release work from.
  • [x] Ensure git fetch --tags (as we potentially rewrite tag when re staging local tag can be out of sync and this command will fail and so fail the release script)
  • [x] Ensure VERSION.txt additions for each release will be meaningful, descriptive, correct text.
  • [x] Stage 10 release with Java 21.
  • [x] Stage 11 release with Java 21.
  • [x] Push release branches release/<ver> to to https://github.com/eclipse/jetty.project
  • [x] Push release tags jetty-<ver> to https://github.com/eclipse/jetty.project
  • [ ] 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.
  • [x] Test CometD.
  • [x] Test Reactive HttpClient.
  • [ ] Test Load Generator.
  • [ ] Test Jetty Docker images.
  • [ ] Test other Jetty OSS integrations.
  • [ ] Check TCK CI.
  • [ ] Test sponsored integrations.
  • [x] 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 website ( follow instructions in jetty-website ).
  • [ ] 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]

Staged potential release 10.0.24 - https://oss.sonatype.org/content/repositories/jetty-1926/

[joakime]

Staged potential release 11.0.24 - https://oss.sonatype.org/content/repositories/jetty-1927/