Re: survey on multiple development versions

[Carl Peterson]

On Tue, Dec 10, 2013 at 12:15 PM, Simon Bailey <address@hidden> wrote:

for instance: 

- the cool new features in 2.17 were \tuplet, tighter spacing, dot.notation.of.objects and \markLengthOn, several articulations feature;
- 2.15 didn't have much exciting for me in it -- here i stuck with 2.14 until 2.16 came out.
- 2.13 was a good development version with the instrument names fixed, q for repeating chords, dotted/dashed slurs, two-sided margins, white-out, segno bar-line, cresc text spanners, the partcombiner, cueDuringWithClef, beam collisions, ... [2.14. was a GOOD release]

My personal upgrading experience is similar. I had a hiatus of a couple of years (at least) when I didn't use LilyPond (dating back to around 2.13.17 or so, IIRC), but recently, I was using 2.16.2 on my main computer until it became necessary to tweak things to fit a stylesheet I was working on, then I installed LilyDev on my iMac and eventually fired up my old Debian box. I used 2.17.26 or so for awhile, until I found out that the most recent releases incorporate MIDI panning, so right now I do my work on a hacked version of 2.17.95 for Mac (copying in modified versions of the part combiner Scheme file and the Feta font). Even though it doesn't take much to integrate those hacks now, I'm reluctant to do much upgrading unless there's a benefit to doing so.