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

Media/WebRTC/libwebrtc Update Process Transition Plan (view source)

667 bytes added , 22 July 2020

Added section on Migrating to GitHub

139

edits

@@ Line 16: / Line 16: @@
 ===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].
+==Migrating libwebrtc to GitHub==
+===Motivation===
+There are a number of factors that make storing our soft fork of libwebrtc in Git appealing.
+Our goal is to maintain as few, approaching zero, changes to the upstream version as possible. The upstream code is stored in a Git repository, so it makes it easier for us to upstream changes as we will no longer have to export patches. Likewise, it will make it easier to cherry pick patches from upstream.
+By only removing files via the vendoring script, we will be able to more easily roll our version forward. As it is today, we will first need to undo all of our local deletions before we begin the merge process.