On Wed, 5 Sep 2018 at 13:37 Zachary Ware email@example.com wrote:
On Wed, Sep 5, 2018 at 3:31 PM Brett Cannon firstname.lastname@example.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?
I would be fine with that. What do others think?
-- Zach _______________________________________________ core-workflow mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct