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

List:       kde-devel
Subject:    Reporting bugs
From:       Mikolaj Machowski <mikmach () wp ! pl>
Date:       2003-09-11 16:01:49
[Download RAW message or body]

Hello,

Official way of reporting bugs is: bugs.kde.org,mail-list, mail to author

I understand merits of bugs.kde.org but it has also its drawbacks. Eg. for 
dial-uper going through all this pages is costly.

Probably in this hot time (preparing stable 3.2 release) nobody will have 
enough time but it would be good to have mail front end to report bugs.
Template should looks like:

Summary: moving whole description to summary if summary is empty
Product: korganizer
Version: CVS
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: calendar conduits
ReportedBy: mikmach@wp.pl
Version:           CVS (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.2.2 
OS:          Linux

Description:
When summary is empty whole description is moved to Summary field. This is 
disurbing. Better solution would be cut only first line and move it to S.

Beside Description: field all others should be in one line. If field is 
empty, return to sender with explanation. Also send explanation of all 
fields and possible values if bugs@kde.org have in subject help or 
something.

To improve chances of good forms it could have mechanism of one-way mailing 
list. When subscribing whole insctruction would be send back to subscriber. 
He/she could use it later as reference.

At least current mechanism of reporting bugs in applications could use kmail 
and queuing...

m.
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]