From MozillaWiki
Jump to: navigation, search
« previous week | index | next week »

Channel Meeting Details

  • Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • #planning for backchannel

Video/Teleconference Details - NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 95312 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 95312 (US)
  • Vidyo Room: Warp Core
  • Vidyo Guest URL
These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.

Previous Actions

  • Cheng:
    • Nothing new has been reported here, dropping it off of our actions
  • QA: print selection on Mac/Windows
    • bug 736915 – Print Selection prints a blank page when the selection is inside a table in SeaMonkey2.8 & Firefox11 and later
  • QA/Jorge: bug 722538 – block AMD Radeon HD 6290/6300/6310/6320 for DIRECT2D
  • RelEng: scoping of custom WN page for 3.6->12/13
  • Alex: to set up a meeting about 12/13 boundary with OS versions (esp. w/r/t 3.6.28->13) - bug 723158 needs to happen before Beta 13
    • Thursday at 10AM PT in PB&J
  • Asa: finalize automated 3.6->12 auto update decision
  • Asa: determine if bug 718088 should go out in 13

Schedule Update

  • Beta 3 going to build today, released Friday
  • Firefox 11 post-mortem held tomorrow at 10AM PT in WarpCore
  • Win2k/XP SP1 desupport meeting to be held Thursday (email akeybl if you'd like to be included)
  • Maple uplift (and mobile Beta off of Aurora) plans to be solidified Thursday/Friday
  • Next week's Beta 4 will go to build by 5PM PT and should be kicked off at that time to allow for QA to sign off on Thursday

3.6 EOL

  • (completed) 3/23: 3.6 EOL and Win2K/XP SP1 desupport officially announced
  • Between 3/19 and 4/24 (once FF11 is unthrottled)
    • (completed) MU prompts for 3.6.28 to FF11
    • MU prompts for 3.6.27 and lower to FF11 with strong security messaging, depending on the effectiveness of bug 730095 – Please prepare 3.6.13->10.0.2 MU snippets previously (any updates here Marketing?)
  • 4/24: Firefox 12 released, 3.6 EOL'd
  • Around 5/1 (once FF12 is unthrottled). We can only do one of these at a time:
    • Offer unprompted updates from 3.6 (all versions or .28?) to FF12, possibly with a custom WN page
    • Offer prompted major updates from 3.6 to FF12
  • Around 6/12 (once FF13 is unthrottled). Again, we can only do one of these at a time:
    • Offer prompted major updates from 3.6 to FF12 with EOL messaging
    • Offer unprompted updates from 3.6 to FF12 with the add-on compatibility check disabled (still unclear if this moves users)




  • bug 733793 - Top crash in Aurora - what can we do to move it along?


  • bug 725503 – crash in radhslib.dll from Naomi Internet Filter
    • We're able to reproduce crashes and misbehavior, just not the original signature in the bug
    • Because the DLL is being injected into our process, we're unable to blocklist it
    • Attempts at finding the bump in crashes in nightly didn't yield much
    • Ideas for reproducing? Or could we take forward change for this? bsmedberg has noted that taking any blocklist changes for FF12 would not be advised.




No issues being tracked which are unique to Aurora


Bug Status
bug 738661 crash in nmsvc from CovenantEyes Marcia was investigating -- any update?
bug 738392 Plugin doesn't render inside a CSS transform on Mac Unable to reproduce the proposed regression
Fix landed on Aurora/Beta today
bug 720987 Focus rings keep growing when repeatedly tabbing through elements Unclear what's needed from QA


  • 10.7 builders coming online. whats that means for 10.6 builders in FF12, FF13, FF14
  • bug 739770 tracking "ship mobile beta from mozilla-aurora" investigations.
    • communications about this change-of-plan
  • bug 731299 Create bouncer links for Aurora downloads



  • Possible Firefox 11 chemspill driver: bug 737784 – WYWSIWYG editor in mambo ceases to visualise following update to Firefox11.
    • We've seen bug reports, support requests, and input feedback
    • From looking at support forums, it appears that TinyMCE versions <3.4.3 (released June 2011) are affected
    • Most reports are from CMS admins (small number of users)
    • Affects recent releases of Prestashop, Drupal, Moodle, concrete5, plone, modx, Mambo, Cascade Server CMS
    • Workaround include: using another version of Firefox or browser, updating the TinyMCE version, or changing the way the TinyMCE editors are loaded
    • Possible ride-alongs if we were to chemspill: bug 725152 – Stereoscopic 3D videos not properly detected and security bugs(?)

Firefox 12 will be a normal release in that we'll be offering a normal update for 3.6.x users. We won't be taking any alternate update path (automatic or with disabled add-on check) until we've successfully deployed a normal Firefox 12 release. (- Asa)



Aurora Queries

Beta Queries