Closed Bug 685940 Opened 11 years ago Closed 11 years ago
.6 .X users introductory content upon upgrade to latest browser version
When we launched Fx4 we showed all users the First Run page with introductory "meet your new browser" content to help bridge the leap into such a new browser. (example of that page: http://www.mozilla.org/en-US/firefox/6.0/firstrun/) We then merged users back to seeing either the latest What's New page (upgrades), or the First Run page (first-time users only, again). We'd like to change that back just for 3.6 upgraders. Please show these 3.6 users the introductory content above when they upgrade to the most recent version of Firefox (currently Fx6). That can be done by redirecting them to the First Run page, or by moving that First Run content into a What's New page only these users see. Is this something the web team can do, or are there any Product dependencies?
AFAICT, we only know which versions the users are currently upgrading TO, not FROM. So we can't know if someone is coming from Firefox 6.0.1 or Firefox 3.6. So yeah I think this has Product dependencies.
Laura Mesa - Have a look at this, there seems to be product dependencies to get the desired results here. Can you suggest next steps?
I would speak with Christian Legnitto or Rob Strong to get a better understanding of what we can tell. Start with Christian and he'll send you to Rob or Rel Eng.
Reassigning to clegnitto to determine what's possible.
Assignee: steven → clegnitto
Also, want to clarify--3.6.X users to 7.0 will see this First Run page, right? http://www.mozilla.org/en-US/firefox/7.0/firstrun/?
No. They would see what's new, and we removed it for Fx 7 (I explicitly asked if we should revert the patch or not due to that consideration)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 685958
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.