----- Original Message -----
From: "Jan Warchoł" <[email protected]>
To: <[email protected]>
Cc: "Lilypond Bugreports" <[email protected]>; <[email protected]>
Sent: Sunday, December 12, 2010 8:19 AM
Subject: issue classification was: Odd output
Hi all,
2010/12/10 Marco Correia <[email protected]>:
Thanks!
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.
cheers,
Janek
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:
http://lilypond.org/doc/v2.13/Documentation/contributor/issue-classification
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
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
