Eclipse
/
jetty.project
mirror of https://github.com/jetty/jetty.project.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
jetty.project/.github/ISSUE_TEMPLATE/release-template.md

3.1 KiB
Raw Blame History

name about title assignees labels
Release Process COMMITTER ONLY: Managing the Jetty release process Jetty Releases 9.4.x, 10.0.y, 11.0.y Build

Jetty Versions: This release process will produce releases:

Target Date:

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.
    • Stage 10 release with Java 16.
    • Stage 11 release with Java 16.
    • 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.