-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release proposal: v2.0.1 #1629
Release proposal: v2.0.1 #1629
Conversation
I suspect this will be 2.1.0 due to an upcoming libuv 1.5.0 - #1621 (comment) (which will fix a bunch of issues in our tracker) |
Well, for what it's worth:
|
@imyller do we have issues to work on fixing for you? |
@rvagg nothing unexpected for Just tracking non-core packages needing native module upgrades due to changes made in I'm maintaining OpenEmbedded packaging of io.js (meta-iojs). Embedded side tends to depend more on packages with native modules so |
Oh, you'll love io.js 3.0 in a couple of weeks then. |
libuv |
Yeah, echoing @silverwind here. The io.js train is leaving the station today/tomorrow with fixes. |
@rvagg updated the OP with a new commit list. Tomorrow sounds good, some nice fixes in here. |
current state of master, a few greens recently so it looks like we're getting things into shape https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/651/ also, what happened to all those windows timeouts? perhaps the libuv upgrade has helped there given that it's fixed other windows problems? |
Idk jenkins switched to green and stuff became fine
|
So, counting down for release :) |
https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/652/ running that while I chase up a changelog, there's a couple of things worth expanding on in here and I don't have all the info yet. @trevnorris for the async_wrap additions in particular. |
converted this issue to a pull request, see attached CHANGELOG diff for proposed release notes, PTAL |
- [#1621](https://github.com/iojs/io.js/issues/1621) build errors associated with the bundled libuv | ||
- [#1512](https://github.com/iojs/io.js/issues/1512) should properly fix Windows termination errors | ||
* **addons**: the `NODE_DEPRECATED` macro was causing problems with compiling addons with older compilers, this should now be resolved (Ben Noordhuis) [#1626](https://github.com/iojs/io.js/pull/1626) | ||
* **V8**: upgrade V8 from 4.2.77.18 to 4.2.77.20 with minor changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe mention here that it unbreaks the FreeBSD build.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/changes/fixes/
This is a thing?? LGTM otherwise though. |
I don't think I've seen this CI failure before: (win2012r2) https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/652/nodes=win2012r2/tapTestReport/test.tap-709/ |
@Fishrock123 there's an API for it, use hub to interact with it @indutny or @bnoordhuis can you shed any light on whether the test-tls-ticket-cluster.js failure @ https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/652/nodes=win2012r2/tapTestReport/test.tap-709/ might be a concern? |
https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/653/ another one, no changes |
gah! test-tls-ticket-cluster.js on win2008 this time but ok on 2012, not sure what to make of this, @iojs/crypto |
rebooted the windows build servers, found a bunch of hung msbuild.exe processes on a 2012 and a 2008 machine running again: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/654/ |
only test-debug-port-from-cmdline.js failing on one windows box now, but I have bigger jenkins problems, WOE! |
OK, screw Jenkins, this is only impacting the Ubuntu 10.04 machines right now and is JDK related so I'm going to pretend the JVM isn't a thing that exists and move on with a release. Pushing ahead with tag and build now. |
PR-URL: nodejs#57 Related: nodejs/node#1629 Signed-off-by: Hans Kristian Flaatten <[email protected]>
I'm surprised we haven't had a flurry of "you broke my stuff!!" issues yet the issue & fix that concerns me the most is the
NODE_DEPRECATED
macro causing problems with older compilers, see #1626. I'd like to see the fix for this get out sooner rather than later. So I'm proposing a release in ~48 hours from now.7dde95a8bd
] - async-wrap: remove before/after calls in init (Trevor Norris) #1614bd42ba056a
] - async-wrap: set flags using functions (Trevor Norris) #16144b2c786449
] - async-wrap: pass PROVIDER as first arg to init (Trevor Norris) #161484bf609fd2
] - async-wrap: don't call init callback unnecessarily (Trevor Norris) #161404cc03b029
] - deps: update libuv to 1.5.0 (Saúl Ibarra Corretgé) #1646b16d9c28e8
] - deps: upgrade v8 to 4.2.77.20 (Ben Noordhuis) #16399ec3109272
] - doc: add TC meeting 2015-04-29 minutes (Rod Vagg) #15852c7206254c
] - doc: fix typo in readme.md (AQNOUCH Mohammed) #164371dc7152ee
] - doc: fix PR link in CHANGELOG (Brian White) #1624b97b96d05a
] - install: fix NameError (thefourtheye) #16286ccbe75384
] - js_stream: fix buffer index in DoWrite (Shigeki Ohtsu) #1635c43855c49c
] - src: export the ParseEncoding function on Windows (Ivan Kozik) #15968315b22390
] - src: fix pedantic cpplint whitespace warnings (Ben Noordhuis) #1640b712af79a7
] - src: fix NODE_DEPRECATED macro with old compilers (Ben Noordhuis) #16262ed10f1349
] - src: fix minor inefficiency in Buffer::New() call (Ben Noordhuis) #1577f696c9efab
] - src: fix deprecated use of Buffer::New() (Ben Noordhuis) #15770c8f13df8f
] - tools: remove unused GuessWordSize function (thefourtheye) #1638