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
n...@python.org -
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 possible candidates for ch
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 3.7 branch is avai
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 is
