scm migration (teamware is dead, long live mercurial… and svn… and teamware…)
December 14th, 2006 Stephen Lau
the project i’ve been working on recently is the SCM Migration project, which encompasses the SCM Migration efforts for ON; though it’s hoped that tools/extensions/etc. that we develop can and will be utilised by other software groups.
here are some of the areas that i hope to cover with our project:
- conversion of Teamware workspaces to Mercurial repositories
- conversion of onnv-gate to Mercurial
- conversion of ON development tools to support Mercurial
#2 has partly been achieved via #1. unfortunately, my tools for #1 are pretty tied to ON at the moment. i’d started playing around with writing additional code to genericise my tools to convert any Teamware workspace, but set it aside to work on #3. i’d like to get back to it when we finish some of the more pressing issues though.
#3 is my current primary focus, and is kind of interesting. it encompasses a lot of things actually. a lot of consolidations other than ON, and a lot of individuals use ON tools such as nightly, webrev, wx, etc. one problem we’ve had is code for doing checks, now live in tons of different places (independent tools like cstyle.pl, aggregate tool enhancements like wx, and CRT advocate tools like wsck). one of my goals is to common-ize all these checks into Python modules. we can then write wrappers to call them individually (ala cstyle.py), or call them as inline Python from Mercurial extensions (i.e.: for developer & gate-side Mercurial repository hooks).
richlowe, dmarker, and i have started poking around, filing bugs, and porting code. so far we’ve made progress on cstyle, comments-checking, and copyright checking.
[tags: OpenSolaris]
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
