Hi all,

Going forward would it be worth doing release notes progressively as bug fixes 
and features are added to the code. This may make the actual release process 
easier.
As I have not contributed to bug fixes/features this far I may be missing 
something (e.g. this is already happening)

My 2c.
Regards,
Naveed

-----Original Message-----
From: coreboot [mailto:[email protected]] On Behalf Of Paul Menzel
Sent: Thursday, 21 December 2017 4:24 PM
To: [email protected]
Subject: [coreboot] [RFH] Draft release notes for coreboot 4.7

Dear coreboot folks,


Martin said, that the missing/unwritten release notes are the reason holding up 
the coreboot 4.7 release.

Could the maintainers, developers, and users please jump in and help write 
them. Please use the pad [1]. Some coreboot folks already contributed. Big 
thank you to them.

Also, thanks to the now mostly great and elaborate commit messages, the release 
notes should really just give a broad overview. The detail can then be looked 
up.

Additionally, can you think of the something that has to be adapted by someone 
switching from coreboot 4.6 to coreboot 4.7?


Thanks,

Paul


[1] 
https://linkprotect.cudasvc.com/url?a=https://pads.ccc.de/s7c2eXetAu&c=E,1,jYNN-Jv9ujvYDutxAcDWBlDkhPkoO2Jq8oAI8X4PYtQ7zeuZLh9bn1D2uHLy7YMVUAtUNdCMb3FBPzxNXpO98kzhHUXj62jbpqeLIwjRmHPma5xOv-HkZAk,&typo=1
-- 
coreboot mailing list: [email protected]
https://mail.coreboot.org/mailman/listinfo/coreboot

Reply via email to