Skip navigation.
KDE Developer's Journals

Too Many Bugs

awinterz's picture

I spent many hours the past couple months bug fixing two of my favorite KDE PIM applications (KOrganizer and KMail). And I'm not even making a small dent in the bug pile.

700+ Open KOrganizer Bugs

2600+ Open KMail Bugs

Sure, many of them are wishes. But many are real bugs and crashes too.

It would really help if people could upgrade to KDE 3.5.5 (or at least KDE 3.5.4) and then let us know about bugs that seem to be fixed. Every little bit helps. If the bug is still present, any extra info you could attach to the bug report may also give us a hint. Backtraces are invaluable when going after crashes.

No need to blast us with simple "bug still present in KDE 3.5.5" messages.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
bram schoenmakers's picture

KDE PIM bug triage day

I think it would be really useful if we would pick a Saturday or Sunday to mimic the same we did some weeks ago for Konqueror: one day for validating, squashing and confirming bugs.

Bram Schoenmakers
KDE Netherlands (www.kde.nl)

suslikreal's picture

No need to blast us with

No need to blast us with simple "bug still present in KDE 3.5.5" messages.

How would I know then, that a horde of other ppl already checked for this bug in 3.5.5? If I were (and will) go look for applicability of the bug to updated KDE, i would find a small note like that helpfull.

Is there any other way of setting "checked with current version, still valid" flag for chain-bug-verifiers?

awinterz's picture

Re: No need to blast us with

Yeah, good point.
AFAIK bugs.kde.org doesn't have a VALID-FOR-VERSION=x.y.z flag.

So I agree with you: a "still present in 3.5.5" message would be a good thing too.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.