Stephen Lau wrote:
Now that I've (hopefully) dug myself out of this onnv-gate Hg
regeneration hole, I'd like to start working on this SCM Migration thing.
I believe these are our current tasks:
1) Finalise a priority list of developer/GK tools to convert
(This discussion has already started it looks like)
2) Start an evaluation process for determing what Hg features or
extensions to use (i.e.: forest, mq, etc.)
Various things depend on choices here (and in some respects, choices
here may affect workflow), so this needs to be kicked off soon.
3) Start a draft of a plan for overall/common tool design/architecture
so we don't have 15 engineers all running off every which way
and each reinventing the wheel
This, also, is somewhat dependent on #2. The other important matter
here is which tools need to work with which SCMs.
4) File bugs so we can start tracking developer/GK tool conversion
and getting REs assigned
5) Actual SCM migration conversion tools need to be developed
Some of the tools listed on the page[1] don't necessarily have to exist.
Yes, it's easy to port 'daily_update' - but we don't need it with
Mercurial. So we should keep this in mind.
I'd like to decide how we want to address SVN as well. Some of these
tools will be used by other consolidations/projects that will be using
SVN, so we should try to be mindful that we're not hacking in
Mercurialisms. (e.g.: webrev)
Are consolidations other than CCD and JDS planning on using svn?
webrev is a fine example of something that should work everywhere, but
if those two would be the sole consumers, various other things need not
support subversion.
So here's what I see as immediate next steps:
1) Can we get some volunteers to evaluate Hg features/extensions and
decide whether or not they are appropriate for use?
The Xen folks would have input here no doubt...
I've been using Mq for quite a while, and liking it, though I think the
steps required to merge would need to be considerably simplified.
Again, that kind of gets muddled into workflow.
-- Rich
_______________________________________________
tools-discuss mailing list
[email protected]
