Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Issue triage

Hi Thomas,

My simplified understanding of current severities are:
blocker - to start working on it right away
P1 - important, can wait for next sprint only
P2 - everything else (default)

How adding another level (P3) alone would simplify/systematize it more?

Thanks,
Gennsy

On Fri, Aug 16, 2019 at 1:15 PM <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

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev

Back to the top