QA/Execution/Web Testing/Meetings/2010-08-27: Difference between revisions
< QA | Execution | Web Testing | Meetings
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
*MDN | *MDN | ||
** Figure out what's next / support level | ** Figure out what's next / support level | ||
*Socorro | |||
** running submitter.py script regularly to submit crash dumps to staging | |||
*Automation | *Automation | ||
** AMO | ** AMO | ||
Revision as of 17:55, 27 August 2010
« previous mtg | Web QA Home | next mtg »
Discussion Items / Updates
- Record number of releases; shipped the following in *four days*:
- AMO 5.11.8
- SUMO 2.2.3
- Plugin Check / Plugin Directory 1.2.0
- Mozilla Developer Network (MDN) 0.9
- Input v1.7 (total redesign!)
- We shipped 5 releases with 218 bug fixes (of all sizes, some quite large)
- QMO's WebQA Tools page - Please add tools you use
- Automation Guidelines - is this up-to-date? In order to have a good case for community involvement, we need to be inviting and clear, and I'd like us to adopt what becomes of this as our coding conventions/review guidelines
Project Status / goals for next week (keep it brief)
- AMO
- Working on 5.11.9
- SUMO
- Plugin Check
- Just keep on top of version-update requests as they come in
- Mozilla.com
- Trying to keep up with mobile, performance, etc. mini-fixes
- Input
- MDN
- Figure out what's next / support level
- Socorro
- running submitter.py script regularly to submit crash dumps to staging
- Automation
- AMO
- SUMO
- page object tests are up and running.