summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorAngel Pons <th3fanbus@gmail.com>2019-12-13 16:15:50 +0100
committerPatrick Georgi <pgeorgi@google.com>2019-12-26 10:47:13 +0000
commit58ececfb28f71cd2560fde3a914cca8c7a49c693 (patch)
treefba5d273aeb9d0760e0780b1a29c3070cfa152bc /Documentation
parent66406d475480755870fceae6b05f32a8936030de (diff)
downloadcoreboot-58ececfb28f71cd2560fde3a914cca8c7a49c693.tar.xz
Doc/releases/checklist.md: Correct some inconsistencies
Use periods on every element of a list, and make `IRC` uppercase. Also, correct a grammar mistake that slipped through. Change-Id: Id05865719c7c845265416e89bfd9b02b6d22ca6c Signed-off-by: Angel Pons <th3fanbus@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37709 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Matt DeVillier <matt.devillier@gmail.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/releases/checklist.md34
1 files changed, 17 insertions, 17 deletions
diff --git a/Documentation/releases/checklist.md b/Documentation/releases/checklist.md
index 49045573d3..706d08e379 100644
--- a/Documentation/releases/checklist.md
+++ b/Documentation/releases/checklist.md
@@ -49,34 +49,34 @@ be more frequent than was needed, so we scaled it back to twice a year.
## Checklist
### ~2 weeks prior to release
- [ ] Announce upcoming release to mailing list, ask people to test and
- to update release notes
+ to update release notes.
### ~1 week prior to release
- [ ] 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
+ and to update the release notes.
+- [ ] Update the topic in the IRC channel with the date of the upcoming
+ release.
- [ ] If there are any deprecations announced for the following release,
- make sure that a list of currently affected board and chipsets is
+ 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
+ release commit ids.
### Day of release
- [ ] 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
-- [ ] Run release script
-- [ ] Test the release from the actual release tarballs
-- [ ] Push signed Tag to repo
-- [ ] Announce that the release tag is done on IRC
+- [ ] Test the commit selected for release.
+- [ ] Update release notes with actual commit id, push to repo.
+- [ ] Run release script.
+- [ ] Test the release from the actual release tarballs.
+- [ ] Push signed Tag to repo.
+- [ ] Announce that the release tag is done on IRC.
- [ ] Upload release files to web server
-- [ ] Upload crossgcc sources to web server
-- [ ] Update download page to point to files, push to repo
+- [ ] Upload crossgcc sources to web server.
+- [ ] Update download page to point to files, push to repo.
- [ ] Write and publish blog post with release notes.
-- [ ] Update the topic in the irc channel that the release is done.
-- [ ] Announce the release to the mailing list
+- [ ] Update the topic in the IRC channel that the release is done.
+- [ ] Announce the release to the mailing list.
## Pre-Release tasks
Announce the upcoming release to the mailing list release 2 weeks ahead
@@ -102,7 +102,7 @@ to have in the release. The release was based on the final of those
patches to be pulled in.
When a release candidate has been selected, announce the commit ID to
-the #coreboot irc channel, and request that it get some testing, just
+the #coreboot IRC channel, and request that it get some testing, just
to make sure that everything is sane.
## Generate the release