Qt bug handling suggestion

[George Goldberg]

On Fri, Dec 12, 2008 at 1:26 PM, Andras Mantia <amantia at kde.org> wrote:
> Hi,
>
>  In our bugzilla there are some bugs that are believed to be bugs in Qt, not
> in KDE, yet they affect how KDE looks and works. They are right now under the
> kdelibs product, qt component, here is  a link  to them (hopefully usable):
> http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdelibs&component=qt&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=[Bug+creation]&type0-0-0=noop&value0-0-0=
>
>
> (or http://tinyurl.com/6yv7q8 until it expires).
>
> The problem with this is that Qt developers don't read our bugzilla and we
> cannot be sure that the reporter created a Qt bug report as well. Actually I
> think it is safe to assume that he did not. And even if he did, we don't know
> if it was solved, was rejected or what is the status, so we cannot act in any
> way.
>
> I have two suggestions:
> 1) the bugsquad team would do a kdelibs/qt day and for the reports that are
> still valid would create a Qt report and link the Qt task number into the bug
> report.
>
> 2) for new bugs whoever reviews the bug and decides it is in Qt, please create
> a corresponding Qt report and link the task number into the KDE bug report.
>
> I think this would make a better Qt and a better KDE in the future.

Great idea! I'm sure we can get a bug day sorted out to deal with them
in no time :)


---
George Goldberg