[Python-Dev] Cherry-pick between Python 3.4 RC2 and final? (original) (raw)

Matthias Klose doko at ubuntu.com
Tue Mar 4 23:04:30 CET 2014

Am 04.03.2014 15:52, schrieb Brett Cannon:

I have also filed http://bugs.python.org/issue20851 to make sure the devguide covers running tests from a tarball. If the way the release has been handled has still bugged you enough it can be discussed at the language summit, but it would be the first time we consider putting any restrictions on the RM.

I wouldn't put it this way, but instead ask how to enable the RM to do this kind of work more publicly. I really would like it more if we can extend our buildd infrastructure to automatically test during the time where the trunk and the release candidates don't match. I am aware that this was never done for any release in the past, but maybe this is something that can be enabled for 3.5. But before documenting a process which may change depending on the RM why not try to align the process?

Matthias

More information about the Python-Dev mailing list