ProgramManagement/Firefox/2011-Q3-Goals: Difference between revisions

No edit summary
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Top 3 list==
If we could only achieve 3 goals, I would prioritize the following...
* P1 Socorro features
** Our crash reporting has not really caught up to the changes we made for rapid release, this has to be fixed.
* Hiring - we need dedicated PMs for...
** e10s
** Tracking product features
** Handling add-on, 3rd party, blocklist related tracking
* Spec/requirements for project management tool/dashboard
** The feature pages are too hard to maintain long term. We need more than this and bugzilla to keep track of what is going on.
==Stability==
==Stability==


===Socorro features===
===Socorro features===


* Reports that are based on channel+build_id instead of only version - {{bug|540687}} (2.1, topcrashers), {{bug|657400}} (untargeted, crashes per user)
Ensure that the following are implemented in Socorro in the Q3 timeframe.
**  [https://wiki.mozilla.org/CrashKill/RapidReleaseCrashes Rapid release crash monitoring]
* {{bug|642336}} (untargeted) - summarized overview for signature
* Correlation reports need to become better ({{bug|642325}} - untargeted).
* Content crashes ({{bug|578687}} - 2.2)
** Fennec already sends a significant portions of its crashes with a "content" process type. Not shown in "Browser" default view of topcrashers.
** We need "content" as a category in the topcrashers report.
** The summarized overview from {{bug|642336}} should include how many of those crashes are what process type - "content" being one of those.
** Crashes per user don't include content crashes, which might be a factor in why Fennec graphs look like it's very stable.
* Explosive crash detection ({{bug|629062}} - 2.1) - implement the prototype algorithm in Socorro itself.
* More items from [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=V3-UItweaks&sharer_id=5189 "UItweaks" list] - pick some specific ones?


New reports - '''Open from Q2 list''':
* P1
* hang pairs ({{bug|637661}} - 2.1) - try to get this for non-throttled builds, match when match is available on throttled builds.
** Reports that are based on channel+build_id instead of only version - {{bug|540687}} (2.1, topcrashers), {{bug|657400}} (untargeted, crashes per user)
* Integration of "external" reports: {{bug|640237}} - 2.1, {{bug|640238}} - 2.1, {{bug|640241}} - 2.1, {{bug|640242}} - 2.1, {{bug|641487}} - 2.1
** hang pairs ({{bug|637661}} - 2.1) - try to get this for non-throttled builds, match when match is available on throttled builds.
* DLL Directory ({{bug|577613}} - 2.1)
** Integration of "external" reports: {{bug|640237}} - 2.1, {{bug|640238}} - 2.1, {{bug|640241}} - 2.1, {{bug|640242}} - 2.1, {{bug|641487}} - 2.1
 
* P2
** DLL Directory ({{bug|577613}} - 2.1)
** Content crashes ({{bug|578687}} - 2.2)
** Explosive crash detection ({{bug|629062}} - 2.1) - implement the prototype algorithm in Socorro itself.
** More items from [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=V3-UItweaks&sharer_id=5189 "UItweaks" list] - pick some specific ones?
 
* P3
** {{bug|642336}} (untargeted) - summarized overview for signature
** Correlation reports need to become better ({{bug|642325}} - untargeted).


===Top crashes===
===Top crashes===


* Help launch and track a project to resolve a top crash appearing in the top 20 list for a major release.
** ie: Class of GC crashes like js::gc::MarkObject.
** Success criteria here is something to check in that reduces the crashes in a particular area.
===General===
* Inclusion of Fennec for top crash monitoring, reporting and weekly crashkill meeting.
== Features ==
* Adding comments to plugin crashes - [https://bugzilla.mozilla.org/show_bug.cgi?id=648675 bug 648675]
** Get resourced and implemented.


==General Project Mgmt==
==General Project Mgmt==


* Program and project management staffing plan - with list of projects and hires.
* Six month engineering program and project management staffing plan
*
** List of projects, roles and basic skills required (junior, senior).
* Outline for a project management tool to track features and their progress (shared goal with Deb Richardson)
** Step 1: Scenarios and use cases for PMs to track features.
** Step 2: Detailed spec and requirements for PM tool(s).
* Hire 2-3 program/project managers
 
==Process==
 
* Help revamp the current meeting schedule (joint goal with Christian)

Latest revision as of 20:51, 19 July 2011

Top 3 list

If we could only achieve 3 goals, I would prioritize the following...

  • P1 Socorro features
    • Our crash reporting has not really caught up to the changes we made for rapid release, this has to be fixed.
  • Hiring - we need dedicated PMs for...
    • e10s
    • Tracking product features
    • Handling add-on, 3rd party, blocklist related tracking
  • Spec/requirements for project management tool/dashboard
    • The feature pages are too hard to maintain long term. We need more than this and bugzilla to keep track of what is going on.

Stability

Socorro features

Ensure that the following are implemented in Socorro in the Q3 timeframe.

  • P2
    • DLL Directory (bug 577613 - 2.1)
    • Content crashes (bug 578687 - 2.2)
    • Explosive crash detection (bug 629062 - 2.1) - implement the prototype algorithm in Socorro itself.
    • More items from "UItweaks" list - pick some specific ones?
  • P3
    • bug 642336 (untargeted) - summarized overview for signature
    • Correlation reports need to become better (bug 642325 - untargeted).

Top crashes

  • Help launch and track a project to resolve a top crash appearing in the top 20 list for a major release.
    • ie: Class of GC crashes like js::gc::MarkObject.
    • Success criteria here is something to check in that reduces the crashes in a particular area.

General

  • Inclusion of Fennec for top crash monitoring, reporting and weekly crashkill meeting.

Features

  • Adding comments to plugin crashes - bug 648675
    • Get resourced and implemented.

General Project Mgmt

  • Six month engineering program and project management staffing plan
    • List of projects, roles and basic skills required (junior, senior).
  • Outline for a project management tool to track features and their progress (shared goal with Deb Richardson)
    • Step 1: Scenarios and use cases for PMs to track features.
    • Step 2: Detailed spec and requirements for PM tool(s).
  • Hire 2-3 program/project managers

Process

  • Help revamp the current meeting schedule (joint goal with Christian)