1 |
This directory is the Guile bug data base. |
This directory is the Guile bug data base. |
2 |
|
|
3 |
It contains one file per bug with a simple, mail-message like format. |
It contains one file per bug with a simple, mail-message like format. |
4 |
Each file starts with a number of header lines in the form |
For quick start adding a bug, see TEMPLATE. |
5 |
|
|
6 |
|
Each bug file starts with a number of header lines in the form |
7 |
|
|
8 |
field-name: field-value |
field-name: field-value |
9 |
|
|
21 |
|
|
22 |
A one-line summary of the bug. Mandatory. |
A one-line summary of the bug. Mandatory. |
23 |
|
|
24 |
Tags: tag1, tag2, ... |
Tags: tag1, tag2, ... |
25 |
|
|
26 |
A comma separated list of symbolic tag names (for example |
A comma separated list of symbolic tag names (for example |
27 |
release-critical-1.6). Tags can be used to collect bugs into |
release-critical-1.6). Tags can be used to collect bugs into |
29 |
their meaning. |
their meaning. |
30 |
|
|
31 |
Reported: mailbox, yyyy-mm-dd |
Reported: mailbox, yyyy-mm-dd |
32 |
|
|
33 |
The mail address of the reporter, in RFC2822 mailbox format, |
The mail address of the reporter, in RFC2822 mailbox format, |
34 |
followed by the date of the report, in ISO8601 format. |
followed by the date of the report, in ISO8601 format. |
35 |
|
|
36 |
Assigned: mailbox, yyyy-mm-dd |
Assigned: mailbox, yyyy-mm-dd |
37 |
|
|
38 |
The developer who is working on a fix, and since when. |
The developer who is working on a fix, and since when. |
60 |
|
|
61 |
Meta information about the bug tracking system (like this README file) |
Meta information about the bug tracking system (like this README file) |
62 |
should be put into files that start with a upper case letter. |
should be put into files that start with a upper case letter. |
63 |
|
|