Closed Bug 653636 Opened 13 years ago Closed 13 years ago

Create billboard for major update to 5.0 beta build

Categories

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

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: nthomas, Assigned: jlong)

References

(
URL
)

Details

Bug 652641 is creating a Firefox 5.0 *beta* build to help populate the beta channel and test channel switching, and we're going to do a major update from older 4.0 beta builds to get people there (bug 651982). Consequently we need a billboard which extols the virtues of updating to 5, and it should live at
  https://www.mozilla.com/en-US/firefox/5.0/details/
Note that the target users have not managed to update to 4.0 or 4.0.1 by themselves, despite months of opportunity. Only en-US is needed at this time, but localised pages may be needed later (when we do beta builds for real).

There will also need to be a firstrun page, which encourages people to test channel switching, but I don't know if that is filed yet.

Christian and Marketing probably have input on what the billboard should say. You can see what we said for major updates to 4.0 at 
  https://www.mozilla.com/en-US/firefox/4.0/details/

AIUI this is an urgent request.
Mayumi, Laura - please advise on what the messaging should be here.

Matej - heads up that we'll need some writing help on this.

Steven - heads up that we'll need some building help on this.

Nick - how urgent?
Assignee: nobody → jslater
Hardware: x86 → All
I think that the new billboard dimensions landed before the the betas (see Bug 480178).

The size of the billboard is 700px for the width and 360px for the height for all locales and platforms. The actual width on Windows and Linux ends up being 701px and iirc Mac OS X ends up having a width of 701px and a height of 361px. XUL often adds an extra pixel when specifying the width or height for a child element and allowing the rest of the UI to auto size. So, going with a 700px width by 360px height billboard will be safe.

There is a new method for testing the billboard (this also displays the three possible buttons for this page) by adding a new string preference named app.update.billboard.test_url with a value of the path to the billboard’s html. The path when testing using this method supports file:// urls as well as http(s):// urls. Clicking any of the buttons when testing with this method will close the user interface instead of carrying out their normal action.

Also, the billboard must have an attribute billboard’s html body so that Application Update can verify that the page wasn’t redirected as can be the case when using a hotel’s wifi, etc.
The builds are currently with QA, and part of that will be internal testing for on channel switching. Having a placeholder page up early Friday would be helpful for that (getting a 404 is bad).

So probably not Friday but early next week, but you should ask someone higher up the foodchain for an answer which isn't a guesstimate.
Sorry, just catching up. I didn't realize this was needed for the 5.01b push. That is likely to happen Monday. Is there any other solution beyond doing this? Cv aging copy on an existing billboard?
Changing*
We will be using this URL http://www.mozilla.com/en-US/firefox/5.0beta/details/.  if you want to see the template we will be using, please see http://www.mozilla.com/en-US/firefox/4.0beta/details/.  We are working on this and will post updates.
Christian - If we gave you the updated wordmark and copy could update the billboard?  We have been slamming the Web Dev team with Rapid Release requests last minute and they have other priorities right now for Aurora and Beta so if at all possible I'd rather not bother them for this.
Here's the new copy:

Help Mozilla release faster and determine what makes it to the final beta. Upgrade to the latest version!
A big +1 from me for using the copy in comment #9 with the wordmark in comment #10 in the http://www.mozilla.com/en-US/firefox/4.0beta/details/ design template.

Steven Garrity and I have talked about this a bit and he may be able to help if needed, but if Christian can do it that'd be even better...would prefer not to disrupt Steven's work on other projects if we can help it.

Thanks all-
There's a photoshop file with the background images for both the Firefox 4 Beta and Aurora billboards here if it helps: http://labs.silverorange.com/files/mozilla/beta-update.psd.zip

Let me know if my help is needed.
Steven, how about this - if Christian isn't able to work on it over the weekend, you use that 4 hour head start on us and take it on Monday. Sound ok?
(In reply to comment #13)
> Steven, how about this - if Christian isn't able to work on it over the
> weekend, you use that 4 hour head start on us and take it on Monday. Sound ok?

Sure - as long as Monday is soon enough. Is there a conclusion as to what the visual style should be? Is the light/royal-ish blue from the 4.0beta/details useable?
1) This billboard is specifically to upgrade FF3.7a*, FF4.0b* beta users to FF5.0beta1. No aurora builds involved here.

2) Instead of creating custom new buildboards, I'd be fine using the generic template ones that Christian had made up a few months ago. It would get us unblocked and testing sooner. Any objections to that?
2) Instead of creating custom new buildboards, I'd be fine using the generic
template ones that Christian had made up a few months ago. It would get us
unblocked and testing sooner. Any objections to that?
[YES, SINCE THIS IS NOT A STANDARD BETA WE HAVE TO USE SPECIFIC MESSAGING.  WE ARE TRYING TO USE ALL ASSETS ALREADY AVAILABLE BUT WE DO NEED TO UPDATE THE COPY]
Note: I believe the new billboard size landed for 3.7a3 in bug 480178.
(In reply to comment #14)
> Sure - as long as Monday is soon enough. Is there a conclusion as to what the
> visual style should be? Is the light/royal-ish blue from the 4.0beta/details
> useable?

Yep! In order to keep this simple we can basically use the exact visual style as with http://www.mozilla.com/en-US/firefox/4.0beta/details/, except with new copy & the beta wordmark.

Thanks-
(In reply to comment #16)
> 2) Instead of creating custom new buildboards, I'd be fine using the generic
> template ones that Christian had made up a few months ago. It would get us
> unblocked and testing sooner. Any objections to that?
> [YES, SINCE THIS IS NOT A STANDARD BETA WE HAVE TO USE SPECIFIC MESSAGING.  WE
> ARE TRYING TO USE ALL ASSETS ALREADY AVAILABLE BUT WE DO NEED TO UPDATE THE
> COPY]

Mayumi;

ok, so we'll wait for custom new buildboards. Any ETA?
(In reply to comment #19)
> Any ETA?

Monday.
This is setup in trunk in r88090:
http://www-trunk.stage.mozilla.com/en-US/firefox/5.0beta/details/

Let me know if I missed anything from the thread. The text/wordmark also look good in white, but I opted to keep the wordmark unchanged.

If this looks ok, let me know and I'll merge to stage and prepare for production.
This looks good to me--I think we can stage this ;)
(In reply to comment #7)
> We will be using this URL
> http://www.mozilla.com/en-US/firefox/5.0beta/details/.

I have redone the updates to point at this path, only https.
Merged to stage in r88130. HTTPs should be fine.
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: push-needed
Resolution: --- → FIXED
Thanks Steven!
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: FIXED → ---
Unconfirmed bug? Perhaps resolved.
Definitely confirmed...not fully resolved yet as far as I can tell. (need QA signoff for that)
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA are verifying on www-trunk.stage and then this will go live ? There may be two types of QA here - webQA on the billboard and product QA on the major update, and the latter would need it live in production.
I think its fine to push this to production soon--that way QA can get going.
(In reply to comment #29)
> I think its fine to push this to production soon--that way QA can get going.

Any ETA on getting these into production, so QA can start testing?
James - Can you push this live? The sooner the better.
Assignee: jslater → jlong
pushed to production r88162
URL: http://www-trunk.stage.mozilla.com/en... → http://mozilla.com/en-US/firefox/5.0b...
Status: NEW → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Still has "push-needed"; should that be removed, now?
verified fixed http://www.mozilla.com/en-US/firefox/5.0beta/details/
Status: RESOLVED → VERIFIED
Keywords: push-needed
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.