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?
Since I have new eyes on this project, I may or may not be headed in the right direction, but here are some specifics that I noticed... This page should be updated: http://www.opensolaris.org/os/project/scm-migration/ - (Project Scope) We should focus on the changes needed to support the migration from Teamware to Mercurial and remove references to Subversion. - (Initial Plan) We are way past an Initial Plan, and need to update the page to the current plan. Steve has been helping me get up-to-speed, but I want to make sure we are on the same page. "SVN" should be changed to "Mercurial" everywhere. - The plan should talk about all the tool development and changes and the migration strategy (ie. SFW then ON Consolidation migration). Also, for testing, I'm categorizing the changes into the following buckets: 1. Workspace tool changes and new tools that affect all developers 2. Gatekeeping tool changes and new tools that affect gatekeepers 3. Anything affected by SCCS keyword removal I need a comprehensive list of all the tools associated with this project. I'm looking at the project gate to see what things have been updated, and the following lists, but they seem out-of-date. http://www.genunix.org/wiki/index.php/gateTools http://www.opensolaris.org/os/community/tools/scm/on-scm-tools/ >> 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 updated the page to word things better. During the SFW and ON gate migrations, there will be a period where we have a Teamware gate and a Mercurial gate in operation near the same time (ie. somewhat in-sync). At a high level, some may think of this as "running in parallel". I have found the phrase "running in parallel" provides comfort to most users when big changes are happening. If this phrase isn't accurate at all, then let me know what you think is better, or give me list of the conversion steps. I'm new to the project. Thanks for the input. Jim
