Problem reports have to be in a particular form so that a program can easily manage them. Please remember the following guidelines:
•
describe only one problem with each problem report.
•
For follow-up mail, use the same subject line as the one in the automatic acknowledgement. It consists of category, PR number and the original synopsis line. This allows the support site to relate several mail messages to a particular PR and to record them automatically.
•
Please try to be as accurate as possible in the subject and/or synopsis line.
•
The subject and the synopsis line are not confidential. This is because open-bugs lists are compiled from them. Avoid confidential information there.
The severity field is to indicate the severity of the problem. The accepted values are:
critical
The product, component or concept is completely non-operational or some essential functionality is missing (e.g. kernel panic or program core dumps). No workaround is known.
serious
The product, component or concept is not working properly or significant functionality is missing. Problems that would otherwise be considered critical are rated serious when a workaround is known.
non-critical
The product, component or concept is working in general, but lacks features, has irritating behavior, does something wrong, or doesn't match its documentation.
The default value is serious.
The priority field specifies how soon the problem report submitter requires a solution. The accepted values are:
high
A solution is needed as soon as possible.
medium
The problem should be solved in the next release.
low
The problem should be solved in a future release.
The default value is medium.
The class of a problem report can be one of the following:
sw-bug
A general software problem ( `sw' stands for software ).
doc-bug
A problem with the manual pages or other documentation.
change-request
A request for a change from existing behavior that is not a bug ("It's nice, but it would be better if ...").
support
A support problem or question.
The default value is sw-bug.
See the GNU Info file send-pr.info or the document Reporting Problems With send-pr for detailed information on reporting problems