Open Bug 1562621 Opened 6 years ago Updated 5 months ago

Reverting changes on beta/release/esr should not reopen revisions

Categories

(Conduit :: Phabricator, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: Gijs, Unassigned)

References

Details

(Keywords: conduit-triaged)

https://phabricator.services.mozilla.com/D24445 and https://phabricator.services.mozilla.com/D23147 were reopened when they were backed out on release/esr68 in bug 1557256. This shouldn't have happened because the changes are still there on central/nightly.

What's happening is we have two separate commits both referring back to the same Phabricator revision (via the Differential Revision line in the commit description). Phabricator cannot tell the difference between actions performed on different "branches" with how Mozilla's repositories and uplifts work.

The longer term solution for this, which has been under discussion for some time with Release Management, is to require separate revisions for each of the "branches". Part of this work involves automation to reduce the overhead of creating uplift revisions.

For now this issue can be avoided if the commit description is amended during the uplift process to remove the Differential Revision line.

We'll do some investigation here to determine how viable that work around is.

Flags: needinfo?(smacleod)
Flags: needinfo?(smacleod)
Flags: needinfo?(glob)

The current goal is to make uplift requests an explicit moz-phab action, which will create a new phabricator revision for tracking the uplift on each branch.

Flags: needinfo?(glob)
Keywords: conduit-triaged
Priority: -- → P3
See Also: → 1737838
See Also: 1562275
You need to log in before you can comment on or make changes to this bug.