[Python-Dev] Maintaining old releases

"Martin v. Löwis" martin at v.loewis.de
Thu Aug 14 01:11:23 CEST 2008

> There's a difference between never being released, and unavailable in
> the source repository.

So would you have preferred if I had forked another branch that still
contained these patches? Such branch can still be added now. Nothing
that gets added to the source repository ever becomes unavailable.
Re-adding them is fairly easy: they are all in r61179.

Going forward, the question would then be if these patches will ever
get released. So there could be two branches, one that people can commit
arbitrary bug fixes to (which will never be released), and one that
gets security patches (which will get released for five years).

Of course, I would personally find it fairly confusing to have people
commit patches that are explicitly will not be released, and still
aren't experimental or private-use.


More information about the Python-Dev mailing list