Auto-tools/Automation Development/Meetings/130715: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "<small>previous meeting | Meetings | [[Auto-tools/Automation_Development/M...")
 
Line 23: Line 23:


= Roundtable =
= Roundtable =
* TBD
* [Andreea] Bug Priorities
** P1 - critical, constant failures, important enhancements (regressions, tests that fail constantly. I'd say even if skipped)
** P2 - mozmill 2.0 blocker (if release is approaching, this can take higher priority in order to finish in time)
** P3 - not that often failures, medium enhancements
** P4 - new tests - QA needed have priority
** P5 - refactoring, small enhancements
** Dependecies take the blocking bug's priority
*** Our prioritized backlog: https://docs.google.com/spreadsheet/ccc?key=0AgbJACdAek5ndGw5TWNuWWw1VFFzelZHektWRTNaSnc#gid=10


= Goals Overview =
= Goals Overview =

Revision as of 07:55, 15 July 2013

previous meeting | Meetings | next meeting »

Dial in

 # When:     Every Monday at 8:45am PDT/PST
 # Vidyo:    https://v.mozilla.com/flex.html?roomdirect.html&key=PGtLpx3XQGJz
 # Phone:    650-903-0800 or 650-215-1282 x92 Conf# 9654 (US/INTL)
 #           1-800-707-2533 (pin 369) Conf# 9654 (US)
 # IRC:      irc://irc.mozilla.org:6697/#automation
 # IRC logs: http://irclog.gr/#browse/irc.mozilla.org/automation

General

  • Attendees:
    • TBD
  • Chair: TBD
  • Notes: TBD

Last Weeks Action Items

  • [CARRY OVER] Henrik - Start a thread on the public list to collect ideas for the show and tell
  • [DONE] Henrik - Develop patch/update to only enable Mozmill restarts and not user-initiated restarts
    • Not sure what this entry was about, but I'm not going to fix that for 2.0. The bug has been filed btw.
  • [CARRY OVER] Dave, Rob - Discuss gaia-ui tests, autolog, heuristics and html reports

Highlights

  • [%name%] %highlight%
  • New blockers, any updates?
    • %new blockers%
  • You can find all blockers here: http://bit.ly/Tph0NY

Roundtable

  • [Andreea] Bug Priorities
    • P1 - critical, constant failures, important enhancements (regressions, tests that fail constantly. I'd say even if skipped)
    • P2 - mozmill 2.0 blocker (if release is approaching, this can take higher priority in order to finish in time)
    • P3 - not that often failures, medium enhancements
    • P4 - new tests - QA needed have priority
    • P5 - refactoring, small enhancements
    • Dependecies take the blocking bug's priority

Goals Overview

Project Updates

Gaia UI (Dave)

  • Goals progress:
  • TBD

WebAPI (Rob)

  • Goals progress:
  • TBD

WebRTC (Henrik)

  • Goals progress:
  • TBD

Softvision Updates

Desktop Automation

  • Goals progress:
  • TBD

Mobile (Robocop)

  • Goals progress:
  • TBD

Personal Status

For the personal status please check the weekly status updates:

Meeting Notes

The meeting notes for this meeting can be read in the following etherpad:

Action items

  • [NEW] %name%: %task%