[drkonqi] [Bug 317139] Upload Backtraces only as Attachment to Bug Report instead of posting it in the Comment

[Jekyll Wu]

https://bugs.kde.org/show_bug.cgi?id=317139

Jekyll Wu <adaptee at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Jekyll Wu <adaptee at gmail.com> ---
Well, if you consider how developers/triagers read mails sent for new crash
report in their favorite mail clients , you will realize it is bad idea to only
add short summary in the mail and put full information as attachment : the
summary is often not enough to show what the real problem is, so I will need to
open the attachment for full information in order to see which component is
actually problematic and then reassign if necessary.  Really inefficient.

Another thing is attachment is unsearchable through bugzilla, really bad for
identifying duplicates and filtering.

As developer and traiger myself, I find the current combination of "full
information for new reports " and "summary and attachment for amended reports"
good enough. If I want to make any change, it would only be making the summary
containing even more information instead of the opposite. 

Anyway, for a crash report containing dozens of  duplicates/comments, only the
original report(comment #0) contains the full information, so I really don't
think that would introduce great clutter. Also bugzilla web interface makes it
easy to fold/unfold comments.

-- 
You are receiving this mail because:
You are the assignee for the bug.