i initially opened a bug to add mobile beta in this channel (Bug 651005). but after collaborating and discussing options with few stakeholders, we've come a new plan: 1. Adding Mobile Beta in one of the 3 columns Currently it's Aurora, Beta and Final Release. This proposal means the new page will have Desktop Aurora, Desktop Beta and Mobile Beta 2. Where will the final Release go in the page? Since the main purpose of this page is promote the pre-final channels we have, we would like to move final release in one of the promotions at the bottom of the page. 3. but we already have newsletter sign up at the bottom of the page? instead of the newsletters taking up all 3 columns for the bottom of the page, we would like to have the final release (desktop/mobile) promo/download button in one/two of the columns and newsletter sign up. we would also like to include a copy that says the beta will include desktop and mobile. will also open design request for this. live date: may 17th

This is not taking l10n into account, we have our locales currently translating the version we have today, changing the page while they are already working on the first copy is making this a moving target for volunteers.

hi pascal. i understand and i know that there are so many things changing at this time. however, when this page was designed, unfortunately, we did not include any mobile presence. moving forwards, we will try our best to include mobile perspective and design things with both of our desktop and mobile thinking hats on, to lessen redesigning or updating pages. My understanding was that l10n was just getting ready and have not started localizing as we were still making changes to the page and truly apologize if I did not communicate that this page was still undergoing some changes.

We already have that page localized and on production for 33 locales so that's more than just started, I was asked to get this page done as soon as possible at the all-hands.

Steven - Heads up on this one. Complete assets should be heading your way by May 12th.

Re: comment 4. Given timing, planning, l10n demands, etc. for the may 17th mobile beta launch instead of localizing the new version of the channel page can we add the mobile icon and words iterating that these versions are now available for mobile. And then l10n the new version of the page for the june 22nd launch? Pascal, let us know what else you need. - Under the beta button add the mobile phone icon (see attached .png) and the words "Firefox Beta for mobile" [Caitlin please post the Android marketplace link to beta] - Under the the Final release button add the mobile phone icon (see attached .png) and the words "Firefox for mobile" [link to https://market.android.com/details?id=org.mozilla.firefox] - Aurora (nothing to add since there is no mobile aurora channel)

Sorry I didn't make this clear, the page for en-US should still be redesigned as Grace noted in the description for the May 17th mobile launch. My comment reflected that the new design could not be localized in time for the May 17th launch but there should be some mobile presence on non-English pages.

regarding comment #6, yes this is perfectly doable, I will add the strings to the localizers plate today

(In reply to comment #8) > regarding comment #6, yes this is perfectly doable, I will add the strings > to the localizers plate today hi milos, just to summarize our conversation earlier today, mobile and desktop beta might not release on the same day, in which case, we might have to do a little bit of tweaking in the localized pages and live date for the page. if mobile launches before desktop: we to need to make the download button for mobile active and keep the 'coming soon' button for desktop beta if desktop launches before mobile: we need a coming soon button for mobile beta and active download button for desktop beta at the moment, it sounds like mobile will be releasing on the 17th and desktop on the 18th/19th. i should get a better idea hopefully by end of this week. but wanted to give you guys a heads up so you can plan better. please let me know if you have any questions regarding timing.

hi steven, here is the final psd for the new redesign /firefox/channel page: http://people.mozilla.com/~gjimenez/redesignfirefoxchannelpage.psd please note the rss feed under the rapid release blog section. in addition, per my note above to the l10 team, I want to give you a heads up regarding releases and live date of the page. i understand that this bug and page is currently planned for 2.5 release (17th live date) but would need to make some tweaks depending on final release dates. (beta) if mobile and desktop releases at the same day: page is good as is. (beta) if mobile releases before desktop: we need to keep the 'coming soon' button for the Desktop beta (like how it is now in the current /firefox/channel page) and have the green download button for the mobile for beta (beta) if desktop releases before mobile: we need the coming soon button for the mobile for beta and have a green download button for desktop beta at the moment, it sounds like mobile will be releasing on the 17th and desktop on the 18th/19th. i should get a better idea hopefully by end of this week. but wanted to give you guys a heads up so you can plan better. in addition, mobile for beta logo might be changing as well and should have the final logo in the next couple of days. please let me know if you have any questions regarding timing or if you need additional design support. my understanding are all the changes that needs to happen above are changeable from the webdev side. thanks!

I see that the mockup includes a checkbox to agree to the Privacy Policy in the newsletter sign-up. The current page just includes a link to the privacy policy - is that sufficient?

(In reply to comment #11) > I see that the mockup includes a checkbox to agree to the Privacy Policy in > the newsletter sign-up. The current page just includes a link to the privacy > policy - is that sufficient? hi steven, just checked with winston. he and alex (legal) just had a chat about this and it sounds like we do need the "i agree" check box there and the link should be sufficient for now. thanks for checking

(In reply to comment #12) > (In reply to comment #11) > > I see that the mockup includes a checkbox to agree to the Privacy Policy in > > the newsletter sign-up. The current page just includes a link to the privacy > > policy - is that sufficient? > > hi steven, > > just checked with winston. he and alex (legal) just had a chat about this > and it sounds like we do need the "i agree" check box there and the link > should be sufficient for now. thanks for checking sorry just to clarify. * we do need the check box there + the link to the privacy page * in terms of copy, the link to the privacy policy page is sufficient for now (no additional copy needed)

one last more request, can we get rid of the first tier footer. a bit confusing and redundant given we already have a whole section of newsletter sign up. (see attachment)

hi steven, just a follow up from our meeting today, confirming that the beta for mobile download button links to the android market [https://market.android.com /details?id=org.mozilla.firefox]. we wont have a maemo beta channel. additionally, we also need to take out the all systems and languages link below the button and "list of supported devices" link http://www.mozilla.com/en-US/mobile/platforms/ thanks for checking.

We've got this page setup now in trunk in r88764. As the blog isn't live yet, we're importing headlines from the Wordpress Blog as a placeholder. Please review and let us know if anything needs adjusting.

Committed a small bug fix for the feed caching in r88825.

(In reply to comment #17) > We've got this page setup now in trunk in r88764. As the blog isn't live > yet, we're importing headlines from the Wordpress Blog as a placeholder. > > Please review and let us know if anything needs adjusting. hi steven. looks great. per our conversation, please update the name of the blog to "future releases" (vs rapid release). link to the blog is blog.mozilla.com/futurereleases please let me know if you need any additional info

Updated with the proper blog title and the real blog URL for importing, both in trunk in r88839. Un-broke localized versions of the page in trunk in r88840 (sorry Pascal). Merged all to stage in r88843. Ready for QA on stage.

layout really broken in IE6

(In reply to comment #21) > layout really broken in IE6 Fixed in trunk in r88849. Let me know if it's fixed in trunk for you and I'll merge to stage.

Merged to stage in r88854.

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

(In reply to comment #24) > qa-verified-stage http://www.stage.mozilla.com/en-US/firefox/channel/ Looks like there's something weird going on with the copy under Beta for Mobile. It starts off right, but then slips into the old copy from Final Release. The correct copy is: • Experience cutting edge mobile features still in development • Provide feedback to help refine and polish what will be in the final release The copy under Aurora is also incorrect. It should be: • Experience the newest innovations before they go to beta in an environment that’s not for the faint of heart • Provide feedback on features and performance to help determine what makes the final release Also, should the button beneath desktop beta be a download button, as it was in the final mockup I saw, or did that change somewhere along the way? (In reply to comment #19) > hi steven. looks great. per our conversation, please update the name of the > blog to "future releases" (vs rapid release). link to the blog is > blog.mozilla.com/futurereleases I'd prefer if we could say "Follow the Future Release Blog" instead of "Future Releases Blog," which tracks weird. Grace, is that OK?

(In reply to comment #25) > (In reply to comment #24) > > qa-verified-stage http://www.stage.mozilla.com/en-US/firefox/channel/ > > Looks like there's something weird going on with the copy under Beta for > Mobile. It starts off right, but then slips into the old copy from Final > Release. The correct copy is: > > • Experience cutting edge mobile features still in development > • Provide feedback to help refine and polish what will be in the final > release > > The copy under Aurora is also incorrect. It should be: > > • Experience the newest innovations before they go to beta in an environment > that’s not for the faint of heart > • Provide feedback on features and performance to help determine what makes > the final release > > Also, should the button beneath desktop beta be a download button, as it was > in the final mockup I saw, or did that change somewhere along the way? > > > (In reply to comment #19) > > hi steven. looks great. per our conversation, please update the name of the > > blog to "future releases" (vs rapid release). link to the blog is > > blog.mozilla.com/futurereleases > > I'd prefer if we could say "Follow the Future Release Blog" instead of > "Future Releases Blog," which tracks weird. Grace, is that OK? thanks for checking matej. steven, can we still make the changes? matej, re: download button, beta for desktop is launching later than mobile. mobile is going tomorrow and desktop wednesday/thursday. hence the button still says coming soon.

Wording mix-up from comment #25 is fixed in trunk in r88870. The blog title change suggestion is done in trunk r88871. Both are merged to stage in r88872. Thanks for catching that Matej.

hi steven. thanks for this. is this page good to go? just a quick update, beta for mobile has a new release date. the new target release date is this Thursday, 5/19. took it out of the 2.5 milestone. desktop can also go the same day or the day after 5/20. keeping 2 separate bugs to push update on channel page separate for now. mobile: 653288 (5/19) desktop: 657374 (5/19 or 5/20)

The page is ready, but if desktop/mobile don't go at the same time, we'll have to do some work to de-couple them.

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

hi steven. can we please make sure we update the beta button color and link: https://market.android.com/details?id=org.mozilla.firefox_beta. thanks!

In r89177 use curl to download blog feed instead of file_get_contents and ignore anything but http 200 responses.

pushed to production r89178 I have not pushed r89177 yet until we test it on the staging servers.

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