Many users have old projects on very old versions of Lilypond, and
sometimes you just want to make a small edit, not update your whole project
to use the new version. It's important for documentation to be available.

On Mon, Feb 13, 2023, 8:41 AM Kevin Cole <dc.l...@gmail.com> wrote:

> On Mon, Feb 13, 2023 at 11:33 AM Lukas-Fabian Moser <l...@gmx.de> wrote:
> >
> > Hi Kevin,
> >
> > > On the other hand, I strongly favor sticking with a distribution's
> > > package rather than starting every day with a "git pull". So, I'm
> > > always slightly behind the latest and greatest.
> >
> > Just for the record: Your description omits the (actually quite
> > convenient) middle between the two extremes: Namely, that it's quite
> > easy to keep up with current LilyPond development by downloading and
> > using the respective (unstable) builds that are released every few weeks
> > to months.
>
> The point I was trying to make was "Does there REALLY need to be
> documentation for versions 2.13 to 2.25?  Maybe 2.20 to 2.25 would
> suffice."
>
>

Reply via email to