[Python-Dev] question re: default branch and release clone

["Martin v. Löwis"]

> And if changes like this are added now, they will be included in 3.2.4
> but not in 3.3.0. Is this bad?

This is the standard for any security fix: such a fix would be added to
3.1.6, 3.2.4, 3.3.1, and 3.4.0, but not to 3.2.3 or 3.3.0.

So
   version(A) > version(B)
does not imply
   has_fix(A, F) if has_fix(B, F)

(for Python releases A and B and fix F)

The same would regularly happen with any bug fix, too, except we only
have one bug fix branch at nearly every point in time (except that
we have the 2.7 branch as well).

Regards,
Martin

P.S. Python 3.1 will continue to receive security fixes until June 2014,
3.2 will receive them until February 2016, 3.3 until September 2017. For
2.7, a policy needs to be set after the last bug fix release of 2.7 was
made.