QA/QMO
< QA
Jump to navigation
Jump to search
_ QMO (quality.mozilla.org) is the new Home of Mozilla QA.
QMO was completely redesigned in Fall 2008. Our goal with the redesign was to make it easier for anyone to get involved with Mozilla QA, provide existing community members a chance to get better organized, and promote the community projects and events that people can work on.
You can find below the contact information for QMO:
Contacts
General
- Overall QMO Lead (technical lead, coordination with webdev etc)
- Tomcat Email
- Content Lead
- Aakash Email
- Development Lead
- Paul Craciunoiu Email
- Community Team
- Paul Booker Email
- Mark Wong
Project Development
Planned Releases
Past Releases
QMO meeting notes
Here is the link to the QMO meeting notes for Webdev+QA tracking: QA/QMO/QMOdev_Meeting_Notes
QMO Improvement Projects
- Discoverability Project
- Aakash Email
- Docs Page Redesign Project
- Aakash Email
Release Guidelines
Definitions
- Milestone release = a release made up of any number of bugs that are part of a goal for QMO
- Security release = a small and quick release made up of security bugfixes ONLY. A security release is not part of the milestone releases (no milestone number is required here)
- Push = pushing the code changes from the SVN production branch to the live site.
Best Practice
- Security related bugs are committed to stage, verified, committed to production and pushed as quickly as possible.
- Regular (not security related) bugs are only committed to stage at first.
- Drupal has fairly frequent security releases. To make it quick and easy for those to be pushed live when they come out, other bugfix code should not be committed to production until it is ready for the milestone release.
- Bugs are verified on stage before the push
- Code from verified bugs is committed to production on (or very close) to push date
- Bugs are re-verified on production after the push
- Bugs that have not been committed to production are postponed to the next milestone
QMO Content Teams
| Purpose | Focus | Assignee |
|---|---|---|
| BUGS | Bugzilla queries, triaging, logging, regression finding, etc | Stephen-Juan-Aakash |
| DATA | Metrics, crash analysis, hendrix feedback, bug stats, etc | Al-Henrik |
| CODE | QA tools, applications, test automation, test development, community projects, etc | Clint-Tomcat-Martijn-Bob-Mikael |
| CODE COVERAGE | Code Coverage of Firefox Browser | Murali |
| TEST | Focus: Test case writing, Litmus related stuff, release testing, exploratory testing, etc | Marcia-Tracy-Tony |