Bugzilla keywords and bug priority policy for the release

[halla at valdyas.org]

On 2026-03-10 12:11, Dmitry Kazakov wrote:
> Hi, all!
> 
> We had a small discussion on IRC about bug priorities and bugzilla
> management, and we got to the following conclusions:
> 
> 1) Krita 6.0.0 (based on Qt6) will be released as an "unstable"
> version of Krita for testing purposes only. Krita 5.3.0 (based on Qt5)
> will be a real "stable" version. [1]
> 2) Hence Qt6-only bugs are considered as low-priority for now (until
> the release is done)
> 3) If a Qt6-only bug is a crash bug, then is should be fixed before
> the release to make sure that distribution builds don't crash for
> users, whose distributions don't provide Qt5 anymore.

Yes, that sounds reasonable, also because this also means that wayland 
bugs aren't release blockers anymore.

> 
> Based on that I think we should use the following rules for keyword
> assignment on bugzilla:
> 
> * `qt6` --- the bug is reproducible on Qt6 only, on any operating
> system/platform
> * `wayland-only` --- the bug is reproducible in the native Wayland
> sessions, i.e. it can only happen in Krita 6.0.0 and should go
> together with `qt6` tag
> * `regression` --- the bug is **not** reproducible in Krita 5.2.16 and
> **is** reproducible in Krita 5.3.0. The bugs reproducible in Krita
> 6.0.0 only cannot be considered a regression for now
> * `release_blocker` --- this is a critical bug in Krita 5.3.0 and
> should be fixed before the release. Bugs in Krita 6.0.0 can be
> considered as release blockers only if they are crash or dataloss
> bugs.

I'm fine with that.


> 
> What do you think about that?
> 
> [1] - we need to discuss how to treat this requirement in the layout
> of downloads.kde.org [1] and in AppImage updaters.--
> Dmitry Kazakov
> 
> Links:
> ------
> [1] http://downloads.kde.org

I'm not sure how to handle that...