DOM/Triage

From MozillaWiki
< DOM
Revision as of 20:16, 21 January 2016 by Overholt (talk | contribs) (Add rough suggested frequencies)
Jump to navigation Jump to search

New bugs - do this daily

Let's ensure newly-filed bugs in a variety of DOM-ish components are actionable as soon as possible after their filing. This doesn't mean we're going to fix them sooner but that they'll be fixable when we get around to attempting to fix them. Inspiration taken from Platform/GFX/TriageSchedule.

  • is this bug in the correct component?
  • ask for any missing information (ex. platform, URL, STR)
  • do we need a regression range?
  • CC people who should be CC'd
  • if this is a bug you think we should fix soon, assign or needinfo the person
  • if this is about a low-frequency intermittent bug that isn't on the top orange list, it's probably ok to ignore it
  • note: an assumption here is that bugs with non-nobody assignees are progressing towards a fix in some way
  • do we need to have a 'dom-noted' whiteboard to exclude bugs that have been looked at?

New "DOM" bugs filed in the past 48 hours

Orange bugs - do this daily if possible

  • are any of these in areas you can fix?
  • are any of these in DOM-ish components that aren't getting traction? can you politely nudge someone on the team to take a look?
  • are any of these obviously in the wrong component and moving them would help get closer to a resolution?

Top orange bugs

Chipping away at bugs that may have been forgotten - doesn't have to be done daily

  • is there anything needed to make this bug actionable?
  • is this bug even valid anymore?

25 "DOM" bugs (there are more, this is just 25 of them) that haven't been touched for at least 4 weeks