Hello,
I would like to discuss a topic about creating bugzillas bugs.
I took a bug 747410. I have change the function creating a new bug to
follow the default template [1] (see the description field). You may see a
result in the partner-bugzilla [2].
I am not completely aware of abtr architecture and I am abrt newbie. So, I
would like to ask you for review of my further idea how to format a problem.
The following lines describes default sections and their content. I have
hammered it out with great assistance of Jirka and Karel.
Thanks in advance.
[Section]
Description of problem:
[Content]
Content of the comment file.
[Section]
Version-Release number of selected component (if applicable):
[Content]
Content of the package file.
[Section]
How reproducible:
[Content]
Content of the how reproducible file. The file should be created by GUI
during handling of the report to bugzilla event.
[Section]
Steps to Reproduce:
[Content]
Content of the steps to reproduce file. The file should be created by GUI
during handling of the report to bugzilla event.
[Section]
Actual results:
[Content]
Content of the actual results file. The file should be created by GUI during
handling of the report to bugzilla event.
[Section]
Expected results:
[Content]
Content of the expected results file. The file should be created by GUI
during handling of the report to bugzilla event.
[Section]
Additional info:
[Content]
This section must contain a version of the libreport lib on the beginning.The
rest of this section should be filled by content of the most valuable files.
It brings a problem how to recognize that a text within a file provides some
added value? A simply metric for added value could be readability and ease of
understanding. How to recognize that file is human readable and is easily
understandable? It is probably impossible to recognize those types of files
automatically. Some expert should make this decision. In case when new types
of files can be invented by a newly created plugin it seems to be useful to
have a possibility to disable insertion of particular files to this section.
The black listed files could be stored in the bugzilla configuration.
The known files that should not be inserted to this section:
- open_fds
- maps
- dso_list
Long files, not readable files, not understandable files and binary files
should be provided as attachments of a bug. (Only as attachment and not as a
description of files in this section.)
In the current implementation only big files and binary files are not inserted
to this section. And not only files created by the abrt or a plugin are
inserted to this section. Every text file placed in a problem directory wich
is short enough is inserted. It makes the additional section unclear.
The proposed configuration is not necessary. I can add the known files to a
black list in source code. It is the fastest an easiest way.
Regards
Jakub
[1]
https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%...
[2]
https://partner-bugzilla.redhat.com//show_bug.cgi?id=782210