1 @c -*- coding: us-ascii; mode: texinfo; -*-
6 * Introduction to issues::
7 * Issue classification::
8 * Adding issues to the tracker::
12 @node Introduction to issues
13 @section Introduction to issues
15 First, @qq{issue} isn't just a politically-correct term for
16 @qq{bug}. We use the same tracker for feature requests and code
17 TODOs, so the term @qq{bug} wouldn't be accurate.
19 Second, the classification of what counts as a bug vs. feature
20 request, and the priorities assigned to bugs, are a matter of
21 concern @strong{for developers only}. If you are curious about
22 the classification, read on, but don't complain that your
23 particular issue is higher priority or counts as a bug rather than
27 @node Issue classification
28 @section Issue classification
35 New: the item was added by a non-member. Should be reviewed by
39 Accepted: the Bug Meister added it, or reviewed the item.
42 Started: a programmer is working on a bugfix. (used infrequently,
43 but should be used more often)
52 Invalid: issue should not have been added in the current state.
55 Duplicate: issue already exists in the tracker.
58 Fixed: programmer claims to have fixed the bug. The Bug Meister
59 should check the input code in an official binary release.
62 Verified: Bug Meister has confirmed that the issue is closed.
71 Type-Defect: a problem that requires no (or very little) new code
75 Type-Enhancement: a problem (or new feature) that requries a
76 significant amount of new code.
79 Type-Collision: overlapping notation. (this label takes
80 precedence over -Defect and -Enhancement)
83 Type-Task: not used, I think. TODO: start using it or delete it.
86 Type-Other: anything else. TODO: start using it or delete it.
95 Priority-High: lilypond segfaults.
98 Priority-Regression: it used to work.
101 Priority-Medium: normal priority; this is the highest priority a
102 non-crashing, non-regression bug report can receive.
103 (regardless of the perceived importance)
106 Priority-Low: less important than normal.
109 Priority-Postponed: no fix planned. Generally used for things
110 like Ancient notation, which nobody wants to touch.
114 Opsys lables: pretty self-explanatory.
121 Security: not used. TODO: delete, unless anybody is serious about
125 Performance: not used. TODO: delete.
128 Usability: not used. TODO: delete.
131 Maintainability: hinders developent of LilyPond. For example,
132 improvements to the build system, or @qq{helper} python scripts.
135 Bounty: somebody is willing to pay for the fix.
138 Engraving-nitpick: output is not beautiful, but not strictly
139 speaking @qq{wrong}. For example, a slur shape which does not
140 collide with any notation, but looks ugly.
143 Warning-nitpick: graphical output is fine, but lilypond prints a
144 false/misleading warning message.
149 @node Adding issues to the tracker
150 @section Adding issues to the tracker
154 only done by Bug Meister, unless you're really certain you know