[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: issue classification was: Odd output

From: Phil Holmes
Subject: Re: issue classification was: Odd output
Date: Sun, 12 Dec 2010 11:11:45 -0000

----- Original Message ----- From: "Jan Warchoł" <address@hidden>
To: <address@hidden>
Cc: "Lilypond Bugreports" <address@hidden>; <address@hidden>
Sent: Sunday, December 12, 2010 8:19 AM
Subject: issue classification was: Odd output

Hi all,

2010/12/10 Marco Correia <address@hidden>:

I can't believe that this is seen as a low priority enhancement...! This
completely renders lilypond unusable for the task I need it, which is to serve
as a printer for computer generated music. The output is not ugly - it is
plain wrong!

I agree with Marco, in my opinion this issue should be medium priority defect.
Or even a high priority one (i took a look at current high priority
defects and they don't look much grave than this one).

Actually, i'd like to discuss issue classification in general, because
in my opinion it could use a lot of improvement. Should i do this now
on developers list, or maybe wait until 2.14 is out? Or wait for GOP?
I don't want to disrupt current development process too much.


As bug-meister, I'd think that classification is now my baby. I'm not a developer, so discussing it doesn't slow development, apart from some noise on -devel. The current classification is at:

Happy to have some suggestions for improvements.

The downside is that if we do change it, the right-and-proper thing to do would be to check the classification of all open issues. Not sure that would happen short term :-(

Phil Holmes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]