Media/WebRTC/libwebrtc Update Process/automation plan: Difference between revisions

adding notes on how to run the update
(adding notes on how to run the update)
(adding notes on how to run the update)
Line 232: Line 232:


* Operational notes
* Operational notes
- Running prep-repo.sh with a fresh github clone of moz-libwebrtc will likely display instructions on how to add recent moz-central changes made in third_party/libwebrtc to the top of the patch stack in github.  This is expected and necessary for successfully vendoring changes into third_party/libwebrtc.
- Running <code>prep-repo.sh</code> with a fresh github clone of moz-libwebrtc will likely display instructions on how to add recent moz-central changes made in <code>third_party/libwebrtc</code> to the top of the patch stack in github.  This is expected and necessary for successfully vendoring changes into <code>third_party/libwebrtc</code>.
 
- two main types of errors will cause <code>loop-ff.sh</code> to exit; the first is a rebase conflict, the second is a build error due to api changes in upstream code.
119

edits