A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-October/082828.html below:

[Python-Dev] for __future__ import planning

[Python-Dev] for __future__ import planning [Python-Dev] for __future__ import planningEric Smith eric at trueblade.com
Sat Oct 4 01:43:00 CEST 2008 
Brett Cannon wrote:
>> Christian rightly points out that with four active trees, we're going to a
>> pretty big challenge on our hands.  How do other large open source projects
>> handle similar situations?
>>
> 
> Beats me. Are that many projects crazy enough to have that many active branches?

Is it really that bad? Once 3.0 is released, it's not like we're going 
to be patching 2.6 and 3.0 all that much. All the "real development" (by 
which I mean most of the checkins) will be on 2.7 and 3.1. The biggest 
challenge I see is the buildbots.

Eric.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4