939984 - Input every release and notes into nucleus.mozilla.org

Status: RESOLVED WONTFIX

(Websites :: Nucleus, defect)

Description

[Justin Crawford [:hoosteeno] [:jcrawford]]

When rolling out the new release notes, we'll publish them all to a URL like /b/en-US/firefox/17.0.5/releasenotes/. That way we can use a URL like /en-US/firefox/17.0.5/releasenotes/ to compare the two. We need to do that for all notes, to make sure they look OK.

* If they look OK we can put in specific apache rule to redirect that note
* If they don't look OK we should file a bug blocking this one

Comment 1

[Justin Crawford [:hoosteeno] [:jcrawford]]

One more thing:

* Once we've done this for all notes, we can create a blanket rule for release notes. Then we can close this bug.

Comment 2

[Justin Crawford [:hoosteeno] [:jcrawford]]

Lukas will be inputting this data and tracking it in a Google spreadsheet that we'll use to file additional bugs for groups of releases that are ready for the redirection mentioned in comment 0.

Comment 3

[Lukas Blakk [:lsblakk] use ?needinfo]

Handing this over to Sylvestre, I will provide him with the spreadsheet and we will ensure all the dev-allizom notes for each release match current SVN served notes.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

So, to sum up, we decided not to go in this direction. It requires way too much work.

Working on 10.0 & 10.0 beta (only for Desktop) took about 1 hour and half.

I found various issues:
* mismatch in the text (ex: "See bug" missing)
* too many items in bedrock (some of them are listed as fixed in 10.0 while the official website says ESR 10.0.7 or 11.0)
* no category selected
* wrong category
* missing items in bedrock
* wrong declaration in nucleus (ie usage of "Fixed in release:" but not marked as "Is known issue")

Instead, we decided to implement bug 1041712