[Development] Qt 5.6 LTS - who defines criteria what gets "bug fixed"

[Koehne Kai]

> -----Original Message-----
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany.com at qt-project.org] On Behalf Of
> Welbourne Edward
> Sent: Thursday, February 25, 2016 10:33 AM
> To: development at qt-project.org
> Subject: Re: [Development] Qt 5.6 LTS - who defines criteria what gets "bug
> fixed"
> [...]
> I'd also be glad of such a page - I get to do bug triage (setting priority on
> newly submitted bugs) some sporadic weeks and would be glad of some
> guidance on what kinds of bug deserve what priority.  As an
> illustration: when I use Debian's reportbug facility, it asks me about the
> severity (roughly corresponding to priority) of the issue and explains
> carefully (see [0]) what the Debian project's criteria are for each severity
> level.

The current descriptions of the priorities in JIRA [1] IMO aren't too helpful, since they focus too much on impact on a release. But I also feel that the right priority is a computation of several factors, including Severity, Impact, whether it's a regression, and whether there's a workaround.

Based on this I tried to come up with an 'algorithm' for JIRA bug priorities a while ago:

https://wiki.qt.io/JIRA-Priorities

In general I think the prioritization works somewhat, except that we're putting way too many things in the P2 basket.

Kai

[1]: https://bugreports.qt.io/secure/ShowConstantsHelp.jspa?#PriorityLevels