350548 - create content for Firefox 2 Beta 2 release notes, start page, download page

Status: RESOLVED FIXED

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

Description

[Mike Beltzner [:beltzner, not reading bugmail]]

Need to create content for:

http://www.mozilla.org/projects/bonecho/releases/2.0b2.html (release notes)
http://www.mozilla.org/projects/bonecho/index-2.0b2.html  (start page)

See bug 344151 for reference/examples.

Comment 1

[Mike Beltzner [:beltzner, not reading bugmail]]

--> taking, will have stuff by midday PDT tomorrow

Comment 2

[Reed Loden [:reed]]

Reminder to me: Update download.js with new l10n build information.

Also, I'll need the usual stuff for VARIABLES (this is 2.0b1's info):
%%VAR FIREFOX-DEVEL-WIN32-SIZE 5.4MB
%%VAR FIREFOX-DEVEL-X86LINUX-SIZE 8.9MB
%%VAR FIREFOX-DEVEL-MACOSX-SIZE 17MB
%%VAR FIREFOX-DEVEL-WIN32-DL-TIME 14.7 min @ 56k/s
%%VAR FIREFOX-DEVEL-X86LINUX-DL-TIME 24.2 min @ 56k/s
%%VAR FIREFOX-DEVEL-MACOSX-DL-TIME 46.2 min @ 56k/s

Comment 3

[Mike Beltzner [:beltzner, not reading bugmail]]

Graphics to come in bug 350601 - thanks Steven!

Comment 4

[Mike Beltzner [:beltzner, not reading bugmail]]

http://www.mozilla.org/projects/bonecho/releases/releasenotes-bonecho-beta2.png checked in and available for use

Comment 5

[Chris Beard]

cc'ing pkim as we'll want these graphics to match the revised brand guidelines being put in place for Firefox 2.

Comment 6

[Paul Kim]

Confirming that we'll be getting an updated treatment of the "Firefox 2" wordmark when revised brand assets are handed off to us next week. 

Comment 7

[Chris Beard]

Perhaps we could hack the beta2 graphic to be closer to the new guidelines in the interim? i.e. adding "mozilla" and using a different colour for "2".  The treatment of "beta 2" in the proposed graphic here seems unbalanced to me. This isn't a show stopper though, this is a nice to have. 

Comment 8

[Paul Kim]

Attachment: in progress wordmark of Firefox 2

Here's a cut and paste from the in progress brand guidelines showing the treatment Chris Beard is referencing.

Comment 9

[Mike Beltzner [:beltzner, not reading bugmail]]

Attachment: first draft of content

Notes:

 - I ended up revamping a bit of the "What's New" content provided by Mary (hee, hee!) to make it a little more clear in a few places, and to embed the links in the text itself; mary/pkim/cbeard, please review!

 - I think this is all the relevant release notes that we need to include, timr/marcia, please review!

 - I think the HTML isn't totally screwed up, reed, please review!

Comment 10

[Mike Beltzner [:beltzner, not reading bugmail]]

Attachment: first draft of content (UTF-8)

Grrrr. Now in UTF-8!

Comment 11

[Paul Kim]

Looks good Mike -- need to add a closing </a> tag after the opening <a href> tag in the blurb on Phishing Protection.

And there's a cleanup required on aisle 7:
"and shortcut lets users quickly re-open" should change to "and a shortcut lets users quickly re-open"

Comment 12

[Mike Beltzner [:beltzner, not reading bugmail]]

Thanks, Paul; reed's got a working version (that also fixes some other errors I made such as the charset, invalid close comment tag, and mis-capitalization of "Add-ons") here:

http://mozilla-org.landfill.bugzilla.org/projects/bonecho/releases/2.0b2.html

He'll post the final version here before committing. Any other changes?

Comment 13

[Paul Kim]

Attachment: Updated release notes image

I've updated the background image with the revised wordmark for Firefox 2. Given the vertical dimensions of the layout there isn't room to put in the "Mozilla" mark up top. Please have a look.

Comment 14

[Sherman Dickman]

Just a note to let folks know that I have phishing protection content on my radar.

Comment 15

[Pascal Chevrel:pascalc]

A few nitpicks:

In the release notes "web" is sometimes capitalized, sometimes not.

I don't understand why in this sentence :
"Current users of Mozilla Firefox 1.x should not use Firefox 2 Beta 2" the older product is called "Mozilla Firefox" while the newer product is only "Firefox".

"before reporting any bugs to Bugzilla." English is not my primary language, but shouldn't "bugs" be at singular form?

"These Release Notes cover what's new" What's new is called "changes" in the document body, plus it is the only item not listed on the sidebar menu and I expect this section to be what most beta testers will want to know.

the "Other Changes" link on the sidebar lead nowhere

"Firefox 2's theme and user interface have have been updated" have, is repeated

"makes it easier to to add, " to, is repeated.

in the html "close tab" shouls be <cite>close tab</cite> so as to follow the target language quoting conventions.

<h3 id="download"><a name="download">Downloading Firefox 2 Beta 2</a></h3>

There is no need to duplicate the anchor and we should use IDs everywhere since the name attribute is deprecated in XHTML (which I expect will be used for localized products pages)

The "All systems" section has bad HTML in terms of semantics, "phishing protection" - "history and bookmarks"... are clearly titles defining the following text and unordered list of only one bullet item does not really make sense. We should be using definition lists here (<dl><dt>phishing protection</dt><dd>bla bla</dd>).

The hreflang attribute should be indicated on links, it is not really useful for English speakers but I guess this page will be used as a basis for the final Fx2 release notes and this will be required on localized versions of the release notes (the reader needs to know if he understands the language of the target link before clicking on it).

Comment 16

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to comment #15)
> In the release notes "web" is sometimes capitalized, sometimes not.

Mozilla.com uses "Web" consistently, so should we. The only place where we shouldn't capitalize it is in the term "websites".

> I don't understand why in this sentence :
> "Current users of Mozilla Firefox 1.x should not use Firefox 2 Beta 2" the
> older product is called "Mozilla Firefox" while the newer product is only
> "Firefox".

Sure, let's ditch "Mozilla".

> "before reporting any bugs to Bugzilla." English is not my primary language,
> but shouldn't "bugs" be at singular form?

No, plural is correct here.

> "These Release Notes cover what's new" What's new is called "changes" in the
> document body, plus it is the only item not listed on the sidebar menu and I
> expect this section to be what most beta testers will want to know.

Agreed. Let's change the section title to "What's New in this Development Milestone" and add a "whatsnew" internal anchor to that section and a "What's New" item to the sidebar.

> the "Other Changes" link on the sidebar lead nowhere

There's no content, but it does lead to the "otherchanges" internal anchor. When content appears, it'll go there.

> "Firefox 2's theme and user interface have have been updated" have, is repeated
> 
> "makes it easier to to add, " to, is repeated.

Whoops!

> in the html "close tab" shouls be <cite>close tab</cite> so as to follow the
> target language quoting conventions.

Agreed.

> <h3 id="download"><a name="download">Downloading Firefox 2 Beta 2</a></h3>
> 
> There is no need to duplicate the anchor and we should use IDs everywhere since
> the name attribute is deprecated in XHTML (which I expect will be used for
> localized products pages)

Sure.

> The "All systems" section has bad HTML in terms of semantics, "phishing
> protection" - "history and bookmarks"... are clearly titles defining the
> following text and unordered list of only one bullet item does not really make
> sense. We should be using definition lists here (<dl><dt>phishing
> protection</dt><dd>bla bla</dd>).

I guess, sure. I don't think this is a big deal. I'll leave it up to reed if he wants to change it.

> The hreflang attribute should be indicated on links, it is not really useful
> for English speakers but I guess this page will be used as a basis for the
> final Fx2 release notes and this will be required on localized versions of the
> release notes (the reader needs to know if he understands the language of the
> target link before clicking on it).

The final release notes will be fully localized and hosted on mozilla.com with, I expect, fully localized links. I don't think this is needed, and am hoping that we not actually use this document as a template, so let's not worry about this now.

Comment 17

[Reed Loden [:reed]]

(In reply to comment #16)
I've made all the requested changes (except for the hreflang thing). Please look at http://mozilla-org.landfill.bugzilla.org/projects/bonecho/releases/2.0b2.html and see if it looks ok.

Comment 18

[Mary]

Please add a period to the end of the "Client-side session and persistent storage" description.  Thanks!

Comment 19

[Pascal Chevrel:pascalc]

Attachment: product number on wrong line

The product numbers do not stick to the product name, see the bug on screenshot.

We need non-breaking spaces on product numbers like :
Firefox 2 beta 2
Mac OS X

Comment 20

[Pascal Chevrel:pascalc]

Th screenshot is also showing the old 1.0 theme and not the new FF2 theme, since beta 2 main change is the visual refresh, I think it should be updated.

(tell me if I am being too picky, I know that I can be kind of annoying sometimes ;) )

Comment 21

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to comment #19)
> Created an attachment (id=236107) [edit]
> product number on wrong line

I don't think this is a huge issue, but if it's a simple fix, might as well make it.

(In reply to comment #20)
> Th screenshot is also showing the old 1.0 theme and not the new FF2 theme,
> since beta 2 main change is the visual refresh, I think it should be updated.

Not a blocker, especially since the theme that's in the RC2 candidates isn't going to be the final expression of the theme. And no, you're not being annoying, but I don't think we should be aiming for perfection on these release notes; we'll get a new screenshot for the final release notes, to be sure.

Comment 22

[Reed Loden [:reed]]

Attachment: Release Notes, as on test site

Release notes from http://mozilla-org.landfill.bugzilla.org/projects/bonecho/releases/2.0b2.html

Comment 23

[Mike Beltzner [:beltzner, not reading bugmail]]

Attachment: content for Firefox 2 Beta 2 Start page

Reed, check my HTML on this. Used the updated "What's New" name and list from the release notes. Think my URLs are right, fingers crossed!

Comment 24

[Mike Beltzner [:beltzner, not reading bugmail]]

Comment on attachment 236135 [details]
Release Notes, as on test site

nit: can we add a <br/> at the end of each <li> of the "What's New" section? Or add CSS padding between each <li>? It needs a touch more breathing space.

Comment 25

[Reed Loden [:reed]]

Comment on attachment 236140 [details]
content for Firefox 2 Beta 2 Start page

r=reed

I made a couple of modifications for some stuff in my local copy.

Comment 26

[Reed Loden [:reed]]

RCS file: /cvsroot/mozilla-org/html/projects/bonecho/index-2.0b2.html,v
done
Checking in index-2.0b2.html;
/cvsroot/mozilla-org/html/projects/bonecho/index-2.0b2.html,v  <--  index-2.0b2.html
initial revision: 1.1
done
Checking in releases/2.0b2.html;
/cvsroot/mozilla-org/html/projects/bonecho/releases/2.0b2.html,v  <--  2.0b2.html
new revision: 1.2; previous revision: 1.1
done

Leaving this open, as I have lots of other stuff to do for the release web-wise. :(

Comment 27

[Mike Beltzner [:beltzner, not reading bugmail]]

Updating description; preed, can you let reed know when the locale builds have been pushed to the bouncer mirrors?

Comment 28

[Marek Stępień [:marcoos, inactive]]

Regarding all-beta.html on the stage server: xh is Xhosa, for native name should ask Dwayne Bailey.

Comment 29

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

languageNames.properties within the localization itself (which is what I used for almost all the rest) says "isiXhosa".

Comment 30

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

For the record, the way I generally add languages to the all.html list is using this list of language codes:
http://www.w3.org/WAI/ER/IG/ert/iso639.htm
this list of country codes:
http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html
and this shell script that operates on a checkout of the l10n repository:

> #!/bin/bash
> cd /builds/l10n-1.8/l10n || exit
> find . -maxdepth 1 -type d | cut -b3- | grep -v "^CVS$" | grep -v "^$" | sort | while read LOCALENAME; do
>         LANGNAME=$(echo $LOCALENAME | sed -e's/-.*//')
>         grep "^$LANGNAME[[:space:]]*=" $LOCALENAME/toolkit/chrome/global/languageNames.properties | sed -e's/\([[:alpha:]]*\)[[:space:]]*=[[:space:]]*\(.*\)/\1=\2/'
> done

and then this URL to escape the output of that shell script (all at once):

> javascript:"<pre>" + unescape(escape(prompt("Enter string")).replace(/%u/g,"\\u").replace(/%([89ABCDEF])/g,"\\u00$1")) + "</pre>"

Comment 31

[Mike Beltzner [:beltzner, not reading bugmail]]

For the redirects at /projects/bonecho, the release announcement for beta2 will be located at:

http://developer.mozilla.org/devnews/index.php/2006/08/31/firefox-2-beta-2-milestone-released/

Comment 32

[Reed Loden [:reed]]

Before I go to sleep for a couple of hours, as I didn't get much last night due to fire alarm issues, beltzner wanted me to post my todo list.

I need somebody to do what dbaron said in comment #30 to get the locale name info for xh and zu locales. I think I have all the other ones, but it would be nice if somebody checked that for me.


(In reply to comment #31)
> For the redirects at /projects/bonecho, the release announcement for beta2 will
> be located at http://developer.mozilla.org/devnews/index.php/2006/08/31/firefox-2-beta-2-milestone-released/

Justin, did you put the RewriteCond/RewriteRule stuff for /projects/bonecho in the httpd config? If so, please update it to this:
-----------------
RewriteEngine on
RewriteCond %{HTTP_USER_AGENT} ^.*\s(?:BonEcho|Firefox)/2\.0b2$
RewriteRule ^(?:index\.html)?$ index-2.0b2.html [L]
RewriteRule ^(?:index\.html)?$ http://developer.mozilla.org/devnews/index.php/2006/08/31/firefox-2-beta-2-milestone-released/ [L]
----------------

Also, can somebody figure out why http://www-stage.mozilla.org/projects/bonecho/ is giving an error 500?


There are some other things I have to do, but they are quickies, and I can do them either now or after I wake up.

Comment 33

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to comment #32)
> I need somebody to do what dbaron said in comment #30 to get the locale name
> info for xh and zu locales. I think I have all the other ones, but it would be
> nice if somebody checked that for me.

Not a blocker. We can just leave these out until we know, or enter a non-native name and fix it later, or whatever. These guys are asleepsies now, anyway :)

> Justin, did you put the RewriteCond/RewriteRule stuff for /projects/bonecho in
> the httpd config? If so, please update it to this:

I'll file a new IT request for this, we'll only want to push this change the minute we "release".

> Also, can somebody figure out why
> http://www-stage.mozilla.org/projects/bonecho/ is giving an error 500?

Does this block this bug? If not, let's track is separately?

Comment 34

[Nick Thomas [:nthomas] (UTC+12)]

Based on the output I get from dbaron's script (from comment #30), they should be:

xh - isiXhosa
zu - IsiZulu

Dwanye, is that right ? How about the different capitalisation ?

All the languages in 
    zu/toolkit/chrome/global/languageNames.properties 
have some variation of Isi or Isi- prepended to them, including ones like Danish, Dutch etc. A few of the langs in the xh equiv begin ngokwesi.

Comment 35

[Axel Hecht [:Pike]]

The IsiSomething sounds familiar from Dwayne's visit, that should be safe to take.

Comment 36

[Nick Thomas [:nthomas] (UTC+12)]

I've had a look at all-beta.html, checking that only the locales in mozilla/browser/locales/shipped-locales (Tag: FIREFOX_2_0b2_RELEASE) have non null fxbeta in downloads.js

It's looking good apart, apart from the missing 
       nso - Northern Sotho - Sesotho sa Leboa

Comment 37

[Dwayne Bailey]

(In reply to comment #34)
> Based on the output I get from dbaron's script (from comment #30), they should
> be:
> 
> xh - isiXhosa
> zu - IsiZulu
> 
> Dwanye, is that right ? How about the different capitalisation ?

Please refer to http://www.constitutionalcourt.org.za/site/constitution/english-web/ch1.html under section 6 languages.  The map below just maps the names to the ISO code.

I'm listing all 11 - I know you don't need them all yet but they will be needed later.

af - Afrikaans
en - English (now that was an easy one ;) )
nr - isiNdebele
nso - Sepedi (Sesotho sa Leboa is controversial, you can place both if we don't want to offend anyone)
ss - Siswati (my capitalisation here is correct)
st - Sesotho
ts - Xitsonga
tn - Setswana
ve - Tshivenda
xh - isiXhosa
zu - isiZulu

Comment 38

[Reed Loden [:reed]]

(In reply to comment #37)
> nso - Sepedi (Sesotho sa Leboa is controversial, you can place both if we don't
> want to offend anyone)

I've changed "Sesotho sa Leboa" to "Sepedi", as we don't have room for both.

> zu - isiZulu

I've changed "IsiZulu" to "isiZulu".

Are there any more I missed? Of the others you mentioned, I don't think we support most of them.

Checking in download.js;
/cvsroot/mozilla-org/html/download.js,v  <--  download.js
new revision: 1.129; previous revision: 1.128
done

Comment 39

[Axel Hecht [:Pike]]

The others were added to the build after b2, so that's a 'yet'.

Comment 40

[Reed Loden [:reed]]

(In reply to comment #39)
> The others were added to the build after b2, so that's a 'yet'.

Ok, let me know if/when you're releasing those builds so I can add them to the page once the bouncer URLs are in place.

Comment 41

[Mike Beltzner [:beltzner, not reading bugmail]]

I'm marking this bug as FIXED, please file follow ups if there are any left to do.