Jetty Releases 10.0.12, 11.0.12

[olamy]

Jetty Versions:
This release process will produce releases: 10.0.12, 11.0.12

Target Date:
9/9/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".
• 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.
  • https://github.com/orgs/eclipse/projects/27
• Review dependabot status. If there has not been a recent run, run manually and review resulting PRs for inclusion.
• 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 9.4 release with Java 11.
  • 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]

Why is documentation being deployed?

https://oss.sonatype.org/content/repositories/jetty-1783/org/eclipse/jetty/documentation/

[olamy]

Why is documentation being deployed?

https://oss.sonatype.org/content/repositories/jetty-1783/org/eclipse/jetty/documentation/

I just ran the script.

[olamy]

but at least documentation can be simply deployed by downloading then unzip the file https://oss.sonatype.org/content/repositories/jetty-1783/org/eclipse/jetty/documentation/jetty-documentation/10.0.12/jetty-documentation-10.0.12-html.zip
as requested for 12 #8489

[joakime]

but at least documentation can be simply deployed by downloading then unzip the file https://oss.sonatype.org/content/repositories/jetty-1783/org/eclipse/jetty/documentation/jetty-documentation/10.0.12/jetty-documentation-10.0.12-html.zip
as requested for 12 #8489

Ah. OK.

[joakime]

We should look into how we can automate attaching relevant tarballs to the staged release instead.

Example:

1. Main jetty-home tarball (and zip?)
2. Documentation tarball (or zip?)
3. Javadoc (as jar? tarball? zip?)

These can probably be triggered via a github action on release publish, to use the the associated release tag, download the jetty-home from central, build the documentation and javadoc, and attach all 3.

[joakime]

Drop the current staged releases for 10 and 11.
They need to be rerolled with the fix for #8580

[joakime]

@olamy The entry titled "Create the GitHub Project(s) for the next releases." means to create the NEXT Jetty release in the project pages. (not this one).

Eg: For this task list, that means 10.0.13 and 11.0.13 need to be created as a projects

[olamy]

Not sure why but they are here https://github.com/orgs/eclipse/projects

[joakime]

Not sure why but they are here https://github.com/orgs/eclipse/projects

They were not there up until a few minutes ago, when I made them no longer hidden.
Next time, link to them here (like i did in the checklist above)

[joakime]

We need to figure out how to make them no longer "private" as well

[joakime]

@olamy these releases are now available on Maven Central

• https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-home/10.0.12/
• https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-home/11.0.12/

[olamy]

done