lilypond-devel
[Top][All Lists]
Advanced

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

Re: Fixing regressions and serious issues


From: Jean Abou Samra
Subject: Re: Fixing regressions and serious issues
Date: Wed, 20 Jul 2022 13:36:17 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0



Le 20/07/2022 à 11:39, Jonas Hahnfeld a écrit :
On Thu, 2022-07-14 at 17:38 +0200, Jean Abou Samra wrote:
Hi,

In https://lists.gnu.org/archive/html/lilypond-devel/2022-05/msg00099.html,
we talked about targeting the end of this year for the next
stable release. That probably means branching around
the beginning of September, right?
Possibly, yes. If wanted, I can try and prepare a "draft timeline"
based on what we did two years ago and what needs to happen until
around what deadline...


For me at least, that would be helpful.


I'd like to call for attention on the regressions we have
<https://gitlab.com/lilypond/lilypond/-/issues/?label_name%5B%5D=Regression>
as well as some other serious things that should go
into this release: basically, (assuming branching in September)
there is a month and a half left to take care of those.
This is not all that long if not very short, especially since
some people (like me) tend to be less active in August.
I agree, even though I'd like to note that only those marked ~Critical
actually block the release. There are a number of ~Regression issues
that have been there for 2.22.x or even 2.20.0. Whether we want to re-
classify some of the more recent ones as ~Critical, is of course up for
discussion. And fixing issues is obviously still a good idea 😉


You have a good point that which of these should block the
release is not very clear. I guess it would need discussion,
and the energy spent discussing will have been wasted if the
issue just gets fixed before the release, so for now I think
the best investment of energy (or my energy at least) is in
fixing as many as possible of these issues. If some remain by
the time we want to make the release, it will be time to discuss
whether they should block it.





reply via email to

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