Closed Bug 1672277 Opened 11 months ago Closed 10 months ago

Setup WNP for users coming from <83.0 and receiving the 83.0 release

Categories

(Release Engineering :: Release Requests, task)

task
Not set
major

Tracking

(firefox83+ fixed, firefox84 fixed, firefox85 fixed)

RESOLVED FIXED
Tracking Status
firefox83 + fixed
firefox84 --- fixed
firefox85 --- fixed

People

(Reporter: tahn, Assigned: u504868)

References

()

Details

(Whiteboard: [releaseduty])

Attachments

(1 file)

Request is to have the product point to the /whatsnew page in the Firefox 83.0 release and show it (WNP).

  • All users coming from <83.0 and receiving the 83.0 release should be shown the WNP83.0 page.

  • Users in locales at 100% will be shown the content in the WNP 83.0 page (we'll assign that content to the WNP URL).

  • for locales w/o content, they will be shown an evergreen WNP (does not default to en-US)

  • github issue for this work is here

  • The QA test request and the corresponding request in Jira will be filed.

Just a couple clarifications:

id - has a hard coded template not reflected in Pontoon and will need to be added to the final list of locales,

:cocomo, we aim to have the release-specific content shown only to en-US/DE audiences, with all others falling back to evergreen. Do we use Pontoon for this or a hard-coded template?

which Peiying will provide in this bug on October 26th

I think that will come later; we won't have a final list of locales until ~10 days after string merge, so probably more like 11/5 or so.

Flags: needinfo?(pmo)

Let's update this template for future WNP:

(In reply to Justin Crawford [:hoosteeno] [:jcrawford] from comment #1)

Just a couple clarifications:

id - has a hard coded template not reflected in Pontoon and will need to be added to the final list of locales,
The special promotion was created by the Taipei team. We don't have an id specific WNP anymore. It's treated like the other locales. Let's remove it in the request template

:cocomo, we aim to have the release-specific content shown only to en-US/DE audiences, with all others falling back to evergreen. Do we use Pontoon for this or a hard-coded template?
id has completed the evergreen page(s) in Pontoon. Hard coded page means the content doesn't go through Pontoon.

which Peiying will provide in this bug on October 26th

I think that will come later; we won't have a final list of locales until ~10 days after string merge, so probably more like 11/5 or so.
I will mark my calendar to provide the updated locale list before then.

Flags: needinfo?(pmo)
No longer blocks: 1659399
No longer depends on: 1657017, 1660782, 1660783

Confirming locales:
en-US, en-GB, en-CA, en-IE
de-DE, de-CH, de-AT, de-BE

Question: there is a consideration on 11/5 for a go-no go on a global English recommendation in new tab. They're going to decide if this will impact ALL en locales or select ones. Is 11/5 too late to update this list?

With the exception of en-* and de, here is the locale list for the fallback page: https://github.com/mozmeao/www-l10n/blob/master/metadata/firefox/whatsnew/whatsnew-account.json.

@tahn, could you remove id requirement in the initial bug filing? This statement needs to be removed from the template whenever we file a bug for the next WNP. Thank you!!

Flags: needinfo?(tahn)
Flags: needinfo?(tahn)

(In reply to Peiying Mo [:CocoMo] from comment #5)

With the exception of en-* and de, here is the locale list for the fallback page: https://github.com/mozmeao/www-l10n/blob/master/metadata/firefox/whatsnew/whatsnew-account.json.

@tahn, could you remove id requirement in the initial bug filing? This statement needs to be removed from the template whenever we file a bug for the next WNP. Thank you!!

Removed the id requirement!

Blocks: 1676110
Assignee: nobody → jlorenzo
Status: NEW → ASSIGNED

(In reply to tahn from comment #3)

Confirming locales:
en-US, en-GB, en-CA, en-IE
de-DE, de-CH, de-AT, de-BE

Question: there is a consideration on 11/5 for a go-no go on a global English recommendation in new tab. They're going to decide if this will impact ALL en locales or select ones. Is 11/5 too late to update this list?

Tyler, the locale codes en-IE, de-DE, de-CH, de-AT and de-BE are not locale codes we ship Firefox versions for (https://searchfox.org/mozilla-beta/source/browser/locales/all-locale), the whatsnew page on mozilla.org would just redirect users with these locale codes to the de and en-US pages. Do you have more context for why these locale codes are needed for the whatsnew page? Thanks

Flags: needinfo?(tahn)

En-US, en-GB, en-CA and DE.

Flags: needinfo?(tahn)

WNP has been set and publicly available for 24 hours. I don't think there's anything else to do. Please reopen the bug if you disagree.

Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/78ec198ed4f2
update WNP locales list for 83 r=pascalc, a=release
You need to log in before you can comment on or make changes to this bug.