[Python-Dev] Maintaining old releases
"Martin v. Löwis"
martin at v.loewis.de
Thu Aug 14 08:43:06 CEST 2008
> For example, let's project dates for closing 2.6 and 3.0 now, and add
> them to PEP 361.
My view is that they should be closed when 2.7 and 3.1 are released.
Following another informal policy, we were going for an 18 months
release cycle at some time (2.6 clearly took longer), which would
mean that those branches get closed on March 1, 2010. Security
releases will be available until October 1, 2013.
Regards,
Martin
More information about the Python-Dev
mailing list