Media/WebRTC/libwebrtc Update Process: Difference between revisions

add instructions for updating the example config file
(fix typo)
(add instructions for updating the example config file)
Line 39: Line 39:
- Typically, immediately after the code-freeze has lifted, a request is made for the sheriffs to merge elm to mozilla-central.  This done via email, recently to Sebastian Hengst.
- Typically, immediately after the code-freeze has lifted, a request is made for the sheriffs to merge elm to mozilla-central.  This done via email, recently to Sebastian Hengst.


=== Updating moz-libwebrtc ===
=== Post-merge Steps ===
- After the merge from elm to mozilla-central is complete, the moz-libwebrtc github repo should be updated with the new branch of the commit stack for the new release.  There is script that will make the proper branch name and do the push:
- After the merge from elm to mozilla-central is complete, the moz-libwebrtc github repo should be updated with the new branch of the commit stack for the new release.  There is script that will make the proper branch name and do the push:
  bash dom/media/webrtc/third_party_build/push_official_branch.sh
  bash dom/media/webrtc/third_party_build/push_official_branch.sh
- 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


=== Operational notes ===
=== Operational notes ===
119

edits