<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/17/2014 03:20 PM, Victor Stinner
wrote:<br>
</div>
<blockquote
cite="mid:CAMpsgwafgAH3Hy=1JMFhxf0cnZE8vM4-D87jLMNKHC7cDBSvfg@mail.gmail.com"
type="cite">
<pre wrap="">2014-02-17 0:25 GMT+01:00 Larry Hastings <a class="moz-txt-link-rfc2396E" href="mailto:larry@hastings.org"><larry@hastings.org></a>:
</pre>
<blockquote type="cite">
<pre wrap="">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!
</pre>
</blockquote>
<pre wrap="">
Does it mean that the default branch is open for changes which target 3.4.1?
</pre>
</blockquote>
<br>
Basically, yes.<br>
<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>