If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Firefox GA] Implement Firefox Release Notes Page

RESOLVED INCOMPLETE

Status

www.mozilla.org
General
RESOLVED INCOMPLETE
6 years ago
5 years ago

People

(Reporter: akeybl, Assigned: jlongster)

Tracking

unspecified
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
+++ This bug was initially created as a clone of Bug #715321 +++

Splitting out James' work (template work and page generation) from Steven's (implementing the new design)
(Reporter)

Updated

6 years ago
Assignee: nobody → jlong
(Assignee)

Comment 1

6 years ago
As far as I know, this is what I need to do:

* The resolved issue tag under Known Issues should link to the latest channel notes from the version of Firefox in which the issue is fixed, with a tag of "RESOLVED in vXY" (RESOLVED in v11)
* We should probably have run.py automatically run for all releases in the Releases table. Each time we post, I'll go over any weird diffs caused by regenerating all of the notes
* The templates need to change so that "Did you know that most of the contention Firefox Support was written by volunteers?" reads instead "Did you know that most of the content Firefox Support was written by volunteers?"
* Link for beta notes should have 10.0beta in them instead of 10.0b1 (sorry for the churn)

I've done this except for #3 (slight wording change). I need the updated templates now from Steven to proceed (and an updated db).

Update is here: https://github.com/jlongster/relnotes/commit/6df59dece98df3a6befadad25fa630a75e55cf31
(Assignee)

Updated

6 years ago
Target Milestone: --- → 1.4
(Assignee)

Comment 2

6 years ago
Alex,

I've finished everything I think. Can you get me an updated db soon? All I did was add a new record in the Releases tables for version 9 of Firefox (the current version). Also, still waiting on the buildouts of the GA release notes page.

I've regenerated the current release notes with the new generator. Please take a look at the following urls:

http://www-dev.allizom.org/en-US/firefox/9.0/releasenotes/ (this is blank because there are no issues attached to version 9 yet)
http://www-dev.allizom.org/en-US/firefox/10.0/releasenotes/
http://www-dev.allizom.org/en-US/firefox/11.0a2/auroranotes/
(Reporter)

Comment 3

6 years ago
Created attachment 592300 [details]
Link Within Unresolved -> Link Under Resolved

(In reply to James Long (:jlongster) from comment #2)
> http://www-dev.allizom.org/en-US/firefox/9.0/releasenotes/ (this is blank
> because there are no issues attached to version 9 yet)
> http://www-dev.allizom.org/en-US/firefox/10.0/releasenotes/
> http://www-dev.allizom.org/en-US/firefox/11.0a2/auroranotes/

These look great! The only comment I have at this point is that the latest designs call for issues resolved in later builds to be listed under the "Unresolved" tag (as opposed to within a "Resolved" tag).

I'll be putting together a final DB for release notes this weekend, building out pages from https://github.com/jlongster/relnotes/commit/6df59dece98df3a6befadad25fa630a75e55cf31.

Also sounds like the implemented design is ready in https://bugzilla.mozilla.org/show_bug.cgi?id=715321#c5. Hopefully it's a quick drop-in on Monday.
(Assignee)

Comment 4

6 years ago
I'm going to finish off this work in bug 715321
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Comment 5

6 years ago
Oh, Alex, just saw your comment 3. I will make that change.
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.