I created the "needs backport to 3.7" label on GitHub
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.
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
I'm not sure. Maybe the release managers know? There is PEP 101..
On Jan 31, 2018 6:43 PM, "Alex Gaynor" <alex.gaynor@gmail.com> wrote:
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
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 Sent: Thursday, February 1, 2018 10:44 To: Mariatta Wijaya Cc: core-workflow; python-committers 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
On Jan 31, 2018, at 18:58, Mariatta Wijaya <mariatta.wijaya@gmail.com> wrote:
I'm not sure. Maybe the release managers know? There is PEP 101..
I’ll bet Ned is either updating PEP 101 as he goes, or is keeping notes to update that PEP once things calm down. It’s a rare enough event, and this is the first time with git, so I’m sure there was a fair bit to figure out.
$ git worktree add ../3.7 3.7 # ftw!
-Barry
On 1/31/2018 7:03 PM, Barry Warsaw wrote:
$ git worktree add ../3.7 3.7 # ftw!
f:\dev\3x> git worktree add ../37 3.7 fatal: invalid reference: 3.7
f:\dev\3x> git worktree add -b 3.7 ../37 3.7 fatal: Not a valid object name: '3.7'.
# However f:\dev\3x> git checkout 3.7 # 'exposes' the existing branch so after git checkout master git worktree add ../37 3.7 # seems to work
tjr
participants (5)
-
Alex Gaynor -
Barry Warsaw -
Mariatta Wijaya -
Steve Dower -
Terry Reedy