Hi Tina,
Am 07.07.26 um 18:23 schrieb Tina Petzel:
And this I think is exactly why using unstable versions is not really suitable
for an online score writing and sharing system like this one. With stable
versions Jocelyn has to support essentially one lilypond version (since stable
generally implies that patch releases don’t break API). With unstable this
would mean she has to support potentially every unstable version out there.
I think offering compilation against the latest unstable version or something is
a nice feature. But supporting every single development version out there is
going to be a lot — and probably not necessary.
I completely agree. And I notice that, in my everyday work, I now tend
to simply write
\version "2.26"
and not think any further - especially for code that I might give to
others - if I don't need \beamBreak. Of course, over the course of time
it's probable that I'm going to start writing 2.27.xx again, the more
new features are added to the 2.27 that I don't want to miss out on.
Basically, we're at a point of time (shortly after the release of a
stable version) where the wish for an unstable version seems exaggerated.
Supporting latest unstable release already gives you these features if you
really need them.
I think that would be wonderful (and enough). But it would mean a
constant need to update on Jocelyn's side.
Lukas
