On Tue 14 Mar 2017 16:25, Greg Troxel <g...@lexort.com> writes: > Andy Wingo <wi...@pobox.com> writes: > >> However! Even though the code says 2.2.0 and the tag says 2.2.0, the >> release is not until Thursday. I will not upload the tag yet. > > I have just barely caught up with 2.0.x in pkgsrc, and haven't gotten to > testing 2.1.x yet. I wonder how many platforms 2.1.x has been tested > on, and really I mean "has it been tested on other than GNU/Linux".
Things are in the early days, you are right. GNU/Linux and macOS have been tested. Cygwin builds and works though it has some test errors; we are working on it. I don't know about mingw yet. I think there might be some errors on the other BSDs but I don't know yet. > So if you think it's ready, I would suggest preparing a 2.2.0rc1, or > simply a new 2.1.x with the notion that aside from version numbers it's > an RC, and call for all people engaged in packaging to try to package it > as 2.2, and to give them a few weeks. I have done exactly that in the past weeks with 2.1.7 and 2.1.8 :) I think a 2.2.1 will follow very soon (within a month or so from 2.2.0, I would imagine), so any portability fixes will naturally be included there. That's about the same timeframe you are asking for, so all is well in that regard. Happy hacking, Andy
