Critical issues

[Karl Hammar]

Graham complaind about 10 critical issues in the last lilypond report.

***

Issue  815: Enhancement: AJAX-powered search auto-completion for the online 
documentation

Why is this a critical issue for the lilypond release?

***

Issue 1080: Regression: bar lines in double bar are positioned too close 
together

"pnorcks" mentions commit 27a4d9354effb09c696925881ec4df007da8a0db
as a possible cause. Reverting part of that commit:

diff --git a/lily/bar-line.cc b/lily/bar-line.cc
index d3f21e5..85b2e52 100644
--- a/lily/bar-line.cc
+++ b/lily/bar-line.cc
@@ -196,11 +196,9 @@ Bar_line::compound_barline (Grob *me, string str, Real h,
       /*
        should align to other side? this never appears
        on the system-start?
+      */
       m.add_at_edge (X_AXIS, RIGHT, thin, 0);
       m.add_at_edge (X_AXIS, RIGHT, thin, thinkern);
-      */
-      m.add_at_edge (X_AXIS, LEFT, thin, thinkern / 2);
-      m.add_at_edge (X_AXIS, RIGHT, thin, thinkern / 2);
     }
   else if (str.find ("S") != NPOS || str == "|._.|")
     {

gives me the attached grace-start result which resembles the 2.13.17 
result presented in the bug tracker.

What should we do about it?

***

Issue  989: ensure that no information is only in the regtests

Though Graham complain about this issue in the "report",
this seems to be taken by Valentin. He has a list at
http://wiki.lilynet.net/index.php/Regtests

What to do about it?
Shall we discuss individual items on the list?

***

Issue  915: Multi-measure rests dependent on prefatory matter in other staves

There seems to be a fix: http://codereview.appspot.com/931041/show
Do you need help testing the fix?

***

Issue 1031: constantly-changing input/regression/rest-collision-beam-note.ly

If it is changes every time, what is the correct output?

grace-start.pdf
Description: grace-start.pdf