Skip to content

Requesting an uplift to a release branch

Jump to bottom
lmarceau edited this page Oct 8, 2025 · 8 revisions

Context

Once the uplift is created towards the release branch with @Mergifyio backport release/vXXX.X, you need to request a review from @relman on the @mergify PR. They will decide if the uplift can land in the upcoming release.

Uplift request

Copy this form into your PR and answer the questions below. Here is an example of such request filled for a pull request.

  1. [User impact if declined]: In addition to the STR (steps to reproduce) reported in the bug if you can explain on a deeper level aspect of how an end user would be impacted with/without your change

  2. [Is this code covered by automated tests?] Yes/No/Unknown

  3. [Has the fix been verified in Nightly?] Was the fix verified in a nightly build, e.g. by the reporter or QA?

  4. [Needs manual test from QA?] Yes/No

    • [If yes, steps to reproduce] Either point to an existing comment listing STR or elaborate here directly.

  5. [List of other uplifts needed] If this patch depends on other changes that are not present on the target branch, list them here (and request approval in the other bugs as well)

  6. [Risk to taking this patch]: Low/Medium/High

  7. [Why is the change risky/not risky? (and alternatives if risky)]

    When saying something is "low", "medium", or "high" risk please justify

    E.g.: Low risk because its a one line CSS change impacting only settings page

    E.g.: Medium, given the code complexity and integration with other areas of code that might be impacted. Expect regressions in areas like...

    E.g.: Risky, given the complex nature the bake time we have have on central or other branches. High rate of fallouts/regression. Could be mitigated by more manual testing in areas or running some targeted test cases... If the issue could be worked around by disabling a certain feature, or with a different, less-risky, patch for uplift, mention this here.

  8. [String changes made/needed] Please answer this as "none" if no string changes were made. String changes need to be approved by a l10n driver since they impact the work of localization teams.

Clone this wiki locally