Closed Bug 1318922 Opened 8 years ago Closed 7 years ago

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

Categories

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

defect

Tracking

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

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

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.0 to the beta audience (RC1).
Blocks: xp-eol
Summary: Stop updating desktop Firefox 53.0 on XP/2003/Vista → Migrate desktop Firefox release on XP/2003/Vista to ESR 52
No longer blocks: xp-eol
[Tracking Requested - why for this release]:

Firefox 52 will be the last Release version to support XP/Vista, so we will need to migrate XP/Vista Release users to ESR 52 and stop sending Release updates for 53+.
Tracking 52/53+ so that this work can be done.
Does this mean we'll be generating a partial MAR for a 51 to 52 ESR migration?

Will someone be able to manually do this by changing the update channel on 51 from "release" to "esr"?
(In reply to Mike Kaply [:mkaply] from comment #3)
> Does this mean we'll be generating a partial MAR for a 51 to 52 ESR
> migration?
> 
> Will someone be able to manually do this by changing the update channel on
> 51 from "release" to "esr"?

We plan to update XP/Vista users running Release 51 directly to 52 ESR. If an XP/Vista user somehow manages to install Release 52, we will also update them to 52 ESR.

Rail, will the update from 51 to ESR 52 be a full or partial MAR?
Assignee: nobody → rail
Flags: needinfo?(rail)
(In reply to Mike Kaply [:mkaply] from comment #3)
> Does this mean we'll be generating a partial MAR for a 51 to 52 ESR
> migration?

The plan is to use complete MARs to avoid extra work for Releng and QA around the next busy merge cycle. 

> Will someone be able to manually do this by changing the update channel on
> 51 from "release" to "esr"?

Yes.

1) change defaults/pref/channel-prefs.js to use "esr"
2) change update-settings.ini to accept "firefox-mozilla-esr" MAR files.

The channel switching MAR will do the same thing.
Flags: needinfo?(rail)
Depends on: 1334535
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.