The same Uplift request form appears on phabricator regardless of whether the target repo is beta/release or ESR. However, the ESR form should be different than that of beta.
From Bugzilla the forms look like this:
ESR Uplift Approval Request
If this is not a sec:{high,crit} bug, please state case for ESR consideration:
User impact if declined:
Fix Landed on Version:
Risk to taking this patch:
Why is the change risky/not risky? (and alternatives if risky):
Beta/Release Uplift Approval Request
User impact if declined
Is this code covered by automated tests?
Has the fix been verified in Nightly?
Needs manual test from QE?
If yes, steps to reproduce
List of other uplifts needed
Risk to taking this patch
Why is the change risky/not risky?
(and alternatives if risky)
String changes made/needed
Is Android affected?
If there is a limitation on this, please let me know, we can probably combine them for Phab.
Bug 1882501 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The same Uplift request form appears on phabricator regardless of whether the target repo is beta/release or ESR. However, the ESR form should be different than that of beta.
From Bugzilla the forms look like this:
ESR Uplift Approval Request
If this is not a sec:{high,crit} bug, please state case for ESR consideration:
User impact if declined:
Fix Landed on Version:
Risk to taking this patch:
Why is the change risky/not risky? (and alternatives if risky):
Beta/Release Uplift Approval Request
User impact if declined
Is this code covered by automated tests?
Has the fix been verified in Nightly?
Needs manual test from QE?
If yes, steps to reproduce
List of other uplifts needed
Risk to taking this patch
Why is the change risky/not risky? (and alternatives if risky)
String changes made/needed
Is Android affected?
If there is a limitation on this, please let me know, we can probably combine them for Phab.