4 ms·

They're actually very big on backwards compatibility. It's quite straightforward to work with repositories created by old mercurial versions on and communicate

They're actually very big on backwards compatibility. It's quite straightforward to work with repositories created by old mercurial versions on and communicate with mercurial installs with different versions. The only thing that won't work is features that are only in the newer version. The real effect of the monthly releases is that bugs get cixed in releases, new features get added, and I get to regularly see all of the awesome activity going on in the mercurial world.

Silhouette 13y ago
This is something that has always made us a little nervous about updating here as well. Do you know whether the underlying data structures for repositories are generally maintained with both forward and backward compatibility? Edit: For anyone else interested, I finally found the magic search term I never had before, which led me to this page about upgrading and compatibility: http://mercurial.selenic.com/wiki/UpgradingMercurial http://mercurial.selenic.com/wiki/UpgradingMercurial and this page about potentially breaking changes where they do occur: http://mercurial.selenic.com/wiki/UpgradeNotes http://mercurial.selenic.com/wiki/UpgradeNotes The short version is that older and newer Hg clients and servers and mostly interoperable in all directions, but with a few specific caveats that are worth reading before you upgrade anything. There is also the ability to explicitly change the underlying repository format for compatibility reasons if you need to.