This release checklist based on the release doc captures what activities must happen during a release.
The target release date is: April 20, 2021
The release champion for this release is: B. Best
The role of the release champion is to ensure that all release activities listed in this checklist get completed (by delegation to the broader team or by the release champion themselves). The final task of the release champion during a release is to confirm that all items in the checklist were completed satisfactorily and the release can be declared complete.
Everyone participating in a release, including the release champion are requested to provide feedback into the release retrospective so that the release process can be continuously improved (through simplification and/or automation).
One Week Prior to Release:
[x] Release Champion named whose responsibility is to ensure every item in this checklist gets completed
[ ] Disable nightly testing to free up resources and ensure no competing jobs during release week
[ ] Update list of CA certificates if required, following this security/README
[ ] Run a trial release pipeline to ensure less surprises on release day (typically against a milestone build)
Release Week Checklist:
[ ] Add website banner (automate* via github workflow in website repository) - Announce that we target releases to be available within 48 hours of the GA tags being available
[ ] Launch build pipelines for each version being released (as per release doc) once release tags are available via launch page in Jenkins. Provide links in this issue to each version's pipeline build(s). There may be multiple pipelines per version if primary and secondary platforms are separated to expedite the release. In some cases, where there are unforeseen configuration or infrastructure issues, reruns may be needed.
jdk8 pipeline(s):
primary jdk8 pipeline:
rerun(s):
secondary jdk8 pipeline:
reruns(s):
jdk11 pipeline(s):
primary jdk11 pipeline:
rerun(s):
secondary jdk11 pipeline:
rerun(s):
jdkxx pipeline(s):
primary jdkxx pipeline:
rerun(s):
secondary jdkxx pipeline:
rerun(s):
[ ] Summarize test results. Find each launched build pipeline in TRSS to view a summary of test results. Can use the Release Summary Report feature in TRSS to generate a summary of failures, history and possible issues in markup format to be added to this issue as a comment.
[ ] Triage each build and test failure in the release summary report (following the Triage guidelines) and determine blocking or non-blocking. Supply links to triage issues or docs for each version here.
jdk8 triage summary:
jdk11 triage summary:
jdkxx triage summary:
[ ] Fix blocking failures if they exist and confirm others are non-blocking.
[ ] Get TSC 'ready to publish' approval, once no blocking failures exist.
[ ] Publish the release (run the restricted access release tool job on Jenkins)
[ ] Verify binaries published successfully to github releases repo and website (automate*, this could also be an automated test)
[ ] Update support page (automate* github workflow to create a PR to update support.handlebars)
[ ] Update release notes (automate* - github workflow to create update for release notes page)
[ ] Run homebrew-cask_updater (via Jenkins homebrew-cask_updater job link) once binaries published successfully (this can be automated / triggered by a test for published artifacts)
[ ] Trigger linux installers pipeline currently it is part of the build pipelines (will eventually be updated to run independently)
[ ] Publicize the release via Slack #release channel and Twitter (can be partially automated)
smlambert
commented
3 years ago
This release checklist based on the release doc captures what activities must happen during a release.
The target release date is: April 20, 2021
The release champion for this release is: B. Best
The role of the release champion is to ensure that all release activities listed in this checklist get completed (by delegation to the broader team or by the release champion themselves). The final task of the release champion during a release is to confirm that all items in the checklist were completed satisfactorily and the release can be declared complete.
Everyone participating in a release, including the release champion are requested to provide feedback into the release retrospective so that the release process can be continuously improved (through simplification and/or automation).
One Week Prior to Release:
Release Week Checklist: