Closed Bug 688497 Opened 13 years ago Closed 13 years ago

[Fx7] Update redirect to reflect Fx 7 launch

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lforrest, Assigned: sgarrity)

References

Details

(Whiteboard: r=95400,95419,95436 b=trunk)

Update the landing page redirect to reflect the fact that Fx 7 has launched. Change so everyone not on Fx7 gets /new, while Fx7 people get /fx.
Assignee: nobody → steven
Blocks: 675968
Target Milestone: --- → 3.12
Can we assume that Firefox 6.0 should be switched over to the "ALMOST THERE!" out-of-date page at the release of Firefox 7?

See, for example, the 5.0 out-of-date whatsnew page:
http://www.mozilla.org/en-US/firefox/5.0/whatsnew/
(In reply to Steven Garrity from comment #1)
> Can we assume that Firefox 6.0 should be switched over to the "ALMOST
> THERE!" out-of-date page at the release of Firefox 7?
> 
> See, for example, the 5.0 out-of-date whatsnew page:
> http://www.mozilla.org/en-US/firefox/5.0/whatsnew/

We can! Thanks for thinking of that.
Ok, so it turns out we've already got Fx7 going to /fx rather than /new for the beta. I've also updated the .htaccess files to send the /firefox/6.0/whatsnew/ to the /out-of-date/ ("Almost There!") page.
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Whiteboard: r=95400 b=trunk
We also need to remove the fx6 rewrite so that they are redirected to /new. Just committed that.
Whiteboard: r=95400 b=trunk → r=95400,95419 b=trunk
pushed to production r95428
verified fixed http://www.mozilla.org/en-US/firefox/new/
Status: RESOLVED → VERIFIED
This also needed to be done in the prefetch file. Done.
Whiteboard: r=95400,95419 b=trunk → r=95400,95419,95436 b=trunk
pushed r95436 to production in r95438
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.