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

[Angel Pons (Code Review)]

Attention is currently required from: Felix Singer, Jason Glenesk, Martin L Roth.

Angel Pons 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/998a9a30_ab194361 
PS1, Line 29:
> That seems very nitpicky.  Personally I don't think it matters much. […]

Ack, we'll change it later if we get annoyed enough.

https://review.coreboot.org/c/coreboot/+/68500/comment/4e60aa30_d9715784 
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.
> I reflowed a bunch of sections because they weren't under 72 characters.

Ack, just noted this as there were no changes in the content.

https://review.coreboot.org/c/coreboot/+/68500/comment/600460fc_cbf5a6c0 
PS1, Line 73: - [ ] Run `util/vboot_list/vboot_list.sh` script to update the list of
            :       boards supported by vboot.
> 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?

Yes, sorry for the confusion.