Matt DeVillier has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/84034?usp=email )
Change subject: documentation/release: Update release checklist ......................................................................
documentation/release: Update release checklist
Sync checklist with release template; add new heading for paragraph on pushing the signed tag to make it stand out.
Change-Id: Id49b3f38d3501382b7fb7ac791190c0cacd58a11 Signed-off-by: Matt DeVillier matt.devillier@gmail.com --- M Documentation/releases/checklist.md 1 file changed, 15 insertions(+), 3 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/34/84034/1
diff --git a/Documentation/releases/checklist.md b/Documentation/releases/checklist.md index 29ebdbb..6ef0ac3 100644 --- a/Documentation/releases/checklist.md +++ b/Documentation/releases/checklist.md @@ -66,13 +66,23 @@
## Checklist
-### ~2 weeks prior to release +### ~6 weeks prior to release - [ ] Announce upcoming release to mailing list, ask people to test and to update release notes. - [ ] Start marking patches that should to go into the release with a tag "coreboot_release_X.yy"
+### ~4 weeks prior to release +- [ ] Freezing toolchain state. Only relevant fixes are allowed from this point on. +- [ ] Schedule release meetings + +### ~2 weeks prior to release +- [ ] Meeting with release team +- [ ] Send reminder email to mailing list, ask for people to test, and to update the release notes. +- [ ] Update the topic in the IRC channel with the date of the upcoming release. + ### ~1 week prior to release +- [ ] Meeting with release team - [ ] Send reminder email to mailing list, ask for people to test, and to update the release notes. - [ ] Update the topic in the IRC channel with the date of the upcoming @@ -87,14 +97,15 @@ should get a new release. Announce these branch releases and prepare release notes.
-### Day before release +### Day before release tag - [ ] Make sure patches with tags for the release are merged. - [ ] Announce to IRC that the release will be tomorrow and ask for testing. - [ ] Run `util/vboot_list/vboot_list.sh` script to update the list of boards supported by vboot.
-### Day of release +### Day of release tag +- [ ] Meeting with release team - [ ] Review the full documentation about doing the release below. - [ ] Select a commit ID to base the release upon. - [ ] Test the commit selected for release. @@ -230,6 +241,7 @@ ... ````
+## Push the signed tag When you used the script to generate the release, a signed tag was generated in the tree that was downloaded. From the coreboot-X.Y tree, just run: `git push origin X.Y`. In case you pushed the wrong tag