Denis 'GNUtoo' Carikli has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/37064 )
Change subject: 4.12 release notes: Add some explanation behind depreciations ......................................................................
Patch Set 4:
(1 comment)
https://review.coreboot.org/c/coreboot/+/37064/4//COMMIT_MSG Commit Message:
https://review.coreboot.org/c/coreboot/+/37064/4//COMMIT_MSG@14 PS4, Line 14: notes?
Maybe the depreciation arguments could be a file of its own, not tied to the most recent release?
I think it would also be a important to create a file about deprecation itself with: - Arguments for dropping support for hardware, along with arguments against it (in order not to keep re-doing huge debates about it), and why the argument for dropping hardware won. - How it is possible to change the decision (like majority of developers for + bring a new argument that is compelling and that was not already taken into account). - Ideas on how to deal with deprecation (For instance something that tell people to read the releases notes at each release, submit test results in board-status because it'll require less work to convert the mainboard if it's already working on master, paying people to do the work(how?), etc) - Information on how to decide to force hardware to be converted to a new API or drop boards.
I've the feeling that many developers like me (maybe not the ones that are the most involved) have issue dealing with the idea that the hardware you use, depend on, or your work could be removed as it seems that there is no unique reference on the topic, and that the information is instead scattered around, leading to misunderstanding. If there is such document I would be very happy to be pointed at it.
If not, I'll probably consider working on that but not before next year as I'm overbooked theses days. I'll probably start by digging information in the the community meeting reports since 2017 as I was pointed to it on IRC.