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)
o add-gateling
Would probably be best ignoring anonymous bringover, with 'real'
users could map user->email via the webapp?
o backout
Should just be 'hg backout' (perhaps wrapped to generate an
appropriate message?)
o buglist
hg log -r${LAST_BUILD}:${THIS_BUILD} --template '{desc|strip}'
Filter it just for IDs/case numbers if appropriate.
(backouts?)
o daily_update
remove.
o lock-gate/unlock-gate
Lock via a hook rather than using mercurial's locking? should make it
possible to exempt gate staff from the lock.
o pbcheck
Would be better if this and wx pbchk ran exactly the same checks,
exactly the same way (sharing implementation).
Should refuse to take an obviously bogus putback, should probably
only notify on others (various files in ON don't pass the checks in
their natural state, especially true for cstyle).
RTI check is hard, assuming os.o can't make use of webrticli.
Bug ID check (as in wx, assumed wanted here) is also hard, since that
uses monaco.
o pbconfirm
Simple hook, assuming we can map user->email via the webapp backend
-- Rich
_______________________________________________
tools-discuss mailing list
[email protected]
