[Python-Dev] Request for CPython 3.5.3 release
kevin-lists at theolliviers.com
Mon Jul 4 11:22:01 EDT 2016
On 7/4/16, 3:32 AM, "Python-Dev on behalf of Sven R. Kunze" <python-dev-bounces+kevin-lists=theolliviers.com at python.org on behalf of srkunze at mail.de> wrote:
>On 03.07.2016 16:39, Guido van Rossum wrote:
>> Another thought recently occurred to me. Do releases really have to be
>> such big productions? A recent ACM article by Tom Limoncelli
>> reminded me that we're doing releases the old-fashioned way --
>> infrequently, and with lots of manual labor. Maybe we could
>> (eventually) try to strive for a lighter-weight, more automated
>> release process?
>I can only recommend such an approach. We use it internally for years
>now and the workload for releasing, quality assurance and final
>deployment dropped significantly. We basically automated everything.
>The devs are pretty happy with it now and sometimes "mis-use" it for
>some of its side-products; but that's okay as it's very convenient to use.
>For some parts we use pip to install/upgrade the dependencies but
>CPython might need to use a different tooling for the stdlib and its
>If you need some assistance here, let me know.
I also offer my help with setting up CI and automated builds. :) I've actually done build automation for a number of the projects I've worked on in the past. In every case, doing so gave benefits that far outweighed the work needed to get it going.
>> It would be less work, and it would reduce stress for
>> authors of stdlib modules and packages -- there's always the next
>> release. I would think this wouldn't obviate the need for carefully
>> planned and timed "big deal" feature releases, but it could make the
>> bug fix releases *less* of a deal, for everyone.
>>  http://cacm.acm.org/magazines/2016/7/204027-the-small-batches-principle/abstract
>> (sadly requires login)
>Python-Dev mailing list
>Python-Dev at python.org
More information about the Python-Dev