>>> When I sync my project gate, I like to pull in the changeset which >>> includes the .hgtags update. Do you think that's worth including? Or >>> would it just be confusing? >> >> It's a good suggestion, because that way your project gate children can >> also use the tag. I didn't really play with it, but I imagine that they >> cannot, otherwise. > > That's correct. But the downside is that this is only useful if the > changeset that tags the build changeset is the very next changeset after > the build changeset. If you just pull in the changeset that changes > .hgtags, it's possible that it happened much further down the line, and you > end up pulling a bunch of "real" gate changes that you don't actually want. > > Now, if everyone's careful to tag immediately, then it should be safe.
In particular, the gate scripts that close out a build take care of the tag, and the repository is not open for business while that is going on. So this is a reasonable safe assumption in the gate/clone, but not (necessarily) the world in general. --Mark
