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

Jump to navigation Jump to search
Added link to user repo docs
(Removing misstatement)
(Added link to user repo docs)
Line 28: Line 28:
The upstream tracking repository needs to be created in GitHub, which is tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=1654435 Bug 1654435]. This keeps the work in the native VCS, in a visible place with a review process.
The upstream tracking repository needs to be created in GitHub, which is tracked by [https://bugzilla.mozilla.org/show_bug.cgi?id=1654435 Bug 1654435]. This keeps the work in the native VCS, in a visible place with a review process.
====Creating A User Repository To Hold The Merge Work====
====Creating A User Repository To Hold The Merge Work====
A Mozilla user repository has been created [https://hg.mozilla.org/users/na-g_nostrum.com/libwebrtc-merge-2H2020 here]. All of the revisions related to modifying Gecko during the merge will be kept here after being reviewed.
A Mozilla user repository has been created [https://hg.mozilla.org/users/na-g_nostrum.com/libwebrtc-merge-2H2020 here]. All of the revisions related to modifying Gecko during the merge will be kept here after being reviewed. There are instructions for making the repo '''publishing''' and for enabling support for '''obsolescence''' [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmo/managing-repos.html#editing-a-user-repository here]


====Generating GN files and updating the build====
====Generating GN files and updating the build====
139

edits

Navigation menu