Closed Bug 1455023 Opened 6 years ago Closed 6 years ago

Please reset releases/mozilla-esr60 and projects/jamun to the latest mozilla-beta

Categories

(Developer Services :: Mercurial: hg.mozilla.org, enhancement)

Product:
Developer Services
Component:
Mercurial: hg.mozilla.org
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jlorenzo, Assigned: sheehan)

References

Details

I haven't managed to push the latest mozila-beta to mozilla-esr60 because `hg push -r .` wants me to push mozilla-beta's relbranches. Those relbranches are about 20k changesets to push. We can't go past 7k because of bug 1415233. Therefore, cloning mozilla-central to mozilla-esr60 (bug 1438799) wasn't a good idea after all. 

Similarly, jamun has been outdated. If I want to push incrementally update it to the what's on beta, I have to push the last mergeday, which was more than 7k changesets. Thus, let's reset it too. 

Thank you very much!
The reset is in progress.
Assignee: nobody → sheehan
See Also: → 1455090
projects/jamun has been reset, will move on to esr60 shortly.
releases/esr60 is reset - I filed bug 1455160 to deal with the taskcluster side and :raduiman reconfigured the buildbot scheduler. Let me know if anything else is needed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Thank you very much Connor! I was able to update my copy of jamun and push onto it. I cloned esr60 locally too. Thank you for also checking bug 1455160 is needed. I wasn't sure of it.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.