Closed Bug 1523699 Opened 4 years ago Closed 4 years ago

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


(Release Engineering :: Release Requests, enhancement)

Not set


(firefox66 fixed, firefox67 fixed)

Tracking Status
firefox66 --- fixed
firefox67 --- fixed


(Reporter: erenaud, Unassigned)




(Whiteboard: [releaseduty])

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

  • We still need to include id and zh-TW independently, because they have their own template.

  • en-GB needs to be included by activating the file manually en-US to show up in the URL, you need Peiying to manually activate the file.

  • TBD on content for the page, but we are looking at re-use of the WNP 64 content

See Also: → 1518236
Whiteboard: [releaseduty]

Final strings are in this PR - - they have been extracted for localization

Complete locales (38):
be, cak, cs, cy, da, de, dsb, en-CA, en-GB, en-US, es-AR, es-CL, es-ES, fr, fy-NL, gu-IN, hsb, hu, ia, id, it, ka, nl, nn-NO, pl, pt-BR, pt-PT, rm, ro, ru, sk, sl, sq, sv-SE, tr, vi, zh-CN, zh-TW

List for RelEng:

          - be
          - cak
          - cs
          - cy
          - da
          - de
          - dsb
          - en-CA
          - en-GB
          - en-US
          - es-AR
          - es-CL
          - es-ES
          - fr
          - fy-NL
          - gu-IN
          - hsb
          - hu
          - ia
          - id
          - it
          - ka
          - nl
          - nn-NO
          - pl
          - pt-BR
          - pt-PT
          - rm
          - ro
          - ru
          - sk
          - sl
          - sq
          - sv-SE
          - tr
          - vi
          - zh-CN
          - zh-TW

(In reply to Pulsebot from comment #3)

Pushed by
add WNP list for 66.0 r=flod a=release

Grafted to beta too:
It'll merge to release naturall on Monday during mergeduty.
Will let Sheriffs ttake it to central and close the bug in the following hours.

Closed: 4 years ago
Resolution: --- → FIXED

FYI that the page is live now, 3/12 -

You need to log in before you can comment on or make changes to this bug.