[Python-Dev] Python 3.4: Cherry-picking into rc2 and final
Gregory P. Smith
greg at krypto.org
Mon Feb 17 04:09:50 CET 2014
For 3.4.0rc2 the commit to merge from issue20621 is 52ab9e1ff46a.
On Sun, Feb 16, 2014 at 3:45 PM, Paul Moore <p.f.moore at gmail.com> wrote:
> <http://bugs.python.org/issue20621> is significant enough to be
> resulting in a 3.3.5 release - can you make sure the 3.4 fix goes in?
> I'm not sure how to find the revision number that contains the fix to
> follow the process you outline above, so I'm just mentioning it here &
> on the issue to make sure it's not missed...
> On 16 February 2014 23:25, Larry Hastings <larry at hastings.org> wrote:
> > Right now we're in the "release candidate" phase of 3.4. 3.4.0 rc1 has
> > released, and the next release will be rc2.
> > You might think that anything you check in to the "default" branch in
> > trunk will go into 3.4.0 rc2, and after that ships, checkins would go
> > 3.4.0 final. Ho ho ho! That's not true! Instead, anything checked in
> > "default" between my last revision for "rc1" (e64ae8b82672) and 3.4.0
> > will by default go into 3.4.1. Only fixes that I cherry-pick into my
> > branch will go into 3.4.0 rc2 and final. And my local branch will remain
> > private until 3.4.0 final ships!
> > If you have a Terribly Important Fix That Must Go Into 3.4.0 rc2 or
> > please go to the issue tracker and create a new issue with the following
> > attributes:
> > The title should start with "3.4 cherry-pick: " followed by the revision
> > and a short summary
> > example: "3.4 cherry-pick: b328f8ccbccf __getnewargs__ fix"
> > The version should be "Python 3.4"
> > The assignee should be "larry"
> > The priority should be "release blocker"
> > The comment should *also* contain the revision id (the tracker will turn
> > into a link)
> > I'm also working on automatically publishing the merged/unmerged revision
> > status to a web page. You can see a mock-up here:
> > http://www.midwinter.com/~larry/3.4.merge.status.html
> > The page is marked "beta" because it doesn't have real data yet--I'm
> > experimenting with my automation, so I haven't created the real 3.4 local
> > branch yet. Again, just to be crystal-clear: the revisions marked
> > on that page are just experiments, they aren't actually merged for 3.4.
> > Once I'm ready for real merging, I'll remove the beta warning.
> > (By the way: on that page, clicking on a revision takes you to the
> > web page. Clicking on the first line of the comment expands it to show
> > complete comment.)
> > Please use your best judgment before asking that a revision be
> > into 3.4.0. Our goal in the release candidate phase is to stabilize
> > and to do that we must stop changing it. Only important interface
> > new features, or bugfixes should be checked in now, and preferably they
> > should be low-risk.
> > Cheers,
> > /arry
> > _______________________________________________
> > Python-Dev mailing list
> > Python-Dev at python.org
> > https://mail.python.org/mailman/listinfo/python-dev
> > Unsubscribe:
> > https://mail.python.org/mailman/options/python-dev/p.f.moore%40gmail.com
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev