[python-committers] [RELEASE] Python 3.7.0b1 is now available for testing

On behalf of the Python development community and the Python 3.7 release team, I'm happy to announce the availability of Python 3.7.0b1. b1 is the first of four planned beta releases of Python 3.7, the next major release of Python, and marks the end of the feature development phase for 3.7. You

[python-committers] [IMPORTANT] post 3.7.0b1 development now open

Here we are: 3.7.0b1 and feature code freeze! Congratulations and thanks to all of you who've contributed to the huge number of PEPs, features, bug fixes, and doc changes that have gone into 3.7 since feature development began back in September 2016, after 3.6.0b1, 3.6's feature freeze. Now that

Re: [python-committers] I created the "needs backport to 3.7" label on GitHub

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

Re: [python-committers] I created the "needs backport to 3.7" labelon GitHub

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" wrote: > I’d suggest not porting anything to that branch until Ned gives the okay. > Hopefully it’s locked right now anyway. > > > >

Re: [python-committers] I created the "needs backport to 3.7" labelon GitHub

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

Re: [python-committers] I created the "needs backport to 3.7" label on GitHub

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

Re: [python-committers] I created the "needs backport to 3.7" label on 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 wrote: > I noticed that there is a 3.7 branch now. > So you can use this label if you want

[python-committers] 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. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of

Re: [python-committers] 3.7.0b1 status

On Jan 31, 2018, at 16:14, Ned Deily wrote: > Hang tight, I'm working on that right at this moment :) Almost ready! FYI, I'm going to lock the master branch for a brief period starting right now to do the cutover to 3.8. I'll let you know when it's unlocked. -- Ned Deily

Re: [python-committers] 3.7.0b1 status

On Jan 31, 2018, at 16:03, R. David Murray wrote: > > Hmm. I merge something and put on the backport 3.6 label and just > merged that...and I have no idea if the 3.7 merge was before or > after the b1 cutoff. Is there some way to get git to tell us which > commits are

Re: [python-committers] 3.7.0b1 status

On Wed, 31 Jan 2018 03:17:47 -0500, Ned Deily wrote: > in not more than 24 hours from now. If you wish, feel free to merge > new commits into the master branch for release in 3.8, with the > understanding that any also destined for 3.7.0 will need to be > cherrypicked after the

[python-committers] 3.7.0b1 status

Just a quick update: thanks to all of you who worked long hours to get features completed and merged in for the 3.7 feature code cutoff yesterday. We release elves have been busy behind the scenes baking goodies. So far everything looks OK. But we're taking a little longer than usual: this