- **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 not show the 'release' branch on commit `677c00` like 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)
* The branch list is not in the same order.  Perhaps this is just indeterminate 
both before and now?



---

** [tickets:#7323] ForgeHg: upgrade mercurial dependency**

**Status:** in-progress
**Milestone:** limbo
**Labels:** 42cc 
**Created:** Sat Apr 12, 2014 05:55 PM UTC by Dave Brondsema
**Last Updated:** Tue May 13, 2014 06:49 PM UTC
**Owner:** nobody

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.


---

Sent from sourceforge.net because [email protected] is subscribed to 
https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.

Reply via email to