Closed
Bug 706488
Opened 13 years ago
Closed 13 years ago
Update Config for Fx 9 Whats New Page
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lmesa, Unassigned)
References
Details
Per https://bugzilla.mozilla.org/show_bug.cgi?id=689679 Engagement needs to show a WN page with Fx 9.
Please update the configs in order to do so.
Comment 1•13 years ago
|
||
8.0.1 was late and the 3.6->8 update is yet to come, meaning that 9 will be perceived as occurring in rapid succession (i.e. even more rapid than usual). To me this doesn't seem like the right time to make updates more visible again.
Reporter | ||
Comment 2•13 years ago
|
||
I understand the concern, but we have a brand campaign that will be going out with Firefox 9 led by Slater and Beard we've been planning for this release date for a fw months. I can let him comment here, but this is a priority for the engagement team.
Comment 3•13 years ago
|
||
(In reply to Laura Mesa [:lmesa] [:lvmesa] from comment #2)
> I understand the concern, but we have a brand campaign
Ironically, the concern is very brand-related. Update rage needs to be considered especially because it's no one-time irritation but seems to have a negative impact on the Firefox brand.
Also, at this time, that page may not be a great launch pad for any campaign, regardless of its nature. Chances are that somebody annoyed by updates won't have a positive feeling towards the update page and its content.
Comment 4•13 years ago
|
||
:lmesa, just to confirm, this is needed for 9.0 release, and not needed for the 9.0betas?
Blocks: 701054
Summary: Update Config for Fx 9 WN Page → Update Config for Fx 9 Whats New Page
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to John O'Duinn [:joduinn] from comment #4)
> :lmesa, just to confirm, this is needed for 9.0 release, and not needed for
> the 9.0betas?
That's correct, thanks.
Comment 6•13 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #1)
> 8.0.1 was late and the 3.6->8 update is yet to come, meaning that 9 will be
> perceived as occurring in rapid succession (i.e. even more rapid than
> usual). To me this doesn't seem like the right time to make updates more
> visible again.
Our current strategy for rolling out FF9 is web downloads and manual updates only on 12/20, automatic updates in early January 2012. I don't think "update rage" should therefore be a concern for FF9.
Comment 7•13 years ago
|
||
Will the WN page be displayed for manual updates to Fx 9, as well?(In reply to Alex Keybl [:akeybl] from comment #6)
> (In reply to Dão Gottwald [:dao] from comment #1)
> > 8.0.1 was late and the 3.6->8 update is yet to come, meaning that 9 will be
> > perceived as occurring in rapid succession (i.e. even more rapid than
> > usual). To me this doesn't seem like the right time to make updates more
> > visible again.
>
> Our current strategy for rolling out FF9 is web downloads and manual updates
> only on 12/20, automatic updates in early January 2012. I don't think
> "update rage" should therefore be a concern for FF9.
That means that WN page won't be displayed for manual updates, right?
Comment 8•13 years ago
|
||
There's no difference between background and manual updates for the What's New page, as we serve the same update.xml to both.
If you mean a pave-over install after downloading from mozilla.org, then that depend on the app prefernces, which would mean that What's New would be shown for Fx9.
Comment 9•13 years ago
|
||
Fixed by Rail on bug 701054 - http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/tools/patcher-configs&command=DIFF&root=/cvsroot&file=mozRelease-branch-patcher2.cfg&rev1=1.19&rev2=1.20
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 10•13 years ago
|
||
What channel and builds can be used to test that WN page is displayed at update?
Comment 11•13 years ago
|
||
(In reply to Mihaela Velimiroviciu [QA] from comment #10)
> What channel and builds can be used to test that WN page is displayed at
> update?
From my reading of patches on Bug 701054 it looks like releasetest will act like release always did (give you an auto-update prompt) however release channel would also work, though you'll need to manually check.
So Firefox 8 (or 8.0.1) -> 9 on either release or releasetest
I'll let someone from Mozilla Releng correct me if my understanding of that is wrong though.
Comment 12•13 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #11)
> So Firefox 8 (or 8.0.1) -> 9 on either release or releasetest
Yes, once 9.0 is built.
Comment 13•13 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
Firefox 8.0.1 won't upgrade on releasetest channel ("Firefox is up to date"). Could it be that the new version was not added to the channel?
Comment 14•13 years ago
|
||
9.0 hasn't been built yet, but it should be available in the next 24 hours.
Comment 15•13 years ago
|
||
Verified updates to Firefox 9.
Both manual and background (on releasetest channel) updates work and WN page is displayed.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•