Closed Bug 1318921 Opened 8 years ago Closed 8 years ago

Migrate desktop Firefox Beta 52 on XP/2003/Vista to ESR 52

Categories

(Release Engineering :: Release Requests, defect, P1)

Product:
Release Engineering
Component:
Release Requests
Type:
defect

Tracking

(firefox50 wontfix, firefox51 wontfix, firefox52+ fixed, firefox53+ unaffected)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox50 --- wontfix
firefox51 --- wontfix
firefox52 + fixed
firefox53 + unaffected

People

(Reporter: rail, Assigned: rail)

References

Details

See https://bugzilla.mozilla.org/show_bug.cgi?id=1317780#c11 for the details of the filter we need to set up. This rule should be set up before we publish updates to 53.0b1.
Blocks: xp-eol
Summary: Stop updating desktop Firefox Beta 53 on XP/2003/Vista → Migrate desktop Firefox Beta 53 on XP/2003/Vista to ESR 52
No longer blocks: xp-eol
[Tracking Requested - why for this release]: Beta 52 will be the last Beta version to support XP/Vista, so we will need to migrate XP/Vista Beta users to ESR 52 and stop sending Beta updates for 53+.
status-firefox50: --- → wontfix
status-firefox51: --- → wontfix
status-firefox52: --- → wontfix
status-firefox53: --- → affected
tracking-firefox53: --- → ?
Tracking 52/53+ for the reason in Comment 1.
tracking-firefox52: ? → +
tracking-firefox53: ? → +
Summary: Migrate desktop Firefox Beta 53 on XP/2003/Vista to ESR 52 → Migrate desktop Firefox Beta 52 on XP/2003/Vista to ESR 52
Rail, is this still in progress? I notice no one is assigned.
Flags: needinfo?(rail)
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #3) > Rail, is this still in progress? I notice no one is assigned. Assigning to Rail. He will switch Beta 52 users running XP/Vista to ESR 52 once the first ESR 52 builds exist (and after QA verifies the ESR channel switch works).
Assignee: nobody → rail
status-firefox53: affected → unaffected
Flags: needinfo?(rail)
Depends on: 1334535
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.