Re: [python-committers] "trivial" label replaced with "skip issue"
2017-07-14 20:33 GMT+02:00 Brett Cannon : > In preparation of fully moving over to blurb and per-file news entries (I > don't have an ETA from Larry on when he plans to do explode Misc/NEWS into > individual files), ... Oh, I wasn't aware of this plan. What is the benefit of converting old Misc/NEWS entries? Do you have an idea of many files we will get? Do we plan to remove old entries? Victor ___ 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] "trivial" label replaced with "skip issue"
Getting rid of Misc/NEWS was the whole point. The benefit is that we get rid of Misc/NEWS collisions. The other questions, you can answer for yourself by looking at the PRs. They're all in a row, PR 2714 through PR 2719. 2719 is where most of the conversation is happening. https://github.com/python/cpython/pull/2719 Right now I'm trying to figure out how to fix the Doc build. I don't think there are any other issues. //arry/ On 07/16/2017 04:10 PM, Victor Stinner wrote: 2017-07-14 20:33 GMT+02:00 Brett Cannon : In preparation of fully moving over to blurb and per-file news entries (I don't have an ETA from Larry on when he plans to do explode Misc/NEWS into individual files), ... Oh, I wasn't aware of this plan. What is the benefit of converting old Misc/NEWS entries? Do you have an idea of many files we will get? Do we plan to remove old entries? Victor ___ 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/
Re: [python-committers] "trivial" label replaced with "skip issue"
On Sun, Jul 16, 2017, 07:10 Victor Stinner, wrote: > 2017-07-14 20:33 GMT+02:00 Brett Cannon : > > In preparation of fully moving over to blurb and per-file news entries (I > > don't have an ETA from Larry on when he plans to do explode Misc/NEWS > into > > individual files), ... > > Oh, I wasn't aware of this plan. Just a reminder all the major discussions about workflow changes happen on the core-workflow mailing list with smaller discussions on the core-workflow issue tracker. This specific change has been planned and discussed since the migration was nothing more than a PEP. -brett What is the benefit of converting old > Misc/NEWS entries? Do you have an idea of many files we will get? Do > we plan to remove old entries? > > Victor > ___ 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 3.3.7 release schedule and end-of-life
A quick thanks from me, Ned, for stepping forward to help 3.3 pine for the fjords. On Sat, Jul 15, 2017, 14:51 Ned Deily, wrote: > Python 3.3 is fast approaching its end-of-life date, 2017-09-29. Per our > release policy, that date is five years after the initial release of 3.3, > 3.3.0 final on 2012-09-29. Note that 3.3 has been in security-fix only > mode since the 2014-03-08 release of 3.3.5. It has been a while since we > produced a 3.3.x security-fix release and, due to his commitments > elsewhere, Georg has agreed for me to lead 3.3 to its well-deserved > retirement. > > To that end, I would like to schedule its next, and hopefully final, > security-fix release to coincide with the already announced 3.4.7 > security-fix release. In particular, we'll plan to tag and release 3.3.7rc1 > on Monday 2017-07-24 (UTC) and tag and release 3.3.7 final on Monday > 2017-08-07. In the coming days, I'll be reviewing the outstanding 3.3 > security issues and merging appropriate 3.3 PRs. Some of them have been > sitting as patches for a long time so, if you have any such security issues > that you think belong in 3.3, it would be very helpful if you would review > such patches and turn them into 3.3 PRs. > > As a reminder, here are the guidelines from the devguide as to what is > appropriate for a security-fix only branch: > > "The only changes made to a security branch are those fixing issues > exploitable by attackers such as crashes, privilege escalation and, > optionally, other issues such as denial of service attacks. Any other > changes are not considered a security risk and thus not backported to a > security branch. You should also consider fixing hard-failing tests in open > security branches since it is important to be able to run the tests > successfully before releasing." > > Note that documentation changes, other than any that might be related to a > security fix, are also out of scope. > > Assuming no new security issues arise prior to the EOL date, 3.3.7 will > likely be the final release of 3.3. And you really shouldn't be using 3.3 > at all at this point; while downstream distributors are, of course, free to > provide support of 3.3 to their customers, in a little over two months when > EOL is reached python-dev will no longer accept any issues or make any > changes available for 3.3. If you are still using 3.3, you really owe it > to your applications, to your users, and to yourself to upgrade to a more > recent release of Python 3, preferably 3.6! Many, many fixes, new > features, and substantial performance improvements await you. > > https://www.python.org/dev/peps/pep-0398/ > https://devguide.python.org/devcycle/#security-branches > > -- > Ned Deily > [email protected] -- [] > > ___ > 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/
Re: [python-committers] "trivial" label replaced with "skip issue"
2017-07-16 16:10 GMT+02:00 Victor Stinner : > What is the benefit of converting old Misc/NEWS entries? I guess that the benefit is to use a single format for all NEWS entries. I understand that it will ease the build of the changelog. > Do you have an idea of many files we will get? > Do we plan to remove old entries? Before: 47 files in master. After: 546 files. Ok, it's not much. I didn't know that blurb supports "packing" NEWS entries into a single file, like Misc/NEWS.d/3.5.0a1.rst which contains 598 entries. Cool! My fear was to get 10,000 files in Misc/NEWS and starting to get performance issues with Git on some platforms. With the PR #2719 (convert Misc/NEWS to blurb for master), the Git repository contains 4,340 files. On my laptop, I didn't notice any major performance related to that. Victor ___ 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] [RELEASE] Python 3.6.2 is now available
On behalf of the Python development community and the Python 3.6 release team, I am happy to announce the availability of Python 3.6.2, the second maintenance release of Python 3.6. 3.6.0 was released on 2016-12-22 to great interest and we are now providing the second set of bugfixes and documentation updates for it; the first maintenance release, 3.6.1, was released on 2017-03-31. Detailed information about the changes made in 3.6.2 can be found in the change log here: https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-2 Please see "What’s New In Python 3.6" for more information about the new features in Python 3.6: https://docs.python.org/3.6/whatsnew/3.6.html You can download Python 3.6.2 here: https://www.python.org/downloads/release/python-362/ The next maintenance release of Python 3.6 is expected to follow in about 3 months, around the end of 2017-09. More information about the 3.6 release schedule can be found here: https://www.python.org/dev/peps/pep-0494/ Enjoy! P.S. If you need to download the documentation set for 3.6.2 immediately, you can always find the release version here: https://docs.python.org/release/3.6.2/download.html The most current updated versions will appear here: https://docs.python.org/3.6/ -- Ned Deily [email protected] -- [] ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
