123
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
Jump to navigation
Jump to search
Media/WebRTC/libwebrtc Update Process (view source)
Revision as of 20:53, 20 February 2023
, 20 February 2023move resetting elm to the post-merge section
(add instructions for updating the example config file) |
(move resetting elm to the post-merge section) |
||
| Line 4: | Line 4: | ||
=== Prerequisites === | === Prerequisites === | ||
- Create a new bug for the fast-forward update. It should depend on the previous fast-forward bug. [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example. | - Create a new bug for the fast-forward update. It should depend on the previous fast-forward bug. [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example. | ||
- Builds are done after vendoring in each commit. Having a <code>.mozconfig</code> file that enables cache (either sccache or ccache) will improve the performance of the scripts. | - Builds are done after vendoring in each commit. Having a <code>.mozconfig</code> file that enables cache (either sccache or ccache) will improve the performance of the scripts. | ||
| Line 45: | Line 43: | ||
- Update the example config file for the next fast-forward operation. This should be done in a separate bug, but if it has not been done prior, can be done at the beginning of the fast-forward operation as the first commit on elm. | - Update the example config file for the next fast-forward operation. This should be done in a separate bug, but if it has not been done prior, can be done at the beginning of the fast-forward operation as the first commit on elm. | ||
bash dom/media/webrtc/third_party_build/update_example_config.sh | bash dom/media/webrtc/third_party_build/update_example_config.sh | ||
- Follow the [[Media/WebRTC/libwebrtc_Update_Process#Resetting_Elm|Resetting_Elm]] steps below. | |||
=== Operational notes === | === Operational notes === | ||