I'm aiming to cut a new release next week (Feb 10-16). If there are any questions, comments, concerns, or objections, please raise them here.
cjihrig
All 5 comments
Just out of curiosity, what makes it a minor instead of a patch release?
skypjack
on 7 Feb 2019
@skypjack #2175 would be one reason, new API surface (new define.)
bnoordhuis
on 7 Feb 2019
I think I'm going to look to get https://github.com/libuv/libuv/pull/2160 landed and do a release over the weekend so that Node can make a release on Tuesday the 12th if they so choose. My understanding is that Node on Windows is currently in rough shape.
cjihrig
on 9 Feb 2019
libuv CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1218/
libuv+Node integration CI: https://ci.nodejs.org/view/libuv/job/libuv-in-node/82/
EDIT: Also https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1219/
cjihrig
on 10 Feb 2019
The pi1-docker hosts appear to be having some issues in the integration CI. Looking at the output and some other current Node PR runs, it seems like the issues are unrelated to changes here. Everything else is green though.
cjihrig
on 10 Feb 2019
Related issues
debosvi
路
10Comments
bnoordhuis
路
9Comments
mchandler-blizzard
路
6Comments
fliser
路
7Comments
jorangreef
路
9Comments
Most helpful comment
I think I'm going to look to get https://github.com/libuv/libuv/pull/2160 landed and do a release over the weekend so that Node can make a release on Tuesday the 12th if they so choose. My understanding is that Node on Windows is currently in rough shape.