[Python-Dev] Status of 2.7 and 3.2

[R. David Murray]

On Sun, 7 Jun 2009 at 18:55, "Martin v. Löwis" wrote:
>> B. "Yes."
>>
>>   This answer means that the 3.1 to 3.2 development cycle will need to
>> be truncated by roughly 6 months so that 3.2 can be released before 2.7
>> with any new features of interest. The 3.2 and 2.7 releases should then
>> occur within a few months of each other.
>
> Assuming the policy "release new features for 2.x only after they got
> released for 3.x". I don't think such a policy actually exists.

I'm neutral on time frames, but I think that it _should_ be a policy
that new features only get released to the 2.x branch after they have
been released in the 3.x branch.  Or, rather, I though that policy was
implicit in the idea that we weren't _automatically_ backporting features,
specifically in order to encourage 3.x adoption.  So if 2.7 is going to
come out before 3.2, you'll have to convince me that having new features
in 2.7 that aren't in 3.1 is a good idea :)

Note that I'm not advocating feature freezing the trunk, but rather
having 3.2 come out before or in sync with 2.7.

--David