That's one of the items raised called out in bug 1782086 comment 0: > ## Allow sheriffs and/or relman the ability to trigger merge-automation actions > These days triggering the actions is not very complicated. By allowing sheriffs or relman permission to trigger them, we can guarantee the process can be started ASAP (since sheriffs have 100% coverage). This can help in the event both people on releaseduty are in North American timezones or have something come up and are afk. In bug 1432655 and bug 1666321, we automated several steps. Yet, there are still some manual ones[1]. :gabriel started a conversation for the shipit part[2]. I'm filing this meta-bug because there are a few more things outside of shipit to fully hand off releaseduty to the Release Management team. On top of my head, I'm thinking of: * check the output of treescript is sane * emailing release-drivers@m.o when the merge is done * update the wiki (not sure how feasible it is today) - bug 1414278. [1] https://github.com/mozilla-releng/relengdocs/blob/1ec975b6d8d86eaadfcfe17c24fdfd013c836ab9/how-to/releaseduty/merge-duty/merge_duty.rst [2] https://github.com/mozilla-releng/shipit/issues/1418
Bug 1890753 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
That's one of the items called out in bug 1782086 comment 0: > ## Allow sheriffs and/or relman the ability to trigger merge-automation actions > These days triggering the actions is not very complicated. By allowing sheriffs or relman permission to trigger them, we can guarantee the process can be started ASAP (since sheriffs have 100% coverage). This can help in the event both people on releaseduty are in North American timezones or have something come up and are afk. In bug 1432655 and bug 1666321, we automated several steps. Yet, there are still some manual ones[1]. :gabriel started a conversation for the shipit part[2]. I'm filing this meta-bug because there are a few more things outside of shipit to fully hand off releaseduty to the Release Management team. On top of my head, I'm thinking of: * check the output of treescript is sane * emailing release-drivers@m.o when the merge is done * update the wiki (not sure how feasible it is today) - bug 1414278. [1] https://github.com/mozilla-releng/relengdocs/blob/1ec975b6d8d86eaadfcfe17c24fdfd013c836ab9/how-to/releaseduty/merge-duty/merge_duty.rst [2] https://github.com/mozilla-releng/shipit/issues/1418