| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@evanlucas It might be worth waiting until the changes discussed in #7123 (comment) land. Looks like #7751 + another PR this week. |
Sorry, something went wrong.
|
@gibfahn yea, this isn't going out today. I will incrementally updating this PR. If on Wednesday, v6.x is in a good state, we will push it out. If it needs to wait on things still, then we will wait :]. Thanks for the heads up though! |
Sorry, something went wrong.
|
btw, there are a couple of open PRs labelled v6.x, I think they all are good to go and can be landed/included here? |
Sorry, something went wrong.
|
@addaleax thanks! I'll take a look |
Sorry, something went wrong.
|
@evanlucas Nice, thanks for picking it up this week. :D Maybe mention the translations for the Windows installers in the Notable Changes? @addaleax if they land they will be included, usually we don't hold releases on specific PRs? |
Sorry, something went wrong.
|
@Fishrock123 Sorry, didn’t mean to imply these would need to be included or anything. |
Sorry, something went wrong.
|
did another round of commits. I will plan on shipping early tomorrow morning unless there are any objections. |
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/3333/ |
Sorry, something went wrong.
|
@evanlucas Re: "deps: upgrade to V8 5.0.71.54", some of the back-ports bump the patch level. Might be confusing to release notes readers. |
Sorry, something went wrong.
|
@bnoordhuis ah thanks for the heads up. Any suggestions on how to word to prevent confusion? |
Sorry, something went wrong.
|
Have we resolved the licensing issue with node inspector. I don't think we should ship again without having done that. |
Sorry, something went wrong.
|
looking at the issue where the things to be done are listed: #7123 (comment) it does not look like the licensing issues have been addressed. @ofrobots are those likely to get in soon ? |
Sorry, something went wrong.
Feel free to leave my name out and just say "Upgrade to V8 5.0.71.xx." |
Sorry, something went wrong.
|
@evanlucas the Italian translation introduced a bug that prevents the MSI to be generated. So, even if CI and CITGM are green, the release job will fail. You can either leave it out for this release or wait for #7798 to land (not sure if it qualifies as urgent and can land before 48h have passed?). |
Sorry, something went wrong.
|
@joaocgreis thanks for the heads up. I would be fine with it landing sooner than the 48h if @nodejs/platform-windows is cool with it |
Sorry, something went wrong.
|
I'm going to hold off on this until we know that the plinux issues are not from something in this branch |
Sorry, something went wrong.
|
@evanlucas I thought the plinux hardware was just generally having issues? @mhdawson? @jbergstroem / @rvagg ? |
Sorry, something went wrong.
|
@Fishrock123 yea, I just wanted to confirm |
Sorry, something went wrong.
Notable changes: * **buffer**: * Improve performance of Buffer.from(str, 'hex') and Buffer#write(str, 'hex'). (Christopher Jeffrey) #7602 * Fix creating from zero-length ArrayBuffer. (Ingvar Stepanyan) #7176 * **deps**: Upgrade to V8 5.0.71.xx. (Ben Noordhuis) #7531 * **repl**: Fix issue with function redeclaration. (Prince J Wesley) #7794 * **util**: Fix inspecting of boxed symbols. (Anna Henningsen) #7641 PR-URL: #7782
Sorry, something went wrong.
|
@Fishrock123 there was a specific failure with one of the PRs as opposed to a general issue. Right now not aware of any general issues on the PPC machines. I did investigate and since it seemed tied to the specific PR/machine and as we see has not recreated in the Ci run above suggested we proceed. |
Sorry, something went wrong.
|
@mhdawson I'm pretty sure that issue was happening on more than just that PR, but doesn't look to be happening anymore. Thanks for digging into that!!! |
Sorry, something went wrong.
Notable changes: * **buffer**: * Improve performance of Buffer.from(str, 'hex') and Buffer#write(str, 'hex'). (Christopher Jeffrey) #7602 * Fix creating from zero-length ArrayBuffer. (Ingvar Stepanyan) #7176 * **deps**: * Upgrade to V8 5.0.71.xx. (Ben Noordhuis) #7531 * Backport V8 instanceof bugfix (Franziska Hinkelmann) #7638 * **repl**: Fix issue with function redeclaration. (Prince J Wesley) #7794 * **util**: Fix inspecting of boxed symbols. (Anna Henningsen) #7641 PR-URL: #7782
PR-URL: #7782
|
Ok, final CI before building binaries: https://ci.nodejs.org/job/node-test-pull-request/3376/ |
Sorry, something went wrong.
Notable changes: * **buffer**: * Improve performance of Buffer.from(str, 'hex') and Buffer#write(str, 'hex'). (Christopher Jeffrey) #7602 * Fix creating from zero-length ArrayBuffer. (Ingvar Stepanyan) #7176 * **deps**: * Upgrade to V8 5.0.71.xx. (Ben Noordhuis) #7531 * Backport V8 instanceof bugfix (Franziska Hinkelmann) #7638 * **repl**: Fix issue with function redeclaration. (Prince J Wesley) #7794 * **util**: Fix inspecting of boxed symbols. (Anna Henningsen) #7641 PR-URL: #7782
|
@evanlucas When I suggested "Upgrade to V8 5.0.71.xx", the idea was to replace the .xx with the real patch level at the time of release. :-) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
2016-07-21, Version 6.3.1 (Current), @evanlucas
Notable changes
Commits