Is it possible to just push out a minor release to base that adds the missing enum? I am working on some fixes for memory management in base that I’d like to make it into the next release, but I can’t guarantee finishing in the next couple of days.
David > On 11 Dec 2017, at 07:45, Fred Kiefer <fredkie...@gmx.de> wrote: > > I was hoping for Richard to step up here. If he doesn’t response today, we > should try to go ahead ourselves. I could help later today with the news.texi > file. My impression is that we should use a version number of 1.26.0 as quite > a few changes have piled up. > The release process itself would again be on your side, as you have the > required key for it. It would be great to have this one out tonight to reduce > the confusion that comes from the gui release. > Not sure whether we need another gui release to document the increased base > version. I think we could do without it. > > Fred > >> Am 11.12.2017 um 00:03 schrieb Ivan Vučica <i...@vucica.net>: >> >> I'm happy to help as needed. >> >> >> On Sun, Dec 10, 2017, 20:26 Fred Kiefer <fredkie...@gmx.de> wrote: >> >> >>> Am 09.12.2017 um 14:43 schrieb Ivan Vučica <i...@vucica.net>: >>> >>> I have no opinion on whether we need a synced release; -gui is certainly in >>> need of it as Debian is blocked from pulling in even 0.25.1. >> >> Turns out some to the changes Daniel made in gui require the new enums he >> added to base. That is, GNUstep gui 0.26.0 depends on the unreleased GNustep >> base. That way Debian and all the other systems won’t benefit from that gui >> release until there is also a base release. And we need to update the >> documented required base version in gui. >> >> Fred > > > _______________________________________________ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
