[python-committers] FINAL WEEK FOR 3.7.0 CHANGES! (original) (raw)
Brett Cannon brett at python.org
Thu May 17 14:39:14 EDT 2018
- Previous message (by thread): [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!
- Next message (by thread): [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 17 May 2018 at 14:31 Serhiy Storchaka <storchaka at gmail.com> wrote:
15.05.18 14:51, Ned Deily пише: > This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your > feature fixes, bug fixes, and documentation updates in before > 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days > from now. We will then tag and produce the 3.7.0 release candidate. > Our goal continues been to be to have no changes between the release > candidate and final; AFTER NEXT WEEK'S RC1, CHANGES APPLIED TO THE 3.7 > BRANCH WILL BE RELEASED IN 3.7.1. Please double-check that there are > no critical problems outstanding and that documentation for new > features in 3.7 is complete (including NEWS and What's New items), and > that 3.7 is getting exposure and tested with our various platorms and > third-party distributions and applications. Those of us who are > participating in the development sprints at PyCon US 2018 here in > Cleveland can feel the excitement building as we work through the > remaining issues, including completing the "What's New in 3.7" > document and final feature documentation. (We wish you could all be > here.)
The "What's New in 3.7" document is still not complete. Actually it is far completing. In the previous releases somebody made a thoughtful review of the NEWS file and added all significant changes in What's New, and also removed insignificant entries, reorganized entries, fixed errors, improved wording and formatting. Many thanks to Martin Panter, Elvis Pranskevichus, Yury Selivanov, R. David Murray, Nick Coghlan, Antoine Pitrou, Victor Stinner and others for their great work! But seems in 3.7 this documents doesn't have an editor.
Maybe we should start thinking about flagging PRs or issues as needing a What's New entry to help track when they need one, or always expect it in a PR and ignore that requirement when a 'skip whats new' label is applied. That would at least make it easier to keep track of what needs to be done. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20180517/3bd3598f/attachment.html>
- Previous message (by thread): [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!
- Next message (by thread): [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]