Richard Lowe writes: > James Carlson <james.d.carlson at sun.com> writes: > > > Richard Lowe writes: > >> - The internals changed a little more than they have in the past, so > >> catching cdm up is not as easy as it was previously, especially > >> given that we're going to need to support 1.0.x with some overlap. > > > > It would be really nice to be able to base cdm on some stable > > interfaces, so that we don't need new work every time there's a minor > > (?) upgrade like this. > > The simple answer is "Not really". > > The longer answer is that Mercurial have a page: > http://www.selenic.com/mercurial/wiki/index.cgi/MercurialApi > Which didn't exist at the time much of this was done.
I guess the real question I have here isn't for cdm itself, but for hg: do you know if they're ever going to have such a thing as a stable programming interface? That page says "reasonably stable," but I'm not sure what that means. > > As long as it can do that, this change just means that we need to > > upgrade all the clients before we switch over the gates. It sounds > > like a fairly run-of-the-mill internal ON flag day to me -- "make > > sure you upgrade your hg client before XX/YY/ZZZZ, or you may lose > > access to the gate via NFS." > > I was thinking of projects, whereby the machine holding their project > gate may pickup Mercurial from SFW on the build it integrates, whereas > consumers may not. But yes, it comes down to the same issue, loud, > noticeable announcement. If it works fine with a down-rev client over ssh, then it shouldn't affect most projects, as they're just accessing hg.opensolaris.org remotely. We don't have regular file-based access to those repositories internally (nor even command-line based). It's just the cases of use with NFS that seem to be at issue, and the main ones for that are the not-yet-exported-outside-the-firewall gates. If there are internal Sun projects that are using hg without going through opensolaris.org and using NFS for access, then they'd be in the same boat. It doesn't sound like that bad a change to me, but it certainly needs to be coordinated. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
