[Development] Long-lived P1 issues

[Kai Köhne]

> -----Original Message-----
>[...]
> > (Clicking the ? button next to the priority field in Jira shows the
> > following definition for P1: "Urgent and Important, will STOP the
> > release if matched with set FixVersion field. This includes
> > regressions from the last version that are not edge cases; Data loss;
> > Build issues; All but the most unlikely crashes/lockups/hanging;
> > Serious usability issues and embarrassing bugs & Bugs critical to a
> > deliverable.")
> 
> Was there any outcome from this discussion? Like, re-evaluating priority
> levels and what they mean in terms of release blockers?

I don't think there was any sort of decision or consensus. Which means we keep working with the status quo, as documented in https://bugreports.qt.io/secure/ShowConstantsHelp.jspa?#PriorityLevels

I suggest to simplify P3, P4 descriptions though to

  P2: Important, should be fixed.
  P3: Should be fixed.

(the mentioning that they don't block a release probably stems from a time where P1 meant blocking the release. This is not the case anymore, so what's the point in highlighting that a P2, P3 doesn't block a release?).

Regards

Kai