Hi I think it would be great to have that new release for the next Debian release which is going to happen soon:
https://wiki.debian.org/DebianBuster Happy new year! Gürkan Tel. 076 436 72 00 > On Jan 1, 2019, at 15:32, Stefan Bidigaray <[email protected]> wrote: > >> On Tue, Jan 1, 2019, 07:50 Fred Kiefer <[email protected] wrote: >> >> >> > Am 01.01.2019 um 12:44 schrieb Ivan Vučica <[email protected]>: >> > >> > Hi maintainers, >> > >> > If you want, I can spend some time cutting a release. It has been a while >> > since the last one. Do we need a one? Are there critical bugs we fixed? >> > Are there critical bugs blocking the release? >> >> There weren’t that many changes to GNustep in the last year, but cutting a >> new release would be nice. I have been working on a few changes to the opal >> backend to get PikoPixel working in that setup. Having a release deadline in >> about two weeks could motivate me to finish these changes :-) >> >> >> > There’s a pull request for icu-config removal that we could apply to >> > -base. It might warrant a release. >> >> Yes, I have been thinking about that pull request. The problem is that this >> will break icu on systems where the pkg config for icu isn’t present. I >> think this has been around for at least six years. This should be long >> enough even for GNUstep standards. :-( > > > The icu-config script used to be the recommended method for finding the > libraries. I just liked at the documentation and pkg-config is now > recommended, so making this change would just guarantee future compatibility. > Per the latest ICU documentation, icu-config is deprecated. > >> > If the answer is yes, if you can help me by updating the >> > (non-autogenerated) pieces of the release notes, that would help me a bit. >> > >> > If the answer is yes, I would be cutting the release on a weekend. >> >> Great, but please give me a bit more time. >> >> Fred >> >> >> PS: Did you see the two pull requests for back today? The first one, that >> wasn’t a real pull request rather a question about the code, has triggered >> me to rethink the removal of RContext. Perhaps somebody else could have a >> look too? >> >> >> _______________________________________________ >> Gnustep-dev mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/gnustep-dev > _______________________________________________ > Gnustep-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
