hi steven. opening a bug per our conversation from bug 653288. we need to update the page when beta for desktop release this coming Wednesday/Thursday 5/18-19 the change is pretty minor, we need to activate the beta for desktop download button. currently, it says coming soon. so once beta for desktop is available, the button will then be one of the green download button. in addition, we need the link to the all.html page under the button as well.

updating to 2.5 but live date for the update is happening wednesday 5/18 or thursday 5/19. thanks

Download button added in trunk in r88924.

Fixed button on Macs in r88933.

This is set in trunk unless there's a change to use a non-green color for the beta download buttons. Let me know and I'll merge to stage.

I think we'll want a different color for that beta button. We used orange for Fx4 betas, yes?

(In reply to comment #5) > I think we'll want a different color for that beta button. We used orange > for Fx4 betas, yes? Yes, we can bring that color back. For both Desktop and Mobile Beta buttons, I presume?

yes please.

Looking back at some old Fx4 beta files, I see we used a green button (more fluorescent green vs. the current split-pea green). We could use orange, but was wondering if that would actually compete or overpower the other 2 buttons - also, possibly compete w/ the logos... How about our CTA blue for the button? see attachment...

+1 for comment #8...I like that suggestion better than my original one. Thanks!

Blue looks good to me. Do keep in mind, though, that we now have two beta buttons (desktop & mobile) rather than one beta and one final. It's probably late in the process for this, but I wonder if we should do more to differentiate the mobile beta from the two desktop channels (beta/aurora). Either that, or somehow associate the two beta variations (desktop/mobile).

Hey Steven. Can you provide an example of what you're referring to? I'm not totally getting it.

(In reply to comment #11) > Hey Steven. Can you provide an example of what you're referring to? I'm not > totally getting it. Sure. The mockup shows three columns, all for the desktop: Aurora | Beta | Final This would have been purple (aurora), blue (beta), and green (final). while the actual page now has a different set of columns: Aurora | Beta (desktop) | Beta (mobile) Which means the colors will be purple (aurora), blue (beta), blue (beta). This might be ok, I just wanted to be sure it was clear.

I've implemented the blue for the desktop and mobile beta buttons in trunk (in r88992) so you can see them in context: http://www-trunk.stage.mozilla.com/en-US/firefox/channel/

+1 from me on that mockup. I think it's cleaner to keep with the blue treatment for both Beta buttons, and use the copy in the buttons (as you have it in trunk) to differentiate.

Works for me then. Thanks guys.

hi steven. this looks great. can you please update the link for the beta for mobile link to: https://market.android.com/details?id=org.mozilla.firefox_beta Currently it's linking to https://market.android.com/details?id=org.mozilla.firefox which is the link to the final release. other than that. this looks good. grace

(In reply to comment #16) > hi steven. this looks great. can you please update the link for the beta for > mobile link to: > https://market.android.com/details?id=org.mozilla.firefox_beta Done in trunk in r89044. Merged this and previous changes to stage in r89045. Please test on stage: http://www.stage.mozilla.com/firefox/channel/

(In reply to comment #17) > (In reply to comment #16) > > hi steven. this looks great. can you please update the link for the beta for > > mobile link to: > > https://market.android.com/details?id=org.mozilla.firefox_beta > > Done in trunk in r89044. > > Merged this and previous changes to stage in r89045. > > Please test on stage: http://www.stage.mozilla.com/firefox/channel/ steven, is this one good to go? still marked qa review? http://www.stage.mozilla.com/firefox/channel/ is missing button all.html link to 4.0.1 version? but this link http://www-trunk.stage.mozilla.com/en-US/firefox/channel/ is fine. please confirm

Grace, the issues you mentioned in comment #18 are due to the product-details library not being updated on Stage yet. James is doing that now. When that is done, the page is all set, but we should have QA run through it anyhow.

cool thanks

qa-verified-trunk http://www-trunk.stage.mozilla.com/en-US/firefox/channel/

verified fixed http://www.mozilla.com/en-US/firefox/channel/

production r89178