Media/WebRTC/libwebrtc Update Process Transition Plan: Difference between revisions

Then it should be possible to collapse the path <code>media/webrtc/signaling/*</code> into <code>webrtc/*</code>. Which will once again require numerous path changes, and is tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=1654185 Bug 1654185].

nICEr and SIPCC can be moved into their own repositories, tracked here [https://bugzilla.mozilla.org/show_bug.cgi?id=1654194 Bug 1654194] and here [https://bugzilla.mozilla.org/show_bug.cgi?id=1654188 1654188]. Then they can be moved into <code>third_party</code>, tracked here [https://bugzilla.mozilla.org/show_bug.cgi?id=1654198 Bug 1654198] and here [https://bugzilla.mozilla.org/show_bug.cgi?id=1654189 Bug 1654189]. Doing all of this moving at once will cluster the Mercurial history changes together to avoid unwanted noise later.

===Subdirectory Build-ability===

Before the most recent WebRTC update it was possible to build the different sub directories of the <code>media</code> folder from <code>mach</code>. It would be extremely helpful to update process if we could get this back, as it would decouple building different sub components, such as <code>peerconnection</code> and <code>mediaconduit</code>. One could get a component building before moving onto the next. This is being tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=1654205 Bug 1654205].