BugSquad/Bug Triage: Difference between revisions
New page: One key process in any software development project is the triaging of bugs and new features. The Sugar project has been part of the triage process used by the OLPC team (See http://dev.la... |
|||
| Line 58: | Line 58: | ||
==Questions== | ==Questions== | ||
Would it make sense to have a Sugar milestone (e.g., Sugar 0.82) that is distinct from the OLPC milestones? | Would it make sense to have a Sugar '''milestone''' (e.g., Sugar 0.82) that is distinct from the OLPC milestones? | ||
Or would it make more sense to have a Sugar | Or would it make more sense to have a Sugar '''component''' that maps to an OLPC milestone? | ||
Would it make sense to add keywords? | Would it make sense to add keywords? | ||
| Line 74: | Line 74: | ||
** ''et alia'' | ** ''et alia'' | ||
The assignment of priorities is the difficult one. We need to come up with definitions and a process: | The assignment of priorities is the difficult one. We need to come up with definitions and a process. A first pass: | ||
:Blocker: | :Blocker: catastrophic failure—Sugar will not run or user experience severely impaired (new features would rarely, if ever, fall into this category) | ||
:High: | :High: important to Sugar user experience—either in terms of performance or usability (these would typically be coupled with the "task" ticket type) | ||
:Med: | :Med: enhancements to non-core features (or enhancements that impact individual activities) | ||
:Low: | :Low: odds and ends | ||
[[Category:Devloper]] | [[Category:Devloper]] | ||