[Python-Dev] Documenting branch policy (original) (raw)

Jack Jansen Jack.Jansen at cwi.nl
Tue Sep 9 12:26:54 EDT 2003

On 8-sep-03, at 15:18, Barry Warsaw wrote:

Every release up to and including the final release for a new major

Python version is accompanied by a release branches. There's even some debate about these (I've caught up with the thread, so I know you've withdrawn this change). I've been backing off the use of release branches because they create more complexity in a world where none of us have much time to deal with it.

They served me well for the MacPython-OS9 releases. But as 2.3 is going to be the last of those anyway I could live without them, I guess.

Although: they'd still be useful in case of unforeseen problems with a distribution that are not code-related. Think of things like the Windows installer turning out to be broken on certain machine, so you want to build the installer again (but not Python itself).

Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman

More information about the Python-Dev mailing list