Hey all, At some point, no doubt, we're going to watch to switch to Hg 1.1.
I'd rather do this in a somewhat orderly manner, rather than because someone decides it *must* be done before an Indiana release, We (tools) need to support the version of Hg in the WOS, and that version needs to be held back until we support it (if that makes sense). So we need to have some idea of what we're going to do right about... well, now. Some notes I have: - 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. - Hg 1.0.2 cannot read a workspace created by Hg 1.1 via the local filesystem (over ssh it works, as long as 'hg' on the remote is 1.1, or --remotecmd is used). This would effectively mean that every machine you may access a given workspace from needs to get hg-1.1 at the same time. The former, obviously, we just need to fix our tools to be happy with (I have a workspace which, while ugly, basically functions). The latter is more cumbersome, I don't know what we need to do about that. Thoughts from SCM people? For the sake of sanity, we should drop an entry or two from the tail of the list of supported versions. I'd like to drop 1.0 and 1.0.1 from that list. - 1.0 was replaced in the WOS by 1.0.2, in snv_97 (I think it was...) - 1.0.1 was never delivered, but was listed as "good" because it was the version in some filesystem full of gunk within SMI, and it was easy to verify it was good. We do not intend to support whatever happens to be thrown our way by internal gunk again. That said, if 1.0.1 is *still* the version there, it no doubt needs to continue to work as it has been. Obviously, someone else will have to check that. -- Rich
