[Python-Dev] Python 3.4: Cherry-picking into rc2 and final

Barry Warsaw barry at python.org
Thu Feb 20 03:23:55 CET 2014

On Feb 20, 2014, at 10:24 AM, Stephen J. Turnbull wrote:

>But should Ubuntu desires be distorting a volunteer RE's process?

Ubuntu 14.04 final freeze is April 10[1], so I think that's the drop dead date
for getting 3.4 final into Ubuntu 14.04.  Matthias may correct me, but I think
if we can hit that date (well, maybe a day or two early to be safe) we're good.

Missing that date probably isn't catastrophic, especially if there are few to
no changes between the last Python 3.4 rc before our final freeze, and Python
3.4 final.  What it means is that 14.04 won't ship with the final Python 3.4
and we'll have to do a "stable release update" after 14.04 to catch up to the
Python 3.4 final release.  It does mean that many Ubuntu users won't see it
until 14.04.1, whenever that is, if at all.  But if the only difference is a
version string and sys.version_info, then I don't think that's so bad.  And
ultimately we'll have to do that anyway to get the LTS users Python 3.4.1,
3.4.2, and so on.

Two notes: Matthias just enabled Python 3.4 as the default Python 3, and
there's no going back.  Also, we have aligned the Python release schedules
with external schedules before, most notably Apple a couple of times.  I think
it's reasonable to do so *if* we can do it without sacrificing the quality of
Python 3.4's final release.


[1] https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule

More information about the Python-Dev mailing list