QA/Desktop Firefox/Meetings/2010-06-01: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with '<small> « previous mtg | Desktop Firefox QA Home | next mtg » </small> '''…')
 
 
(6 intermediate revisions by 2 users not shown)
Line 14: Line 14:
= Agenda =
= Agenda =
* 3.5.10 QA Status (abillings/juanb)
* 3.5.10 QA Status (abillings/juanb)
** Done but waiting for 3.6.4 in order to ship. Will ship same day as 3.6.4.
* 3.6.4 QA Status (abillings/juanb)
* 3.6.4 QA Status (abillings/juanb)
** [https://wiki.mozilla.org/Releases/Firefox_3.6.4/Test_Plan#Schedule 3.6.4 Schedule]
** [https://wiki.mozilla.org/Releases/Firefox_3.6.4#Current_Schedule 3.6.4 Schedule]
** Final ship date currently planned for 6/1.
** Final ship date currently planned for sometime very soon.
*** Was 6/1 but Beta went out on 5/28. Crash data and reports need to be evaluated.
*** Final ship date set on 6/3 or so.
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20flag%3Aapproval1.9.2.4%2B%20-status1.9.2%3A.4-fixed&order=map_assigned_to.login_name,bugs.bug_id Fixed necessary for release of 3.6.4]
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20flag%3Aapproval1.9.2.4%2B%20-status1.9.2%3A.4-fixed&order=map_assigned_to.login_name,bugs.bug_id Fixed necessary for release of 3.6.4]
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.2:.4%2B%20-status1.9.2:.4-fixed&order=map_assigned_to.login_name,bugs.bug_id Bugs under investigation for 3.6.4]
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.2:.4%2B%20-status1.9.2:.4-fixed&order=map_assigned_to.login_name,bugs.bug_id Bugs under investigation for 3.6.4]
Line 22: Line 25:
* Firefox 4.0 - (juanb)
* Firefox 4.0 - (juanb)
** Volunteers?
** Volunteers?
** Assignments to be done today.
** [https://spreadsheets.google.com/ccc?key=0AmIl7oXCZpT6dGltcGFaTHRhcmVIMDBrU0JEZG5GUGc&hl=en Feature assignments] to be done today.
* 3.7a5 - next alpha (juanb)
* 3.7a5 - next alpha (juanb)
* Roundtable
* Roundtable
** QA Team and Firefox 4. What's our role?


= Takeways and Action Items =
= Takeways and Action Items =
* 3.5.10/3.6.4 not shipping today. We need a little more baking time and some bug investigation.
* What's the 3.7a5 schedule and what does it mean to the Beta 1 schedule when we are so close to the end of June? (juanb)
** Need to bring this up at platform meeting
* Unassigned features will be assigned by tomorrow morning (matt, juanb)
* Create a page for Firefox 4 feature tracking (juanb)
* Create, if not already, a per-feature template page calling out the information we need to gather per feature: developer interview questions, what's covered by testing, what isn't, what is automated, who are the people involved, reference links, schedules, weekly progress, current state, risk, ... (juanb)
** Revise existing template
* We need meta criteria per milestone where we identify what should be minimum set of QA requirements to ship these milestones (juanb)
* We might need spreadsheet templates tracking work related to features, which might not be captured by high level wikis or spreadsheets. Henrik will propose a template (whimboo)
* 3.7 BFT work due this Friday (all)

Latest revision as of 17:52, 1 June 2010

« previous mtg | Desktop Firefox QA Home | next mtg »

Desktop Firefox QA Team Meetings

  • Every other Tuesday at 10:00AM Pacific
  • Zombocom Conference Room (3rd Floor)
  • 650-903-0800 or 650-215-1282 x92 Conf# 262 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 262 (US)
  • irc.mozilla.org #qa for backchannel


Agenda

Takeways and Action Items

  • 3.5.10/3.6.4 not shipping today. We need a little more baking time and some bug investigation.
  • What's the 3.7a5 schedule and what does it mean to the Beta 1 schedule when we are so close to the end of June? (juanb)
    • Need to bring this up at platform meeting
  • Unassigned features will be assigned by tomorrow morning (matt, juanb)
  • Create a page for Firefox 4 feature tracking (juanb)
  • Create, if not already, a per-feature template page calling out the information we need to gather per feature: developer interview questions, what's covered by testing, what isn't, what is automated, who are the people involved, reference links, schedules, weekly progress, current state, risk, ... (juanb)
    • Revise existing template
  • We need meta criteria per milestone where we identify what should be minimum set of QA requirements to ship these milestones (juanb)
  • We might need spreadsheet templates tracking work related to features, which might not be captured by high level wikis or spreadsheets. Henrik will propose a template (whimboo)
  • 3.7 BFT work due this Friday (all)