Mike Kupfer wrote: > Any comments before I send this out? In particular, any other major > accomplishments or upcoming tasks that I should mention? I want to give > a reasonably accurate description of what we've done and what we have > left to do, without drowning anyone in detail. > > thanks, > mike > > From: Mike Kupfer <mike.kupfer at sun.com> > To: tools-discuss at opensolaris.org, on-discuss at opensolaris.org > cc: scm-migration-dev at opensolaris.org > Subject: SCM Migration status > X-Mailer: MH-E 8.0.3; nmh 1.0.4; XEmacs 21.4 (patch 21) > -------- > 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--some of which are used by SFW--ported to work with both > TeamWare and Mercurial. Some of the tools (e.g., webrev, nightly) also > work with Subversion. > > 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.) > > The tools changes are available from our project page. (As mentioned > above, these tools should work with both TeamWare and Mercurial.)
Established a scm test repository and updated the test plan. Posted Mercurial test suite and tools test suite baselines. > 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. Adding python api to CTI for TET so we can develop tests in python using the standard test framework. Cheers, Jim
