Hey guys, It seems like we've got solutions for 1933, 1943, and 1948. 2160 was fixed as a side note to the website pdf patch by Alberto. Dealing with git branches (issue 2100) is the only one that isn't either finished or really close to being finished, but I expect that patch just needs something like 1 hour of writing+research+reviews.
Unfortunately, I'm leaving for Glasgow in 3 hours, so any official releases with the fixed 1933/1943/1948 will have to wait until Friday afternoon. If you're really anxious to test stuff, by all means build binaries with those fixes, upload them to a private server, and ask users to test them. Best-case scenario: we could have the third release candidate on Friday 6 Jan, with the official 2.16 release on Friday 13 Jan. That's an extremely ambitious schedule, so it's more realistic to think of 2.16 before the end of January -- but given the sudden interest [1] in having a stable release, I think that's certainly doable! [1] recall that I define "interest" as "writing or discussing patches", not "writing emails to say how much you want other people to do some kind of work". Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
