Release Management/Engineering Dashboard: Difference between revisions

Jump to navigation Jump to search
Line 6: Line 6:


= Design =
= Design =
Goal: To ensure that critical bugs are fixed before a necessary deadline, non-critical fixes still get attention in a timely fashion, and to make obvious what work is assigned or could be assigned to an individual.
== P1 Requirements==
* Need an account created on bugzilla that can view security bugs
* Drilling down the org chart to see bugs per individual and then grouped by team
** See [https://github.com/mozilla/bztools/blob/master/scripts/phonebook.py phonebook] script here that already does a little bit of this
** We'll want to improve our ability to track based on org chart (outreach to managers to put 'manager' in their details, for example, or auto-grouping people based on depth? Other ways to track who is on what team)
* Being able to drill down a bugzilla chart to see related bugs (Could add a library in https://github.com/mozilla/bztools that will provide related bugs quickly for a bug)
== P2 Requirements ==
* Graphs to see the bug counts in each list over time - will help managers track progress as well
* Ability to assign bugs and change priority/criticality through the interface
== Dashboard spec (by individual)==
<pre>
For work in (Beta, Aurora, Critical, Feature, Nightly) queries:
{{ CHANNEL }}: {{ VERSION }} - {{ STATUS }} (eg: FF18 - Beta 5 goes to build today, shipping on 1/7)
* Sec-critical bugs
* Tracking non-sec bugs
* Unassigned critical bugs in watched components (please take these!)
* Your team's critical bugs
</pre>
<pre>
== Dashboard spec (by component) ==
Beta: FF13 (code freeze passed, released in 1 day)
Critical bugs in these components
Aurora: FF14 (code freeze in X days, released in Y days)
Critical bugs in these components
Other high priority work
High priority bugs in these components
Feature bugs
Feature bugs in these components
== Definitions needed ==
Define "critical" bug queries, with weighting based upon query, priority and criticality
tracking for release or blocking-fennec, combined with other queries
Define "other high priority" bug queries, with weighting based upon query, priority and criticality
topcrash (startupcrash before reproducible before others sorted by first report)
sg: (crit before moderate, sorted by first report)
performance (?)
Define "feature" bug queries
basecamp
k9o
Has '[feature]' in the whiteboard


= Schedule =
= Schedule =
Confirmed users
4,467

edits

Navigation menu