[Qt-interest] (Qt support salesforce "downgrade", bug priorities) (was Qt for the iPad?)
Andreas Pakulat
apaku at gmx.de
Wed Apr 14 11:13:45 CEST 2010
On 14.04.10 18:04:48, Ross Bencina wrote:
> Thiago Macieira <thiago at kde.org> wrote:
> >As for fixing bugs, that's about priorities: yours and ours will not always
> >match. The team has a lot to do and fixing the P0s and P1s as well as
> >getting
> >the releases out are very important. (Where P1 means "will stop the release
> >from happening" and P0 means "stops Qt development itself so stop whatever
> >you're doing and do this NOW")
>
> While we're on the topic of bug classification... I would like to see any
> cosmetic rendering bug which makes an app look broken (ie badly computed
> update rects which break redraws) raised to P0. I have had support tell me
> that rendering bugs will not be fixed in a minor update because they are not
> "critical" enough. This is completely unacceptable. What commercial app
> would ship with a redraw bug -- like lines corrupting a widget due to
> un-updated regions when scrolling?
Maybe you're writing apps where 100% correct looks are very important, but
I think there are apps where the functionality is more important to the
customer than a graphical glitch.
Andreas
--
Beware of low-flying butterflies.
More information about the Qt-interest-old
mailing list