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 .... ?
Keeping the download page and the WOS out of sync sounds suboptimal.
Seems like you push it into the WOS, and subsequently update the
downloads, as needed, where "need" could be:
1. A new released, numbered version has passed internal tests
2. There are fixes that we want/need
...and this seems to correspond to the "or on request" clause above.
I haven't thought about what happens after the switch, or whether that
should imply less frequent updates or not.
--Mark
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
