The Bug-meister is the human face behind the collection of LilyPond
bugs. He (or she, of course) keeps an eye on bugs in LilyPond,
especially those where LilyPond produces incorrect notation or
typography. This is a very important job, since good responses to
bugreports makes LilyPond look good for struggling users.
- He'll be reading the bug-lilypond and lilypond-user mailing
list, replying to bugreporters and distilling small failure cases
for each report.
- Every bug goes into the bug-collection.
In the collection for each bug, there is
- A .ly snippet, trimmed as far as possible.
- An image demonstrating the problem.
- A description of what is wrong.
- Whether the bug concerns a new feature, or breaks existing
- If the latter, the version number where the bug started
- The severity of the bug: a bug should get priority if it causes
crashes, when there are no workarounds, or if it affects a large
number of people.
- After the developers claim to have fixed a bug, the bug-meister