EngineeringProductivity/Meetings/2012-01-30: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 6: Line 6:


* bughunter
* bughunter
**
** [jeads] new url submission
** crafting docs and training on how to use bughunter


* eideticker
* eideticker
Line 32: Line 33:
** [mcote] woo almost online again!
** [mcote] woo almost online again!
*** waiting on security review
*** waiting on security review
** [mcote] will need a speedtest review also
** and toolbox, gofaster, etc..


* peptests
* peptests
Line 42: Line 45:
*** [[http://people.mozilla.org/~jmaher/sxs/sxs.html status graph]]
*** [[http://people.mozilla.org/~jmaher/sxs/sxs.html status graph]]
** working on analyzing tp5 and figuring out next steps
** working on analyzing tp5 and figuring out next steps
** [jeads] defined first set of UI changes for
** [jeads] defined first set of UI changes.  Starting to implement


* [[https://wiki.mozilla.org/Auto-tools/Projects/Compatibile_By_Default_Automation addon-compat]]
* [[https://wiki.mozilla.org/Auto-tools/Projects/Compatibile_By_Default_Automation addon-compat]]
Line 58: Line 61:
* A*Team best practices
* A*Team best practices
** [jgriffin] [[https://intranet.mozilla.org/Auto-tools/PulseConfig documented pulse]] server and setup
** [jgriffin] [[https://intranet.mozilla.org/Auto-tools/PulseConfig documented pulse]] server and setup
** [bc] trying to wrap his mind around what is needed and how to coordinate.


== Upcoming Events ==  
== Upcoming Events ==  

Revision as of 21:05, 27 January 2012

New Format

The Overview

  • bugzilla
  • bughunter
    • [jeads] new url submission
    • crafting docs and training on how to use bughunter
  • eideticker
    • [wlach] [checkerboarding tests] are more repeatable and analyzable
    • [wlach] helping ctalbert set up the eideticker machine in mountain view.
      • looking into a CI automation using eideticker.
  • mobile automation
    • [jmaher] robocop is landed and will be running in staging Monday
    • [jmaher] next steps are tpan/tzoom on talos
    • [jmaher] need to resolve some reftest failures
    • [ctalbert] new direction for s1/s2 startup automation
      • [new framework] to run these
      • writing utilities for common automation tasks on live phones
      • will be using instrumentation that is output to adb
  • marionette
    • [mdas] [Automation] for b2g was turned on!
      • tests were written by the b2g team and using the framework already
    • [mdas] [content management] calls are mostly done
    • [jgriffin] writing docs!
    • getting ready for security review next week
  • brasstacks
    • [mcote] woo almost online again!
      • waiting on security review
    • [mcote] will need a speedtest review also
    • and toolbox, gofaster, etc..
  • peptests
    • [mcote] make mozprofile work with proxied locations and permissions for privileged code!
    • next steps: turn back on for try server without live network access.
  • [Signal from Noise]
    • landed ignoreFirst change for talos on m-c
    • working on analyzing tp5 and figuring out next steps
    • [jeads] defined first set of UI changes. Starting to implement
  • [addon-compat]
    • [wlach] defined the platforms in bug 718660
    • [wlach] plan is to run endurance tests with small set of addons
  • WebRTC build hacking
  • A*Team best practices
    • [jgriffin] [documented pulse] server and setup
    • [bc] trying to wrap his mind around what is needed and how to coordinate.

Upcoming Events

All times Pacific Time, click on link to find your timezone

Round Table

* Next week's MC?
* when should we do a documentation update (mcote started this last month)

Misc

Find something you think is cool, interesting, funny, or exciting and put it here