Do not mark upstream bug as Resolved in kde bug system

Leon Feng rainofchaos at gmail.com
Mon Feb 11 04:41:26 UTC 2013


Today I read a blog post about "Yet Another KDE QA Failure" here:
http://www.freehackers.org/thomas/2013/02/10/yet-another-kde-qa-failure/

In my opinion, the root cause of this problem is the kde bug system. When
we mark a bug upstream, it is resolved. But in reality, it is *not*. The
bug is resolved only when upstream fix it.

I have the same doubt when I first triange and mark the bug as upstream.
This time,  the gentoo one shows how much damage a wrong status mark could
bring up.

The proposal: The kde bugzilla system should be changed. Do not mark  bug
resolved when we conclude it is upstream bug. Only mark a upstream bug
resolved when upstream actually fix it.

Feng Chao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kde-www/attachments/20130211/72bd63b0/attachment.html>


More information about the kde-www mailing list