A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-February/132388.html below:

[Python-Dev] Python 3.4: What to do about the Derby patches

[Python-Dev] Python 3.4: What to do about the Derby patches [Python-Dev] Python 3.4: What to do about the Derby patchesSerhiy Storchaka storchaka at gmail.com
Sun Feb 16 21:36:58 CET 2014
16.02.14 20:31, Larry Hastings написав(ла):
> So here we are in the "release candidate" period for 3.4, and we still
> have all these unmerged Derby patches.  And it's simply too late in the
> release cycle to merge them for 3.4.0.
>
> Here's how I propose we move forward.

Your plan LGTM (except one question below).

> 4) We accelerate the schedule for 3.4.1 slightly, so we can get these
> new signatures into the hands of users sooner. Specifically, I propose
> we ship 3.4.1 two months after 3.4.0.  I figure we would release 3.4.1
> rc1 on Sunday May 4th, and 3.4.1 final on Sunday May 18th.

How this will affect the schedule for 3.3.x? Will it accelerately 
switched to security-only fix mode?


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4