Closed
Bug 1569741
(hg51)
Opened 7 years ago
Closed 4 years ago
[meta] Mercurial 5.1 upgrade and compatibility
Categories
(Developer Services :: Mercurial: hg.mozilla.org, task)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sheehan, Unassigned)
References
Details
(Keywords: leave-open, meta)
Attachments
(1 file)
Tracker bug for Mercurial 5.1 upgrades.
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/9efa8e908c25
hgext: mark client-side extensions as compatible with Mercurial 5.1
|
Reporter | |
Comment 2•6 years ago
|
||
No code changes required for passing tests here. This includes running
the tests using Mercurial 5.1 in the Docker image virtualenvs.
The only change in tests is the removal of extension setup timings in
blackbox log. This feature is moved behind a debug flag in 5.1+ (which
is probably more correct behaviour). These lines will be removed when
we run the actual upgrade on the server.
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/e73e374878f3
hgext: mark extensions as compatible with Mercurial 5.1 r=glob
|
|
Reporter | |
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•