RetroSearch Browse

Tue Feb 18 05:36:43 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-February/132442.html

On 2/17/2014 6:20 PM, Victor Stinner wrote:
> 2014-02-17 0:25 GMT+01:00 Larry Hastings <larry at hastings.org>:
>> You might think that anything you check in to the "default" branch in Python
>> trunk will go into 3.4.0 rc2, and after that ships, checkins would go into
>> 3.4.0 final.  Ho ho ho!  That's not true!  Instead, anything checked in to
>> "default" between my last revision for "rc1" (e64ae8b82672) and 3.4.0 final
>> will by default go into 3.4.1.  Only fixes that I cherry-pick into my local
>> branch will go into 3.4.0 rc2 and final.  And my local branch will remain
>> private until 3.4.0 final ships!
>
> Does it mean that the default branch is open for changes which target 3.4.1?

Presumably. That is what I started doing today.

However, the top section of 3.4 News says 3.4.0rc2 rather than 3.4.1. It 
should be relabeled and a 3.4.0rc2 sections with items actually added to 
3.4.0c2 (and those items should not be in the 3.4.1 section.

-- 
Terry Jan Reedy

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

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

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