Re: [python-committers] Proposed release schedule for Python 3.5.4

2017-06-21 Thread Serhiy Storchaka
2017-06-22 5:58 GMT+03:00 Larry Hastings : > There have only been two (2) checkins into the 3.4 branch since 3.4.6 was > released back in January: > > f37b0cb230069481609b0bb06891b5dd26320504 > bpo-25008: Deprecate smtpd and point to aiosmtpd > > fa53dbdec818b0f2a0e22ca12a49d83ec948fc91 > I

[python-committers] Proposed release schedule for Python 3.5.4

2017-06-21 Thread Larry Hastings
It's time to start planning the next 3.5 release, 3.5.4. Note that this will be the last 3.5 "bugfix" release; after 3.5.4, the 3.5 branch will only be open for security fixes. 3.5.4 will also be the last release of 3.5 with binary installers. I propose to tag and release 3.5.4 on these d

Re: [python-committers] link from github to bpo?

2017-06-21 Thread Mariatta Wijaya
PR 2304 is merged. "View Details" still exists (scroll all the way down). When the PR is not yet merged (e.g. https://github.com/python/cpython/pull/2316), the UI looks different. Click 'Show all checks' to get the link back to bpo. Mariatta Wijaya On Wed, Jun 21, 2017 at 1:21 PM, R. David Murr

Re: [python-committers] link from github to bpo?

2017-06-21 Thread R. David Murray
On Wed, 21 Jun 2017 10:02:58 -0700, Mariatta Wijaya wrote: > Yes, for that PR, scroll down and click the "View Details" button. > Click the Details link next to bedevere/issue number status check. > It will take you to the issue in bpo. Note that this will only exist if the PR is still open (not

Re: [python-committers] link from github to bpo?

2017-06-21 Thread Mariatta Wijaya
Yes, for that PR, scroll down and click the "View Details" button. Click the Details link next to bedevere/issue number status check. It will take you to the issue in bpo. There is also an open issue in bedevere, where the link will be added at the bottom of the PR message. https://github.com/pyt

[python-committers] link from github to bpo?

2017-06-21 Thread Ethan Furman
My apologies if this has been discussed/answered before, but is there a link from the github side to the bpo side? For example, I'm looking at https://github.com/python/cpython/pull/2304 and it would be great if such a link existed to take me directly to the bpo issue. -- ~Ethan~ _

Re: [python-committers] Bedevere now automatically removes "needs backport to *" labels

2017-06-21 Thread Brett Cannon
On Tue, 20 Jun 2017 at 08:37 Victor Stinner wrote: > 2017-06-20 16:56 GMT+02:00 Mariatta Wijaya : > > I think it's because there was no 'needs backport to 3.4' label from PR > > 1849, so it doesn't make the comment about 3.4 backport PR. > > Oh, I see. These labels don't exist :-) Maybe we should

[python-committers] Fun fact, The Knights Who Say "Ni" (bot) complained about CLA on Modules/expat/

2017-06-21 Thread Victor Stinner
Hi, Fun fact: I cherry-picked a change from libexpat into Modules/expat (VS2008 fix for stdint.h), and I kept the author. Then The Knights Who Say "Ni" (bot) complained that Sebastian Pipping didn't sign the CLA :-) https://github.com/python/cpython/pull/2312#issuecomment-310091014 I fixed the i