*need all.html/beta * Need to update copy * localized builds for FX5 beta *We need to have this ready by May17 (depending when we will get all the localized beta builds) but would be good to have the page ready ;)

Laura, please add this one of the releases before May 17. Thanks!

This will inherit the changes from bug 650423 (with beta info instead of aurora, of course), so that's a good reference point.

Hey Steven - Sending your way - not needed until 5/17 but would be good to get started on when you can.

CC'ing Anthony since his product-details work for Aurora will be pertinent for this page too. That said, we might be able to just re-use the existing beta page/code.

hi steven and anthony, are we all set here? is there anything else I can provide to get the page started? thanks!

I can set up the page if Anthony can help with the product-details aspect.

(In reply to comment #6) > I can set up the page if Anthony can help with the product-details aspect. thanks Steven! Anthony, please let us know if you have any questions or need additional info in order to set up the product-details portion.

Anthony, how about re-purposing the all-beta.html page we had for the Firefox 3.6 and 4.0 betas?

Sorry for the delay, this was lost in my bugmail while travelling. So we need to know the download link pattern that's going to be used. Who can give us that? We should be able to reuse most of the previous code for betas.

Adding John and Nick to see if they can get us the download link pattern.

Even though end users will only see a version of 5.0, RelEng needs to track sets of beta builds. To do that we are going to use versions of 5.0b1, 5.0b2, etc in our systems, and that will follow through into the download URLs. So the builds on immediately after the merge from aurora (May 17) we will have URLs like http://download.mozilla.org/?product=firefox-5.0b2&os=win&lang=en-US (since we've already used 5.0b1 for the fake beta). Each time we do another beta build the last number in the product will increment. So this is very like what we did for 4.0 betas.

Actually, that may be incorrect. I need to check what we decided about pushing these beta releases to the mirrors.

It looks like the existing all-beta.html page is still there, just redirected to all.html while there is no beta running. Just need to un-comment-out line #228 in .htaccess to disable this redirect. Reassigning this to Anthony (let me know if you need any help).

Actually, it's line 405 that disables this. I've done that in r88696. So http://www-trunk.stage.mozilla.com/en-US/firefox/all-beta.html is viewable but it has a very old look. Steven, would you like me to recreate this page based on all-aurora.html ? I will update product-details to 5.0b2 next week. Nick, any news on the confirmed download pattern?

hi anthony, just a follow up from our conversation this morning, please use the same template for this page: http://www.mozilla.com/en-US/firefox/all-aurora.html copy should be: Download Firefox Beta in your language Experience cutting edge features with more stability Provide feedback to help refine and polish what will be in the final release please let me know if i can provide any additional info. thanks

(In reply to comment #14) I've confirmed we will be using the pattern in comment #11, so it's the same as all.html with versions which will be 5.0b2, 5.0b3, etc. However, I suspect people will want to hide the bN part of the version away and just say 5.0, which will match what's inside the app.

Committed r88917 for product-details and r88919 for trunk.

qa-verified-trunk http://www-trunk.stage.mozilla.com/en-US/firefox/all-beta.html

(In reply to comment #16) > However, I > suspect people will want to hide the bN part of the version away and just > say 5.0, which will match what's inside the app. I see the version as 5.0b2 on www-trunk.stage. Was there some out-of-bug discussion on whether that was OK ?

Comments, Anthony?

I never got people asking strongly for removing the bN part so I haven't done it. I feel like this page should be as specific as possible about what you're about to download so displaying it feels ok. Plus, the all-aurora.html page displays 5.0a2 and no one complained about that. But if it's something we want to hide, it could be done. It shouldn't block the release though.

My argument is that the b2 part is strictly an implementation detail on the Release Engineering side, and the actual application is 5.0 and will be for all beta versions in this cycle (as requested by the product management team). If we need to know the specific version (for QA or whatever) we can check the download URLs. Normally I'd advocate giving more information to the user, but in this case I think consistency trumps that. That's my 2c, anyway.

(In reply to comment #22) > My argument is that the b2 part is strictly an implementation detail on the > Release Engineering side, and the actual application is 5.0 and will be for > all beta versions in this cycle (as requested by the product management > team). If we need to know the specific version (for QA or whatever) we can > check the download URLs. > > Normally I'd advocate giving more information to the user, but in this case > I think consistency trumps that. That's my 2c, anyway. agree with nick. we shouldn't have 5.0b2. can we update and just make it say 5.0? thanks rik!

How about something hacky/quick like this? =================================================================== --- productDetails.class.php (revision 89144) +++ productDetails.class.php (working copy) @@ -608,6 +608,10 @@ continue; } + $_build_version = preg_replace('/[ab][0-9]+$/', + '', + $_build_version); + $_is_current_version = ($_build_version == $_latest_version) ? ' class="curVersion" ' : ''; // Special case: If the current version is the same as our oldest version,

I've opened bug 658552 for this followup. Christian: it brakes the page for me.

merge to stage r89165

qa-verified http://www-trunk.stage.mozilla.com/en-US/firefox/all-beta.html

pushed to production r89178

verified fixed http://www.mozilla.com/en-US/firefox/all-beta.html