Closed
Bug 659786
Opened 13 years ago
Closed 13 years ago
Firefox BETA users who go to moz.com do NOT see the What's New (Panda Page)
Categories
(www.mozilla.org :: General, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
2.8
People
(Reporter: christine.brodigan, Assigned: sgarrity)
References
()
Details
Guys, Blake noticed that since launch Firefox Beta users continue to land on firefox.com and get firefox.com/new - instead of receiving the "You've Been Updated" messaging. Can we figure out and push a fix? We might want to think about a "What's new" experience for Beta and Aurora users in the future, so we aren't reusing the same page for current Firefox users. -CB
Comment 1•13 years ago
|
||
yes yes yes to this!
> We might want to think about a "What's new" experience for Beta and Aurora
> users in the future, so we aren't reusing the same page for current Firefox
> users.
This is a great idea, but should be handled separately from this bug. Chrissie, can you take point on that? Goal would be to figure out what we need to do to create a unique in-product experience for Beta & Aurora users.
James, Pinging you on this - any possibility it will be fixed to go out in this week's release? Best, CB
Updated•13 years ago
|
Target Milestone: --- → 2.6
Comment 3•13 years ago
|
||
2.6 is going out today, so this will have to be within the 2.7 timeframe.
Target Milestone: 2.6 → 2.7
Comment 4•13 years ago
|
||
Sadly, I haven't been able to get to this and I'm out until Thursday. Is Anthony around? He could do this if he's ok with that. Assigning to him until you all figure out someone else to do it.
Assignee: jlong → anthony
(In reply to comment #4) > Sadly, I haven't been able to get to this and I'm out until Thursday. Is > Anthony around? He could do this if he's ok with that. Assigning to him > until you all figure out someone else to do it. Anthony is still out, so assigning over to Steven with fingers crossed, otherwise, let's move it to the next milestone.
Assignee: anthony → steven
Assignee | ||
Comment 6•13 years ago
|
||
There is a whatsnew page for the Firefox 5 beta: http://www.mozilla.com/en-US/firefox/5.0beta/firstrun/ (actually a redirect from /firefox/5.0/whatsnew/) I think the core issue here is that when you go to mozilla.com with the beta (or aurora, you end up on /firefox/new/ rather than /firefox/fx/). That isn't related to the whatsnew page(s) though. The current behaviour for mozilla.com is: If browser is Firefox 4.0.1 -> /firefox/fx/ Anyone else -> /firefox/new/ Can I get confirmation that the desired behaviour is for those running a recent Beta or Aurora build of Firefox should also get bumped from mozilla.com to /firefox/fx/ rather than /firefox/new/? The result would be something like this: If browser is Firefox 4.0.1 or 5.X or 6.X -> /firefox/fx/ Anyone else -> /firefox/new/
Comment 7•13 years ago
|
||
(In reply to comment #6) > The current behaviour for mozilla.com is: > > If browser is Firefox 4.0.1 -> /firefox/fx/ > Anyone else -> /firefox/new/ > > Can I get confirmation that the desired behaviour is for those running a > recent Beta or Aurora build of Firefox should also get bumped from > mozilla.com to /firefox/fx/ rather than /firefox/new/? This is correct. The basic idea of this bug is to broaden our current redirect strategy to encompass our new release channels. For the time being, we'd like the channel users on the latest channel versions to also see /firefox/fx, as you describe above. In the future we may want to do even more segmentation, for example, give users on old Beta versions a Beta tester version of the firefox/new page, but for now let's start with basic redirect parity. > The result would be something like this: > > If browser is Firefox 4.0.1 or 5.X or 6.X -> /firefox/fx/ > Anyone else -> /firefox/new/ You got it!
Comment 9•13 years ago
|
||
reopening as Firefox 6.x goes to http://www.stage.mozilla.com/en-US/firefox/new/ on stage
Assignee | ||
Comment 10•13 years ago
|
||
Thanks Raymond. Fixed in trunk in r90445. Merged to stage in r90446. That leaves two revisions to merge from stage to production after QA: r90116 and r90446
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Keywords: qawanted
Resolution: --- → FIXED
Target Milestone: 2.7 → 2.8
Comment 11•13 years ago
|
||
qa-verified-trunk http://www.stage.mozilla.com/en-US/firefox/fx/
Keywords: qawanted
Comment 12•13 years ago
|
||
pushed to production r90568
Comment 13•13 years ago
|
||
verified fixed http://www.mozilla.com/en-US/firefox/fx/
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Updated•12 years ago
|
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.
Description
•