[ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
[ < Issue classification ] | [ Up : Issues ] | [ Summary of project status > ] |
7.5 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.
In order to assign labels to issues, Bug Squad members should log in to their google account before adding an item.
Normal issues
- Check if the issue falls into any previous category given on the relevant checklists in Bug Squad checklists. 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
Status
,Type-
, andPriority-
labels.Include output with the first applicable method:
-
If the issue has a notation example which fits in one system,
generate a small ‘bug.preview.png’ file with:
lilypond -dpreview bug.ly
-
If the issue has an example which requires more than one system
(i.e. a spacing bug), generate a ‘bug.png’ file with:
lilypond --png bug.ly
-
If the issue requires multi-page output, then generate a
‘bug.pdf’ file with the normal:
lilypond --png bug.ly
-
If the issue has a notation example which fits in one system,
generate a small ‘bug.preview.png’ file with:
-
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
user
andbugs
), then reply to all those mailing lists as well. The email should contain a link to the issue you just added.
Patch reminders
Note: This is not a Bug Squad responsibility; we have a separate person handling this task.
There is a special category of issues: reminders of an existing
patch. These should be added if a patch has been sent to a
lilypond mailing list (generally lilypond-devel
, but they
sometimes appear on bug-lilypond
as well) and has had no
discussion for at least 3 days. Do not add issues for
patches under active discussion.
Before adding a patch-reminder issue, do a quick check to see if it was pushed without sending any email. This can be checked for searching for relevant terms (from the patch subject or commit message) on the webgit page:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git
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 bugs
and
devel
), then reply to all those mailing lists as well. The
email should contain a link to the issue you just added.
[ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
[ < Issue classification ] | [ Up : Issues ] | [ Summary of project status > ] |