The Firefox Android code is on GitHub. The Android team uses Bugzilla
for bugs and GitHub for code reviews and release branches. They
currently request uplifts in Bugzilla.
What process should Android engineers use to request uplifts if they're
not using Phabricator or Lando? FWIW, this will be a temporary problem
because we're merging the Firefox Android code from GitHub to
mozilla-central. Then they will be using Phabricator and Lando. This has
been a long project that I think will wrap up in Q1.
chris
On 10/27/2023 8:35 AM, Connor Sheehan wrote:
Hello Firefox developers,
tl;dr: Uplift requests are moving from Bugzilla to Lando/Phabricator.
Please create uplifts with `moz-phab uplift` or Lando and submit the
uplift request form on Phabricator. The process is outlined here:
https://wiki.mozilla.org/index.php?title=Release_Management/Requesting_an_Uplift
<https://wiki.mozilla.org/index.php?title=Release_Management/Requesting_an_Uplift>
Here is an example of a completed request:
https://phabricator.services.mozilla.com/D176307
<https://phabricator.services.mozilla.com/D176307>
---
We are making some changes to the Firefox uplift process, tracked in
https://bugzilla.mozilla.org/show_bug.cgi?id=uplift-automation
<https://bugzilla.mozilla.org/show_bug.cgi?id=uplift-automation>. For
anyone who hasn't submitted an uplift before, uplifts are requests
made by Firefox developers to Release managers, requesting a patch or
set of patches be pushed directly to our release repositories. This
bypasses the usual 8 to 12 week release cycle and is useful for
security patches, infrastructure patches and many other use cases.
We are moving the process of requesting and landing uplifts from
Bugzilla to Phabricator and Lando. You can now submit patches to
Phabricator for uplift using Lando (which does not require a local
checkout with the patch applied), or by using the `moz-phab uplift`
command. The uplift request questionnaire will be submitted on
Phabricator, using the same menu as "Accept Revision" and other review
actions. Lando will enforce a review from the `release-managers`
review group and enforce the uplift request questionnaire is submitted
on at least one patch in the stack. If patches fail to land, it is now
the developer's responsibility to resolve merging issues and re-land
patches.
As the changes made by each uplift request are tracked in new
Phabricator revisions, the normal Phabricator processes and automation
are available. For example, if a patch requires significant changes
to cleanly apply to the target repository, you'll have the option to
ask for code review prior to landing.
This new process will reduce the overhead time for handling uplift
requests placed on the Release management team and avoiding the need
to run local VCS operations. It will also decrease the attack surface
by revoking some special push privileges. We also expect this change
to enable faster requesting and landing of uplift requests, as the
uplift process is more closely aligned with the regular process for
submitting and landing patches.
Thanks to the Release Management team and all the engineers who took
part in the pilot.
Cheers,
Connor
--
You received this message because you are subscribed to the Google
Groups "[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bfa5c189-40f0-429b-ad50-72b5b9990f37n%40mozilla.org
<https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bfa5c189-40f0-429b-ad50-72b5b9990f37n%40mozilla.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/71aba477-9b7d-41ac-a597-c95ed7af4d55%40mozilla.com.
