Hi folks,
after a weeks stewing, I would like to propose a couple of things for today's Che Sos:
1. Let's kill the "level/xxx" tags: only 3 out of > 1200 open issues have one of those, obviously no-one is using them 2. Triage only adds the "Severity" label, and only for bugs and assigns the issue to a team for planning. The team is free to pass on the issue if they don't think they are responsible. 3. Let's not assign the "triage needed" for kinds task, question or planning
/Thomas
On Fri, 2019-08-16 at 12:15 +0200, tmader@xxxxxxxxxx wrote: HI Y'all,
I think it's great we have dedicated folks looking at new issues every day. Communicating triage results makes our prioritization much more transparent to the development team and the community at large. However, in a post-7.0 world, we shoudl tune our process a bit
Responsibility for planning to milestones should switch away from the triage person back to team leads an PM. Concretely, the triage person should no longer be responsible for assigning a milestone. Instead we should be working more with severities. We have a nice definition of bug severities here ( https://github.com/eclipse/che/wiki/Labels#bug-severities), but in practice, I find them applied in a haphazard fashion. What I would suggest is to add a priority p3 (minor bug, nitpick) and to clarify the meanings of the severities (and give examples of what should be considered blocker/p1, etc.)
I've taken the liberty of adding a topic to the next che-SoS
/Thomas
|
