- **status**: code-review --> closed
- **Milestone**: limbo --> forge-jun-13
---
** [tickets:#7323] ForgeHg: upgrade mercurial dependency**
**Status:** closed
**Milestone:** forge-jun-13
**Labels:** 42cc
**Created:** Sat Apr 12, 2014 05:55 PM UTC by Dave Brondsema
**Last Updated:** Fri May 23
- **status**: in-progress --> code-review
- **Comment**:
Closed #593. Updated `je/42cc_7323`
First point fixed. Indeed, branch list is in indeterminate order in both cases.
---
** [tickets:#7323] ForgeHg: upgrade mercurial dependency**
**Status:** code-review
**Milestone:** limbo
**Labels:**
- **status**: code-review --> in-progress
- **QA**: Dave Brondsema
- **Comment**:
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:
* The log view does
- **status**: in-progress --> code-review
- **Comment**:
Closed #576. `forgehg:je/42cc_7323`
Updated mercurial to 3.0, adjusted some API calls (not many).
There are a couple of things in changelog, that I was worried about,
specifically:
- hg heads now shows all branch heads, use --topo for ol
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.
---
** [tickets:#7323] ForgeHg: upgrade mercurial dependency**
**Status:** code-review
**Milestone:** limbo
**Labels:** 42cc
**Cr
---
** [tickets:#7323] ForgeHg: upgrade mercurial dependency**
**Status:** open
**Milestone:** limbo
**Created:** Sat Apr 12, 2014 05:55 PM UTC by Dave Brondsema
**Last Updated:** Sat Apr 12, 2014 05:55 PM UTC
**Owner:** nobody
The mercurial revision that ForgeHg/setup.py (and requirements-sf
