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

RESOLVED FIXED

Status

enhancement
--
major
RESOLVED FIXED
3 months ago
Last month

People

(Reporter: erenaud, Assigned: sfraser)

Tracking

unspecified
Dependency tree / graph

Firefox Tracking Flags

(firefox67+ fixed, firefox68 fixed)

Details

(Whiteboard: [releaseduty], )

Attachments

(2 attachments)

Reporter

Description

3 months ago

Request is to have the product point to the /whatsnew page in the Firefox 67.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 implying that we need L10n (Peiying) to manually activate the file.

  • TBD on content for the page, but new copy and design is indicated.

  • The Accounts team is onboard with the required schedule milestones

Schedule:
Deadline for final copy - 4/5
Deadline for final design - 4/16
Coded page on demo for stakeholder QA review - 4/30
RC week - 5/6
WNP 67 page go live - on or before - 5/6
Release date - 5/14

Reporter

Updated

3 months ago
Summary: Setup WNP for users coming from <66.0 and receiving the 66.0 release → Setup WNP for users coming from <67.0 and receiving the 67.0 release

(In reply to Eric Renaud [:erenaud] from comment #0)

Deadline for final copy - 4/5

Was the final copy sent to the l10n pipeline?

Flags: needinfo?(erenaud)

(In reply to Pascal Chevrel:pascalc from comment #1)

Was the final copy sent to the l10n pipeline?

Final copy wasn't delivered until midday on April 8, working on getting strings coded and extracted now for exposure to l10n ASAP.

Flags: needinfo?(erenaud)

Comment 3

2 months ago

Pardon me that I didn't notice this ticket earlier.
We just decided the current zh-TW whatsnew page template can be removed. (But we'll keep the Indonesian template)
I just filed a ticket for that here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1545705

Comment hidden (obsolete)

Apparently I can't tag or edit a comment (filed bug 1548758 for that).

Better list for releng

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

@thomas
Not sure who's in charge on RelEng, given jlund is out and this bug is unassigned. Maybe Tom?

:sfraser is on releaseduty for the 67 cycle (see here).

Flags: needinfo?(sfraser)
Assignee

Updated

2 months ago
Assignee: nobody → sfraser
Flags: needinfo?(sfraser)

Comment 8

2 months ago
Pushed by sfraser@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1002276e26e2
add WNP list for 67.0 r=flod a=release

Comment 11

2 months ago
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/6ba447d9eece
Revert changes to beta locales for 68.0.

Comment 12

2 months ago
bugherder
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED

Simon, flod. This was a bug for the 67 release, it is marked as fixed but 67 is still marked as affected and if I look at https://searchfox.org/mozilla-beta/source/browser/config/whats_new_page.yml it doesn't seem to match the list of locales I see in comment #5.

Coud you confirm that what we have on the beta branch is what we want for our 67 release? Thanks

Flags: needinfo?(sfraser)
Flags: needinfo?(francesco.lodolo)

+1 from me, looks like searchfox is out of date.

Flags: needinfo?(sfraser)

Thanks, setting 67 as fixed then :)

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