Closed
Bug 1203188
Opened 9 years ago
Closed 9 years ago
Update merge day docs to include b2g branching
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rail, Assigned: rail)
Details
I killed the steps in https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FMerge_Duty%2FSteps&diff=1057806&oldid=1057658 There are also https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/Central_will_become_an_odd_numbered_Gecko_version https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/Central_will_become_an_even_numbered_Gecko_version
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → rail
Would the merge day wiki need to be updated to work with Taskcluster as well? Who is handling this part? Would Selena have to be pinged?
Flags: needinfo?(rail)
Assignee | ||
Comment 2•9 years ago
|
||
I believe it should just work for TC. https://github.com/taskcluster/mozilla-taskcluster/blob/master/src/config/default.yml#L94-L109 is what should be updated to get the tasks scheduled.
Flags: needinfo?(rail)
Assignee | ||
Comment 3•9 years ago
|
||
After talking to hwine the situation became clearer. This branching is not that different from 2.2r branching except the repo we will be cloning from.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•