Closed Bug 1003346 (merge-day-automation) Opened 11 years ago Closed 7 years ago

merge day automation

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1432655

People

(Reporter: mozilla, Unassigned)

References

Details

No description provided.
Depends on: 1003361
Alias: merge-day-automation
Depends on: 988613
Depends on: 918055
Depends on: 946019
Depends on: 962863
Depends on: 962869
Depends on: 1003634
Depends on: 1018521
Depends on: 1036573
Depends on: 1011794
Depends on: 1022907
I would have loved to see this bug go to zero open dependencies. The bulk of the work left is in vcs-sync; once gecko.git and l10n are cut over to new vcs-sync that should eliminate a lot of duplicate work and complexity around merge day. Pete's got that. (For git->hg, I'm hoping we stop needing gaia in hg once mulet replaces b2g desktop, which would remove that bit of complexity.) Outside of that, there are some small helper scripts that could make this nicer, and moving the b2g balrog channels out of tree would make that portion lower-touch as well. But I think that, despite the hiccups we hit this past merge day, things are comparable to pre-shipit release automation levels. It would be awesome to see shipit-style button-push merge days, especially if/when creating a new gecko branch is simplified.
Assignee: escapewindow+mozbugs → nobody
No longer depends on: 962869
No longer depends on: 962863
No longer depends on: 946019
anything else to do here?
Flags: needinfo?(rail)
bug 1011794 is the only blocker. It would be great to revisit that bug before closing this one. Or close this one and let bug 1011794 live alone.
Flags: needinfo?(rail)
Component: General Automation → General
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.