release22-maint vs. release22-branch
What's the difference between these two tags? Do we need them both? Neil
What's the difference between these two tags? Do we need them both?
AFAIK: release22-maint is what we use for post-2.2 maintenance releases release22-branch was used briefly just before the 2.2 release Also: release22 was the 2.2 release itself r221 was the 2.2.1 release --Guido van Rossum (home page: http://www.python.org/~guido/)
So can we do "cvs tag -d release22-branch"? It took me a while to figure out which tag to use for bugfixes.
I'm not sure how wise it is to remove tags, ever. Maybe we should have a pep to document the tags. --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum <guido@python.org> writes:
release22-maint is what we use for post-2.2 maintenance releases
release22-branch was used briefly just before the 2.2 release
It is custom in other projects to have only one branch for both, and having the x.y.0 release just be a tag on the x.y maintenance branch. This requires freezing the maintenance just before the release to everybody but the release manager, but since the branch is not use for anything but the immediate upcoming release, this is no problem. I suggest that this is done that way for Python 2.3 also. Regards, Martin
It is custom in other projects to have only one branch for both, and having the x.y.0 release just be a tag on the x.y maintenance branch. This requires freezing the maintenance just before the release to everybody but the release manager, but since the branch is not use for anything but the immediate upcoming release, this is no problem.
I suggest that this is done that way for Python 2.3 also.
Good idea. This requires changes to PEPs 101 and 102. Would you mind fixing these or suggesting a fix to Barry? --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (3)
-
Guido van Rossum -
martin＠v.loewis.de -
Neil Schemenauer