[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Upstream bugs... (Qt)
From:       Ian Wadham <iandw.au () gmail ! com>
Date:       2009-11-27 2:02:21
Message-ID: 200911271302.21692.iandw.au () gmail ! com
[Download RAW message or body]

On Friday 27 November 2009 1:39:02 am Alexis Ménard wrote:
> Since Qt Development Frameworks have an open bug tracker i would like to
> invite people to report bugs into it.
> 
> As you can see in this bug (https://bugs.kde.org/show_bug.cgi?id=210146),
> it's marked as CLOSED UPSTREAM. But if nobody reports the bug in Qt's
> bugtracker, there is no way for Qt developers to know that the bug exists
>  (i knew it because i'm following Plasma). Right now filtering by
> closed/upstream gives Trolls nothing since there is not enough information.
> I'm sure there are some other bugs that need a proper report.
> 
> So if you marked the bug CLOSED UPSTREAM please create one in the Qt
> bugtracker and link it into the KDE bugtracker so people can follow it.
> 
> Don't be afraid Qt's bugtracker is friendly :D.
> 
How friendly is it? ... ;-)

Re https://bugs.kde.org/show_bug.cgi?id=197686  I reported this in your
task tracker around 7 Oct, with a short Qt-only test case by Christoph Feck.

About 2 weeks later I got an "auto-reply" email to say it had been flagged as
New Issue N262490.  A few hours later, another email said it was accepted
as task 262507 (22 Oct 09).  On 28 Oct 09 a further email said that the
public bug-tracking system was now operational and my bug could be
found at http://bugreports.qt.nokia.com/browse/QTBUG-4965 after which
I have received no further emails (as I would have from Bugzilla).

Looking at that link, and clicking on Transitions I find the bug was "Opened"
on 23 Nov 09 (a month after it got a number), it was Verified within an hour
and Closed on 26 Nov 09, 3 days later, though with what result I cannot
tell, going on that information.  Did someone fix it?

Clicking on "All" I find that Thierry Bastian might have fixed it (there are
some strange numbers there).  So what do I have to do to close the circle
and test the fix against my application?  If I can find out that the
application works now, I can remove my workaround code before the
KDE 4.4 release.

Regarding friendliness, the mills of Qt grind slowly but no doubt exceedingly
fine, however from here the process looks rather bureaucratic and slow and
there is no feedback after the bug is registered, even though I have followed
all your required procedures.  Must I keep checking the link every few days?
And what does it tell me anyway?  And why all these numbers (issue #, task #
and bug # --- Bugzilla has just one per report)?

How do I find out if/when a Qt bug has been fixed?  And how do I get a copy
of the fix so as to do end-to-end testing of my application?  And can this 
information be made readily available to all reporters of Qt bugs (not just
me), now and in the future?

All the best, Ian W.


 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]