122
edits
Media/WebRTC/libwebrtc Update Process/automation plan: Difference between revisions
Media/WebRTC/libwebrtc Update Process/automation plan (view source)
Revision as of 22:50, 25 February 2022
, 25 February 2022fix formatting errors on questions
(Add info on updatebot) |
(fix formatting errors on questions) |
||
| Line 191: | Line 191: | ||
I think we may need to do this to avoid large-scale breakage and | I think we may need to do this to avoid large-scale breakage and | ||
make it easier to fix issues. | make it easier to fix issues. | ||
* Do we want to manually advance the process as quickly as | * Do we want to manually advance the process as quickly as possible, and then modify our scripts to start taking advantage of update-bot? | ||
This allows a more finely tuned process to help us get caught up, | This allows a more finely tuned process to help us get caught up, | ||
but pushes out the integration with update-bot. | but pushes out the integration with update-bot. | ||
* How/when do we start integrating webrtc.org's unittests into our | * How/when do we start integrating webrtc.org's unittests into our try runs? | ||
This may need to happen in our tree (probably post-vendoring) because | This may need to happen in our tree (probably post-vendoring) because | ||
the process of getting the webrtc tree buildable is a long process | the process of getting the webrtc tree buildable is a long process | ||
requiring lots of network. | requiring lots of network. | ||
* Do we want to add our fixup-patch to the moz-libwebrtc branch and | * Do we want to add our fixup-patch to the moz-libwebrtc branch and move the branch forward in the official repo to make it more clear what was previously vendored? | ||