Danek Duvall wrote:
As a recent problem with cadmium has demonstrated, our (my?) policy for
updating the copy of SUNWmercurial in the WOS is not optimal. What I've
been doing, rather simply, is to push a released, numbered, version of
mercurial whenever such a beast passes its internal tests. Given the
rather lengthy time between mercurial releases, this means we have the
opportunity to run into bugs that get left unfixed for long periods of
time.
To shore that up I periodically (or on request) rebuild the packages and
post them on the SCM downloads page, based on whatever's tip in the
mercurial repo.
So what do y'all think should happen here? Should I push mercurial tip
into the WOS once every two weeks? Or hg-stable? Or just on request? Or
leave the WOS alone and update the downloads page .... ?
Thanks,
Danek
I'm wary of just updating it to tip every two weeks and pushing it. Or
even hg-stable for that matter, without testing it properly against our
uses with Cadmium.
I'd say our best policy should be choose a hg-stable version, backport
any fixes we need (e.g.: the Mq strip patch for Cdm), and integrate
that. When a new release of hg-stable comes out, backport any fixes we
need, test it appropriately with Cadmium (and any other uses from within
our CBE: gate hooks, Check modules, etc.) - if tests pass, then lather,
rinse, repeat.
For now that version seems to be 0.9.3 + the two backported patches we need.
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
