Closed Bug 1480557 Opened 6 years ago Closed 6 years ago

Upgrade Mercurial to 4.7 in build-puppet

Categories

(Release Engineering :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: sheehan, Unassigned)

References

Details

We would like to get Mercurial clients in CI and other automation running Mercurial 4.7. The puppet repo at https://github.com/mozilla-releng/build-puppet references Mercurial in quite a few places, including some very old versions of Mercurial such as version 1.4.3 here https://github.com/mozilla-releng/build-puppet/blob/68a3aef535dfa34dd0f4d0404c70c57a6693b2fd/modules/packages/manifests/mercurial.pp#L9. It is not clear to an outsider where the relevant Mercurial references in the repo live.

I would like to request that someone update Mercurial to version 4.7 in the relevant areas (or point me to these areas so I can make the upgrades) and provide commit hashes of the changes. We will then update the Mercurial client upgrade documentation at https://hg.mozilla.org/mozilla-unified/annotate/tip/taskcluster/docs/versioncontrol.rst so that an upgrade can be performed by someone outside of Release Engineering in the future. :)
Connor this is the only bug left for 4.7.  Is it still relevant?  My  understanding is that you and Greg are concentrating on 4.8
Flags: needinfo?(sheehan)
No, this is irrelevant now. I'll close as WFM. We'll be opening a similar bug for 4.8 in the near future though.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(sheehan)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.