Preview of 3.4 rc2 (so far) is up
The URL has changed slightly. Please go here: http://midwinter.com/~larry/3.4.status/ You'll notice two things: * a "merge.status.html" file, which shows you the list of revisions that I've cherry-picked after rc1. * a tarball containing the resulting source tree. As I cherry-pick more revisions, I'll add new tarballs and update the merge status. For the record, I've passed over only two requested cherry-pick revisions so far: http://bugs.python.org/issue20646 select and kqueue round the timeout aways from zero http://bugs.python.org/issue20679 improve Enum subclass behavior I haven't rejected them, I just want more review. If you'd like to see these changes get cherry-picked for 3.4.0 rc2 (and final) please review them or convince someone else to contribute a review. Only thirty cherry-picked revisions so far. Gosh, you're making my life easy, guys, //arry/
On 19 Feb 2014 14:05, "Larry Hastings" <larry@hastings.org> wrote:
The URL has changed slightly. Please go here:
You'll notice two things: a "merge.status.html" file, which shows you the list of revisions that
a tarball containing the resulting source tree. As I cherry-pick more revisions, I'll add new tarballs and update the merge status.
For the record, I've passed over only two requested cherry-pick revisions so far:
http://bugs.python.org/issue20646 select and kqueue round the timeout aways from zero
http://bugs.python.org/issue20679 improve Enum subclass behavior
I haven't rejected them, I just want more review. If you'd like to see
I've cherry-picked after rc1. these changes get cherry-picked for 3.4.0 rc2 (and final) please review them or convince someone else to contribute a review.
Only thirty cherry-picked revisions so far. Gosh, you're making my life
easy, guys, Larry, you announced your preferred release candidate management process too late to rely on it entirely - you should still audit all the deferred blockers and release blockers flagged for 3.4, and ask for an update on their status, with a pointer to the archived python-dev post describing how to request that the change be included in 3.4.0 rather than being left to 3.4.1. I know at least I have been setting those on the assumption things would work the same as they have in previous releases, since you hadn't said anything prior to rc1 about doing things differently. Regards, Nick.
/arry
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
Am 19.02.2014 11:04, schrieb Nick Coghlan:
On 19 Feb 2014 14:05, "Larry Hastings" <larry@hastings.org <mailto:larry@hastings.org>> wrote:
The URL has changed slightly. Please go here:
You'll notice two things: a "merge.status.html" file, which shows you the list of revisions that I've
cherry-picked after rc1.
a tarball containing the resulting source tree. As I cherry-pick more revisions, I'll add new tarballs and update the merge status.
For the record, I've passed over only two requested cherry-pick revisions so far:
http://bugs.python.org/issue20646 select and kqueue round the timeout aways from zero
http://bugs.python.org/issue20679 improve Enum subclass behavior
I haven't rejected them, I just want more review. If you'd like to see these changes get cherry-picked for 3.4.0 rc2 (and final) please review them or convince someone else to contribute a review.
Only thirty cherry-picked revisions so far. Gosh, you're making my life easy, guys,
Larry, you announced your preferred release candidate management process too late to rely on it entirely - you should still audit all the deferred blockers and release blockers flagged for 3.4, and ask for an update on their status, with a pointer to the archived python-dev post describing how to request that the change be included in 3.4.0 rather than being left to 3.4.1. I know at least I have been setting those on the assumption things would work the same as they have in previous releases, since you hadn't said anything prior to rc1 about doing things differently.
To be fair this isn't really different from 3.3.0, just that I didn't require a specific format for issues and went through all changes manually. Georg
On 19 February 2014 20:09, Georg Brandl <g.brandl@gmx.net> wrote:
Am 19.02.2014 11:04, schrieb Nick Coghlan:
On 19 Feb 2014 14:05, "Larry Hastings" <larry@hastings.org <mailto:larry@hastings.org>> wrote:
The URL has changed slightly. Please go here:
You'll notice two things: a "merge.status.html" file, which shows you the list of revisions that I've
cherry-picked after rc1.
a tarball containing the resulting source tree. As I cherry-pick more revisions, I'll add new tarballs and update the merge status.
For the record, I've passed over only two requested cherry-pick revisions so far:
http://bugs.python.org/issue20646 select and kqueue round the timeout aways from zero
http://bugs.python.org/issue20679 improve Enum subclass behavior
I haven't rejected them, I just want more review. If you'd like to see these changes get cherry-picked for 3.4.0 rc2 (and final) please review them or convince someone else to contribute a review.
Only thirty cherry-picked revisions so far. Gosh, you're making my life easy, guys,
Larry, you announced your preferred release candidate management process too late to rely on it entirely - you should still audit all the deferred blockers and release blockers flagged for 3.4, and ask for an update on their status, with a pointer to the archived python-dev post describing how to request that the change be included in 3.4.0 rather than being left to 3.4.1. I know at least I have been setting those on the assumption things would work the same as they have in previous releases, since you hadn't said anything prior to rc1 about doing things differently.
To be fair this isn't really different from 3.3.0, just that I didn't require a specific format for issues and went through all changes manually.
That's the part that worries me - if Larry is assuming the post to python-dev is enough to get people to change their behaviour at short notice, I'm concerned things that should be release blockers won't end up blocking doing so. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 02/19/2014 02:04 AM, Nick Coghlan wrote:
On 19 Feb 2014 14:05, "Larry Hastings" <larry@hastings.org <mailto:larry@hastings.org>> wrote:
The URL has changed slightly. Please go here:
<http://midwinter.com/%7Elarry/3.4.status/>
You'll notice two things: a "merge.status.html" file, which shows you the list of revisions
a tarball containing the resulting source tree. As I cherry-pick more revisions, I'll add new tarballs and update
that I've cherry-picked after rc1. the merge status.
For the record, I've passed over only two requested cherry-pick
http://bugs.python.org/issue20646 select and kqueue round the timeout aways from zero
http://bugs.python.org/issue20679 improve Enum subclass behavior
I haven't rejected them, I just want more review. If you'd like to see these changes get cherry-picked for 3.4.0 rc2 (and final) please review them or convince someone else to contribute a review.
Only thirty cherry-picked revisions so far. Gosh, you're making my
revisions so far: life easy, guys,
Larry, you announced your preferred release candidate management process too late to rely on it entirely - you should still audit all the deferred blockers and release blockers flagged for 3.4, and ask for an update on their status, with a pointer to the archived python-dev post describing how to request that the change be included in 3.4.0 rather than being left to 3.4.1. I know at least I have been setting those on the assumption things would work the same as they have in previous releases, since you hadn't said anything prior to rc1 about doing things differently.
The release is still about a month away. And yes I still plan to go through the release blockers. //arry/
On 20 February 2014 10:31, Larry Hastings <larry@hastings.org> wrote:
On 02/19/2014 02:04 AM, Nick Coghlan wrote:
The release is still about a month away. And yes I still plan to go through the release blockers.
Thanks. I confess I had missed that rc2 -> final was already 3 weeks rather than the 2 weeks between rc1 and rc2, so my mental timeline was off. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
About 21 of those are related to asyncio. On 2/19/2014, 7:42 AM, Antoine Pitrou wrote:
On Tue, 18 Feb 2014 20:03:31 -0800 Larry Hastings <larry@hastings.org> wrote:
Only thirty cherry-picked revisions so far. Gosh, you're making my life easy, guys, That's a large number of cherry-picked revisions. How many are actually release-critical?
Regards
Antoine.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/yselivanov.ml%40gmail.com
On 02/19/2014 07:20 AM, Yury Selivanov wrote:
About 21 of those are related to asyncio.
On 2/19/2014, 7:42 AM, Antoine Pitrou wrote:
On Tue, 18 Feb 2014 20:03:31 -0800 Larry Hastings <larry@hastings.org> wrote:
Only thirty cherry-picked revisions so far. Gosh, you're making my life easy, guys, That's a large number of cherry-picked revisions. How many are actually release-critical?
Regards
Antoine.
Yes, I'm allowing in basically all the asyncio changes, because a) there's no installed base, and b) Guido is himself very heavily involved in those changes. It's my opinion that asyncio is going to get a lot of scrutiny after 3.4.0 ships, so even though it's marked provisional it's important to get it right. And I don't have enough domain knowledge to be able to pick and choose their changes. So I'm relying on Victor / Guido / Yury, merging all their changes, and hoping for the best. I really am hoping it'll settle down soon, though, //arry/
On Wed, Feb 19, 2014 at 4:42 PM, Larry Hastings <larry@hastings.org> wrote:
Yes, I'm allowing in basically all the asyncio changes, because a) there's no installed base, and b) Guido is himself very heavily involved in those changes. It's my opinion that asyncio is going to get a lot of scrutiny after 3.4.0 ships, so even though it's marked provisional it's important to get it right. And I don't have enough domain knowledge to be able to pick and choose their changes. So I'm relying on Victor / Guido / Yury, merging all their changes, and hoping for the best.
I really am hoping it'll settle down soon, though,
I am actively clamping down on these now. Yuri's and Victor's youthful enthusiasm is adorable. :-) -- --Guido van Rossum (python.org/~guido)
participants (6)
-
Antoine Pitrou -
Georg Brandl -
Guido van Rossum -
Larry Hastings -
Nick Coghlan -
Yury Selivanov