677978 - Update Firefox 5 What's New page with "Almost There" messaging

Status: VERIFIED FIXED

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

Description

[Laura Forrest]

As discussed on IRC, please change the Fx 5 page to the "almost there" page design once Fx 6 is launched. 

Example: http://www.mozilla.com/en-US/firefox/4.0/whatsnew/

Laura Mesa: This was done to Fx4 folks when Fx5 was released - it should be done again, right? Let me know if this is a dup.

Comment 1

[Laura Mesa [:lmesa] [:lvmesa]]

(In reply to Laura Forrest from comment #0)
> As discussed on IRC, please change the Fx 5 page to the "almost there" page
> design once Fx 6 is launched. 
> 
> Example: http://www.mozilla.com/en-US/firefox/4.0/whatsnew/
> 
> Laura Mesa: This was done to Fx4 folks when Fx5 was released - it should be
> done again, right? Let me know if this is a dup.

Thanks for doing this--I had forgotten about this!  +1 from me.

Comment 2

[Laura Forrest]

Steven - you also mentioned that 3.6 folks were not getting this page. They should be. Can you apply it to them as well?

Comment 3

[Steven Garrity [:sgarrity]]

Can this happen immediately after Fx6 is released? If so, we won't bother updating the 5.0 whatsnew page with the latest round of features/promos, if not, we should update it.

Comment 4

[Laura Mesa [:lmesa] [:lvmesa]]

(In reply to Steven Garrity from comment #3)
> Can this happen immediately after Fx6 is released? If so, we won't bother
> updating the 5.0 whatsnew page with the latest round of features/promos, if
> not, we should update it.

Yes, I think so.

Comment 5

[Steven Garrity [:sgarrity]]

Done in trunk in r93615.

This change now sends Firefox 3.6 and Firefox 5 users to the /firefox/out-of-date/ whatsnew/firstrun page (the "Almost There" page). Fx4 already goes there.

This change also removes the  6.0 -> 6.0beta firstrun/whatsnew/releasenotes/details pages.

I'll file another bug to clean up the files for the for 3.6 and 5.0 firstrun/whatsnew pages a few days after the launch.

Comment 6

[Anthony Ricaud (:rik)]

Why are we telling 3.6 users that it's out of date? We still support it at the moment.

Comment 7

[Laura Mesa [:lmesa] [:lvmesa]]

(In reply to Anthony Ricaud (:rik) from comment #6)
> Why are we telling 3.6 users that it's out of date? We still support it at
> the moment.

Well, it is out of date, to be fair. 3.6 is not the most current release and we're trying to move our users from 3.6 to the latest version. 

We're not saying its no longer supported, just that its not the most up to date version.

Comment 8

[Pascal Chevrel:pascalc (PTO until Sept 2)]

The out of date page says "Thanks you for downloading Firefox", people seeing this page via Whatsnew have not downloaded Firefox, they have been updated by Firefox to the latest security release for their channel. I think this page was designed for the Firstrun experience.

Comment 9

[Laura Mesa [:lmesa] [:lvmesa]]

(In reply to Pascal Chevrel:pascalc from comment #8)
> The out of date page says "Thanks you for downloading Firefox", people
> seeing this page via Whatsnew have not downloaded Firefox, they have been
> updated by Firefox to the latest security release for their channel. I think
> this page was designed for the Firstrun experience.

This is true. Maybe we can change it to say "Thank you for updating". It was designed ofr the FR experience, but I think it still achieves what we want it to do. Would you agree with that wording change?

Comment 10

[Pascal Chevrel:pascalc (PTO until Sept 2)]

Sure, I am actually more thinking of the l10n impact there ;)

Comment 11

[Steven Garrity [:sgarrity]]

We're using a single "out-of-date" page for both firstrun and whatsnew (http://www.mozilla.com/en-US/firefox/out-of-date/).

Might we be able to come up with some more generic text that will apply in both firstrun and whatsnew cases? If not, we can setup two variations of the out-of-date page.

Comment 12

[Laura Mesa [:lmesa] [:lvmesa]]

Rereading the copy, I feel like download actually works for both scenarios (update and fresh download).  John, what do you think?

Comment 13

[Steven Garrity [:sgarrity]]

Apparently we don't have an 'out-of-date' page that will work for 3.6 users in non en-US locales. The localized page implies possible security risks of being out of date, which isn't true of 3.6, which is till being updated.

Given this situation, I've reverted the 3.6 change that was part of this bug so 3.6 users will continue to get the 3.6 firstrun/whatsnew pages.

It seems the 3.6 situation is a bit more complicated. If people still feel it should change, let's open a new bug for it and not pull it into the Firefox 6 release process.

Comment 14

[Steven Garrity [:sgarrity]]

I think we can call this fixed. If anyone wants to adjust the "Thanks for downloading..." wording, please re-open.

Comment 15

[Laura Mesa [:lmesa] [:lvmesa]]

(In reply to Steven Garrity from comment #13)
> Apparently we don't have an 'out-of-date' page that will work for 3.6 users
> in non en-US locales. The localized page implies possible security risks of
> being out of date, which isn't true of 3.6, which is till being updated.
> 
> Given this situation, I've reverted the 3.6 change that was part of this bug
> so 3.6 users will continue to get the 3.6 firstrun/whatsnew pages.
> 
> It seems the 3.6 situation is a bit more complicated. If people still feel
> it should change, let's open a new bug for it and not pull it into the
> Firefox 6 release process.

Ok, thanks Steven. Laura, we should likely file a bug for that ;)

Thanks for closing.

Comment 16

[raymond [:retornam] (inactive)]

qa-verified-trunk http://www-trunk.stage.mozilla.com/en-US/firefox/out-of-date/

Comment 17

[raymond [:retornam] (inactive)]

verified fixed http://www.mozilla.com/en-US/firefox/5.0/whatsnew/