Difference between revisions of "Migrate from CVS to Bazaar"
From EPICSWIKI
(→To Do: Adding Howto doc) |
(→CVS Conversion: Branches only need 2-part version numbers.) |
||
| Line 26: | Line 26: | ||
* Various uninteresting CVS branches and version tags will not be brought over. | * Various uninteresting CVS branches and version tags will not be brought over. | ||
* Release version tag names will be converted into the formats Rx.y.z or Rw.x.y.z | * Release version tag names will be converted into the formats Rx.y.z or Rw.x.y.z | ||
* Release branch tag names will be converted into the format Bx.y | * Release branch tag names will be converted into the format Bx.y | ||
Latest revision as of 20:25, 14 December 2009
This page describes my current project to convert the EPICS CVS repository to use the Bazaar DVCS and host the result at Launchpad.net.
To Do
- Write Bazaar (bzr) How-To documentation for developers
- Create and configure Launchpad (lp) teams and projects
- Final cvs repository conversion to bzr
- Lock CVS repo
- Convert (see below)
- Extract Jeff's trunk changes since 2009-09 to a separate branch
- Upload all branches to lp
- ... what's missing here? ...
- Announce
CVS Conversion
This works best if I first convert from CVS to a Subversion dumpfile using cvs2svn and then import that into Bazaar with svn2bzr.
cvs2svn --options cvs2svn.options svn2bzr.py --scheme=trunk base.svn-dump base.bzr
The cvs2svn.options file configures the following transformations:
- APS user names are converted to the email address of the author if they are still active in the community. For authors who have left the email address will point to core-talk but with the user's name still.
- Various uninteresting CVS branches and version tags will not be brought over.
- Release version tag names will be converted into the formats Rx.y.z or Rw.x.y.z
- Release branch tag names will be converted into the format Bx.y
