#7323 ForgeHg: upgrade mercurial dependency
The mercurial revision that ForgeHg/setup.py (and requirements-sf.txt) specify, is old and not available on pypi to install (although old releases are at http://mercurial.selenic.com/release/ if needed for testing, etc).
We should upgrade the ForgeHg code to use the latest mercurial version. http://mercurial.selenic.com/wiki/UpgradeNotes has release notes which we can compare against the code to find things that need to be changed.
Closed #576.
forgehg:je/42cc_7323Updated mercurial to 3.0, adjusted some API calls (not many).
There are a couple of things in changelog, that I was worried about, specifically:
But it turned out they affect only UI-related commands. Seems like we don't use anything else that may broke.
Did you find http://mercurial.selenic.com/wiki/ApiChanges ? I didn't find that document until now. It seems much more relevant for us than the UpgradeNotes doc.
No, I did not. I've read through it now and I believe all relevant changes are made already. Specifically this:
Which was addressed in my first two commits in the branch:
a6e843cand25dc958. Other API methods wasn't used by ForgeHg.Great :)
I've used https://sourceforge.net/p/coils/code/ as a test case of a large real-world hg repo. After cloning it locally and pushing into allura with the latest forgehg & mercurial, I've found:
677c00like it does previously:https://sourceforge.net/p/coils/code/ci/28d6d08385ec15cb529f976e4700b799b2649aa5/log/?path= (It does list the 'release' branch in the full branch list correctly)
Closed #593. Updated
je/42cc_7323First point fixed. Indeed, branch list is in indeterminate order in both cases.