2012/9/30 Jesus Cea <j...@jcea.es>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 29/09/12 10:35, Georg Brandl wrote:
>> Until the last ordinary 3.2 bugfix release is done (which will be
>> soon), the usual procedure for 3.x will be to check into 3.2, merge
>> into 3.3, and then merge into default, except of course for a)
>> fixes of 3.3-only features and b) trivial things like typos that
>> you don't feel have to be in 3.2.4.
>>
>> default is now Python 3.4, and new features can be committed
>> there.
>
> So, if I understand correctly, the current situation is this:
>
> 2.6: Security fixes only
> 2.7, 3.2, 3.3: Bugfixes only
> 2.3, 2.4, 2.5, 3.0, 3.1: Dead
3.1 still recieves security fixes.
>
> After 3.2.4 is published ("soon"), 3.2 would move to "security fixes
> only". Am I right?
>
> I wonder if we have a deadline for supporting 2.6 yet. How about 2.7?.
2.7 will get at least 5 years of support.
--
Regards,
Benjamin
_______________________________________________
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
