Update WNP and release docs for Springfield (fixes #1)#11
Update WNP and release docs for Springfield (fixes #1)#11maureenlholland wants to merge 1 commit intomainfrom
Conversation
maureenlholland
changed the title
|
|
||
| | Whatsnew URL: <https://www.mozilla.org/en-US/firefox/99.0a1/whatsnew/> | ||
| | Template path: <https://github.com/mozilla/bedrock/blob/main/bedrock/firefox/templates/firefox/nightly/whatsnew.html> | ||
| Whatsnew URL: <https://www.firefox.com/en-US/whatsnew/140.0a1> |
There was a problem hiding this comment.
I think we have plans to change the Nightly & Dev WNP urls too, but this is where they currently live on FXC
There was a problem hiding this comment.
However are the FXC endpoints being used, at all? I still get in-product links to WMO, and there are no redirects from WMO for these other channels.
| | Whatsnew URL: <https://www.mozilla.org/en-US/firefox/99.0/whatsnew/> | ||
| | Template path: <https://github.com/mozilla/bedrock/tree/main/bedrock/firefox/templates/firefox/whatsnew> | ||
| Whatsnew URL: <https://www.firefox.com/en-US/whatsnew/145> | ||
|
|
||
| - Template path: <https://github.com/mozmeao/springfield/blob/main/springfield/cms/templates/cms/whats_new_page.html> | ||
|
|
||
| !!! note | ||
| Before moving to CMS-powered whatsnew pages on Springfield with v145, Bedrock whatsnew URLs followed a different pattern: <https://www.mozilla.org/en-US/firefox/99.0/whatsnew/> |
There was a problem hiding this comment.
I think these are kinda still valid both. (With some of the extra tribal knowledge, like what versions, locales, and the major version fixup done along the way deliberately?) ~ The CMS-powered pages are only selectively redirected, but the actual inproduct links point everyone to WMO by default, so locales and versions matched are not served from evergreen FXC as https://www.firefox.com/it/whatsnew/123.4 — but from evergreen WMO still https://www.mozilla.org/it/firefox/123.4/whatsnew/ … correct?
maureenlholland
added
the
do not merge
|
DO NOT MERGE until we know when product will start directing WNP traffic directly to Springfield I don't really want to do an interim WNP update (unless we know it's going to be a long time before we remove the redirect behaviour). This is meant to be preparation for Springfield-based WNPs |
|
@maureenlholland The upsteam work is finished if you want to revisit this. The docs have changed a lot since then though so there may be a fair bit of work to resolve the conflicts. |
3 participants
No description provided.