715321 - [Firefox GA] Implement Firefox Release Notes Page

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Alex Keybl [:akeybl]]

design bug: 706400

1 page for desktop
1 page for mobile 

Live Date: 1/31

Comment 1

[Alex Keybl [:akeybl]]

A few changes to the implementation that I'd like to make before pushing the GA release notes

* 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)
* We'll need to pull the bug list for the new requested bug list in 697632 from the DB. I'll provide the DB, and it'll be a quick listing from the DB based upon the Firefox version

Comment 2

[Grace Jimenez :grace]

hi all, 

here is the final psd:
http://mozilla.tyflanagan.com/artwork/Firefox/FFx_GA_Desktop_Notes_BugFixes.zip

the design can be found here: bug 706400

Comment 3

[Alex Keybl [:akeybl]]

(In reply to Alex Keybl [:akeybl] from comment #1)
> A few changes to the implementation that I'd like to make before pushing the
> GA release notes

James and I discussed the changes in comment #1 last week, and he mentioned he'd have the time to look into it later this week.

James - let me know if you'd like me to split that work into another bug. The large majority of it isn't blocked on Steven's work.

Comment 4

[Grace Jimenez :grace]

hi steven and james,

I was wondering if you had a chance to look into this yet. 

The page needs to be live Tuesday, 31st of Jan. 
However, Alex still needs to update the content.


Thanks!

Comment 5

[Steven Garrity [:sgarrity]]

James, the images/css are in trunk (r100518) and I've made a pull request on GitHub (https://github.com/jlongster/relnotes/pull/2) for the changes to the template.

Comment 6

[James Long (:jlongster)]

Hey Steven,

The changes look good, with one problem. I think it broke the beta releasenotes:

http://www-dev.allizom.org/en-US/firefox/10.0/releasenotes/

Comment 7

[James Long (:jlongster)]

The last thing I need is an updated DB. The pages look good to me but it's hard to test what they will be like without the final DB.

Comment 8

[Grace Jimenez :grace]

hi alex, 

can you please update?

thanks!

Comment 9

[James Long (:jlongster)]

I've integrated the newest design changes that show "Unresolved on X" and "Resolved on Y". A good example of this is here:

http://www-dev.allizom.org/en-US/mobile/10.0beta/releasenotes/

Comment 10

[Alex Keybl [:akeybl]]

2 last things - 

* "Did you know that most of the content Firefox Support was written by volunteers?" -> Did you know that most of the content in Firefox Support was written by volunteers?
* Did https://bugzilla.mozilla.org/attachment.cgi?id=588550 ever get implemented? We'll want to link to a static page with a list of bugs that I'll paste in.

Comment 11

[James Long (:jlongster)]

(In reply to Alex Keybl [:akeybl] from comment #10)
> * Did https://bugzilla.mozilla.org/attachment.cgi?id=588550 ever get
> implemented? We'll want to link to a static page with a list of bugs that
> I'll paste in.

It never did. What format will you be pasting them in? What markup should the page have?

Comment 12

[Alex Keybl [:akeybl]]

(In reply to James Long (:jlongster) from comment #11)
> It never did. What format will you be pasting them in? What markup should
> the page have?

Do we need to loop Steven back in to get that page implemented? I can conform to whatever for pasting in the buglist - not an issue for me.

Comment 13

[Alex Keybl [:akeybl]]

Found another bug when generation the release notes (en-US/firefox/10.0/releasenotes/index.html) - 

            <a href="/en-US/mobile/10.0beta/releasenotes">Mobile</a>

should be 

            <a href="/en-US/mobile/10.0/releasenotes">Mobile</a>

Comment 14

[James Long (:jlongster)]

(In reply to Alex Keybl [:akeybl] from comment #12)
> (In reply to James Long (:jlongster) from comment #11)
> > It never did. What format will you be pasting them in? What markup should
> > the page have?
> 
> Do we need to loop Steven back in to get that page implemented? I can
> conform to whatever for pasting in the buglist - not an issue for me.

Naw, I just built it. How's this look? http://www-dev.allizom.org/en-US/firefox/9.0/releasenotes/buglist.html

Comment 15

[Alex Keybl [:akeybl]]

Attachment: Latest release notes DB (1/30)

Attaching the latest relnotes DB with updated "What's new" and "Known issues".

One additional change to the release template I'd still like make is to have

"If interested, please see the <a href="https://www.mozilla.org/en-US/firefox/{{ version }}/releasenotes/buglist.html">complete list of changes</a> in this release."

underneath

    {% if release_text %}{{ release_text }}{% endif %}
    {% if product_text %}{{ product_text }}{% endif %}

in order to support the upcoming bugslist page

Comment 16

[Alex Keybl [:akeybl]]

(In reply to James Long (:jlongster) from comment #14)
> (In reply to Alex Keybl [:akeybl] from comment #12)
> > (In reply to James Long (:jlongster) from comment #11)
> > > It never did. What format will you be pasting them in? What markup should
> > > the page have?
> > 
> > Do we need to loop Steven back in to get that page implemented? I can
> > conform to whatever for pasting in the buglist - not an issue for me.
> 
> Naw, I just built it. How's this look?
> http://www-dev.allizom.org/en-US/firefox/9.0/releasenotes/buglist.html

Looks good to me - let's comment out the "View bugs for:" and slider on the buglist for now - I plan to only post a single monolithic list with FF10.

Comment 17

[James Long (:jlongster)]

Removed slider on buglist page

Comment 18

[James Long (:jlongster)]

Ok, changes in comment 15 and comment 16 are done.

Comment 19

[James Long (:jlongster)]

The release notes

Comment 20

[raymond [:retornam] (inactive)]

The link to http://www-dev.allizom.org/en-US/firefox/10.0/releasenotes/buglist.html is a 404

Comment 21

[James Long (:jlongster)]

I think Alex just pushed that page.

Comment 22

[Ty Flanagan]

Hoping this is isolated to my browser, but I noticed the bugs & corresponding description are not aligned properly:  http://cl.ly/2L0Z2l3u351v1e2Z3L1x

Comment 23

[Alex Keybl [:akeybl]]

(In reply to Ty Flanagan from comment #22)
> Hoping this is isolated to my browser, but I noticed the bugs &
> corresponding description are not aligned properly: 
> http://cl.ly/2L0Z2l3u351v1e2Z3L1x

Yeah James and I were discussing. We're going to go with the old buglist for this release and include this in the next (and presumably last) round of changes over the next 6 weeks.

Comment 24

[Alex Keybl [:akeybl]]

Attachment: Patch to add bug #s to template.

Found another issue where bug numbers were not being outputted for known issues in the template, fixed in http://viewvc.svn.mozilla.org/vc?view=revision&revision=100771

Attached is the patch to fix the templates.

Comment 25

[James Long (:jlongster)]

pushed out in r100793. The htaccess switch to turn them on is not pushed out yet.

Comment 26

[James Long (:jlongster)]

this is flipped live on production r100798