RetroSearch Browse

Fri Apr 1 17:39:59 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-April/110360.html

Am 01.04.2011 14:49, schrieb Antoine Pitrou:
> On Fri, 01 Apr 2011 13:37:42 +0100
> Michael Foord <fuzzyman at voidspace.org.uk> wrote:
>> > I think I was unclear: I'm not advocating doing doc fixes in security-only
>> > branches; I'm just explaining why it wouldn't even make sense to do these
>> > fixes.
>> >
>> I understood. I was suggesting we modify to allow doc changes that fix 
>> errors and push updated docs *online* (not do fresh releases) and asking 
>> why not do that (other than policy)?
> 
> Well, I think the tradeoff is simply: do you want to do more work?
> (or, given the same amount of work, do you think allocating your
> workforce to backporting doc fixes is worthwhile?)

Absolutely.  I don't want to maintain that infrastructure.

Georg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-April/110360.html below:

building Python from source on multiarch Debian/Ubuntu