I've been mulling over the problem of how to tag builds in the Mercurial
repository today. The easy solution is to of course just tag the builds
on the day the gate closes - but this doesn't take into account backouts
or respins...
So each build is, essentially a branch of onnv-gate and needs to be
treated as such.
Mercurial's official position is that "a branch == a repository", but it
is possible to do in-line branches via tagging with multiple heads.
My proposal is to do in-line branch/tagging of builds-only (not weekly
source drops) to the Mercurial repository. This will cause some
deviation from onnv-gate in that the act of tagging introduces a
changeset, but that's unavoidable - and I think the benefits outweigh
the minor deviation. I just want to make sure this is in sync with what
the ON GK's will be doing going forward once we flip the big switch and
ON officially becomes Mercurialised. :)
Does this sound reasonable?
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
