It was suggested to me shortly before the holidays that it would be good for the SCM Migration project to send a status report to the community groups that are sponsoring it (Tools and ON). I'm not sure how often to send these--is monthly often enough?
If you're not familiar with the project, we're working on migrating SFW and ON from TeamWare to Mercurial. The project page--including a more precise scoping statement--is at http://www.opensolaris.org/os/project/scm-migration/. Accomplishments: since the project started, we've gotten most of the ON developer tools, and all of the tools we intend to migrate, ported to work with both TeamWare and Mercurial. These tools should also be usable by SFW. Some of the tools (e.g., webrev, nightly) also work with Subversion. Binaries are available from our project page. A beta-quality[1] Mercurial mirror of the ON gate is available. (There's already a pointer to this workspace on the ONNV project page.) We've also been working on a formal test plan and test suite. A repository has been set up for the test suite, and we've started looking at existing tests. Upcoming work: we have several open bugs to deal with, including some issues with Mercurial itself. (There's a link to the bug list on the project page.) Also, the high-level task list and schedule need a major overhaul. We need version 0.9.5 (or later) of Mercurial running on the opensolaris.org servers, so we will be working with the ops team to get those servers upgraded to a recent build of Nevada. We may also be needing a newer version of Python, to deal with a regexp scaling problem that was very recently uncovered. We're also working on a Python API to work with CTI for TET[2]. This should make for easier integration of existing Python test code and any new tests that are written in Python. Some of the modified tools are ready for code review; see http://www.genunix.org/wiki/index.php/Developer_Tools for the list (check the "Status Notes" column). Our webrev (there's a link from the project page) is currently being updated nightly. If anyone's interested in reviewing tools now and would like a more stable webrev, let me know. mike [1] Translation: we're not aware of any issues with it, but we reserve the right to throw it away and start over before the final ON migration. That would be a lot of work, though, so we're highly motivated to stick with the current repository. [2] http://www.opensolaris.org/os/community/testing/testsuites/ctifortet/
