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/132438.html below:

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

[Python-Dev] Python 3.4: Cherry-picking into rc2 and final [Python-Dev] Python 3.4: Cherry-picking into rc2 and finalVictor Stinner victor.stinner at gmail.com
Tue Feb 18 00:20:03 CET 2014
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?

Victor
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