QA/Firefox3/TestPlan/PostMortem: Difference between revisions

m
no edit summary
mNo edit summary
Line 8: Line 8:
== What worked ==
== What worked ==
* 8 alphas, 5 betas, and 3 RC builds.  With 16 builds leading up to the final release, i felt there was lots of adequate testing on solidifying the release. [tchung]
* 8 alphas, 5 betas, and 3 RC builds.  With 16 builds leading up to the final release, i felt there was lots of adequate testing on solidifying the release. [tchung]
* Colloborative efforts by build and QA team on each milestone release.  As we had more, we moved quicker and more careful on our testpasses. [tchung]
* Colloborative efforts by build, QA team, and web team on each milestone release.  As we had more, we moved quicker and more careful on our testpasses. [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]
* 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]
Confirmed users
6,361

edits