Bukama commented on PR #129: URL: https://github.com/apache/maven-gh-actions-shared/pull/129#issuecomment-2587680070
> The definitions here are more what I would call Severity than Priority. There are bug tracking systems and projects that make a distinction between the two (e.g. Google's Buganizer) though I recognize this approach is not universal. This was also my thought when I've read the description of the labels, which are all focus on bugs, but don't take features/improvements into account. Can be please add severity labels too to be more specific on bugs? Classic examples for the difference are: * An error which crashes the systems, but happens only under very special circumstances. This can/will have a severity of "high/critical", because the system crashes. On the other side the priority might be low, because occurs only rarely. * A spelling/grammar mistake on the invoice: Severity low (functionality is not affected), but high priority, because it's visible on every customers invoice. P.S. I know that priority is a thing that often does not get maintained, as those may change over time. We have to see how this works out. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
