ReleaseEngineering/Merge Duty: Difference between revisions

Jump to navigation Jump to search
Line 25: Line 25:
* {{bug|1017923}} Tracking bug for 21-jul-2014 migration work
* {{bug|1017923}} Tracking bug for 21-jul-2014 migration work


Mergeduty should start looking at patches/owners the week before.
Best practice: the patches are based on gecko_version so they get uplifted automatically.
NOTE: the tracking bugs themselves should NOT have patches in them.  Dependent bugs should be filed for each thing that needs to be uplifted, and assigned to someone with the context to do it properly.  Best practice: the patches are based on gecko_version so they get uplifted automatically.


= Future Merge Duty Bugs =
= Future Merge Duty Bugs =


Move these under tracking bugs once they are created:
Move these under tracking bugs once they are created:
Confirmed users
4,971

edits

Navigation menu