Sorry to have a long email thread since my merge and thanks all for the comments. In general, I still feel current process is a little complicated for the maintainers who don't daily work on EDK2 like me. I have less than %5 of time spent on open source EDK2 UefiPayloadPkg since I focus on bootloaders. It would be great if I could spend the time mainly on code review instead of the process as of now.
Even after I read https://github.com/tianocore/tianocore.github.io/wiki/EDK-II- Development-Process#the-maintainer-process-for-the-edk-ii-project as Liming pointed out, Some info is still not clear for me. E.g. what's the purpose for putting cover letter to patch set pull request (it looks we could not trace to this PR from code)? is it mandatory or optional? What if there is no cover letter in the patch set in patch #0 summary? For the patch I merged, I am still not very sure what info I should put there. I don't know why Laszlo mentioned BZ for my merge since there is no BZ mentioned in the patchset. And I also don't know why Laszlo mentioned to send email after the patch is merged since I don't find this requirement in the development process. I don't think it is doable to ask all the maintainers to monitor EDK2 mail list on how others are doing since there are so many emails every day, especially there is no any patch for UefiPayloadPkg for several months. I hope we could simplify the process and have a clear steps in the process soon. So that the maintainers could focus on the actual code review. Thanks, Guo -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#65641): https://edk2.groups.io/g/devel/message/65641 Mute This Topic: https://groups.io/mt/76902353/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
