Graham Percival wrote:
> - enhancement: something which requires new code.
>
> - accepted: default status once added (by a member)
> - fixed: programmer thinks it's resolved
> - verified: Bug Meister checks the results in an official binary
> and agrees it's resolved
>
> - priority-high: lilypond crashes
> - priority-regression: it worked before
> - priority-medium: this is the highest priority for "normal" bugs.
> No, we don't care if you have a comission due tomorrow, or it
> looks like the output of microsoft word.
> - priority-low: if the Bug Meister thinks it isn't important,
> and/or isn't likely to be fixed. For example, anything touching
> Ancient music automatically gets a priority-low, since nobody's
> touched that code in the past four[1] years, and nobody will
> probably touch it in the *next* four years.
>
> [1] I might be using the definition of "four" which encompasses
> the numbers 3 or 2. Whatever, it's been a long time in
> lilypond-years. :)
Graham,
this is informative! Might as well cc this to CG 6.2 with a
heading like "TODO: clean this up."
Or not. You're the boss in that department...
Thanks, though.
- Mark
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
