The default bug view has changed. See this FAQ.

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

RESOLVED FIXED

Status

Release Engineering
Releases
P1
normal
RESOLVED FIXED
4 months ago
12 days ago

People

(Reporter: rail, Assigned: rail)

Tracking

(Blocks: 1 bug)

unspecified
Dependency tree / graph

Firefox Tracking Flags

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

Details

(Assignee)

Description

4 months ago
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).

Updated

4 months ago
Blocks: 1130266
Summary: Stop updating desktop Firefox 53.0 on XP/2003/Vista → Migrate desktop Firefox release on XP/2003/Vista to ESR 52
Blocks: 1315083
No longer blocks: 1130266
[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+.
status-firefox50: --- → wontfix
status-firefox51: --- → wontfix
status-firefox52: --- → wontfix
status-firefox53: --- → affected
tracking-firefox53: --- → ?
status-firefox52: wontfix → affected
tracking-firefox52: --- → ?
Tracking 52/53+ so that this work can be done.
tracking-firefox52: ? → +
tracking-firefox53: ? → +

Comment 3

2 months ago
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
status-firefox53: affected → ---
Flags: needinfo?(rail)
(Assignee)

Comment 5

2 months ago
(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
(Assignee)

Updated

a month ago
Priority: -- → P1
(Assignee)

Updated

17 days ago
Status: NEW → RESOLVED
Last Resolved: 17 days ago
Resolution: --- → FIXED
(Assignee)

Updated

13 days ago
status-firefox52: affected → fixed
status-firefox53: --- → fixed
You need to log in before you can comment on or make changes to this bug.