Hi,
For those of you not on the call today, we reviewed the SCM Migration
Project in preparation for Steve being out of the office in May. One of
the outcomes of the meeting is this email alias :-)
Notes, SCM Migration Project Review Meeting
4/19/07
Attendees:
Bonnie Corwin
Danek Duvall
Mike Kupfer
Steve Lau
Rich Lowe
* Updates/Questions
- Kelli Dupee will be helping us at least through May, hopefully a
a little longer.
- Kelli will focus on:
- beta test plan;
- pulling together training materials for Phase 1: ON moving
to Mercurial;
- planning process changes and pulling together any training
materials for Phase 2: ON moving outside
- Since the team is growing, we'll set up a project alias for
logistical use. We'll still use tools-discuss for technical
discussions.
- Three engineers in Beijing are getting up to speed on Mercurial
and Python. Their names are on the tasks they will be working.
* Task List Review: http://genunix.org/wiki/index.php/SCMMigrationTasks
- Gate/Gatekeeper tools is the biggest hole.
- Danek can help part-time
- Danek/Steve will talk next week and determine completion
estimates.
- Best plan seems to be for Danek to work on these (as opposed
to finding additional help) because he made so many changes/
additions during his recent tenure as gatekeeper.
- Versioning
- Steve will write up/post a synopsis of the plan for versioning
(the results of his conversations with Service).
- Only work needed is removal of %I% in source files.
- Other keyword work
- Rich/Steve have already done some removal.
- Will leave #ident lines and make it a check module item.
- IAM.xml fro ARC
- Published but not stable.
- We're relying on this to be a stable interface.
- Steve to add item (w/ John Plocher as owner) for stablizing work.
Steve will let John know about the new task.
- Cadmium support
- Mostly feature-complete. Rich to implement backup/restore.
- Discussion about whether it should remain part of ONbld or
be its own packages.
- Will leave as part of ONbld. Steve will update list.
- Webrev
- Rich has working version. Relies on Cadmium.
- Decision: Reliance ok for now. Rich to extend webrev so it
doesn't need Cdm loaded - but instead uses Cdm out of
onnv-tools workspace. Standalone webrev can happen post-
migration.
- Discussion about flp files. No resolution. Will continue to
discuss as part of xref work.
- "Developing in ON" paper. Bonnie will contact some people to
see if anyone is willing to start work on converting this to
be about working with Mercurial. Then we'll worry about adding
Cadmium information.
* Generic Command Hook and 'strip' equivalent
- Version of the generic command hook pushed out soon. Bonnie
will let the alias know when it's available.
- Bonnie will push for a plan/delivery date for strip functionality.
If it can't be done, we have an option but need to know.
* Mercurial Stoppers
- Mike has a partial list. Will incorporate feedback and put
out to tools-discuss.
- Danek has some questions around rename - he and Steve will
discuss and create a list so we can determine what are
usability questions and what are issues/bugs we will want
addressed/fixed.
- Bonnie will let Matt know a list is coming.
* Solaris Stoppers
- 14 bugs marked with 'hg_trans' keyword. Some fixed in our code.
- Steve will send out list and status.
- Other people could help with these.
* Discussion about project workspaces
- Conversion Tool
- Tool to convert project workspaces would be useful.
- Should not try to preserve file history.
- Bonnie will ask for a resource.
- Process
- Discussion around how to suggest teams move. Result:
- New projects or recently-created projects need to use
Mercurial.
- Existing projects that are targeting integration before
ON moves to Mercurial or just after ON moves should wait.
Those integrating just after ON moves should convert at
the time of integration.
<Need ON move date so can be specific about the window>
- Existing projects expecting to integrate farther out
after ON moves can choose when to move. We recommend
people convert early because squishing deltas will be
easier than staying in sync with ON once it moves.
* Miscellaneous
- deleted_files
- There will be no deleted_files hierarchy in the Mercurial
tree because Mercurial has real delete capability.
- We will have the immediate follow-on putback (after the big
'SCM Migration' wad puts back) to remove the deleted_files
hierarchy so that it is preserved in the history, but removed
from the working copy.
* Next Steps
- Bonnie will send out a list of resources needed.
- Danek/Steve will figure out estimates for gate/gatekeeper tools
work.
