Show whatnsew page to ESR24 users when they're offered ESR 31.2.0



Release Engineering
3 years ago
2 years ago


(Reporter: nthomas, Assigned: nthomas)


Dependency tree / graph

Firefox Tracking Flags

(firefox-esr3133+ affected)



(1 attachment)



3 years ago
Spun out from bug 1009893. We had a whatsnew page shown after updates to Australis in Firefox 29, and for Sync in Firefox 30, and plan to for 31 as well. When ESR24 users update to 31 the request is to show a whatsnew again. Presumably this would be something like:
  24.0* -> 31.2.0   get
  31.0.*/31.1.*     no whatsnew

There's an interesting difference with the ESR audience. There will be large orgs that deploy new versions themselves, not using our updater. This will look like a paveover install to us, so we'd have to set a pref in-app to show a whatsnew page on the first start. We'd need some version detection too, so that it only happened when the previous version was < 31.0 (or 29.0). Or maybe we just leave that 'training' to the orgs themselves.

Some other part of the audience will be people getting updates from us, which this request would affect. It'd be interesting to know what proportion we're talking about.
status-firefox-esr24: --- → affected
tracking-firefox-esr24: --- → 31+
This actually needs to get tracked for ESR24 33+ (which will be the last ESR24 build and will ship alongside 31.2 with auto-updates to ESR31 offered -- setting ESR24 nom to ? until we have 33+ in the options there.
tracking-firefox-esr24: 31+ → ?
Blocks: 1056834
Tracking for ESR31 because we do not actually do any more builds of the ESR24, we will need this to be in the updates that are created for 24->31 - correct?
status-firefox-esr24: affected → ---
status-firefox-esr31: --- → affected
tracking-firefox-esr24: ? → ---
tracking-firefox-esr31: --- → 33+
Flags: needinfo?(rail)
Yeah. The bug blocks bug 1056834, where we will do this as a part of Firefox 31.2.0 ESR.
Flags: needinfo?(rail)
Assigning to Nick since he's on the hook for 31.2.0 ESR
Assignee: nobody → nthomas

Comment 5

3 years ago
Created attachment 8500362 [details] [diff] [review]
[tools] Add ESR17 & 24 versions, whatsnew page, slight logic fix

This will
* fix the openUrl bumping to put 31.2.0 in the url instead of 31.2.0esr, avoiding work for the website people
* set all snippets to open a whatsnew at the standard location, I'll have to remove that for 31.0 and 31.1.1 after the fact
* adds all the 17.0.x and 24.x.y releases, making sure to have past-update lines for the most recent 24.8.z
Attachment #8500362 - Flags: review?(mgervasini)
Attachment #8500362 - Flags: review?(mgervasini) → review+
Attachment #8500362 - Flags: checked-in+

Comment 6

3 years ago
Snippets are modified -

Comment 7

3 years ago
And redone for build3.

Comment 8

3 years ago
mgerva - fyi, we'll need to do this for 31.3.0 builds too.

Comment 9

3 years ago
We did do 31.3.0, and 31.4.0 is in bug 1121123.


3 years ago
Depends on: 1121209
Is there anything that need to do in this bug?

Comment 11

2 years ago
Thanks for the reminder to look at this again. RelMan OK'd not creating whatsnew for ESR24 via IRC on 20150224.
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.