Jetpack/Triage Process: Difference between revisions

Jetpack/Triage Process (view source)

No change in size , 16 April 2012

m

no edit summary

Confirmed users

396

edits

Revision as of 20:09, 12 April 2012 (view source) Mossop (talk \| contribs) (Created page with "Bugs in the Add-on SDK component are aggressively triaged to make sure everyone can understand the importance the triage team (product manager, engineering manager, module owner ...")		Revision as of 18:46, 16 April 2012 (view source) KWierso (talk \| contribs) mNo edit summary Newer edit →
Line 1:		Line 1:
	Bugs in the Add-on SDK component are aggressively triaged to make sure everyone can understand the importance the triage team (product manager, engineering manager, module owner and bugmaster) place on fixing the bug. The goal is transparency for the developers who file bugs and work on the SDK and ~~devleopers~~ who use the SDK and want to understand when things might be fixed.		Bugs in the Add-on SDK component are aggressively triaged to make sure everyone can understand the importance the triage team (product manager, engineering manager, module owner and bugmaster) place on fixing the bug. The goal is transparency for the developers who file bugs and work on the SDK and developers who use the SDK and want to understand when things might be fixed.

	All bugs that are filed should start with an empty priority (--) so the triage team see them at the next triage meeting and can evaluate the importance.		All bugs that are filed should start with an empty priority (--) so the triage team see them at the next triage meeting and can evaluate the importance.