Confirmed users
6,361
edits
QA/Firefox3/TestPlan/PostMortem: Difference between revisions
Jump to navigation
Jump to search
m
→What worked
m (→What worked) |
|||
| Line 11: | Line 11: | ||
* Having a blocking-firefox3 or blocking1.9 flag was key to getting the right bugs triaged. Knowing they were getting triaged each day was comforting that they werent just sitting in the queue. [tchung] | * Having a blocking-firefox3 or blocking1.9 flag was key to getting the right bugs triaged. Knowing they were getting triaged each day was comforting that they werent just sitting in the queue. [tchung] | ||
* Weekly firefox meetings with a structure and progress report for each team. [tchung] | * Weekly firefox meetings with a structure and progress report for each team. [tchung] | ||
* Some items were well documented (content handling, download manager, addons manager) | |||
* QA's push for severe bugs in an RC push was well recieved, but it was a hard push since the bar was higher | |||
* Developers were generally responsive to QA | |||
* Some teams had their own status meetings (Mac meetings, leaks meetings, performance meetings) | |||
* QA began creating own builds (debug builds, leak guage, tryserver builds) | |||
* At first, crash bugs weren't getting much attention and devs were defensive, bug they warmed up over time and cooperated. | |||
* Devs scheduling pushed into QA time initially, but began accepting QA dates. | |||
* Build team was responsive, automation tools helped speed up process. | |||
== What didnt work == | == What didnt work == | ||