Firefox/Channels/Meetings/2011-12-29: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Previous Actions == * <strike>'''ashughes''': Respond to Christian's email and make a decision for QA</strike> '''DONE''' ** QA will attempt to sign off on Friday * <strike>jo...") |
(→Beta) |
||
| Line 38: | Line 38: | ||
===Beta=== | ===Beta=== | ||
* Beta 2 | * Beta 2 [https://wiki.mozilla.org/Releases/Firefox_10/Test_Plan#Beta_2 test plan] | ||
** On track to release on Friday -- no blocking issues found as of yet | |||
** {{bug|713991}} - Geolocation fails consistently | |||
** | ** {{bug|714045}} - Site favicon not displayed in Panorama if entering Panorama before site has loaded completely | ||
** problem with updates from 10.0b1, rail is regenerating snippets which should resolve the issue | |||
** | |||
** | |||
** | |||
===Other === | ===Other === | ||
Revision as of 21:45, 29 December 2011
Previous Actions
ashughes: Respond to Christian's email and make a decision for QADONE- QA will attempt to sign off on Friday
joduinn to check with IT about capacity/load in PHX/v.a.m.o.DONE- IT said 10% is fine, and now they have said 100% is fine
bug 713964 filed to track unthrottling to 10%, if IT are ok with this.DONE- Auto updates are enabled @ 10%
Firefox 9
- The Yahoo messenger bug bug 713014 may be due to bug 696020
- QA found a possible gelocation regression when near a place with tons of access points (bug 713991)
Add-ons
Aurora
- Do we need to do the compat bump on AMO now that we have compatible by default?
- We will continue doing the compatibility bumps. The only difference is that we won't be doing positive bumps (telling devs the add-on passed and increasing the maxVersion on AMO), only negative bumps (telling devs the add-on didn't pass compatibility checks).
- The negative bump logs will also serve as a source of incompatibility data
Beta
- bug 711275 Make sure appVersion changes with every Firefox 10 beta - will ensure that the add-ons default to compatible path will be hit on each beta update
- We had to not do this because Fx wouldn't install over previous Fx10 betas. It sees 10.0 (previous appVersion) as > 10.0b2 (new/altered app version)
- We decided to go back to normal for b2, which means the default compatible path isn't hit for b2
- Investigating bumping it to 11.0 for future betas to work around the issue
- SM folks are aware
- Have we seen any compatible by default add-on issues? How would issues show up? Have we blocked any add-ons yet?
- Is QA running automated tests with the top 500 add-ons (and top 50 installed permutations?)
- QA lead looks to be Virgil Dicu (form the feature page)
Stability
- Need to get a fix for bug 711900
- Worried that it is stumping some heavy hitters (bz, gavin, etc)
Roundtable
Aurora
Beta
- Beta 2 test plan
- On track to release on Friday -- no blocking issues found as of yet
- bug 713991 - Geolocation fails consistently
- bug 714045 - Site favicon not displayed in Panorama if entering Panorama before site has loaded completely
- problem with updates from 10.0b1, rail is regenerating snippets which should resolve the issue
Other
- We are going to have Blekko look for bad version sniffing (that may affect Firefox 10)
- When is this happening?
- What to do with emails with questions/bugs from users to android marketplace account?
- Alex and christian are taking point communicating with Amazon. Let's not have multiple threads which could confuse them.
Triage
- Christian updated the queries on Firefox/Channels