Richard Lowe wrote: > Jim Walker <James.Walker at Sun.COM> writes: > >> Mike, >> >> I think the outline looks good. I think focusing, like you do, >> on what will be new and how to use Mercurial will be of >> most interest to the engineering staff. >> >> You may want to add a bit more content at the beginning or the >> end that talks about the SCM Migration project itself. Also, it >> might be a good time to update some of the project webpages to make >> them more current. > > I updated the tasks page on genunix a week or so ago, I don't think > any of the others contain anything specific enough to be out of date, > am I missing something? > >> BTW. I'm starting to add testing content to the project as I >> map things out: >> http://www.opensolaris.org/os/project/scm-migration/testing/ > > Items #5 and #7 there could do with some explanation: > > 5. SFW gate uses Teamware and Mercurial in parallel > 7. ON gate uses Teamware and Mercurial in parallel > > Could you be more specific on what you mean by "in parallel"? It's > infeasible to run both SCMs as nominal masters, side-by-side, and I > assume that isn't what you mean, but I can't tell what it is you do > mean.
I believe Jim meant that the tools we integrate into ON would be capable of being used for both Teamware & Mercurial in parallel. At least that's how I interpret step 5 (since ON will still be using them in Teamware workspaces while SFW will be using them in Mercurial repositories). For step 7, both ON & SFW will be using them in Mercurial repos but it's conceivable the Teamware features will still be in use (NWS? Install?). At that point we'll want to send a heads up saying "Teamware features are still present, but won't be maintained by ON developers anymore" or something to that effect. cheers, steve -- stephen lau // stevel at sun.com | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development
