Hi
Would it make sense to backport your fix to old releases and bump
those release numbers to a .1 on the end?
Some see releases as mere synchronization tags & nice PR. Some releases are also branches in gerrit but there are none affected by this (latest is 4.12 and it was introduced in 4.13). There is a precedent where 4.8 was bumped to 4.8.1 because all boards were broken.
I don't have a strong opinion on this. Do people really use the releases in production or are most using git anyway? It's a bit weird to have releases that you'd have to advertise as *don't use*, but I've seen us do that in the past (because issues are quite often just fixed in master).
Kind regards Arthur
On Tue, Apr 12, 2022 at 12:52 AM Peter Stuge peter@stuge.se wrote:
Arthur Heymans wrote:
I think this issue might affect a lot more systems than I initially
thought.
Would it make sense to backport your fix to old releases and bump those release numbers to a .1 on the end?
//Peter _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org