Converting a large project from 2.18 to 2.19: what to expect?

[Shevek]

Hi,

I'm currently in the process of composing a symphony in Lilypond 2.18.2.
There are a few graphical bugs that are making me consider converting the
project to the current 2.19 (parentheses/accidental collision, tempo mark
spacing with uniform-stretching), but I'm hesitant to jump immediately
because I have like 20k+ lines of code, some of which was already updated
from 2.16, and also libraries of custom snippets.

So my questions:

1) How stable is 2.19 for end users on a demanding project? It seems like
forever since 2.18, so I'm sort of surprised there hasn't been 2.20 already.
Is there some major problem I should be worried about in 2.19?

2) What should I expect to break under 2.19? Music output changes to look
out for as I proofread? Things that might make snippets or Scheme behave
differently or not be backwards compatible?

3) Are there any notable regressions in terms of graphical output? My music
already looks pretty great overall in 2.18.2, so I don't want to go through
the trouble of upgrading to fix graphical bugs if I'll just be trading them
for different graphical bugs. From experience so far, it seems my project is
expansive enough that there's a good chance I'll run into any given
graphical bug, unless it's specific to early music notation or something.

Thanks so much for your help. I realize this is a pretty broad question.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Converting-a-large-project-from-2-18-to-2-19-what-to-expect-tp201938.html
Sent from the User mailing list archive at Nabble.com.