Release proposal: v1.4.3 #1017
Description
Mainly targetting improved Windows support, see #1005. Ideally we could knock off a few more of those failures in this release but it sounds like #1008 is enough on its own to warrant a 1.4.3. I can prioritise this within the next day (it may end up being tomorrow evening, PST).
- [
ca3c50b789] - build: add basic arm64 support (Ben Noordhuis) #1028 - [
08e89b1880] - doc: update AUTHORS list (Rod Vagg) #1018 - [
ea02d90cd0] - doc: add julianduque as collaborator (Julian Duque) #1021 - [
dfe7a17784] - doc: fix typos and sources in WORKING_GROUPS.md (&! (bitandbang)) #1022 - [
6d26990d32] - doc: Clean up net.Socket (Ryan Scheel) #951 - [
c380ac6e98] - doc: suggest alternatives to deprecated APs (Benjamin Gruenbaum) #1007 - [
3d6440cf2a] - src: fix --without-ssl build (Ben Noordhuis) #1027 - [
2b47fd2eb6] - stream_base:.writev()has limited support (Fedor Indutny) #1008
Activity
Fishrock123 commentedon Mar 1, 2015
Seems like we should get #1008 out by then if we can't fix the rest. +1
snostorm commentedon Mar 1, 2015
We're ready for this via nodejs/iojs.org#252
piscisaureus commentedon Mar 2, 2015
+1
rvagg commentedon Mar 2, 2015
2015-03-02, Version 1.4.3, @rvagg
Notable changes
writev()support, particularly Windows. Changes introduced in 1.4.1, via #926, broke some functionality for these platforms, this has now been addressed. #1008 (Fedor Indutny)Known issues
process.send()is not synchronous as the docs suggest, a regression introduced in 1.0.2, see #760 and fix in #774dns.setServers()while a DNS query is in progress can cause the process to crash on a failed assertion #894Commits
rvagg commentedon Mar 2, 2015
test run: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/232/
piscisaureus commentedon Mar 2, 2015
Tons of failures on windows :(
rvagg commentedon Mar 2, 2015
Not making a whole lot of progress here, those timeouts could be knocked out in one go if someone has the time to figure it out.
I'm happy go ahead with the release pending tests on the other platforms.
/cc @indutny & @piscisaureus can you check my wording in Notable Items and Known Issues above please?
rvagg commentedon Mar 2, 2015
@piscisaureus I'd love to have fewer failures on Windows but this is an incremental process. Would love to find more Windows contributors!
snostorm commentedon Mar 2, 2015
I'll be offline for the night soon, but nodejs/iojs.org#252 is up to date against the latest in iojs/website#master.
rvagg commentedon Mar 2, 2015
https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/233/ again, with a couple of new commits for the ARMv8 stuff
indutny commentedon Mar 2, 2015
LGTM, good job, man!
On Monday, March 2, 2015, Sean Ouimet notifications@github.com wrote:
piscisaureus commentedon Mar 2, 2015
Me too - let's prioritize finding more Windows contributors until I (or someone else) has time.
rvagg commentedon Mar 2, 2015
https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/234/
rvagg commentedon Mar 3, 2015
RC: https://jenkins-iojs.nodesource.com/job/iojs+release+nightly/95/
Landing @ https://iojs.org/download/nightly/v1.4.3-nightly20150303ca3c50b789 I think
rvagg commentedon Mar 3, 2015
tagged and building: https://jenkins-iojs.nodesource.com/job/iojs+release/43/
rvagg commentedon Mar 3, 2015
done v1.4.3 @ https://iojs.org/dist/latest/
jbergstroem commentedon Mar 3, 2015
armv6l seems to be missing
rvagg commentedon Mar 3, 2015
Patience, grasshopper, it too shall land, all in good time