Media/WebRTC/libwebrtc Update Process: Difference between revisions

tweak formatting
(put elm reset steps inline with prereqs)
(tweak formatting)
Line 5: Line 5:
* Create a new bug for the fast-forward update.  It should depend on the previous fast-forward bug.  [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example.
* Create a new bug for the fast-forward update.  It should depend on the previous fast-forward bug.  [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example.
* Before each new merge cycle elm needs to be reset to Central.
* Before each new merge cycle elm needs to be reset to Central.
# Ensure you have filed a bug for the next merge cycle, and further ensure that the next merge cycle bug has the previous merge cycle bug as a dependency.
*# Ensure you have filed a bug for the next merge cycle, and further ensure that the next merge cycle bug has the previous merge cycle bug as a dependency.
# File a bug as a clone of [https://bugzilla.mozilla.org/show_bug.cgi?id=1822294 Bug 1822294] and add your new bug as dependency to the next merge cycle bug.
*# File a bug as a clone of [https://bugzilla.mozilla.org/show_bug.cgi?id=1822294 Bug 1822294] and add your new bug as dependency to the next merge cycle bug.
# Wait for the repo admins to reset the repository.
*# Wait for the repo admins to reset the repository.
# Celebrate
*# Celebrate
* Builds are done after vendoring in each commit.  A minimal, default .mozconfig is provided during the prep_repo step below.
* Builds are done after vendoring in each commit.  A minimal, default .mozconfig is provided during the prep_repo step below.
* Starting with a fresh clone of elm is recommended for each new chromium milestone.
* Starting with a fresh clone of elm is recommended for each new chromium milestone.
119

edits