Liming, On 09/17/20 03:49, gaoliming wrote: > Guo: > On pull request, > https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process#the-maintainer-process-for-the-edk-ii-project > section 7 gives the requirement. > If <new-integration-branch> is a patch series, then copy the patch #0 summary > into the pull request description. > > Laszlo: > I think we can enhance wiki page > https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process#the-maintainer-process-for-the-edk-ii-project > to add another step to reply the patch mail with the merged pull request or > commit after PR is merged.
this document is usually edited by Mike, so I'd prefer Mike to add such a step. But... I've given this some more thought. I don't feel that the argument "it's not documented" is a completely fair excuse, from long-time maintainers. It's not like we invent a new workflow element every two weeks. I think it's fair to expect that maintainers learn new things by doing it and by watching others do it. No particular maintainer lives and works in a bubble. If they merge a series, close a BZ, report back on the list, populate a PR with useful information -- all those steps are *visible* to everyone else. And other long-term maintainers could simply start copying good practices they see. I'm not talking about closely following other maintainers' work, just acknowledging / not completely ignoring their activitities. Laszlo -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#65352): https://edk2.groups.io/g/devel/message/65352 Mute This Topic: https://groups.io/mt/76901786/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
