eb80e053b6
Having the release notes mostly ready one week before the release allows for better review. Some statistics, the actual release date and commit ID can only be filled in on release day, but there's a tried & true technique for that: placeholders. It's also a nice touch to have the release notes of a release within its source tarballs, so push them right before creating the release (since changes in Documentation/releases won't break coreboot in any way). Change-Id: Iad7ba1ba4fc841bf437f2a997428b7f636e15422 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/36957 Reviewed-by: HAOUAS Elyes <ehaouas@noos.fr> Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> |
||
---|---|---|
.. | ||
checklist.md | ||
coreboot-4.1-relnotes.md | ||
coreboot-4.2-relnotes.md | ||
coreboot-4.3-relnotes.md | ||
coreboot-4.4-relnotes.md | ||
coreboot-4.5-relnotes.md | ||
coreboot-4.6-relnotes.md | ||
coreboot-4.7-relnotes.md | ||
coreboot-4.8.1-relnotes.md | ||
coreboot-4.9-relnotes.md | ||
coreboot-4.10-relnotes.md | ||
coreboot-4.11-relnotes.md | ||
coreboot-4.12-relnotes.md | ||
index.md |