[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.21.0 release plans and considerations
From: |
Jonas Hahnfeld |
Subject: |
Re: 2.21.0 release plans and considerations |
Date: |
Mon, 02 Mar 2020 17:40:46 +0100 |
User-agent: |
Evolution 3.34.4 |
Am Montag, den 02.03.2020, 10:48 +0100 schrieb Jonas Hahnfeld:
> Am Sonntag, den 01.03.2020, 15:39 +0100 schrieb David Kastrup:
> >
> > But fortunately, we are now at the point where 2.20 _and_ 2.21 are going
> > to be a thing rather soon. Assuming that things like the Python3
> > migration don't cause more of a standstill for 2.21.0 than we imagine,
> > but then one can still decide to stop being disciplined until things are
> > fixed enough to get 2.21.0 done.
>
> Understood. In that case I'll work to prepare GUB for 2.21.0, at least
> something I can likely help with.
See https://github.com/gperciva/gub/pull/71. Incidentally this only
works for mingw after #5799 is applied (or at least the first commit).
So while it has the potential to break, it actually fixes things 😉
FTR: I guess the offending commit is b51e6224ab ("Issue 5776/1: Drop
check for std::vector::data()") where I innocently removed an inclusion
of config.hh. I'd argue that it has been broken before, this was only
uncovered by removing the include.
Regards
Jonas
signature.asc
Description: This is a digitally signed message part
Re: 2.21.0 release plans and considerations, Han-Wen Nienhuys, 2020/03/04
- Re: 2.21.0 release plans and considerations, Jonas Hahnfeld, 2020/03/04
- Re: 2.21.0 release plans and considerations, Han-Wen Nienhuys, 2020/03/05
- Re: 2.21.0 release plans and considerations, Jonas Hahnfeld, 2020/03/05
- Re: 2.21.0 release plans and considerations, Han-Wen Nienhuys, 2020/03/05
- Re: 2.21.0 release plans and considerations, Jonas Hahnfeld, 2020/03/05
- Re: 2.21.0 release plans and considerations, Phil Holmes, 2020/03/05