139
edits
Media/WebRTC/libwebrtc Update Process/automation plan: Difference between revisions
Media/WebRTC/libwebrtc Update Process/automation plan (view source)
Revision as of 01:23, 19 October 2022
, 19 October 2022Adding motivation
(Adding links for third_party relocation notes) |
(Adding motivation) |
||
| Line 260: | Line 260: | ||
== Moving third_party/libwebrtc/third_party/* to third_party/* == | == Moving third_party/libwebrtc/third_party/* to third_party/* == | ||
=== Motivation === | === Motivation === | ||
(lib)webrtc and Firefox share a number of dependencies. Both projects expect that their dependencies will live under a `third_party` in their respective project roots. libwebrtc is a dependency of Firefox, presenting an organizational problem. Additionally there are libraries that are expected to exist in the deployment environments. This can pose a problem where Firefox supports systems with older versions of those libraries than libwebrtc does. This cluster of issues runs counter to a number of our WebRTC team Q4 goals. | |||
* Reduce the number of libwebrtc patches, with an emphasis on build patches | |||
* Reduce the merge process complexity | |||
* Reduce our response time to security issues | |||
* Uplifting patches | |||
Additionally, resolving these issues would assist with broader product goals. | |||
* Improve performance | |||
* Reduce build time | |||
=== Approach === | === Approach === | ||
=== Notes === | === Notes === | ||