[Digikam-devel] # of B.K.O entries - was: [Bug 137958] 0.9rc1crashes

Gilles Caulier caulier.gilles at gmail.com
Sat Jun 2 07:55:12 BST 2007

2007/6/1, Arnd Baecker <arnd.baecker at web.de>:
> On Fri, 1 Jun 2007, Gilles Caulier wrote:
> > No need to full B.K.O with unresolvable files (:=)))
> ;-)
> The B.K.O  currently 323 open bugs just for digikam ...
> What about a bug-squashing week-end at some point,

totally agree.

to go through all bugs, see if they are still valid, try
> to get fresh feed-back, or even provide fixes?
> (This is also something where non-coders could contribute!)

Absolutly. All Crash reports must be do in priority.

And also :

- moving bugs on the right component if necessary.
- post messages to get more debug informations if necessary (gdb, valgrind).
- post messages to get more context informations to reproduce the bug.

Also - is there a way to mark some bugs to be addressed
> at some later stage (i.e. 0.9.3, ....)?
> Somehow the KDE bug tracker does not seem to be that feature-rich ...

because you need more right to do it. Here, with my account, i can do it.

If you is interressed to help us in this task (and we need really help for
that), you need to contact bugzilla admin to cahnge your account. I'm not
admin myself, i cannot do it...

On B.K.O page, you can see that it maintened by "webmaster at kde.org". I'm not
sure if it's the right way to change bugzilla account properties, but i
cannot find others way...


Best, Arnd
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20070602/c25f7ec2/attachment.html>

More information about the Digikam-devel mailing list