[Python-Dev] Switch to 2.4a0 on trunk?

[Fred L. Drake, Jr.]

Barry Warsaw writes:
 > Well, here's the problem.  The branch was already created with
 > release23-branch, and there doesn't appear to be a way to rename a
 > branch tag.  Fred's going to dig into the docs to see if he can find a
 > clue, but if anybody else has direct experience with renaming branch
 > tags, please speak up!

Boy have we dug!  Did the nasty with a test repository as well.

 > The other option is to just stick with release23-branch as the
 > maintenance branch tag.

Thomas Heller writes:
 > As far as I know, you create a new tag with the new name,
 > specifying '-r old-tag' as the revision to tag. Then you can delete
 > the old tag.

If these weren't branch tags, that would be exactly what we want.  The
CVS manual says this doesn't work for branch tags.  It's right.

Here's what we've come up with:

1. Create a fresh checkout from the release23-branch tag.  Capture the
   cvs output (all the "U somefile" lines) for use in the next step.

2. Massage the cvs output to create input for xargs --null:

   sed 's/^U //' cvsoutput | tr '\n' '\000' >xargsinput

3. Use xargs --null to drive a cvs admin command:

   cat xargsinput | xargs --null cvs admin -N release23-maint:release23-branch

4. Send an email to python-dev to let people test.

Note that the release23-branch tag is left alone.  It's not worth the
risk of removing it.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Zope Corporation