[Python-Dev] release22-maint vs. release22-branch

[Guido van Rossum]

> 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/)