On 16/04/15 14:50, Paul Tagliamonte wrote:
Aloha, Developers!
Many of our projects in Debian are written in Python -- yay, Python!
However, a large chunk are implemented in Python 2 -- Booo, Python 2!
Background
==========
Python 2 is scheduled to be EOL'd upstream officially and for good in 2020.
Afaict the current documentation I can find (
https://hg.python.org/peps/rev/76d43e52d978 ) python 2.7 will be
supported for "at least" 10 years after the initial python2.7 release
which would mean july 2020. Do you have more recent information that
changes the "at least" to "exactly"?
We're in 2015 now (wow, that went quickly), and keeping our release cadence up
(3 years a pop) puts Stretch up in 2018, and Buster in 2021.
I just ran the sums (took the differences in days using openoffice calc,
then divided by 365.25)
woody->sarge 2.88 years
sarge->etch 1.84 years
etch->lenny 1.86 years
lenny->squeeze 1.98 years
squeeze->wheezy 2.23 years
wheezy-> jessie 1.97 years (assuming it releases as announced)
I assume there is no intention of a repeat of the woody->sarge cycle ;)
If we are optimistic and assume that the jessie->stretch and
stretch->buster cycles will be the same length as the sarge->etch cycle
that puts the stretch release in febuary 2017 and the buster release in
december 2018. If we are pessimistic and assume that the jessie->stretch
and stretch->buster cycles will be the same length as the
squeeze->wheezy cycle that puts the stretch release in july 2017 and the
buster release in october 2019.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/553063cb.4090...@p10link.net
