Re: 2.20 release roadmap

[Jacques Menu]

What is the problem in GUB today, and what can be done to help solve it?

JM

> Le 20 sept. 2019 à 07:23, Urs Liska <address@hidden> a écrit :
> 
> 
> 
> Am 20. September 2019 02:23:58 MESZ schrieb Carl Sorensen <address@hidden 
> <mailto:address@hidden>>:
>> We are stuck for release because GUB is not working properly.  Until we
>> get GUB to work properly, we cannot make a release.
>> 
>> As far as I know now, the answer is in fact indefinite.
> 
> But is that the actual roadblock for the *2.20* release, not just *any*? I 
> mean: once that's solved, there was discussion about another 2.19 release, 
> but would that also mean 2.20 can be immediately released?
> 
> Of course it's futile since I can't help much, but it would becreally great 
> to have a "stable" release by January . We'll have the music engraving 
> conference in Salzburg (that Werner announced  a few days ago), where we 
> expect other software to be presented too. It would be awkward - to put it 
> mildly - to talk about our program that hasn't seen  a stabke release in six 
> years bx then ...
> 
> Urs
> 
>> 
>> Thanks,
>> 
>> Carl
>> 
>> 
>> On 9/19/19, 6:14 PM, "Andrew Bernard" <address@hidden>
>> wrote:
>> 
>> I do hope this is not seen as impertinent, because it is not intended 
>> that way. It's curious that I have asked the question about 2.20
>> release 
>> more than once and each time received no reply (unless lost in my
>> mailers).
>> 
>> Most projects will give some sort of indication about future releases. 
>> If the indication for lilypond is simply 'indefinite' that's alright, 
>>   but I would be keen to know.
>> 
>> 
>>   Andrew
>> 
>> 
>>   On 18/9/19 1:44 pm, Andrew Bernard wrote:
>>> Hello All,
>>> 
>>> I asked the same on the user list, but no response. Is there any 
>>> roadmap as to when 2.20 may be released? Are there any plans to do
>> so?
>>> 
>>> I KNOW we are very under-resourced. I'd very much like to help with 
>>> the development but I regret to say I have never been able to wrap my
>> 
>>> mind around the lilypond source code and how it all works, so I can't
>> 
>>> contribute, although I would very much like to. For some reason, 
>>> despite experience in software, I personally find it very opaque. But
>> 
>>> that's just me.
>>> 
>>> As always, sincere thanks to those who do work on this amazing
>> software.
>>> 
>>> Andrew
>>> 
>>> 
>> 
>>   _______________________________________________
>>   lilypond-devel mailing list
>>   address@hidden
>>   https://lists.gnu.org/mailman/listinfo/lilypond-devel
>> 
>> 
>> _______________________________________________
>> lilypond-devel mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-devel
> 
> -- 
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden <mailto:address@hidden>
> https://lists.gnu.org/mailman/listinfo/lilypond-devel 
> <https://lists.gnu.org/mailman/listinfo/lilypond-devel>