[Top][All Lists]

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

Re: branching stable/2.22?

From: David Kastrup
Subject: Re: branching stable/2.22?
Date: Thu, 03 Sep 2020 17:02:33 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Jonas Hahnfeld <> writes:

> Am Mittwoch, den 26.08.2020, 00:05 +0200 schrieb Han-Wen Nienhuys:
>> On Tue, Aug 25, 2020 at 11:17 PM Jonas Hahnfeld <> wrote:
>> > > I think the stabilization effort could be a joint effort by the entire
>> > > dev team, by agreeing with the team to hold off on new features and
>> > > invasive changes for a period of time (say, 1 to 2 months).
>> > 
>> > My feeling is that we should prioritize on bug fixes, but not actively
>> > block the development of features.
>> Right - but we should refrain from changes that will make the
>> backporting process more difficult, so it is still a freeze of sorts.
> So what do we do here?
> 0) Do nothing and continue to break things
> 1) Prioritize fixes over features

The breakage we currently get was not because of features.  Mainly it
was because of overhauling code base and build system.  There is very
little payoff for the end user, apart from moderate performance
improvements.  And of course a higher likelihood that their distribution
will not discontinue distribution of LilyPond.

> 2) Agree on some sort of freeze
> 3) Branch off stable/2.22 and cherry-pick only fixes

I think that "some sort of freeze" makes sense only in light of defining
goals to achieve for the next stable release.  As long as those goals
still necessitate disruptive/extensive changes, there is not much of a
point in branching.

David Kastrup

reply via email to

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