Closed Bug 561507 Opened 15 years ago Closed 15 years ago

revise Major Update window for 3.6.4 release

Categories

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

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jslater, Assigned: sgarrity)

References

(
URL
)

Details

Attachments

(1 file)

Screenshot showing Windows, Mac, and Linux rendering
105.32 KB, image/png
Details
Based on the most recent findings from the metrics team (http://blog.mozilla.com/metrics/2010/04/21/why-people-don%E2%80%99t-upgrade-their-browser-%E2%80%93-part-iv/) we'd like to make some text changes to the 3.6.4 update window. A couple of initial options are below, based around the theme from the data that people are concerned about the process taking too long. Edits or other suggestions are encouraged, of course. #1 Title: Upgrade for Stability, Security Subtitle: Free, and Only Takes a Minute -Improved stability: fewer crashes! -Compatible with your favorite add-ons. -Plugin check & other new security tools. #2 Title: Free Firefox Upgrade Subtitle: Improved stability: fewer crashes! -Upgrade only takes a minute or two. -Compatible with your favorite add-ons. -Thousands of new themes to choose from.
I like these options because they're applicable to all platforms. The major update dialog I just got (http://grab.by/4025) says my Firefox on Mac won't crash when plugins do, which isn't true.
One other note about comment #1 - I'm not sure would wrote the text for the 3.6.4 beta pop-up, but it wasn't me...would really like to be looped in on those projects to ensure consistency of messaging. Thanks.
(In reply to comment #2) > One other note about comment #1 - I'm not sure would wrote the text for the > 3.6.4 beta pop-up, but it wasn't me...would really like to be looped in on > those projects to ensure consistency of messaging. Thanks. The text for the advertised 3.6.4 beta opt-in update was written by Christian and me, and circulated to the release-drivers@ mailing list which is the standard procedure of record for beta releases. It is not intended to be the billboard used when we ship Firefox 3.6.4. I agree that the updated billboard text in comment 0 is more appropriate for the general Firefox 3.0.x / 3.5.x -> Firefox 3.6.x advertised upgrade offers. @fligtar: the content was specifically different for the beta channel because we were doing a first-time-ever opt-in upgrade for beta channel users. There is a redirect in place for OSX users who should not see the text about OOPP; we've gotten sporatic reports of it not working, but QA has confirmed that for stock installs of Firefox 3.6.3 on beta channel, OSX users don't see that text. There may be something odd in your UA string.
Assignee: jslater → beltzner
Gah, didn't mean to assign this to myself; sorry. My suggestion for text would be a hybrid of John's options: Title: Get Firefox 3.6 for free Subhead: Quick and easy update * Works with all your add-ons * Faster and more stable browsing * Keeps you safer as you browse
Assignee: beltzner → jslater
(In reply to comment #4) > Title: Get Firefox 3.6 for free > Subhead: Quick and easy update > > * Works with all your add-ons > * Faster and more stable browsing > * Keeps you safer as you browse This generally looks good to me, but I'd suggest changing the title/subtitle to: title: Get the New Firefox subtitle: Quick, easy and free update! The changes are mainly for word count, but also to downplay the version number a bit. Mike, if this looks good to you I'll make sure it gets built soon.
Maybe "Get the Newest Firefox"? Whichever, works for me.
(In reply to comment #6) > Maybe "Get the Newest Firefox"? Whichever, works for me. I like that even better, thanks. Steven, we'd like to make some text changes to the major update pop-up...can you help? Here's the new copy: Title: Get the Newest Firefox Subtitle: Quick, easy and free update! * Works with all your add-ons * Faster and more stable browsing * Keeps you safer as you browse URL should be http://www.mozilla.com/en-US/firefox/3.6.4/details/ (Mike/Christian, correct me if I'm wrong). Thanks!
Assignee: jslater → steven
Depending on your target audience, the url in comment #7 may be incorrect. AIUI we have these major update billboards: 3.0.x -> 3.6.x for beta/release users http://www.mozilla.com/en-US/firefox/3.6/details/from-3_0.html 3.5.x -> 3.6.x for beta/release users http://www.mozilla.com/en-US/firefox/3.6/details/index.html 3.6.x -> 3.6.4 for beta users http://www.mozilla.com/en-US/firefox/3.6.4/details/index.html
(In reply to comment #8) > Depending on your target audience, the url in comment #7 may be incorrect. AIUI > we have these major update billboards: > > 3.0.x -> 3.6.x for beta/release users > http://www.mozilla.com/en-US/firefox/3.6/details/from-3_0.html > > 3.5.x -> 3.6.x for beta/release users > http://www.mozilla.com/en-US/firefox/3.6/details/index.html We want to make the changes in both of these places, IMO. We've already done the big scary warning for Firefox 3.0.x users, and I think we want to get similarly aggressive for both sets. The alternative is to regenerate the update snippets so they both point the same place; your choice! > 3.6.x -> 3.6.4 for beta users > http://www.mozilla.com/en-US/firefox/3.6.4/details/index.html This change isn't for beta users; that audience got a very different set of update billboards, and is irrelevant here (was a red herring in earlier comments)
(In reply to comment #9) > (In reply to comment #8) > > Depending on your target audience, the url in comment #7 may be incorrect. AIUI > > we have these major update billboards: > > > > 3.0.x -> 3.6.x for beta/release users > > http://www.mozilla.com/en-US/firefox/3.6/details/from-3_0.html > > > > 3.5.x -> 3.6.x for beta/release users > > http://www.mozilla.com/en-US/firefox/3.6/details/index.html > > We want to make the changes in both of these places, IMO. We've already done > the big scary warning for Firefox 3.0.x users, and I think we want to get > similarly aggressive for both sets. > > The alternative is to regenerate the update snippets so they both point the > same place; your choice! Let's just update both URLs -- regenerating the snippets at this point is a PITA and forces re-testing.
I've updated these two in trunk (r66619): en-US/firefox/3.6/details/from-3_0.html en-US/firefox/3.6/details/index.html Preview here: http://www-trunk.stage.mozilla.com/en-US/firefox/3.6/details/from-3_0.html http://www-trunk.stage.mozilla.com/en-US/firefox/3.6/details/index.html The headline wraps a bit - maybe we could/should tweak the font sizes and line-height a bit given this text?
(In reply to comment #11) > The headline wraps a bit - maybe we could/should tweak the font sizes and > line-height a bit given this text? Agreed...can you play with it a bit to make it fit on one line? If it's really not going to work, "Get the New Firefox" is also an option (although I prefer "Newest").
Font spacing/size tweaked in r66626 and r66627. It's a bit tight, but I think it works. Note that it's a bit tighter on Windows (will post a screenshot).
Here's a screenshot showing how the fonts render in Windows, Mac, Linux (in that order).
(In reply to comment #14) > Created an attachment (id=442688) [details] > Screenshot showing Windows, Mac, and Linux rendering > > Here's a screenshot showing how the fonts render in Windows, Mac, Linux (in > that order). Looks good to me, thanks Steven.
(In reply to comment #15) > (In reply to comment #14) > > Created an attachment (id=442688) [details] [details] > > Screenshot showing Windows, Mac, and Linux rendering > > > > Here's a screenshot showing how the fonts render in Windows, Mac, Linux (in > > that order). > > Looks good to me, thanks Steven. Whats left to do here?
(In reply to comment #16) > Whats left to do here? Steven, are we cool on the front end stuff here? WebQA, what do you guys think?
(In reply to comment #17) > (In reply to comment #16) > > Whats left to do here? > > Steven, are we cool on the front end stuff here? WebQA, what do you guys think? It looks good to me from the WebQA standpoint, which is just basic rendering, doctype validation, and link checking; all those pass. Not sure about localizability, etc.
This is ready to go as far as I'm concerned.
FWIW, the issue in comment #1 was fixed by adding in a header (http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-US/firefox/3.6.4rc/details/index.html?r1=66727&r2=66813) So we can have dynamic content based on platform if wanted.
Mayumi - can you review the content in comment 11 and if you're OK with it we can push so that localization can start? The links will be seen by Firefox 3.0.x and 3.5.x users as part of an advertised (dialog pops up unrequested) major update offer to come after we ship Firefox 3.6.4.
Reviewed and no further edits from me.
Then I think this can go live.
ok, I am starting localization of this new Major update text. A question, is it ok to delete older Major update window file for all locales now? That is: http://www.mozilla.com/en-GB/firefox/2.0/details/ http://www.mozilla.com/en-GB/firefox/3.0/details/ http://www.mozilla.com/en-GB/firefox/3.5/details/
(In reply to comment #24) > http://www.mozilla.com/en-GB/firefox/2.0/details/ > http://www.mozilla.com/en-GB/firefox/3.0/details/ > http://www.mozilla.com/en-GB/firefox/3.5/details/ I don't think we can remove these - the MU snippets are still on the wire for anyone running those older versions of Firefox, and point to those URLs.
ok, too bad :)
The en-US version and CSS is merged from trunk to stage in r68262.
Localization is tracked in bug #569851
Time to close this bug ?
Depends - looks like we didn't push a CSS file. Stephen, can you confirm and push the CSS change if it needs to go live, then resolve this bug? Compare: trunk: http://www-trunk.stage.mozilla.com/en-US/firefox/3.6/details/from-3_0.html live: http://www.mozilla.com/en-US/firefox/3.6/details/from-3_0.html trunk: http://www-trunk.stage.mozilla.com/en-US/firefox/3.6/details/index.html live: http://www.stage.mozilla.com/en-US/firefox/3.6/details/index.html (if the CSS fix happened in a different bug, then by all means, close this one out!)
I checked, there was a diff between stage and production. Pushed to production in http://viewvc.svn.mozilla.org/vc?view=revision&revision=70474
Keywords: push-needed
Thanks, Christian! Resolving this fixed.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
I also just looked at the live pages and everything looks as it should.
Component: www.mozilla.org/firefox → www.mozilla.org
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.

Attachment

General

Creator:
Created:
Updated:
Size: