-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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: 2.3.0 #1939
Comments
I'd like to get #1934 fixed since it's colouring our jenkins bots red which may distract attention from other bugs. |
Sorry @Fishrock123 I think I neglected to |
yeah, for the last release (at least, perhaps more?) I removed the SEMVER-MAJOR from that so as not to confuse, it's a floating patch now. |
Oops, accidentally deleted that from my phone. The semver-major is a false positive. @rvagg were you also traveling? I'd like to get this out on like Friday if possible, but I'll be at nodeconf so maybe we should wait until Monday? |
At the risk of being alarmist over something trivial, might #1761 be semver-major? (Meta-question: Should I actually be talking about this in #1761 or here? Or is that dealer's choice?) It changes swallowing tabs in The old behavior wasn't documented (as far as I know), but it does seem like it was a choice and by design. And it seems at least conceivable that it is relied upon by some people in a way that will break things for them. (And they may see the existing behavior as a feature and not a bug.) Something like "My code took the user input and stripped out all the space characters but now it comes in with tabs and so there's whitespace and when I pass the string to my database call it blows up." Granted, that's a scenario where someone is Doing It Wrong, but a breaking change is a breaking change. |
If it is deemed semver-major I suggest reverting and relanding on next.
|
Heh. Hope I'm wrong then. On Thu, Jun 11, 2015 at 8:17 AM Jeremiah Senkpiel notifications@github.com
|
AFAIK tabs were the only character not accepted by readline, which was caused by an incorrectly implemented feature that made all tabs disappear, regardless of whether or not the feature was on. It was marked as |
@Fishrock123 thanks for the heads-up, I think it's important enough to get this out ASAP so I'll ship it this time tomorrow. Question about semver-major moved to #1761, if a leaning towards semver-major arises then we'll move it to |
The bug fix version but not security fix of openssl-1.0.2c will be released soon. |
#1958 is opened for upgrading to openssl-1.0.2c |
Upgrading to 1.0.2c was finished. Please go ahead to release. |
|
#1961 should land beforehand. The EDIT: landed! |
test-cluster-worker-wait-server-close.js is failing because of a timeout - note how it's at 60s for each failure, we can't release without this one resolved because it's across so many build slaves, so I'm investigating but other help would be appreciated too if anyone else has time. |
ah, looks like it landed @ #1953, thanks @sam-github https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/825/ running again to see whazzup |
My alternative test shows that it was timing out because the master client couldn't connect to the worker server. Id it's run directly on the same box it should pass. Something to do with setting the LOCALHOST environment variable. @jbergstroem was helping me test this out and has a gist with more information. |
@trevnorris LOCALHOST is not really relevant -- It's used to verify ipv4 testing in FreeBSD jails where routing 127.0.0.1 will give you the jail ip, making tests like @rvagg looks green to me! (I also verified this being fixed by #1953 but took at bit longer to land since the merge to iojs/master was slightly delayed) |
working on release notes, this is a big deal cause of so many commits .. |
How does this look, anyone? 2015-06-13, Version 2.3.0, @rvaggNotable changes
|
@rvagg Edit: Scheduling a new appointment at the eye doctor. |
I'm not commenting on the OpenSSL bit, but the rest of it LGTM. |
tagged & building @ https://jenkins-iojs.nodesource.com/job/iojs+release/73/ amendments to the changelog can be done via PR if anyone has any, sorry for the short time on call for review! |
LGTM |
running smoke test and seeing some failures on coffeescript, grunt and request but I don't think they are related to this release .. quickly investigating |
Just downloaded the MSI (x64, Windows Server 2012 R2) and perform an install over
|
nope, not intentional, nothing has changed with msi building for a long time, can you screenshot that for us? |
Completely uninstalling and deleting io.js files from the system works around this issue, i.e. on fresh attempt all components are marked to be installed. |
The libuv part LGTM.
|
All binaries including armv6 are up, so this release is done. |
PR-URL: nodejs#69 Close nodejs#68 Related: nodejs/node#1939 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
I think it would be prudent to have a 2.3.0 release before 3.0.0, as we've accumulated quite a few commits.
79bb5e1...91d0a8b
(changelog-maker broke with the rename of things..?)
(there's some semver-minor stuff in there.)
cc @rvagg
The text was updated successfully, but these errors were encountered: