Firefox/Channels/Meetings/2012-05-17: Difference between revisions

 
(11 intermediate revisions by 8 users not shown)
Line 34: Line 34:


==Add-ons==
==Add-ons==
<br>
* {{bug|754723}} - Blocklist old versions of Flash Player. Not a hard/soft block, just an update notification.
 
== Stability ==
== Stability ==
===Aurora===
===Aurora===
Line 43: Line 44:
<br>
<br>
== QA ==
== QA ==
* Q: Do you have an ETA on a 10.8 test plan?
** [https://etherpad.mozilla.org/Mt-Lion-Test-Plan Draft Plan]
===Aurora===
===Aurora===
<br>
<br>
===Beta===
===Beta===
<br>
[http://bit.ly/IhfxAz QAWANTED Bugs]: nothing blocking QA at this point
 
== RelEng ==
== RelEng ==
<br>
<br>
== Marketing/Communications ==
== Marketing/Communications ==
<br>
<br>
Beta Naming suggestion: Let's continue to use our current language around Beta even though we're speeding up dev cycles since we want to avoid the confusion we saw around "rapid release" naming. Beta is still the same, it's just on a different cycle. No new name needed.
== Support ==
== Support ==
q: any version info for the adobe reader bug? anything new to go on?
* q: any version info for the adobe reader bug? anything new to go on?
* Bug filed for Foxit Reader. Ongoing investigation: https://bugzilla.mozilla.org/show_bug.cgi?id=752311
* Have we filed bugs from [https://wiki.mozilla.org/Firefox/Channels/Meetings/2012-05-15#Support 5/15]?
** Netflix/Youtube audio not stopping when you close: https://bugzilla.mozilla.org/show_bug.cgi?id=756250
** The latest dev Firebug version ([http://blog.getfirebug.com/2012/05/11/firebug-1-10a8/ 1.10]) works with Aurora so it should be fine with release.


== Roundtable ==
== Roundtable ==
Rapid Betas meta-bug: {{bug|755978}} please add blocking of bugs you're using to track and RB work if you don't see them already listed.
Rapid Betas meta-bug: {{bug|755978}} please add blocking of bugs you're using to track and RB work if you don't see them already listed.
Notification bar for outdated plugins:
* What's the User Experience here? Can a user dismiss the notification and never see it again? Do they get prompted by the bar on every tab, for multiple plugins?
* Ideally they'd get a prompt, visit plugin-check page, and update all that apply
* Can we look at doing this route (instead of blocklisting vs. doing nothing) for most/all plugins? Outdated versions of plugins once newest version is verified?  Top N plugins?
Pulling Fennec Release from Market
Merge Day moving to the Monday before Release Days (Tuesday)


== Actions ==
== Actions ==
Confirmed users
685

edits