Re: branching stable/2.22?

[Han-Wen Nienhuys]

On Thu, Sep 3, 2020 at 11:16 AM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>
> Am Mittwoch, den 26.08.2020, 00:05 +0200 schrieb Han-Wen Nienhuys:
> > On Tue, Aug 25, 2020 at 11:17 PM Jonas Hahnfeld <hahnjo@hahnjo.de> 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
> 2) Agree on some sort of freeze
> 3) Branch off stable/2.22 and cherry-pick only fixes

I think the real problem is that we don't know exactly how many
problems there are that would be unacceptable in a stable release. So
we need a way to coax people normally on stable releases to try out
our current master, so we know where we are. Could we rename the
current 2.21 as 2.22-RC1 or 2.21.90 and hopefully get some feedback?

-- 
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen