kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

The problem with this is interpretation.  One man's important is another
man's don't care.  The other issue is that there is no way to prevent
anyone for changing the severity level any time they want.  It would be
nice if we could restrict who sets the bug severity level to the
kicad-bug-squad members.  Unfortunately, launchpad doesn't allow for
this or it would have been done a long time ago.  I'm fine with trying
it and see how it works.  If it doesn't work, we can always try
something else.

On 2/19/2018 8:57 AM, Jeff Young wrote:
> I’d like to have 5 priority levels:
> 
>   * crash with data loss
>   * crash with no data loss
>   * high-impact with no viable workaround
>   * high-impact with workaround
>   * low-impact
> 
> 
> Right now we’re sort of lumping the last 2 into “Low”, which I find
> troublesome.
> 
> On the other hand, we’re pretty good at reacting to the top two, so I’d
> rather lose that distinction (which we could re-capture in a tag).  
> 
> So the proposal would be:
> 
> Severe: crash (tag with data-loss if applicable)
> High: high-impact with no viable workaround
> Medium: high-impact with workaround
> Low: low-impact
> 
> Thoughts?
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>