RetroSearch Browse

Tue May 12 19:38:23 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-May/139968.html

On 05/12/2015 10:23 AM, Ned Deily wrote:
> One possible issue with Workflow 1 is that there would need to be an additional set of buildbots (for 3.5, in addition to the existing 3.x (AKA "trunk"), 3.4, and 2.7 ones) for the period from beta 1 until at least 3.5.0 is released and, ideally, until 3.4 support ends, which following recent past practice, would be relatively soon after 3.5.0.

Good point.  Though I could concievably push the 3.5.0 rc repo up to an 
hg.python.org "server-side clone" and kick off the buildbots from there.
> Where does 3.6.x fit into Workflow 2?

It doesn't.  Workflows 0 and 2 mean no public development of 3.6 until 
after 3.5.0 final ships, as per tradition.

//arry/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150512/5a0dc756/attachment.html>

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

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

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