If it's protected then backport PR can still happen, but then only Ned can merge it, right? On Jan 31, 2018 6:59 PM, "Steve Dower" <steve.dower@python.org> wrote:

I’d suggest not porting anything to that branch until Ned gives the okay. Hopefully it’s locked right now anyway.

Top-posted from my Windows phone

*From: *Alex Gaynor <alex.gaynor@gmail.com> *Sent: *Thursday, February 1, 2018 10:44 *To: *Mariatta Wijaya <mariatta.wijaya@gmail.com> *Cc: *core-workflow <core-workflow@python.org>; python-committers <python-committers@python.org> *Subject: *Re: [python-committers] I created the "needs backport to 3.7" labelon GitHub

Is there documentation somewhere on "how to create a release branch" that we should add "creating a label" step to?

Alex

On Wed, Jan 31, 2018 at 6:40 PM, Mariatta Wijaya < mariatta.wijaya@gmail.com> wrote:

I noticed that there is a 3.7 branch now.

So you can use this label if you want miss-islington to backport a PR to 3.7.

_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

--

"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero

GPG Key fingerprint: D1B3 ADC0 E023 8CA6