Account confirmers, canmove, Confirmed users
2,357
edits
No edit summary |
|||
| Line 25: | Line 25: | ||
==Priorities== | ==Priorities== | ||
;P1: | ;P1: All other work stops, all team focuses on it, our product is broken. | ||
;P2: | ;P2: This is important enough that we cannot *not have* someone assigned to it and work on it. It might be a new feature or a bug that affects many users. Also, a bug that blocks someone else's work. | ||
;P3: | ;P3: We recognize this needs to be done, but we won't work on it until all P2s are assigned: "I'm not sure exactly what I should be working on right now, so I'll assign one of P3s to myself and start hacking on it." | ||
;P4: | ;P4: This would be nice to have, but is not crucial and doesn't block us. Usually, a good-first-bug that we can afford leaving open for a newcomer to pick up. | ||
;P5: | ;P5: Not used. | ||
==Severity== | ==Severity== | ||