A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023054.html below:

[Python-Dev] Stability and Change

[Python-Dev] Stability and ChangeGordon McMillan gmcm@hypernet.com
Thu, 11 Apr 2002 08:48:08 -0400
On 11 Apr 2002 at 0:46, Skip Montanaro wrote:

> ...  Guaranteeing the shelf-life of releases for
> potentially two years, when PythonLabs typically
> releases every six months, means you're going to
> have four active releases going at any one time.
> That means every bug fix that is applied to the main
> CVS trunk has to at least be considered for
> backporting to all those other releases, maybe not
> applied, but at least considered.  Practically
> speaking, that means you need a release manager for
> each of those active releases, and they have (or a
> combination of people) have to commit to that
> activity for two years.  

I think you are overstating by a bit. If a bug fix
doesn't apply to release N, it (normally) won't apply
to release N-1. The oldest release will see only
a small fraction of the activity the most recent has.

Of course, more work is still more work.

-- Gordon
> http://www.mcmillan-inc.com/ 





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