- Time: Tuesday at 9:15 AM PST / 12:15 PM EST / 5:15 PM UTC.
- Place: Mozilla HQ, Sick Bay (Vidyo room "Services")
- Phone (US/Intl): 650 903 0800 x92 Conf: 98616#
- Phone (Toronto): 416 848 3114 x92 Conf: 98616#
- Phone (US): 800 707 2533 (pin 369) Conf: 98616#
Ops
Hardware
Projects
Other Notes
Engineering
Sagrada
Metrics (rmiller/vng)
- finishing the node.js metlog client. adding support for client configuration (including sender, global settings, filters, and plug-ins) from a JSON format
- setting up a complete metlog stack with statsd+graphite+pencil running within vagrant
SyncStorage/AITC (rfkelly)
Done:
- Worked through some loadtesting weirdness in AITC stage. Not exactly *fixed* yet, but at least I understand what was going on.
- Various Sync1.1 tweaks in response to folks hosting their own server.
- Preparing for a Sync1.1 release from trunk, so we can run metlog in the wild.
Next:
- Get Sync1.1+metlog ready to launch.
Queuey (bbangert/hannosch)
Token Server (tarek/alexis)
Signing (rtilder)
- Services Operations will be taking over running the hardware for the signing service and HSMs.
- Will be working with jbonacci and jv's crew to make it work
Sync
Firefox Sync (gps)
Android Sync (rnewman/nalexander/liuche)
Notifications
Client/Server (jbalogh/jrconlin)
QA
Client Testing and Sign-offs (tracy)
- Sync exposed an OOM crasher (bug 756549 - Sync updates cause explosive memory usage leading to OOM) caused by the fix in bug 723350 - Simplify gcMallocBytes accounting
- That fix was backed out this morning
- I'll attempt to confirm. But I wasn't reliably reproducing in recent testing.
- Verified several bug fixes around key reallocation on Android.
- Verified J-Pake screen rotation and screen sleep fixes.