Hi Andrew,

Absolutely, supporting other versions is on my TODO list, and I'll post back here when it's done.
I used the term "unstable" because I saw the term "unstable development 
versions" [1] on the Lilypond website (e.g., at 
http://lilypond.org/development.html), not because I have had any issues 
with 2.19. I interpreted that (perhaps incorrectly — please correct me 
if I'm wrong) as meaning that things are in flux such that songs that 
were valid in one version might not be valid in the next version.
I'm looking forward for a "2.20" or "stable" version to reduce confusion 
around this. I will support 2.19.80, but want to make sure that I do it 
properly and support multiple versions for the above reason.
Best,
Joshua

[1] I've also seen the term "stable development version" used, but not consistently.
On 2018-01-07 20:38, Andrew Bernard wrote:
Hi Joshua,

There was a thread recently about the use of the term 'unstable'. The 2.19 line at the present state of development is not unstable, quite the opposite. It's a self deprecating term of open source modesty that has the negative effect of making people think this line should be avoided. Better to think of the 2.19 line as simply the development version. Consequently, there is a large number of people using it, hence the requests you have seen. Do consider it.
Andrew


On 8 January 2018 at 11:39, Joshua Netterfield <jos...@nettek.ca <mailto:jos...@nettek.ca>> wrote:

    That is correct. Only 2.18.2 is currently supported. In the
    future, Hacklily may look for a "version" statement and use an
    unstable version if

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to