[M] Change in coreboot[master]: Docs/releases: Update release checklist document

[Martin L Roth (Code Review)]

Attention is currently required from: Felix Singer, Jason Glenesk, Angel Pons.

Martin L Roth has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/68500 )

Change subject: Docs/releases: Update release checklist document
......................................................................

Patch Set 1:

(3 comments)

File Documentation/releases/checklist.md:

https://review.coreboot.org/c/coreboot/+/68500/comment/1086952f_0120f63c 
PS1, Line 29:
> Hmmm, this file seems to use single spaces after periods. […]

That seems very nitpicky.  Personally I don't think it matters much.  If someone wants to go back through later and change it, that's fine.

https://review.coreboot.org/c/coreboot/+/68500/comment/2cbc470d_ce71b101 
PS1, Line 12: Our releases aren't primarily a vehicle for code that is stable across
            : all boards: The logistics of testing the more than 100 boards that are
            : spread out all continents (except Antarctica, probably) on a given tree
            : state are prohibitive for project of our size.
            : 
            : Instead, the releases are regular breakpoints that serve multiple
            : purposes: They support cooperation between multiple groups (corporations
            : or otherwise) in that it's easier to keep source trees synchronized
            : based on a limited set of commits. They allow a quick assessment of the
            : age of any given build or source tree based on its git version (4.8-1234
            : was merged into master a few months after 4.8, which came out in April
            : of 2018. 4.0-21718's age is harder to guess).
            : 
            : And finally we use releases to as points in time where we remove old
            : code: Once we decide that a certain part of coreboot gets in the way of
            : future development, we announce on the next release that we intend to
            : remove that part - and everything that depends on it - after the
            : following release.  So removing feature FOO will be announced in release
            : X for release X+1. The first commit after X+1 is fair game for such
            : removal.
> So this section was reflowed.

I reflowed a bunch of sections because they weren't under 72 characters.

https://review.coreboot.org/c/coreboot/+/68500/comment/248edbbf_f5b0beaf 
PS1, Line 73: - [ ] Run `util/vboot_list/vboot_list.sh` script to update the list of
            :       boards supported by vboot.
> Shouldn't we do this when doing the release?

Sorry, what do you mean "when doing the release"?  Everything in this list is done as part part of doing the release.

Do you mean closer to the day of the release?