A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2015-May/139969.html below:

[Python-Dev] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)

[Python-Dev] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!) [Python-Dev] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)Larry Hastings larry at hastings.org
Tue May 12 19:39:39 CEST 2015
On 05/12/2015 10:23 AM, Chris Angelico wrote:
> Will this model be plausibly extensible to every release? For
> instance, when a 3.5.1 rc is cut, will the 3.5 branch immediately
> become 3.5.2, with a new 3.5.1 branch being opened on bitbucket?

Yes, we could always do it that way, though in the past we haven't 
bothered.  Development on previous versions slows down a great deal 
after x.y.1.


//arry/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150512/3620406c/attachment.html>
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