[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release schedule for 2.20

From: Urs Liska
Subject: Re: Release schedule for 2.20
Date: Wed, 09 May 2018 14:44:08 +0200
User-agent: K-9 Mail for Android

Am 9. Mai 2018 12:18:37 MESZ schrieb Aaron Hill <address@hidden>:
>On 2018-05-09 02:49, Malte Meyn wrote:
>> But an increasing number of questions asked in forums or on the lists
>> can be answered by “compile current master or wait for 2.21.0”. And a
>> huge number of answers requires at least 2.19.xx but people
>> understandably don’t want to install an “unstable” version.
>> Since the first prerelease seven months have passed, people wonder
>> whether 2.20.0 will happen in a few weeks, a few months or even
>> in the future.
>I should have stated originally that I am not trying to force anything 
>here.  I totally understand that the developers on this project may be 
>most comfortable with the approach of "we'll release it when it's
>not a moment before".  Rather, I was curious if the team had a planned 
>roadmap they were currently targeting, and where one could easily track
>that information.  It sounds like nothing of that sort really exists.  
>This is not ideal but hardly something to stress about.
>What does have impact for me is whether the next release is still many 
>months out or longer.  Knowing a little bit about the schedule, I can 
>more easily justify the time expense of getting a build environment set
>up to be able to run from master or some other staging branch.  I have 
>no qualms of running "bleeding-edge" bits.  That said, it is always
>convenient to be able to work from pre-built binaries, although those 
>understandably take time to create and publish.

This very much looks to me that your best bet is to install the latest release 
from the 2.19 series.
The only reason to compile yourself would be to incorporate custom patches.


>So, I apologize if I have ruffled any feathers here.
>-- Aaron Hill
>lilypond-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]