It looks like this needs to be done by a project manager. For an issue to be critical it needs to be a regression error, that is, it works before but doesn't now. Did it work in 2.16? if so, post that here: https://code.google.com/p/lilypond/issues/detail?id=3778#c4
Knute Snortum (via Gmail) On Tue, Apr 29, 2014 at 5:07 AM, Jan Rosseel <j...@rosseel.com> wrote: > Federico Bruni <fedelogy <at> gmail.com> writes: > > > thanks, added to the tracker: > > > > https://code.google.com/p/lilypond/issues/detail?id=3778 > > > > Is it possible to raise the seviry of the bug in the tracker? It is listed > now as ugly, but in effect it is worse: under certain conditions, it makes > music unreadable. As such, this can be considered critical. > > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
