[python-committers] Currently working on the release of Python 3.8.0rc1
Team, amazing job on getting us back on track over the weekend. Thank you All release blockers and deferred release blockers solved. And there was relatively little additional activity on the branch -- as expected at this point! Thank you for this, it will help get the release candidate out on time. I'm working on cutting RC1 today Hopefully all sanity checks, as well as building the source tarball and the binary installers for macOS and Windows will all work out fine and we'll be seeing RC1 out tonight. RC2 and the date of 3.8.0 gold If we manage to avoid the need for RC2, we will be able to release 3.8.0 on October 14th. If we need an RC2, that will slip by a week. I hope we won't. Ideally RC1 should be identical codewise to 3.8.0. To help our chances, please avoid any source-related activity on the 3.8 branch from now until the release of 3.8.0. Yes, that also counts for bug fixes unless they are critical. (Yeah, it might be a bit annoying but nobody wants to be the person who introduced a last minute regression in a major release.) Note I didn't say I forbid any activity. I have no power over you, actually. More importantly though, I trust your judgement if you assess some bug is bad enough the fix absolutely has to get into 3.8.0. Moreover, I specifically said source-related activity because... 3.8.0 is important. To some users it will be the first and the last release in the 3.8 series they will see. We need you to focus on the docs now Are all your changes properly documented? Did you notice other changes you know of to have insufficient documentation? Can you help with the "What's New" document? anxiously configure-&&-makingly y'rs - Ł signature.asc Description: Message signed with OpenPGP ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/ACMKEQNGK4FVUIZ6TYD5H26OSPIO5GSN/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Currently working on the release of Python 3.8.0rc1
On Mon, 30 Sep 2019 at 17:48, Łukasz Langa wrote: > > Team, > amazing job on getting us back on track over the weekend. > > Thank you > All release blockers and deferred release blockers solved. And there was > relatively little additional activity on the branch -- as expected at this > point! Thank you for this, it will help get the release candidate out on time. > > I'm working on cutting RC1 today > Hopefully all sanity checks, as well as building the source tarball and the > binary installers for macOS and Windows will all work out fine and we'll be > seeing RC1 out tonight. I've filed https://bugs.python.org/issue38326 as a release blocker, as I don't think we should be cutting RCs when changes have been made to a PEP-approved API without any pre-merge design discussion. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/UXZJ6BKHTHNPNHCSSFN6BM75SELGUPOG/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Currently working on the release of Python 3.8.0rc1
> On 30 Sep 2019, at 16:09, Nick Coghlan wrote: > > I've filed https://bugs.python.org/issue38326 as a release blocker, as > I don't think we should be cutting RCs when changes have been made to > a PEP-approved API without any pre-merge design discussion. Nick, Victor, as co-authors of said PEP, please reach a decision ASAP. - Ł signature.asc Description: Message signed with OpenPGP ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/BB6Q6WVKJC6F7SX4XVVJIFS2I7NFI322/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Currently working on the release of Python 3.8.0rc1
On 9/30/2019 3:48 AM, Łukasz Langa wrote: To help our chances, please avoid any source-related activity on the 3.8 branch from now until the release of 3.8.0. Yes, that also counts for bug fixes unless they are critical. (Yeah, it might be a bit annoying but nobody wants to be the person who introduced a last minute regression in a major release.) In the past, x.y.zrc1 has been tagged and branched somehow so that commits to x.y are commits to x.y.z+, the future x.y.(z+1). (I never paid attention to the details). For instance, 3.7 is currently 3.7.4+. As soon as Ned makes 3.7.5rc1, commits to 3.7 will go to 3.7.5+, the future 3.7.6, and will not disturb 3.7.5rc1 until Ned cherry picks them into the rc branch for 3.7.5. Similarly, 3.8 is currently 3.8.b4+. As soon as you make 3.8.0rc1, if you do it the same way x.y.0rc1 has been done before recently, 3.8 commits should go to 3.8.0+, the future 3.8.1. Nothing should go into 3.8.0 until you pull it in or authorize it for those who know how to put it there (I don't). There should be no need to halt 3.8 activity. tjr ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/IDOZFUKWL2JRFVNZVGXLWBHDSYKQEBII/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Steering Council Election Timeline
Hi folks - Per PEP 13, a new Steering Council will be voted in after each feature release. As Victor has pointed out, 3.8 is scheduled for 2019-10-21 so we should start talking about the election. The Steering Council discussed this and the timeline proposed for the vote is as follows: * The nomination period will begin Nov 1, 2019 (do not post nominations until then) * Nomination period will end Nov 15, 2019 * Voting will begin Dec 1, 2019 * Voting will end Dec 15 Nominations will be collected via https://discuss.python.org/ (more details to follow). I will be handling all the email notifications related to the election and Ernest will continue to run the elections. I will send more information out in a couple of weeks. In the meantime, don't hesitate to reach out if you have any questions or concerns. Thank you, Ewa ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/PLDUMAJOLHM5W6FWOMSGUBN2Q7Z6D3JM/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Steering Council Election Timeline
The steering council also proposes that no changes be made to PEP 13 between Nov 1 and Dec 15. ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/TST4UFEAOUXMPABQLXLDM6T5PHLIUQHP/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Currently working on the release of Python 3.8.0rc1
Hello Łukasz, I consider this one critical enough to get into 3.8: https://bugs.python.org/issue38319 Long story short: shutil.copyfile() and socket.sendfile() are broken on 32-bit platforms for files >= 2GiB. shutil.copyfile() was modified by me in the 3.8 cycle so the bug only affects 3.8 and 3.9. On Mon, Sep 30, 2019 at 3:48 PM Łukasz Langa wrote: > Team, > amazing job on getting us back on track over the weekend. > > *Thank you* > All release blockers and deferred release blockers solved. And there was > relatively little additional activity on the branch -- as expected at this > point! Thank you for this, it will help get the release candidate out on > time. > > *I'm working on cutting RC1 today* > Hopefully all sanity checks, as well as building the source tarball and > the binary installers for macOS and Windows will all work out fine and > we'll be seeing RC1 out tonight. > > *RC2 and the date of 3.8.0 gold* > If we manage to avoid the need for RC2, we will be able to release 3.8.0 > on October 14th. If we need an RC2, that will slip by a week. I hope we > won't. Ideally RC1 should be identical codewise to 3.8.0. > > To help our chances, please avoid any source-related activity on the 3.8 > branch from now until the release of 3.8.0. Yes, that also counts for bug > fixes unless they are critical. (Yeah, it might be a bit annoying but > nobody wants to be the person who introduced a last minute regression in a > major release.) > > Note I didn't say I forbid any activity. I have no power over you, > actually. More importantly though, I trust your judgement if you assess > some bug is bad enough the fix absolutely has to get into 3.8.0. Moreover, > I specifically said source-related activity because... > > 3.8.0 is important. To some users it will be the first and the last > release in the 3.8 series they will see. > > *We need you to focus on the docs now* > Are all your changes properly documented? > Did you notice other changes you know of to have insufficient > documentation? > Can you help with the "What's New" document? > > anxiously configure-&&-makingly y'rs > - Ł > ___ > python-committers mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/ACMKEQNGK4FVUIZ6TYD5H26OSPIO5GSN/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- Giampaolo - http://grodola.blogspot.com ___ python-committers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/VC7XNBK65YBNUHKXC7PNMJQCU5P5YJ4X/ Code of Conduct: https://www.python.org/psf/codeofconduct/
