LTS release checklist #122
Conversation
| - [ ] Publish pre-release Github release | ||
|
|
||
| - [ ] Send announcement email | ||
|
|
There was a problem hiding this comment.
Add here: Check with security team that no security update is planned. If there is, the rest of this checklist does not apply (but hold any updates until the public pre-announcement to the jenkinsci-advisories mailing list).
While every effort is done to inform release team, better safe than sorry. Especially with rotating people.
There was a problem hiding this comment.
What do you mean by the rest of the checklist does not apply?
Doesn't the changelog still need publishing, along with all the other checks done, and someone needs to run the release albeit a different job?
|
|
||
| - [ ] Check LTS changelog status | ||
|
|
||
| - [ ] Create or update release branch in jenkins-infra/release, e.g. `stable-2.263` |
There was a problem hiding this comment.
Should happen way before then to allow for review.
|
|
||
| - [ ] Run job on [release.ci.jenkins.io](https://release.ci.jenkins.io/blue/organizations/jenkins/core%2Fstable%2Frelease/branches/) | ||
|
|
||
| - [ ] Publish changelog |
There was a problem hiding this comment.
Needs to happen at least 1 day before release if it's a security update to give us time to rebase any security content.
| @@ -0,0 +1,71 @@ | |||
| --- | |||
| name: "🥇 New LTS release checklist" | |||
There was a problem hiding this comment.
Random emoji I picked, can remove or replace with a better one
Co-authored-by: Mark Waite <mark.earl.waite@gmail.com> Co-authored-by: Daniel Beck <1831569+daniel-beck@users.noreply.github.com>
Co-authored-by: Mark Waite <mark.earl.waite@gmail.com>
|
Feel free to just push direct @MarkEWaite might be easier, I’ll try get back to this tomorrow and see how it’s looking |
|
|
||
| - [ ] Create or update release branch in jenkins-infra/release, e.g. `stable-2.263` |
There was a problem hiding this comment.
This is already covered in an earlier checklist item
| - [ ] Create or update release branch in jenkins-infra/release, e.g. `stable-2.263` |
|
|
||
| - [ ] Confirm the [Red Hat installer acceptance test](https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-lts-redhat-rpm/) is passing | ||
|
|
||
| - [ ] Adjust state of all [Jira issues](https://issues.jenkins.io/) fixed in the release (see the [changelog](https://www.jenkins.io/changelog-stable) for issue links) |
There was a problem hiding this comment.
what does this mean @MarkEWaite? update the released as field?
| blank_issues_enabled: false | ||
| contact_links: | ||
| - name: "❓ IRC" | ||
| url: https://kiwiirc.com/nextclient/irc.freenode.net/?#jenkins-release |
There was a problem hiding this comment.
GitHub seems to ignore irc / ircs links 😢
Co-authored-by: Mark Waite <mark.earl.waite@gmail.com> Co-authored-by: Daniel Beck <1831569+daniel-beck@users.noreply.github.com> (cherry picked from commit f10b1aa)
See issue:
timja#1
Templates:
https://github.com/timja/release/issues/new/choose
Would be good to have a description against each and maybe timings of when it should all happen
Interested in all feedback