From 5d24231427bd57d9304ef75d1b9aa552321942ae Mon Sep 17 00:00:00 2001 From: Patrick Georgi Date: Mon, 10 May 2021 23:25:59 +0200 Subject: Documentation/releases: Add more details about release notes There are some steps when updating the release notes that are easily missed (see: I missed them for 4.14), so document them. Change-Id: Icdb69eb74f8dd3a7189eb8803b0259c4e6a31f96 Signed-off-by: Patrick Georgi Reviewed-on: https://review.coreboot.org/c/coreboot/+/54032 Tested-by: build bot (Jenkins) Reviewed-by: Arthur Heymans --- Documentation/releases/checklist.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'Documentation') diff --git a/Documentation/releases/checklist.md b/Documentation/releases/checklist.md index 7e66c4d2f2..50d99f6b12 100644 --- a/Documentation/releases/checklist.md +++ b/Documentation/releases/checklist.md @@ -59,8 +59,9 @@ be more frequent than was needed, so we scaled it back to twice a year. - [ ] If there are any deprecations announced for the following release, make sure that a list of currently affected boards and chipsets is part of the release notes. -- [ ] Finalize release notes (as much as possible), without specifying - release commit ids. +- [ ] Finalize release notes as much as possible +- [ ] Prepare release notes template for following release +- [ ] Update `Documentation/releases/index.md` - [ ] Run `util/vboot_list/vboot_list.sh` script to update the list of boards supported by vboot. @@ -68,7 +69,7 @@ be more frequent than was needed, so we scaled it back to twice a year. - [ ] Select a commit ID to base the release upon, announce to IRC, ask for testing. - [ ] Test the commit selected for release. -- [ ] Update release notes with actual commit id, push to repo. +- [ ] Submit release notes - [ ] Create new release notes doc template for the next version. - [ ] Fill in the release date, remove "Upcoming release" and other filler from the current release notes. -- cgit v1.2.3