LTS 2.289.1

[res0nance]

2.289.1 Release checklist

Release Lead

@res0nance

Prep work

• LTS baseline discussed and selected in the Jenkins developers mailing list

• Create or update release branch in jenkinsci/jenkins, e.g. stable-2.277

• Create or update release branch in jenkins-infra/release, e.g. stable-2.277

• Create or update release branch in jenkinsci/packaging, e.g. stable-2.277

• Create pull request to update bom to the weekly version that will be the base of the release line (strike this out for new point release)

• Create pull request to update configuration-as-code integration tests to the weekly version that will be the base of the release line (strike this out for new point release)

• Review Jira and GitHub pull requests for additional LTS candidates, adding the 'lts-candidate' label, and ensure that all tickets are resolved in jira

• Backporting announcement email - generate-backporting-announcement script

• Update jira labels with the selected issues, e.g. 2.277.2-fixed, 2.277.2-rejected

• Backport changes, create a local branch in jenkinsci/jenkins, run the list-issue-commits script to locate commits via jira ID, some manual work is required to locate them if the issue ID wasn't present at merge time, backport with git cherry-pick -x $commit

• Open backporting PR with into-lts label and summary of changes in description from lts-candidate-stats script and the selected Jira lts-candidates

• Review ATH, bom and configuration-as-code integration tests results

• Prepare LTS changelog based on the style guide using the changelog generator - PR-4383

• Prepare LTS upgrade guide based on previous upgrade guides - PR-4383

RC creation

• Merge backporting PR in jenkinci/jenkins using a merge commit (do not squash)

• Create or update release branch in jenkins-infra/release, e.g. stable-2.277.

• Create or update packaging branch in jenkinsci/packaging, e.g. stable-2.277

• Run job on release.ci.jenkins.io

• Publish a pre-release Github release, currently we don't have a changelog for RCs

• Send announcement email

• Check with security team that no security update is planned. If a security update is planned, revise the checklist after the public pre-announcement to the jenkinsci-advisories mailing list

LTS release

• Publish changelog (one day prior to the release in case of a security update)

• Run job on release.ci.jenkins.io

• Check LTS changelog is visible on the downloads site

• Publish GitHub release pointing to LTS changelog

• Confirm Datadog checks are passing

• Confirm the Debian installer acceptance test is passing

• Confirm the Red Hat installer acceptance test is passing

• Adjust state of Jira issues fixed in the release (see the changelog for issue links) and remove the lts-candidate label from Jira issues resolved in the release

• Create pull request to update bom to the newly released version

• Create pull request to update configuration-as-code integration tests to the newly released version

• Run trusted.ci.jenkins.io Docker image creation job

• Update ci.jenkins.io to the new LTS release (note: repo is private, requires infra team membership)

[timja]

Huge thanks @res0nance for this