| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@nodejs/tsc @nodejs/lts |
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/451/ On initial run, everything green except for one test timeout in a test in pi1-raspbian-wheezy (https://ci.nodejs.org/job/node-test-binary-arm/150/RUN_SUBSET=5,nodes=pi1-raspbian-wheezy/) |
Sorry, something went wrong.
|
@srl295 ... I know you are looking to get ICU bumped up to 56 in v4.x. Is it possible to get that work completed and landed in master by monday? If yes, I can cherry pick it into this for 4.2 |
Sorry, something went wrong.
|
This morning El miércoles, 7 de octubre de 2015, James M Snell notifications@github.com
|
Sorry, something went wrong.
|
Picked three additional commits from master onto v4.x, rebased and updated the CHANGELOG |
Sorry, something went wrong.
|
Outstanding Issues before we can close on this: |
Sorry, something went wrong.
|
Does it include my Buffer::New fix? Cc @trevnorris On Thursday, October 8, 2015, James M Snell notifications@github.com
|
Sorry, something went wrong.
|
It does, thanks! |
Sorry, something went wrong.
|
@nodejs/collaborators ... this is a last call for v4.2! I can get semver-patch and conservative semver-minor commits that land in master pulled over into v4.x but want to get things locked down so we can run a variety of tests over the weekend to make sure things are solid before cutting the v4.2.0 LTS release on monday. If there are any PRs you think should be landed in v4.x, attach the land-on-v4.x label to the PR and mention me in a comment. |
Sorry, something went wrong.
|
Pulled in a couple more commits, rebased and updated changelog. Still waiting on the ICU 56 bump and any other last call items. (will land the ICU 56 bump in v4.x once a @mhdawson is done with a bit of sniff testing on his end) |
Sorry, something went wrong.
|
ICU update landed. Now waiting for a fix for #3283 . |
Sorry, something went wrong.
😋 |
Sorry, something went wrong.
Sorry, something went wrong.
|
Yep. This makes the assumption that that will close by then.
|
Sorry, something went wrong.
|
@jasnell we have a conflict with my PR @ #3212 for adding process.release.lts. I'm proposing a simple version that just adds it as a straight property without the node_version.h stuff—I don't see a reason this change needs to exist at all on master which is why there's no special macro work. At a minimum I'd like to include the test and the doc changes from #3212, I'm also in favour of "Argon" vs "argon". Thoughts? |
Sorry, something went wrong.
|
@rvagg ... I can easily back my changes on that out of the proposal PR. I
|
Sorry, something went wrong.
+1 this spelling |
Sorry, something went wrong.
|
Can we include #3299 in this, too? (also, kinda wish we'd call it "Blaze It" but oh well. That 🚢 has sailed) |
Sorry, something went wrong.
Locking this down. Not going to pull anything else from master unless it's a bug fix. @nodejs/collaborators @nodejs/lts ... please start smoke testing this! |
Sorry, something went wrong.
|
@rvagg @Fishrock123 @mhdawson @nodejs/lts ... anything further needed on this? Looking to cut the release on Monday morning. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Suggestion for notable items section changes from what you currently have, to be consistent: ## Notable changes The first Node.js LTS release! See https://github.com/nodejs/LTS/ for details of the LTS process. * **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) [#3281](https://github.com/nodejs/node/pull/3281) * **node**: - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) [#2411](https://github.com/nodejs/node/pull/2411) - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) [#3102](https://github.com/nodejs/node/pull/3102) - Added `process.release.lts` to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg) [#3212](https://github.com/nodejs/node/pull/3212) * **npm**: Upgraded to npm 2.14.7 from 2.14.4, see [release notes](https://github.com/npm/npm/releases/tag/v2.14.7) for full details (Kat Marchán) [#3299](https://github.com/nodejs/node/pull/3299) Also, Known issues instead of Known Issues. |
Sorry, something went wrong.
|
@jasnell I think #3212 is good to go and matches what you have here, it hasn't had review since I changed it, however, so can I get you to merge it if you start working on the release soon? I'll be 💤 for the next 8 hours or so, so don't count on me being around. |
Sorry, something went wrong.
|
@jasnell also, when you post to the nodejs.org blog, perhaps put a little blurb at the top about what it means for this to be LTS, where to get more information and to expect a v5 that's not LTS to be out by the end of the month. I'm betting there's a significant number of people that haven't heard the message about LTS (and a lot who have but don't know what LTS stands for so have been ignoring it). |
Sorry, something went wrong.
|
@rvagg excellent. Ok. I'll be starting on finalizing this around 8:00am
|
Sorry, something went wrong.
The first Node.js LTS release! See https://github.com/nodejs/LTS/ for details of the LTS process. * **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) #3281 * **node**: - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) #2411 - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) #3102 - Added `process.release.lts` to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg) #3212 * **npm**: Upgraded to npm 2.14.7 from 2.14.4, see release notes: https://github.com/npm/npm/releases/tag/v2.14.7 for full details (Kat Marchán) #3299 PR-URL: #3258
The first Node.js LTS release! See https://github.com/nodejs/LTS/ for details of the LTS process. * **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) #3281 * **node**: - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) #2411 - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) #3102 - Added `process.release.lts` to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg) #3212 * **npm**: Upgraded to npm 2.14.7 from 2.14.4, see release notes: https://github.com/npm/npm/releases/tag/v2.14.7 for full details (Kat Marchán) #3299 PR-URL: #3258
Sorry, something went wrong.
|
@Fishrock123 ... I just finished building the main release artifacts and was smoketesting a bit before tagging. Is this one critical? |
Sorry, something went wrong.
|
nm... I'll go ahead and land it. Needs to be the last one tho. Will kick off a new iojs+release run in a sec |
Sorry, something went wrong.
Sorry, something went wrong.
|
@indutny @Fishrock123 ... Y'all are killing me here ;-P |
Sorry, something went wrong.
The first Node.js LTS release! See https://github.com/nodejs/LTS/ for details of the LTS process. * **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) #3281 * **node**: - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) #2411 - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) #3102 - Added `process.release.lts` to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg) #3212 * **npm**: Upgraded to npm 2.14.7 from 2.14.4, see release notes: https://github.com/npm/npm/releases/tag/v2.14.7 for full details (Kat Marchán) #3299 PR-URL: #3258
The first Node.js LTS release! See https://github.com/nodejs/LTS/ for details of the LTS process. * **icu**: Updated to version 56 with significant performance improvements (Steven R. Loomis) #3281 * **node**: - Added new `-c` (or `--check`) command line argument for checking script syntax without executing the code (Dave Eddy) #2411 - Added `process.versions.icu` to hold the current ICU library version (Evan Lucas) #3102 - Added `process.release.lts` to hold the current LTS codename when the binary is from an active LTS release line (Rod Vagg) #3212 * **npm**: Upgraded to npm 2.14.7 from 2.14.4, see release notes: https://github.com/npm/npm/releases/tag/v2.14.7 for full details (Kat Marchán) #3299 PR-URL: #3258
|
Release done. |
Sorry, something went wrong.
Sorry, something went wrong.
|
I'm gonna go lay down now. I need a nap. |
Sorry, something went wrong.
|
@jasnell Sorry didn't see that thread earlier but it wouldn't it make sense to add src: replace naive search in Buffer::IndexOf under notable changes? And the additional argument for indexOf needs to be documented. I was a bit surprised this PR was merged first into LTS. |
Sorry, something went wrong.
|
@skomski ... PRs to add it to the notable changes in the CHANGELOG for both master, v4.x and the new.nodejs.org entry would be good. You're right, it should be called out. Landing semver-minor bits like that is fine as we come up to the LTS release.. landing it after we cut the LTS is a no-no.. and I felt it was a good enough improvement that it made sense to get it in (especially since we were doing a minor bump for the LTS anyway). |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Aiming for Monday release. This is for the LTS release. Notable changes still need to be documented and there's still likely a small handful of issues that need to be closed and included (see https://github.com/nodejs/node/pulls?page=1&q=is%3Apr+label%3Aland-on-v4.x+-label%3Alts-landed-on-v4.x&utf8=%E2%9C%93)