| [ << Issues ] | [Top][Contents] | [ Regression tests >> ] |
| [ < Issue classification ] | [ Up : Issues ] | [ Regression tests > ] |
8.4 Adding issues to the tracker
Note: This should only be done by the Bug Squad or experienced developers. Normal users should not do this; instead, they should follow the guidelines for Bug reports.
- Check if the issue falls into any previous category given on the relevant checklists in Triaging bugs. If in doubt, add a new issue for a report. We would prefer to have some incorrectly-added issues rather than lose information that should have been added.
- Add the issue and classify it according to the guidelines in
Issue classification. In particular, the item should have
Statusand type labels. - Include output. Usually, the problem can be demonstrated in an image
created using
lilypond -dcrop bug.ly, which generates bug.cropped.png. However, for spacing bugs, this image may not show the problem; attach the full PDF produced by a normallilypondinvocation in this case. - After adding the issue, please send a response email to the same
group(s) that the initial patch was sent to. If the initial email
was sent to multiple mailing lists (such as both
userandbugs), then reply to all those mailing lists as well. The email should contain a link to the issue you just added.
If patches are sent to the bug list, please submit them via GitLab
(or help the author to do so). Alternatively, if discussion is
needed, forward the patch to lilypond-devel.
| [ << Issues ] | [Top][Contents] | [ Regression tests >> ] |
| [ < Issue classification ] | [ Up : Issues ] | [ Regression tests > ] |