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 Cond
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
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
I'm not sure. Maybe the release managers know? There is PEP 101..
On Jan 31, 2018 6:43 PM, "Alex Gaynor" 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 <
On Jan 31, 2018, at 18:58, Mariatta Wijaya 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 g
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 existi
