Angel Pons has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/31127 )
Change subject: Documentation: describe coreboot on the dev site's landing page ......................................................................
Patch Set 3: Code-Review+1
(3 comments)
https://review.coreboot.org/#/c/31127/2/Documentation/index.md File Documentation/index.md:
https://review.coreboot.org/#/c/31127/2/Documentation/index.md@23 PS2, Line 23: PCBIOS
or IBMBIOS. "The x86 software interrupt hardware abstraction layer that looks like CP/M's" ;) […]
Ack, I'm not used to seeing it written in a single word
https://review.coreboot.org/#/c/31127/2/Documentation/index.md@123 PS2, Line 123: DSCM
yes
Ack
https://review.coreboot.org/#/c/31127/2/Documentation/index.md@138 PS2, Line 138: These releases see some very limited testing and mostly serve : as synchronization points for deprecation notices and for other projects : such as external distributions.
I'm curious: why?
<IMHO> It shows how our concept of "release" differs from the usual meaning. Most of the releases I see on the internet are (or try to be) stable versions for anyone to use, whereas master is considered unstable. Here, however, the releases are merely a tag on a specific commit, and there's no further development on them. So, if a problem is discovered after a release has been done, it is either not corrected at all on said release (usually for minor bugs) or, if a bug is severe, the release has to be redone (see v4.8.1). coreboot master may see breakage from time to time, but it usually works. </IMHO>
I may have written nonsense above. If so, please let me know. Thanks.