[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documentation: Should we possibly have aliases for current stable an
From: |
Kevin Cole |
Subject: |
Re: Documentation: Should we possibly have aliases for current stable and current devel? |
Date: |
Mon, 13 Feb 2023 11:40:40 -0500 |
On Mon, Feb 13, 2023 at 11:33 AM Lukas-Fabian Moser <lfm@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."
- Documentation: Should we possibly have aliases for current stable and current devel?, Valentin Petzel, 2023/02/13
- Re: Documentation: Should we possibly have aliases for current stable and current devel?, Jean Abou Samra, 2023/02/13
- Re: Documentation: Should we possibly have aliases for current stable and current devel?, David Wright, 2023/02/13
- Re: Documentation: Should we possibly have aliases for current stable and current devel?, Kevin Cole, 2023/02/13
- Re: Documentation: Should we possibly have aliases for current stable and current devel?, Saul Tobin, 2023/02/13
- Re: Documentation: Should we possibly have aliases for current stable and current devel?, Kevin Cole, 2023/02/13
- Re: Documentation: Should we possibly have aliases for current stable and current devel?, Jean Abou Samra, 2023/02/13
Re: Documentation: Should we possibly have aliases for current stable and current devel?, Lukas-Fabian Moser, 2023/02/13