Hi again, About a week ago, I announced our plans to do a new coreboot release, which is scheduled to take place next Wednesday, November 18. This means we're currently at the "~1 week prior to release" point of our release checklist (at https://doc.coreboot.org/releases/checklist.html).
To this end, please test the devices you have with master, fix (or at least report) regressions you encounter, and propose additions to the release notes. Furthermore, I would earnestly appreciate that any risky changes be postponed until after the release is done, in order to minimize the impact of any possible breakage. Owing to the lack of developers and testers for Denverton-NS, it has been proposed as a candidate for removal in a future release: https://review.coreboot.org/47539 If anyone is still interested in keeping this platform supported in the future, please consider becoming a maintainer or providing the means to boot-test its code. Personally, I believe the root of the problem is testing: most coreboot developers don't have access to a Denverton-NS system to boot-test any changes, so it's impossible to ensure changes won't accidentally break something. Thanks, Angel _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
