Re: [python-committers] [Python-Dev] Should I delay 3.5.3 and 3.4.6 by two weeks?
> On Dec 18, 2016, at 9:26 PM, Larry Hastings wrote: > > So, if you have an opinion, please vote for one of these three options: > • Don't slip 3.5.3. and 3.4.6. > • Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. > • Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to > slip again without us having to change the release. I vote for not slipping. 2.7.13 is out. 3.6.0 is almost out. And it would be nice to have the others done as well. That way, we know the whole source tree is open and can start moving forward without reservations. Also, I would like the 3.6.0 announcement to not get drowned-out or attenuated by other announcements around older releases (i.e. it would be nice if 3.6.0 was the actual latest release of any version for a while). Raymond ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] [Python-Dev] Should I delay 3.5.3 and 3.4.6 by two weeks?
On Mon, 19 Dec 2016 at 06:29 Terry Reedy wrote: > On 12/19/2016 12:26 AM, Larry Hastings wrote: > > > > > > Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and > > 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle" > > around the release. I expect a flood of adoption of 3.6, and people > > switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it > > just seemed sensible. > > > > 3.6 just slipped by two weeks. So now there's less than two weeks > > between 3.6.0 final shipping and tagging the release canddiates for > > 3.5.3 and 3.4.6. This isn't as much time as I'd like. > > > > If I had total freedom to do as I liked, I'd slip my releases by two > > weeks to match 3.6. But there might be people planning around 3.5.3 and > > 3.4.6--like Guido was waiting for 3.5.3 for something iirc. > > > > So, if you have an opinion, please vote for one of these three options: > > > > * Don't slip 3.5.3. and 3.4.6. > > I am mildly in favor of this. There are already known bugs in 3.5 that > will not get fixed, no matter how long you delay the final maintenance > release. There are even bugs left in 2.7 after 6 years of fixing. In > the meanwhile, it is a mild nuisance to have 3 3.x maintenance branches > open. > > I don't know when Brett will move us to GIT and how that might impact > the timing. > Slipping doesn't affect me yet as all the pieces are still not quite in place. So a shift in release just shifts the blackout period for the week prior to the 3.5.3 release. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?
Le 19/12/2016 à 06:26, Larry Hastings a écrit : > > So, if you have an opinion, please vote for one of these three options: > > * Don't slip 3.5.3. and 3.4.6. > * Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. > * Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to > slip again without us having to change the release. I would myself vote for a delay. How long exactly doesn't really matter. Motivation : I would like a fix for https://bugs.python.org/issue28427 to get in 3.5.3. The fix is ready but a quick look by the current dict specialists may be welcome (though I can do without as well :-)). Reviewer workforce may be scarce especially around end-of-Gregorian-year festivities. Regards Antoine. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Can we delete https://hg.python.org/coding/cpython/?
It's erroneously labeled as the "official python repo" and created by some stranger. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Can we delete https://hg.python.org/coding/cpython/?
Killed. On Mon, Dec 19, 2016, at 14:23, Brett Cannon wrote: > It's erroneously labeled as the "official python repo" and created by > some > stranger. > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
