+++ This bug was initially created as a clone of Bug #1337066 +++ ESR60 will be the first ESR entirely built on Taskcluster. In order to test out the whole process and (staging) updates on this branch, we would require the ESR60 branch earlier than usual. Could you please clone mozilla-central to releases/mozilla-esr60? We will need it in the middle of next week. In order to prevent divergence from the real train, we plan to re-clone the repo later in the beta cycle. Does that sound feasible? Thanks in advance!

(In reply to Johan Lorenzo [:jlorenzo] from comment #0) > +++ This bug was initially created as a clone of Bug #1337066 +++ > > ESR60 will be the first ESR entirely built on Taskcluster. In order to test > out the whole process and (staging) updates on this branch, we would require > the ESR60 branch earlier than usual. Exciting! > Could you please clone mozilla-central to releases/mozilla-esr60? We will > need it in the middle of next week. Will go kick this off now. > In order to prevent divergence from the real train, we plan to re-clone the > repo later in the beta cycle. Does that sound feasible? I don't *think* that'll cause any problems.

https://hg.mozilla.org/hgcustom/version-control-tools/rev/1a78578cb10cd701dd534504196c22c2796637f2 hgwsgi: add mozilla-esr60 (bug 1438799) r?sheehan

Pushed by klibby@mozilla.com: https://hg.mozilla.org/hgcustom/version-control-tools/rev/1a78578cb10c hgwsgi: add mozilla-esr60 r?sheehan

huh, that push didn't do what I wanted it to do, but it's a simple enough change that I'm not going to fret over it. will need to do a deploy to get that hgwsgi change onto production once the clone of m-c is complete

And looks like gps did a deploy last night, so this is available: https://hg.mozilla.org/releases/mozilla-esr60/

For reference, this wasn't a good idea after all. We needed to reset mozilla-esr60 in bug 1455023.