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

List:       kde-devel
Subject:    bugs.kde.org, whichlist and problems
From:       Felix Seeger <felix.seeger () gmx ! de>
Date:       2002-07-14 10:04:45
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

I think bugs.kde.org is not good to use at the moment.


The main Problems for me:
- - Finding dublicates is not really possible.
  The most bugs which are listed are not usefull and I wonder why they are 
listed.
- - The search in the database is to slow, sometime it is very very very very 
slow.

Good things:
The crash option is great.

How to make it better:

1.
If the Severity it entered before the search in the database, the matches will 
be more usefull.
- - I don't need a wishlist entry if I report a crash or a bug.
- - If I report a wish, I don't need to see bugs.
Maybe this will speed up the search.
2.
The matches for the package for that I report a bug should be listed first.
Maybe you can create a kdelibs hit list, so if one of the keywords are entered 
some kdelibs bugs are displayed first.
3.
Bugs with no package (spam) which are closed should not be listed in the 
dublicate list.


hope that helps
have fun
Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9MUy9S0DOrvdnsewRAgjJAJ9VbmMfzgENufH4PqPrRbmU8H1zMQCfclsj
Dw60rqeOadUc/J3EmTcmeX8=
=r6LM
-----END PGP SIGNATURE-----

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]