On Wed, May 18, 2011 at 10:37 PM, Georg Brandl <g.brandl at gmx.net> wrote: > On 18.05.2011 21:09, "Martin v. Löwis" wrote: >> Am 18.05.2011 20:39, schrieb Hagen Fürstenau: >>>> On behalf of the Python development team, I am pleased to announce the >>>> first release candidate of Python 3.2.1. >>> >>> Shouldn't there be a tag "v3.2.1rc1" in the hg repo? >> >> http://hg.python.org/releasing/3.2.1/ >> >> Regards, >> Martin >> >> P.S. "Shouldn't" makes it sound as if there was a mistake. > > To clarify: once the final is done, the repo Martin mentioned will be > merged back to main and then vanish. Can't this work be done in the branch of main repo, so that everybody can track the progress in place? Is there any picture of the process similar to http://nvie.com/posts/a-successful-git-branching-model/ ? -- anatoly t.
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