Sept. 5, 2018
8:37 p.m.
On Wed, Sep 5, 2018 at 3:31 PM Brett Cannon <brett@python.org> wrote:
So the reasoning behind setting "awaiting merge" is because the "needs" label is meant to represent what is holding up the PR from being closed, and so a PR from a core dev is really just blocked on merging since they don't have to receive a review.
Now, if people would rather move it over to "needs review" by default like any other PR then that's fine as well, but I don't know if that's going to help with INADA-san's worry about so many issues making a label less useful.
What about no label at all on core dev PRs by default, but if one gets added the standard flow is followed? -- Zach