Bug 1579940 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

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

- en-GB needs to be included by activating the file manually en-US to show up in the URL implying that we need L10n (Peiying) to manually activate the file.

- id - this needs to be added to the list of locales so they will receive the hard coded template with Firefox Lite content

- There will be an additional hard coded template shown (w. English copy) to users geo-located in India. This issue in github is a dependency for that page - https://github.com/mozilla/bedrock/issues/7637  - We need to confirm if a locale needs to be identified for this or if en-US will suffice for this purpose.

- New copy and design is forthcoming and the strings will be final, extracted on or before 9/18/2019
Request is to have the product point to the /whatsnew page in the Firefox 70.0 release and show it (WNP). 

- en-GB needs to be included by activating the file manually en-US to show up in the URL implying that we need L10n (Peiying) to manually activate the file.

- id - this needs to be added to the list of locales so they will receive the hard coded template with Firefox Lite content

- There will be an additional hard coded template shown (w. English copy) to users geo-located in India. This issue in github is a dependency for that page - https://github.com/mozilla/bedrock/issues/7637  - We need to confirm if a locale needs to be identified for this or if en-US will suffice for this purpose.

- New copy and design is forthcoming and the strings will be final, extracted on or before 9/18/2019

- all users coming from <70.0 and receiving the 70.0 release should be show this page (if they are in the locales in which the content has been localized, the list that l10n will provide on Oct 11). 

- for locales w/o content, they should not be shown a page (does not default to en-US)

Back to Bug 1579940 Comment 0