diff --git a/.editorconfig b/.editorconfig
index ca97ab47dfea49..2b0070686f4d5c 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -4,6 +4,7 @@ root = true
 end_of_line = lf
 charset = utf-8
 trim_trailing_whitespace = true
+insert_final_newline = true
 
 [vcbuild.bat]
 end_of_line = crlf
@@ -37,3 +38,6 @@ indent_size = ignore
 end_of_line = ignore
 trim_trailing_whitespace = ignore
 charset = ignore
+
+[{test/fixtures,deps,tools/eslint,tools/gyp,tools/icu,tools/msvs}/**]
+insert_final_newline = false
diff --git a/.gitignore b/.gitignore
index 8a6cc149115708..35e3b840e933af 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,19 @@
+# Whitelist dotfiles
+.*
+!deps/**/.*
+!test/fixtures/**/.*
+!tools/eslint/**/.*
+!tools/doc/node_modules/**/.*
+!.editorconfig
+!.eslintignore
+!.eslintrc
+!.gitattributes
+!.github
+!.gitignore
+!.gitkeep
+!.mailmap
+!.remarkrc
+
 core
 vgcore.*
 v8*.log
@@ -16,8 +32,6 @@ node
 node_g
 *.swp
 .benchmark_reports
-/.project
-/.cproject
 icu_config.gypi
 
 /out
diff --git a/BUILDING.md b/BUILDING.md
index b634d34b6d1cca..c657e63514139a 100644
--- a/BUILDING.md
+++ b/BUILDING.md
@@ -123,7 +123,7 @@ To test if Node.js was built correctly:
 > Release\node -e "console.log('Hello from Node.js', process.version)"
 ```
 
-### Android / Android-based devices (e.g., Firefox OS)
+### Android / Android-based devices (e.g. Firefox OS)
 
 Although these instructions for building on Android are provided, please note
 that Android is not an officially supported platform at this time. Patches to
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 708b6811d7d1ad..d23fb40d930b68 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,200 @@
 # Node.js ChangeLog
 
+## 2017-01-03, Version 4.7.1 'Argon' (LTS), @MylesBorins
+
+This LTS release comes with 180 commits. This includes 117 which are test related,
+34 which are doc related, 15 which are build / tool related, and 1 commit which is
+an update to dependencies.
+
+### Notable Changes
+
+* **build**: shared library support is now working for AIX builds (Stewart Addison) [#9675](https://github.com/nodejs/node/pull/9675)
+* **repl**: Passing options to the repl will no longer overwrite defaults (cjihrig) [#7826](https://github.com/nodejs/node/pull/7826)
+* **timers**: Re canceling a cancelled timers will no longer throw (Jeremiah Senkpiel) [#9685](https://github.com/nodejs/node/pull/9685)
+
+### Commits
+
+* [[`c5f82b8421`](https://github.com/nodejs/node/commit/c5f82b8421)] - **assert**: fix deepEqual/deepStrictEqual on equivalent typed arrays (Feross Aboukhadijeh) [#8002](https://github.com/nodejs/node/pull/8002)
+* [[`60883de30f`](https://github.com/nodejs/node/commit/60883de30f)] - **async_wrap**: call destroy() callback in uv_idle_t (Trevor Norris)
+* [[`28dbc460c6`](https://github.com/nodejs/node/commit/28dbc460c6)] - **async_wrap**: make Initialize a static class member (Trevor Norris)
+* [[`bb05cd13db`](https://github.com/nodejs/node/commit/bb05cd13db)] - **async_wrap**: mode constructor/destructor to .cc (Trevor Norris)
+* [[`b1075f6193`](https://github.com/nodejs/node/commit/b1075f6193)] - **benchmark**: split timers benchmark and refactor (Rich Trott) [#9497](https://github.com/nodejs/node/pull/9497)
+* [[`7b4268b889`](https://github.com/nodejs/node/commit/7b4268b889)] - **benchmark,lib,test,tools**: remove unneeded . escape (Rich Trott) [#9449](https://github.com/nodejs/node/pull/9449)
+* [[`54f2ce8ea0`](https://github.com/nodejs/node/commit/54f2ce8ea0)] - **build**: prioritise --shared-X-Y over pkg-config (Rod Vagg) [#9368](https://github.com/nodejs/node/pull/9368)
+* [[`61d377ddcd`](https://github.com/nodejs/node/commit/61d377ddcd)] - **build**: Make configure file parseable on python3 (kalrover) [#9657](https://github.com/nodejs/node/pull/9657)
+* [[`38e0f95d24`](https://github.com/nodejs/node/commit/38e0f95d24)] - **build**: add MAKEFLAGS="-j1" to node-gyp (Daniel Bevenius) [#9450](https://github.com/nodejs/node/pull/9450)
+* [[`d1b6407395`](https://github.com/nodejs/node/commit/d1b6407395)] - **build**: make node-gyp output silent (Sakthipriyan Vairamani (thefourtheye)) [#8990](https://github.com/nodejs/node/pull/8990)
+* [[`ae2eff2997`](https://github.com/nodejs/node/commit/ae2eff2997)] - **build**: start comments at beginning of line (Sakthipriyan Vairamani (thefourtheye)) [#9375](https://github.com/nodejs/node/pull/9375)
+* [[`6f1f955b33`](https://github.com/nodejs/node/commit/6f1f955b33)] - **build**: default to ppc64 on AIX (Gibson Fahnestock) [#9645](https://github.com/nodejs/node/pull/9645)
+* [[`f8d4577762`](https://github.com/nodejs/node/commit/f8d4577762)] - **build**: Add option to compile for coverage reports (Wayne Andrews) [#9463](https://github.com/nodejs/node/pull/9463)
+* [[`f2b00985f0`](https://github.com/nodejs/node/commit/f2b00985f0)] - **build**: add shared library support to AIX build (Stewart Addison) [#9675](https://github.com/nodejs/node/pull/9675)
+* [[`e2c5f41ddf`](https://github.com/nodejs/node/commit/e2c5f41ddf)] - **crypto**: use SSL_get_servername. (Adam Langley) [#9347](https://github.com/nodejs/node/pull/9347)
+* [[`724910a991`](https://github.com/nodejs/node/commit/724910a991)] - **debugger**: refactor _debugger.js (Rich Trott) [#9860](https://github.com/nodejs/node/pull/9860)
+* [[`52f14931a2`](https://github.com/nodejs/node/commit/52f14931a2)] - **deps**: backport GYP fix to fix AIX shared suffix (Stewart Addison) [#9675](https://github.com/nodejs/node/pull/9675)
+* [[`c77ba8ce14`](https://github.com/nodejs/node/commit/c77ba8ce14)] - **doc**: consistent 'Returns:' (Roman Reiss) [#9554](https://github.com/nodejs/node/pull/9554)
+* [[`aecb2cac37`](https://github.com/nodejs/node/commit/aecb2cac37)] - **doc**: adding missing - in README (Italo A. Casas) [#10170](https://github.com/nodejs/node/pull/10170)
+* [[`52c022992e`](https://github.com/nodejs/node/commit/52c022992e)] - **doc**: removing extra space in README (Italo A. Casas) [#10168](https://github.com/nodejs/node/pull/10168)
+* [[`e8c57bbe77`](https://github.com/nodejs/node/commit/e8c57bbe77)] - **doc**: add people to cc for async_wrap (Anna Henningsen) [#9471](https://github.com/nodejs/node/pull/9471)
+* [[`b5eae4463c`](https://github.com/nodejs/node/commit/b5eae4463c)] - **doc**: add link to `net.Server` in tls.md (Devon Rifkin) [#10109](https://github.com/nodejs/node/pull/10109)
+* [[`ad841a29d1`](https://github.com/nodejs/node/commit/ad841a29d1)] - **doc**: clarify fs.createReadStream options (Wes Tyler) [#10078](https://github.com/nodejs/node/pull/10078)
+* [[`338014ef24`](https://github.com/nodejs/node/commit/338014ef24)] - **doc**: rename writing_tests.md to writing-tests.md (Safia Abdalla) [#9867](https://github.com/nodejs/node/pull/9867)
+* [[`b06b2343bc`](https://github.com/nodejs/node/commit/b06b2343bc)] - **doc**: it’s -> its in api/child_process.md (Devon Rifkin) [#10090](https://github.com/nodejs/node/pull/10090)
+* [[`4885573080`](https://github.com/nodejs/node/commit/4885573080)] - **doc**: update Collaborators list in README (Rich Trott) [#9846](https://github.com/nodejs/node/pull/9846)
+* [[`3105becb2c`](https://github.com/nodejs/node/commit/3105becb2c)] - **doc**: remove minor contradiction in debugger doc (Rich Trott) [#9832](https://github.com/nodejs/node/pull/9832)
+* [[`a858e98921`](https://github.com/nodejs/node/commit/a858e98921)] - **doc**: clarify introductory module material (Rich Trott) [#9816](https://github.com/nodejs/node/pull/9816)
+* [[`18c38819fe`](https://github.com/nodejs/node/commit/18c38819fe)] - **doc**: improve description of module `exports` (Sam Roberts) [#9622](https://github.com/nodejs/node/pull/9622)
+* [[`9e68b8d329`](https://github.com/nodejs/node/commit/9e68b8d329)] - **doc**: fix crypto Verify cut-n-paste from Sign (子丶言) [#9796](https://github.com/nodejs/node/pull/9796)
+* [[`fd1a48c9c9`](https://github.com/nodejs/node/commit/fd1a48c9c9)] - **doc**: minor fixes event-loop-timers-and-nexttick.md (Dan Koster) [#9126](https://github.com/nodejs/node/pull/9126)
+* [[`107735a6e1`](https://github.com/nodejs/node/commit/107735a6e1)] - **doc**: changed order of invocations in https.request() example. (atrioom) [#9614](https://github.com/nodejs/node/pull/9614)
+* [[`eb5972fe9b`](https://github.com/nodejs/node/commit/eb5972fe9b)] - **doc**: fix crypto "decipher.setAAD()" typo (子丶言) [#9782](https://github.com/nodejs/node/pull/9782)
+* [[`dc4c348ea3`](https://github.com/nodejs/node/commit/dc4c348ea3)] - **doc**: fix typo in assert code example (Vse Mozhet Byt) [#9704](https://github.com/nodejs/node/pull/9704)
+* [[`16e97ab6c6`](https://github.com/nodejs/node/commit/16e97ab6c6)] - **doc**: fix typo in BUILDING.md (monkick) [#9569](https://github.com/nodejs/node/pull/9569)
+* [[`4f2e25441e`](https://github.com/nodejs/node/commit/4f2e25441e)] - **doc**: remove backtick escaping for manpage refs (Anna Henningsen) [#9632](https://github.com/nodejs/node/pull/9632)
+* [[`c0d44dfcc7`](https://github.com/nodejs/node/commit/c0d44dfcc7)] - **doc**: remove invalid padding from privateEncrypt (JungMinu) [#9611](https://github.com/nodejs/node/pull/9611)
+* [[`0f523583c3`](https://github.com/nodejs/node/commit/0f523583c3)] - **doc**: remove Sam Roberts from release team (Sam Roberts) [#9862](https://github.com/nodejs/node/pull/9862)
+* [[`4eeac8eb8c`](https://github.com/nodejs/node/commit/4eeac8eb8c)] - **doc**: add guide for maintaining V8 (Ali Ijaz Sheikh) [#9777](https://github.com/nodejs/node/pull/9777)
+* [[`34405ddb83`](https://github.com/nodejs/node/commit/34405ddb83)] - **doc**: move TSC and CTC meeting minutes out of core repo (James M Snell) [#9503](https://github.com/nodejs/node/pull/9503)
+* [[`198463a0ff`](https://github.com/nodejs/node/commit/198463a0ff)] - **doc**: fix a typo in the assert.md (Vse Mozhet Byt) [#9598](https://github.com/nodejs/node/pull/9598)
+* [[`aca0ede0d3`](https://github.com/nodejs/node/commit/aca0ede0d3)] - **doc**: fix typo e.g., => e.g. (Daijiro Yamada) [#9563](https://github.com/nodejs/node/pull/9563)
+* [[`c7997939f2`](https://github.com/nodejs/node/commit/c7997939f2)] - **doc**: fix typo about cluster doc, (eg. -> e.g.) (YutamaKotaro) [#9568](https://github.com/nodejs/node/pull/9568)
+* [[`229fa6921f`](https://github.com/nodejs/node/commit/229fa6921f)] - **doc**: fix e.g., to e.g. in doc/http.md (ikasumi_wt) [#9564](https://github.com/nodejs/node/pull/9564)
+* [[`3ad7430f12`](https://github.com/nodejs/node/commit/3ad7430f12)] - **doc**: fix the index order in pseudocode of modules (kohta ito) [#9562](https://github.com/nodejs/node/pull/9562)
+* [[`06732babd3`](https://github.com/nodejs/node/commit/06732babd3)] - **doc**: remove Roadmap Working Group (William Kapke) [#9545](https://github.com/nodejs/node/pull/9545)
+* [[`6775163a94`](https://github.com/nodejs/node/commit/6775163a94)] - **doc**: fix minor style issue in code examples (Daniel Bevenius) [#9482](https://github.com/nodejs/node/pull/9482)
+* [[`aa25c74fe6`](https://github.com/nodejs/node/commit/aa25c74fe6)] - **doc**: grammar and structure revisions of wg doc (Ryan Lewis) [#9495](https://github.com/nodejs/node/pull/9495)
+* [[`1e06ed7e9d`](https://github.com/nodejs/node/commit/1e06ed7e9d)] - **doc**: clarify the exit code part of writing_tests (Jeremiah Senkpiel) [#9502](https://github.com/nodejs/node/pull/9502)
+* [[`3f39a39657`](https://github.com/nodejs/node/commit/3f39a39657)] - **doc**: Fix inaccuracy in https.request docs (Andreas Lind) [#9453](https://github.com/nodejs/node/pull/9453)
+* [[`8380154e22`](https://github.com/nodejs/node/commit/8380154e22)] - **doc**: add npm link to README (Oscar Morrison) [#7894](https://github.com/nodejs/node/pull/7894)
+* [[`65e134ff12`](https://github.com/nodejs/node/commit/65e134ff12)] - **meta**: whitelist dotfiles in .gitignore (Claudio Rodriguez) [#8016](https://github.com/nodejs/node/pull/8016)
+* [[`698bf2e829`](https://github.com/nodejs/node/commit/698bf2e829)] - **repl**: don't override all internal repl defaults (cjihrig) [#7826](https://github.com/nodejs/node/pull/7826)
+* [[`3d45b35f73`](https://github.com/nodejs/node/commit/3d45b35f73)] - **repl**: refactor lib/repl.js (Rich Trott) [#9374](https://github.com/nodejs/node/pull/9374)
+* [[`f5b952b221`](https://github.com/nodejs/node/commit/f5b952b221)] - **test**: refactor and fix test-dns (Michaël Zasso) [#9811](https://github.com/nodejs/node/pull/9811)
+* [[`8b733dca05`](https://github.com/nodejs/node/commit/8b733dca05)] - **test**: refactor test-crypto-binary-default (Michaël Zasso) [#9810](https://github.com/nodejs/node/pull/9810)
+* [[`45af7857d7`](https://github.com/nodejs/node/commit/45af7857d7)] - **test**: refactor and fix test-crypto (Michaël Zasso) [#9807](https://github.com/nodejs/node/pull/9807)
+* [[`e0c8aafad8`](https://github.com/nodejs/node/commit/e0c8aafad8)] - **test**: fix test-buffer-slow (Michaël Zasso) [#9809](https://github.com/nodejs/node/pull/9809)
+* [[`e72dfce2c8`](https://github.com/nodejs/node/commit/e72dfce2c8)] - **test**: added validation regex argument to test (Avery, Frank) [#9918](https://github.com/nodejs/node/pull/9918)
+* [[`a779e7ffec`](https://github.com/nodejs/node/commit/a779e7ffec)] - **test**: clean up repl-reset-event file (Kailean Courtney) [#9931](https://github.com/nodejs/node/pull/9931)
+* [[`4022579b6e`](https://github.com/nodejs/node/commit/4022579b6e)] - **test**: improve domain-top-level-error-handler-throw (CodeVana) [#9950](https://github.com/nodejs/node/pull/9950)
+* [[`d3edaa3dc3`](https://github.com/nodejs/node/commit/d3edaa3dc3)] - **test**: replace var with const in test-require-dot (Amar Zavery) [#9916](https://github.com/nodejs/node/pull/9916)
+* [[`8694811ef0`](https://github.com/nodejs/node/commit/8694811ef0)] - **test**: refactor test-net-pingpong (Michaël Zasso) [#9812](https://github.com/nodejs/node/pull/9812)
+* [[`e849dd0ff3`](https://github.com/nodejs/node/commit/e849dd0ff3)] - **test**: Use strictEqual in test-tls-writewrap-leak (Aaron Petcoff) [#9666](https://github.com/nodejs/node/pull/9666)
+* [[`0662429268`](https://github.com/nodejs/node/commit/0662429268)] - **test**: fix test-tls-connect-address-family (mkamakura) [#9573](https://github.com/nodejs/node/pull/9573)
+* [[`420e7f17d9`](https://github.com/nodejs/node/commit/420e7f17d9)] - **test**: fix test-http-status-reason-invalid-chars (Yosuke Saito) [#9572](https://github.com/nodejs/node/pull/9572)
+* [[`13cace140f`](https://github.com/nodejs/node/commit/13cace140f)] - **test**: fix helper-debugger-repl.js (Rich Trott) [#9486](https://github.com/nodejs/node/pull/9486)
+* [[`aebbc965f9`](https://github.com/nodejs/node/commit/aebbc965f9)] - **test**: refactor large event emitter tests (cjihrig) [#6446](https://github.com/nodejs/node/pull/6446)
+* [[`b5012f3de2`](https://github.com/nodejs/node/commit/b5012f3de2)] - **test**: add expectWarning to common (Michaël Zasso) [#8662](https://github.com/nodejs/node/pull/8662)
+* [[`b98813d97c`](https://github.com/nodejs/node/commit/b98813d97c)] - **test**: refactor test-fs-non-number-arguments-throw (Michaël Zasso) [#9844](https://github.com/nodejs/node/pull/9844)
+* [[`80a752708a`](https://github.com/nodejs/node/commit/80a752708a)] - **test**: refactor test-dgram-exclusive-implicit-bind (Cesar Hernandez) [#10066](https://github.com/nodejs/node/pull/10066)
+* [[`9b974b4d54`](https://github.com/nodejs/node/commit/9b974b4d54)] - **test**: use `assert.strictEqual` (anoff) [#9975](https://github.com/nodejs/node/pull/9975)
+* [[`bc125bd729`](https://github.com/nodejs/node/commit/bc125bd729)] - **test**: change assert.equal to assert.strictEqual (Aileen) [#9946](https://github.com/nodejs/node/pull/9946)
+* [[`5049a10278`](https://github.com/nodejs/node/commit/5049a10278)] - **test**: changed assert.equal to assert.strictEqual (vazina robertson) [#10015](https://github.com/nodejs/node/pull/10015)
+* [[`b5c60edeed`](https://github.com/nodejs/node/commit/b5c60edeed)] - **test**: renamed assert.Equal to assert.strictEqual (Jared Young)
+* [[`f44e828a36`](https://github.com/nodejs/node/commit/f44e828a36)] - **test**: improves test-tls-client-verify (Paul Graham) [#10051](https://github.com/nodejs/node/pull/10051)
+* [[`a1e3967f69`](https://github.com/nodejs/node/commit/a1e3967f69)] - **test**: refactor test-https-agent-session-reuse (Diego Paez) [#10105](https://github.com/nodejs/node/pull/10105)
+* [[`9e46af6412`](https://github.com/nodejs/node/commit/9e46af6412)] - **test**: refactor test-beforeexit-event (Rob Adelmann) [#10121](https://github.com/nodejs/node/pull/10121)
+* [[`adcd6ea66f`](https://github.com/nodejs/node/commit/adcd6ea66f)] - **test**: refactor test-domain-from-timer (Daniel Sims) [#9889](https://github.com/nodejs/node/pull/9889)
+* [[`1377ea87eb`](https://github.com/nodejs/node/commit/1377ea87eb)] - **test**: refactor test-domain-exit-dispose-again (Ethan Arrowood) [#10003](https://github.com/nodejs/node/pull/10003)
+* [[`8a9af6843d`](https://github.com/nodejs/node/commit/8a9af6843d)] - **test**: use const and strictEqual in test-os-homedir-no-envvar (CodeVana) [#9899](https://github.com/nodejs/node/pull/9899)
+* [[`ee038c0e71`](https://github.com/nodejs/node/commit/ee038c0e71)] - **test**: refactor test-dgram-bind-default-address (Michael-Bryant Choa) [#9947](https://github.com/nodejs/node/pull/9947)
+* [[`a090899e93`](https://github.com/nodejs/node/commit/a090899e93)] - **test**: assert.throws() should include a RegExp (Chris Bystrek) [#9976](https://github.com/nodejs/node/pull/997://github.com/nodejs/node/pull/9976)
+* [[`542b40f410`](https://github.com/nodejs/node/commit/542b40f410)] - **test**: refactor test-event-emitter-method-names (Rodrigo Palma) [#10027](https://github.com/nodejs/node/pull/10027)
+* [[`a2023a9d97`](https://github.com/nodejs/node/commit/a2023a9d97)] - **test**: refactor tls-ticket-cluster (Yojan Shrestha) [#10023](https://github.com/nodejs/node/pull/10023)
+* [[`a64f40680f`](https://github.com/nodejs/node/commit/a64f40680f)] - **test**: refactor test-domain-exit-dispose (Chris Henney) [#9938](https://github.com/nodejs/node/pull/9938)
+* [[`a896d4ed36`](https://github.com/nodejs/node/commit/a896d4ed36)] - **test**: refactor test-stdin-from-file.js (amrios) [#10012](https://github.com/nodejs/node/pull/10012)
+* [[`ce14c1e51f`](https://github.com/nodejs/node/commit/ce14c1e51f)] - **test**: refactor test-require-extensions-main (Daryl Thayil) [#9912](https://github.com/nodejs/node/pull/9912)
+* [[`b9c45026f7`](https://github.com/nodejs/node/commit/b9c45026f7)] - **test**: clean up tls junk test (Danny Guo) [#9940](https://github.com/nodejs/node/pull/9940)
+* [[`e3712334a3`](https://github.com/nodejs/node/commit/e3712334a3)] - **test**: update test-stdout-to-file (scalkpdev) [#9939](https://github.com/nodejs/node/pull/9939)
+* [[`63f571e69c`](https://github.com/nodejs/node/commit/63f571e69c)] - **test**: changed assert.Equal to asset.strictEqual (Paul Chin) [#9973](https://github.com/nodejs/node/pull/9973)
+* [[`c3a3480606`](https://github.com/nodejs/node/commit/c3a3480606)] - **test**: refactor test-domain-multi (Wes Tyler) [#9963](https://github.com/nodejs/node/pull/9963)
+* [[`ad27555ff8`](https://github.com/nodejs/node/commit/ad27555ff8)] - **test**: use assert.strictEqual in test-cli-eval (Nigel Kibodeaux) [#9919](https://github.com/nodejs/node/pull/9919)
+* [[`cffd51e815`](https://github.com/nodejs/node/commit/cffd51e815)] - **test**: refactor test-tls-connect-simple (Russell Sherman) [#9934](https://github.com/nodejs/node/pull/9934)
+* [[`1424c25f3e`](https://github.com/nodejs/node/commit/1424c25f3e)] - **test**: refactor test-signal-unregister (mark hughes) [#9920](https://github.com/nodejs/node/pull/9920)
+* [[`920737180f`](https://github.com/nodejs/node/commit/920737180f)] - **test**: refactor test-require-resolve (blugavere) [#10120](https://github.com/nodejs/node/pull/10120)
+* [[`71ab88cc80`](https://github.com/nodejs/node/commit/71ab88cc80)] - **test**: refactor test-fs-read-stream-resume (Matt Webb) [#9927](https://github.com/nodejs/node/pull/9927)
+* [[`6a485da87c`](https://github.com/nodejs/node/commit/6a485da87c)] - **test**: replace equal with strictEqual (Tracy Hinds) [#10011](https://github.com/nodejs/node/pull/10011)
+* [[`b5d87569e1`](https://github.com/nodejs/node/commit/b5d87569e1)] - **test**: use strictEqual instead of equal (Uttam Pawar) [#9921](https://github.com/nodejs/node/pull/9921)
+* [[`c94c2fde8a`](https://github.com/nodejs/node/commit/c94c2fde8a)] - **test**: using const and strictEqual (Fabrice Tatieze) [#9926](https://github.com/nodejs/node/pull/9926)
+* [[`16164b5b44`](https://github.com/nodejs/node/commit/16164b5b44)] - **test**: test-file-write-stream3.js refactor (Richard Karmazin) [#10035](https://github.com/nodejs/node/pull/10035)
+* [[`7391983729`](https://github.com/nodejs/node/commit/7391983729)] - **test**: implemented es6 conventions (Erez Weiss) [#9669](https://github.com/nodejs/node/pull/9669)
+* [[`50ce3f91d7`](https://github.com/nodejs/node/commit/50ce3f91d7)] - **test**: update assert.equal() to assert.strictEqual() (Peter Diaz) [#10024](https://github.com/nodejs/node/pull/10024)
+* [[`3f9d75c481`](https://github.com/nodejs/node/commit/3f9d75c481)] - **test**: use const or let and assert.strictEqual (Christopher Rokita) [#10001](https://github.com/nodejs/node/pull/10001)
+* [[`98afba5676`](https://github.com/nodejs/node/commit/98afba5676)] - **test**: use strictEqual() domain-http (cdnadmin) [#9996](https://github.com/nodejs/node/pull/9996)
+* [[`07680b65fe`](https://github.com/nodejs/node/commit/07680b65fe)] - **test**: refactor test-cluster-worker-events (fmizzell) [#9994](https://github.com/nodejs/node/pull/9994)
+* [[`a3db54416f`](https://github.com/nodejs/node/commit/a3db54416f)] - **test**: update repl tests (makenova) [#9991](https://github.com/nodejs/node/pull/9991)
+* [[`db3cdd2449`](https://github.com/nodejs/node/commit/db3cdd2449)] - **test**: adding strictEqual to test-buffer-indexof.js (Eric Gonzalez) [#9955](https://github.com/nodejs/node/pull/9955)
+* [[`f670b05603`](https://github.com/nodejs/node/commit/f670b05603)] - **test**: strictEqual in test-beforeexit-event.js (CodeTheInternet) [#10004](https://github.com/nodejs/node/pull/10004)
+* [[`70b4d7d3a2`](https://github.com/nodejs/node/commit/70b4d7d3a2)] - **test**: refactor test-child-process-double-pipe (Dan Villa) [#9930](https://github.com/nodejs/node/pull/9930)
+* [[`1e53cf4764`](https://github.com/nodejs/node/commit/1e53cf4764)] - **test**: updated test-stream-pipe-unpipe-stream (Raja Panidepu) [#10100](https://github.com/nodejs/node/pull/10100)
+* [[`57d48ac3f4`](https://github.com/nodejs/node/commit/57d48ac3f4)] - **test**: refactor test-crypto-ecb (michael6) [#10029](https://github.com/nodejs/node/pull/10029)
+* [[`89feb8dc4d`](https://github.com/nodejs/node/commit/89feb8dc4d)] - **test**: refactor test-require-exceptions (Oscar Martinez) [#9882](https://github.com/nodejs/node/pull/9882)
+* [[`59f259c487`](https://github.com/nodejs/node/commit/59f259c487)] - **test**: refactor test-crypto-certificate (Josh Mays) [#9911](https://github.com/nodejs/node/pull/9911)
+* [[`815715d850`](https://github.com/nodejs/node/commit/815715d850)] - **test**: refactor test-domain (Johnny Reading) [#9890](https://github.com/nodejs/node/pull/9890)
+* [[`08cc269338`](https://github.com/nodejs/node/commit/08cc269338)] - **test**: refactor test-cli-syntax (Exlipse7) [#10057](https://github.com/nodejs/node/pull/10057)
+* [[`91d27ce4db`](https://github.com/nodejs/node/commit/91d27ce4db)] - **test**: refactor test-child-process-constructor (k3kathy) [#10060](https://github.com/nodejs/node/pull/10060)
+* [[`ae9e2a21c1`](https://github.com/nodejs/node/commit/ae9e2a21c1)] - **test**: var to const, assert.equal to assert.strictEqual in net (Sean Villars) [#9907](https://github.com/nodejs/node/pull/9907)
+* [[`30c9474286`](https://github.com/nodejs/node/commit/30c9474286)] - **test**: changed vars to const in test-net-better-error-messages-listen-path.js (anoff) [#9905](https://github.com/nodejs/node/pull/9905)
+* [[`bcbf50d9ba`](https://github.com/nodejs/node/commit/bcbf50d9ba)] - **test**: refactor test-http-dns-error (Outsider) [#10062](https://github.com/nodejs/node/pull/10062)
+* [[`00f08640ce`](https://github.com/nodejs/node/commit/00f08640ce)] - **test**: assert.equal -> assert.strictEqual (davidmarkclements) [#10065](https://github.com/nodejs/node/pull/10065)
+* [[`d9cca393e9`](https://github.com/nodejs/node/commit/d9cca393e9)] - **test**: assert.equal -> assert.strictEqual (davidmarkclements) [#10067](https://github.com/nodejs/node/pull/10067)
+* [[`6c64f6c445`](https://github.com/nodejs/node/commit/6c64f6c445)] - **test**: improve test for crypto padding (Julian Duque) [#9906](https://github.com/nodejs/node/pull/9906)
+* [[`37d734ae36`](https://github.com/nodejs/node/commit/37d734ae36)] - **test**: polish test-net-better-error-messages-listen (Hitesh Kanwathirtha) [#10087](https://github.com/nodejs/node/pull/10087)
+* [[`f126b44a3a`](https://github.com/nodejs/node/commit/f126b44a3a)] - **test**: change var to const in test-tls-key-mismatch.js (bjdelro) [#9897](https://github.com/nodejs/node/pull/9897)
+* [[`7538dd5c93`](https://github.com/nodejs/node/commit/7538dd5c93)] - **test**: use strictEqual in cwd-enoent (JDHarmon) [#10077](https://github.com/nodejs/node/pull/10077)
+* [[`39816a43af`](https://github.com/nodejs/node/commit/39816a43af)] - **test**: refactor test-fs-read-stream-inherit.js (Jonathan Darling) [#9894](https://github.com/nodejs/node/pull/9894)
+* [[`7615a0f2cd`](https://github.com/nodejs/node/commit/7615a0f2cd)] - **test**: refactor test-child-process-stdio-inherit (Wes Tyler) [#9893](https://github.com/nodejs/node/pull/9893)
+* [[`2a9ab8ea2a`](https://github.com/nodejs/node/commit/2a9ab8ea2a)] - **test**: change var to const for require and strict equality checks (Harish Tejwani) [#9892](https://github.com/nodejs/node/pull/9892)
+* [[`5cd7e7aaf1`](https://github.com/nodejs/node/commit/5cd7e7aaf1)] - **test**: Update to const and use regex for assertions (Daniel Flores) [#9891](https://github.com/nodejs/node/pull/9891)
+* [[`1a73cc5357`](https://github.com/nodejs/node/commit/1a73cc5357)] - **test**: swap var->const/let and equal->strictEqual (Peter Masucci) [#9888](https://github.com/nodejs/node/pull/9888)
+* [[`552169e950`](https://github.com/nodejs/node/commit/552169e950)] - **test**: replace equal with strictEqual in crypto (Julian Duque) [#9886](https://github.com/nodejs/node/pull/9886)
+* [[`49900e78b0`](https://github.com/nodejs/node/commit/49900e78b0)] - **test**: replace equal with strictEqual (Julian Duque) [#9879](https://github.com/nodejs/node/pull/9879)
+* [[`998db3a003`](https://github.com/nodejs/node/commit/998db3a003)] - **test**: refactor test-tls-timeout-server-2 (Devon Rifkin) [#9876](https://github.com/nodejs/node/pull/9876)
+* [[`aaab51047f`](https://github.com/nodejs/node/commit/aaab51047f)] - **test**: Changed assert.equal to assert.strictEqual (Daniel Pittman) [#9902](https://github.com/nodejs/node/pull/9902)
+* [[`a4488c3cbd`](https://github.com/nodejs/node/commit/a4488c3cbd)] - **test**: refactor test-vm-syntax-error-stderr.js (Jay Brownlee) [#9900](https://github.com/nodejs/node/pull/9900)
+* [[`cff80a5c0e`](https://github.com/nodejs/node/commit/cff80a5c0e)] - **test**: refactor test-tls-destroy-whilst-write (Chris Bystrek) [#10064](https://github.com/nodejs/node/pull/10064)
+* [[`8257671bdc`](https://github.com/nodejs/node/commit/8257671bdc)] - **test**: refactor test-https-truncate (davidmarkclements) [#10074](https://github.com/nodejs/node/pull/10074)
+* [[`457af874b5`](https://github.com/nodejs/node/commit/457af874b5)] - **test**: use strictEqual in test-cli-eval-event.js (Richard Karmazin) [#9964](https://github.com/nodejs/node/pull/9964)
+* [[`2890f0d904`](https://github.com/nodejs/node/commit/2890f0d904)] - **test**: refactor test-tls-friendly-error-message.js (Adrian Estrada) [#9967](https://github.com/nodejs/node/pull/9967)
+* [[`c37ae4a1b6`](https://github.com/nodejs/node/commit/c37ae4a1b6)] - **test**: refactor test-vm-static-this.js (David Bradford) [#9887](https://github.com/nodejs/node/pull/9887)
+* [[`9473fc6c2f`](https://github.com/nodejs/node/commit/9473fc6c2f)] - **test**: refactor test-crypto-cipheriv-decipheriv (Aileen) [#10018](https://github.com/nodejs/node/pull/10018)
+* [[`6ecc4ffb1c`](https://github.com/nodejs/node/commit/6ecc4ffb1c)] - **test**: refactor test for crypto cipher/decipher iv (Julian Duque) [#9943](https://github.com/nodejs/node/pull/9943)
+* [[`a486f6bad4`](https://github.com/nodejs/node/commit/a486f6bad4)] - **test**: refactor test-cluster-setup-master-argv (Oscar Martinez) [#9960](https://github.com/nodejs/node/pull/9960)
+* [[`384c954698`](https://github.com/nodejs/node/commit/384c954698)] - **test**: refactor test-cluster-setup-master-argv (Christine Hong) [#9993](https://github.com/nodejs/node/pull/9993)
+* [[`76645e8781`](https://github.com/nodejs/node/commit/76645e8781)] - **test**: use assert.strictEqual in test-crypto-ecb (Daniel Pittman) [#9980](https://github.com/nodejs/node/pull/9980)
+* [[`9103c3d3fe`](https://github.com/nodejs/node/commit/9103c3d3fe)] - **test**: update to const iin cluster test (Greg Valdez) [#10007](https://github.com/nodejs/node/pull/10007)
+* [[`27c9171586`](https://github.com/nodejs/node/commit/27c9171586)] - **test**: use assert.strictEqual() cluster test (Bidur Adhikari) [#10042](https://github.com/nodejs/node/pull/10042)
+* [[`2453d64aa7`](https://github.com/nodejs/node/commit/2453d64aa7)] - **test**: var -> let/const, .equal -> .strictEqual (shiya) [#9913](https://github.com/nodejs/node/pull/9913)
+* [[`1467c964a4`](https://github.com/nodejs/node/commit/1467c964a4)] - **test**: increase coverage for timers (lrlna) [#10068](https://github.com/nodejs/node/pull/10068)
+* [[`e47195cf78`](https://github.com/nodejs/node/commit/e47195cf78)] - **test**: change equal to strictEqual (Kevin Zurawel) [#9872](https://github.com/nodejs/node/pull/9872)
+* [[`33da22aba1`](https://github.com/nodejs/node/commit/33da22aba1)] - **test**: add toASCII and toUnicode punycode tests (Claudio Rodriguez) [#9741](https://github.com/nodejs/node/pull/9741)
+* [[`4c5d24b632`](https://github.com/nodejs/node/commit/4c5d24b632)] - **test**: refine test-http-status-reason-invalid-chars (Rich Trott) [#9802](https://github.com/nodejs/node/pull/9802)
+* [[`81d49aaeb2`](https://github.com/nodejs/node/commit/81d49aaeb2)] - **test**: exclude no_interleaved_stdio test for AIX (Michael Dawson) [#9772](https://github.com/nodejs/node/pull/9772)
+* [[`b59cf582e4`](https://github.com/nodejs/node/commit/b59cf582e4)] - **test**: refactor test-async-wrap-* (Rich Trott) [#9663](https://github.com/nodejs/node/pull/9663)
+* [[`57cc5cb277`](https://github.com/nodejs/node/commit/57cc5cb277)] - **test**: use setImmediate() in test of stream2 (masashi.g) [#9583](https://github.com/nodejs/node/pull/9583)
+* [[`8345ffb0a0`](https://github.com/nodejs/node/commit/8345ffb0a0)] - **test**: add test case of PassThrough (Yoshiya Hinosawa) [#9581](https://github.com/nodejs/node/pull/9581)
+* [[`beb147a08b`](https://github.com/nodejs/node/commit/beb147a08b)] - **test**: check that `process.execPath` is a realpath (Anna Henningsen) [#9229](https://github.com/nodejs/node/pull/9229)
+* [[`cef5b1fa14`](https://github.com/nodejs/node/commit/cef5b1fa14)] - **test**: add test for broken child process stdio (cjihrig) [#9528](https://github.com/nodejs/node/pull/9528)
+* [[`29ab76b791`](https://github.com/nodejs/node/commit/29ab76b791)] - **test**: ensure nextTick is not scheduled in exit (Jeremiah Senkpiel) [#9555](https://github.com/nodejs/node/pull/9555)
+* [[`b87fe250d2`](https://github.com/nodejs/node/commit/b87fe250d2)] - **test**: change from setTimeout to setImmediate (MURAKAMI Masahiko) [#9578](https://github.com/nodejs/node/pull/9578)
+* [[`eca12d4316`](https://github.com/nodejs/node/commit/eca12d4316)] - **test**: improve test-stream2-objects.js (Yoshiya Hinosawa) [#9565](https://github.com/nodejs/node/pull/9565)
+* [[`4e36a14c15`](https://github.com/nodejs/node/commit/4e36a14c15)] - **test**: refactor test-next-tick-error-spin (Rich Trott) [#9537](https://github.com/nodejs/node/pull/9537)
+* [[`b2b2bc2293`](https://github.com/nodejs/node/commit/b2b2bc2293)] - **test**: move timer-dependent test to sequential (Rich Trott) [#9487](https://github.com/nodejs/node/pull/9487)
+* [[`1436fd70f5`](https://github.com/nodejs/node/commit/1436fd70f5)] - **test**: convert assert.equal to assert.strictEqual (Jonathan Darling) [#9925](https://github.com/nodejs/node/pull/9925)
+* [[`c9ed49da6e`](https://github.com/nodejs/node/commit/c9ed49da6e)] - **test**: run cpplint on files in test/cctest (Ben Noordhuis) [#9787](https://github.com/nodejs/node/pull/9787)
+* [[`10d4f470f8`](https://github.com/nodejs/node/commit/10d4f470f8)] - **test**: enable addons test to pass with debug build (Daniel Bevenius) [#8836](https://github.com/nodejs/node/pull/8836)
+* [[`550393dc78`](https://github.com/nodejs/node/commit/550393dc78)] - **test**: add new.target add-on regression test (Ben Noordhuis) [#9689](https://github.com/nodejs/node/pull/9689)
+* [[`76245b2156`](https://github.com/nodejs/node/commit/76245b2156)] - **test**: refactor large event emitter tests (cjihrig) [#6446](https://github.com/nodejs/node/pull/6446)
+* [[`02e8187751`](https://github.com/nodejs/node/commit/02e8187751)] - **test**: allow globals to be whitelisted (cjihrig) [#7826](https://github.com/nodejs/node/pull/7826)
+* [[`c0c5608bfc`](https://github.com/nodejs/node/commit/c0c5608bfc)] - **test,assert**: add deepEqual/deepStrictEqual tests for typed arrays (Feross Aboukhadijeh) [#8002](https://github.com/nodejs/node/pull/8002)
+* [[`759e8fdd18`](https://github.com/nodejs/node/commit/759e8fdd18)] - **timers**: bail from intervals if _repeat is bad (Jeremiah Senkpiel) [#10365](https://github.com/nodejs/node/pull/10365)
+* [[`553d95da15`](https://github.com/nodejs/node/commit/553d95da15)] - **timers**: use consistent checks for canceled timers (Jeremiah Senkpiel) [#9685](https://github.com/nodejs/node/pull/9685)
+* [[`5c6d908dd7`](https://github.com/nodejs/node/commit/5c6d908dd7)] - **tools**: enable final newline in .editorconfig (Roman Reiss) [#9410](https://github.com/nodejs/node/pull/9410)
+* [[`06e8120928`](https://github.com/nodejs/node/commit/06e8120928)] - **tools**: remove unneeded escaping in generate.js (Rich Trott) [#9781](https://github.com/nodejs/node/pull/9781)
+* [[`fd6b305421`](https://github.com/nodejs/node/commit/fd6b305421)] - **tools**: use better regexp for manpage references (Anna Henningsen) [#9632](https://github.com/nodejs/node/pull/9632)
+* [[`9b36469a3c`](https://github.com/nodejs/node/commit/9b36469a3c)] - **tools**: improve docopen target in Makefile (Sakthipriyan Vairamani (thefourtheye)) [#9436](https://github.com/nodejs/node/pull/9436)
+* [[`e3dc05d01b`](https://github.com/nodejs/node/commit/e3dc05d01b)] - **tools**: make run-valgrind.py useful (Ben Noordhuis) [#9520](https://github.com/nodejs/node/pull/9520)
+* [[`7b1b11a11c`](https://github.com/nodejs/node/commit/7b1b11a11c)] - **tools**: fix run-valgrind.py script (Ben Noordhuis) [#9520](https://github.com/nodejs/node/pull/9520)
+* [[`011ee0ba8b`](https://github.com/nodejs/node/commit/011ee0ba8b)] - **tools**: copy run-valgrind.py to tools/ (Ben Noordhuis) [#9520](https://github.com/nodejs/node/pull/9520)
+
 ## 2016-12-06, Version 4.7.0 'Argon' (LTS), @thealphanerd
 
 This LTS release comes with 108 commits. This includes 30 which are doc
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f9ae4ce624b819..64b4531b63ae6d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -147,7 +147,7 @@ $ git rebase upstream/master
 
 Bug fixes and features **should come with tests**. Add your tests in the
 `test/parallel/` directory. For guidance on how to write a test for the Node.js
-project, see this [guide](./doc/guides/writing_tests.md). Looking at other tests
+project, see this [guide](./doc/guides/writing-tests.md). Looking at other tests
 to see how they should be structured can also help.
 
 To run the tests on Unix / OS X:
diff --git a/Makefile b/Makefile
index 594c91a2b952bc..3160f41c41fd3f 100644
--- a/Makefile
+++ b/Makefile
@@ -8,6 +8,7 @@ PREFIX ?= /usr/local
 FLAKY_TESTS ?= run
 TEST_CI_ARGS ?=
 STAGINGSERVER ?= node-www
+LOGLEVEL ?= silent
 
 OSTYPE := $(shell uname -s | tr '[A-Z]' '[a-z]')
 
@@ -147,10 +148,12 @@ ADDONS_BINDING_GYPS := \
 test/addons/.buildstamp: config.gypi \
 	deps/npm/node_modules/node-gyp/package.json \
 	$(ADDONS_BINDING_GYPS) test/addons/.docbuildstamp
-	# Cannot use $(wildcard test/addons/*/) here, it's evaluated before
-	# embedded addons have been generated from the documentation.
-	for dirname in test/addons/*/; do \
-		$(NODE) deps/npm/node_modules/node-gyp/bin/node-gyp rebuild \
+#	Cannot use $(wildcard test/addons/*/) here, it's evaluated before
+#	embedded addons have been generated from the documentation.
+	@for dirname in test/addons/*/; do \
+		echo "\nBuilding addon $$PWD/$$dirname" ; \
+		env MAKEFLAGS="-j1" $(NODE) deps/npm/node_modules/node-gyp/bin/node-gyp \
+		        --loglevel=$(LOGLEVEL) rebuild \
 			--python="$(PYTHON)" \
 			--directory="$$PWD/$$dirname" \
 			--nodedir="$$PWD"; \
@@ -180,6 +183,7 @@ CI_NATIVE_SUITES := addons
 CI_JS_SUITES := doctool message parallel pseudo-tty sequential
 
 # Build and test addons without building anything else
+test-ci-native: LOGLEVEL := info
 test-ci-native: | test/addons/.buildstamp
 	$(PYTHON) tools/test.py -p tap --logfile test.tap \
 		--mode=release --flaky-tests=$(FLAKY_TESTS) \
@@ -191,6 +195,7 @@ test-ci-js:
 		--mode=release --flaky-tests=$(FLAKY_TESTS) \
 		$(TEST_CI_ARGS) $(CI_JS_SUITES)
 
+test-ci: LOGLEVEL := info
 test-ci: | build-addons
 	out/Release/cctest --gtest_output=tap:cctest.tap
 	$(PYTHON) tools/test.py -p tap --logfile test.tap --mode=release --flaky-tests=$(FLAKY_TESTS) \
@@ -237,7 +242,7 @@ test-timers-clean:
 	$(MAKE) --directory=tools clean
 
 test-v8: v8
-	# note: performs full test unless QUICKCHECK is specified
+#	note: performs full test unless QUICKCHECK is specified
 	deps/v8/tools/run-tests.py --arch=$(V8_ARCH) \
         --mode=$(BUILDTYPE_LOWER) $(V8_TEST_NO_I18N) $(QUICKCHECK_ARG) \
         --no-presubmit \
@@ -245,7 +250,7 @@ test-v8: v8
 	 $(TAP_V8)
 
 test-v8-intl: v8
-	# note: performs full test unless QUICKCHECK is specified
+#	note: performs full test unless QUICKCHECK is specified
 	deps/v8/tools/run-tests.py --arch=$(V8_ARCH) \
         --mode=$(BUILDTYPE_LOWER) --no-presubmit $(QUICKCHECK_ARG) \
         --shell-dir=deps/v8/out/$(V8_ARCH).$(BUILDTYPE_LOWER) intl \
@@ -258,18 +263,17 @@ test-v8-benchmarks: v8
 	 $(TAP_V8_BENCHMARKS)
 
 test-v8-all: test-v8 test-v8-intl test-v8-benchmarks
-	# runs all v8 tests
+# runs all v8 tests
 
 apidoc_sources = $(wildcard doc/api/*.md)
-apidocs = $(addprefix out/,$(apidoc_sources:.md=.html)) \
-		$(addprefix out/,$(apidoc_sources:.md=.json))
+apidocs_html = $(apidoc_dirs) $(apiassets) $(addprefix out/,$(apidoc_sources:.md=.html))
+apidocs_json = $(apidoc_dirs) $(apiassets) $(addprefix out/,$(apidoc_sources:.md=.json))
 
 apidoc_dirs = out/doc out/doc/api/ out/doc/api/assets
 
 apiassets = $(subst api_assets,api/assets,$(addprefix out/,$(wildcard doc/api_assets/*)))
 
-doc-only: $(apidoc_dirs) $(apiassets) $(apidocs) tools/doc/
-
+doc-only: $(apidocs_html) $(apidocs_json)
 doc: $(NODE_EXE) doc-only
 
 $(apidoc_dirs):
@@ -305,8 +309,8 @@ out/doc/api/%.html: doc/api/%.md
 		fi
 	[ -x $(NODE) ] && $(NODE) $(gen-html) || node $(gen-html)
 
-docopen: out/doc/api/all.html
-	-google-chrome out/doc/api/all.html
+docopen: $(apidocs_html)
+	@$(PYTHON) -mwebbrowser file://$(PWD)/out/doc/api/all.html
 
 docclean:
 	-rm -rf out/doc
@@ -680,6 +684,8 @@ CPPLINT_FILES = $(filter-out $(CPPLINT_EXCLUDE), $(wildcard \
 	src/*.h \
 	test/addons/*/*.cc \
 	test/addons/*/*.h \
+	test/cctest/*.cc \
+	test/cctest/*.h \
 	tools/icu/*.cc \
 	tools/icu/*.h \
 	))
diff --git a/README.md b/README.md
index ca908c1aa9312a..fdf6fecfacaa6e 100644
--- a/README.md
+++ b/README.md
@@ -4,8 +4,8 @@
 
 Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js
 uses an event-driven, non-blocking I/O model that makes it lightweight and
-efficient. The Node.js package ecosystem, npm, is the largest ecosystem of open
-source libraries in the world.
+efficient. The Node.js package ecosystem, [npm][], is the largest ecosystem of
+open source libraries in the world.
 
 The Node.js project is supported by the
 [Node.js Foundation](https://nodejs.org/en/foundation/). Contributions,
@@ -217,8 +217,6 @@ more information about the governance of the Node.js project, see
 **Claudio Rodriguez** &lt;cjrodr@yahoo.com&gt;
 * [danbev](https://github.com/danbev) -
 **Daniel Bevenius** &lt;daniel.bevenius@gmail.com&gt;
-* [domenic](https://github.com/domenic) -
-**Domenic Denicola** &lt;d@domenic.me&gt;
 * [eljefedelrodeodeljefe](https://github.com/eljefedelrodeodeljefe) -
 **Robert Jefe Lindstaedt** &lt;robert.lindstaedt@gmail.com&gt;
 * [estliberitas](https://github.com/estliberitas) -
@@ -239,8 +237,8 @@ more information about the governance of the Node.js project, see
 **Ilkka Myller** &lt;ilkka.myller@nodefield.com&gt;
 * [isaacs](https://github.com/isaacs) -
 **Isaac Z. Schlueter** &lt;i@izs.me&gt;
-* [italoacasas](https://github.com/italoacasas)
-**Italo A. Casas**  &lt;me@italoacasas.com&gt;
+* [italoacasas](https://github.com/italoacasas) -
+**Italo A. Casas** &lt;me@italoacasas.com&gt;
 * [iWuzHere](https://github.com/iWuzHere) -
 **Imran Iqbal** &lt;imran@imraniqbal.org&gt;
 * [JacksonTian](https://github.com/JacksonTian) -
@@ -337,8 +335,6 @@ more information about the governance of the Node.js project, see
 **Yorkie Liu** &lt;yorkiefixer@gmail.com&gt;
 * [yosuke-furukawa](https://github.com/yosuke-furukawa) -
 **Yosuke Furukawa** &lt;yosuke.furukawa@gmail.com&gt;
-* [zkat](https://github.com/zkat) -
-**Kat Marchán** &lt;kzm@sykosomatic.org&gt;
 
 Collaborators (which includes CTC members) follow the
 [COLLABORATOR_GUIDE.md](./COLLABORATOR_GUIDE.md) in maintaining the Node.js
@@ -362,15 +358,12 @@ Releases of Node.js and io.js will be signed with one of the following GPG keys:
 `C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8`
 * **Rod Vagg** &lt;rod@vagg.org&gt;
 `DD8F2338BAE7501E3DD5AC78C273792F7D83545D`
-* **Sam Roberts** &lt;octetcloud@keybase.io&gt;
-`0034A06D9D9B0064CE8ADF6BF1747F4AD2306D93`
 
 The full set of trusted release keys can be imported by running:
 
 ```shell
 gpg --keyserver pool.sks-keyservers.net --recv-keys 9554F04D7259F04124DE6B476D5A82AC7E37093B
 gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
-gpg --keyserver pool.sks-keyservers.net --recv-keys 0034A06D9D9B0064CE8ADF6BF1747F4AD2306D93
 gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
 gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
 gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
@@ -391,6 +384,7 @@ keys:
 * **Timothy J Fontaine** &lt;tjfontaine@gmail.com&gt;
 `7937DFD2AB06298B2293C3187D33FF9D0246406D`
 
+[npm]: https://www.npmjs.com
 [Website]: https://nodejs.org/en/
 [Contributing to the project]: CONTRIBUTING.md
 [Node.js Help]: https://github.com/nodejs/help
diff --git a/WORKING_GROUPS.md b/WORKING_GROUPS.md
index 25414cd3392a82..a29309d7f71621 100644
--- a/WORKING_GROUPS.md
+++ b/WORKING_GROUPS.md
@@ -24,7 +24,6 @@ back in to the CTC.
 * [Diagnostics](#diagnostics)
 * [i18n](#i18n)
 * [Evangelism](#evangelism)
-* [Roadmap](#roadmap)
 * [Docker](#docker)
 * [Addon API](#addon-api)
 * [Benchmarking](#benchmarking)
@@ -41,66 +40,65 @@ back in to the CTC.
 
 ### [Website](https://github.com/nodejs/website)
 
-The website working group's purpose is to build and maintain a public
-website for the `Node.js` project.
+The website Working Group's purpose is to build and maintain a public
+website for the Node.js project.
 
-Its responsibilities are:
-* Develop and maintain a build and automation system for `nodejs.org`.
-* Ensure the site is regularly updated with changes made to `Node.js` like
-releases and features.
-* Foster and enable a community of translators.
+Responsibilities include:
+* Developing and maintaining a build and automation system for nodejs.org.
+* Ensuring the site is regularly updated with changes made to Node.js, like
+  releases and features.
+* Fostering and enabling a community of translators.
 
 ### [Streams](https://github.com/nodejs/readable-stream)
 
-The Streams WG is dedicated to the support and improvement of the Streams API
-as used in Node.js and the npm ecosystem. We seek to create a composable API that
-solves the problem of representing multiple occurrences of an event over time
-in a humane, low-overhead fashion. Improvements to the API will be driven by
-the needs of the ecosystem; interoperability and backwards compatibility with
-other solutions and prior versions are paramount in importance. Our
-responsibilities include:
+The Streams Working Group is dedicated to the support and improvement of the
+Streams API as used in Node.js and the npm ecosystem. We seek to create a
+composable API that solves the problem of representing multiple occurrences
+of an event over time in a humane, low-overhead fashion. Improvements to the
+API will be driven by the needs of the ecosystem; interoperability and
+backwards compatibility with other solutions and prior versions are paramount
+in importance.
 
+Responsibilities include:
 * Addressing stream issues on the Node.js issue tracker.
 * Authoring and editing stream documentation within the Node.js project.
 * Reviewing changes to stream subclasses within the Node.js project.
 * Redirecting changes to streams from the Node.js project to this project.
 * Assisting in the implementation of stream providers within Node.js.
-* Recommending versions of readable-stream to be included in Node.js.
-* Messaging about the future of streams to give the community advance notice of changes.
-
+* Recommending versions of `readable-stream` to be included in Node.js.
+* Messaging about the future of streams to give the community advance notice of
+  changes.
 
 ### [Build](https://github.com/nodejs/build)
 
-The build working group's purpose is to create and maintain a
-distributed automation infrastructure.
-
-Its responsibilities are:
-* Produce Packages for all target platforms.
-* Run tests.
-* Run performance testing and comparisons.
-* Creates and manages build-containers.
+The Build Working Group's purpose is to create and maintain a distributed
+automation infrastructure.
 
+Responsibilities include:
+* Producing packages for all target platforms.
+* Running tests.
+* Running performance testing and comparisons.
+* Creating and managing build-containers.
 
 ### [Diagnostics](https://github.com/nodejs/diagnostics)
 
-The diagnostics working group's purpose is to surface a set of comprehensive,
-documented, and extensible diagnostic interfaces for use by
-Node.js tools and JavaScript VMs.
-
-Its responsibilities are:
-
-* Collaborate with V8 to integrate `v8_inspector` into Node.js.
-* Collaborate with V8 to integrate `trace_event` into Node.js.
-* Collaborate with Core to refine `async_wrap` and `async_hooks`.
-* Maintain and improve OS trace system integration (e.g. ETW, LTTNG, dtrace).
-* Document diagnostic capabilities and APIs in Node.js and its components.
-* Explore opportunities and gaps, discuss feature requests, and address
+The Diagnostics Working Group's purpose is to surface a set of comprehensive,
+documented, and extensible diagnostic interfaces for use by Node.js tools and
+JavaScript VMs.
+
+Responsibilities include:
+* Collaborating with V8 to integrate `v8_inspector` into Node.js.
+* Collaborating with V8 to integrate `trace_event` into Node.js.
+* Collaborating with Core to refine `async_wrap` and `async_hooks`.
+* Maintaining and improving OS trace system integration (e.g. ETW, LTTNG, dtrace).
+* Documenting diagnostic capabilities and APIs in Node.js and its components.
+* Exploring opportunities and gaps, discussing feature requests, and addressing
   conflicts in Node.js diagnostics.
-* Foster an ecosystem of diagnostics tools for Node.js.
+* Fostering an ecosystem of diagnostics tools for Node.js.
 
 ### i18n
 
-The i18n working groups handle more than just translations. They
+The i18n Working Groups handle more than just translations. They
 are endpoints for community members to collaborate with each
 other in their language of choice.
 
@@ -108,16 +106,14 @@ Each team is organized around a common spoken language. Each
 language community might then produce multiple localizations for
 various project resources.
 
-Their responsibilities are:
-* Translations of any Node.js materials they believe are relevant to their
-community.
-* Review processes for keeping translations up
-to date and of high quality.
-* Social media channels in their language.
-* Promotion of Node.js speakers for meetups and conferences in their
-language.
+Responsibilities include:
+* Translating any Node.js materials they believe are relevant to their
+  community.
+* Reviewing processes for keeping translations up to date and of high quality.
+* Managing and monitoring social media channels in their language.
+* Promoting Node.js speakers for meetups and conferences in their language.
 
-Note that the i18n working groups are distinct from the [Intl](#Intl) working group.
+Note that the i18n Working Groups are distinct from the [Intl](#Intl) Working Group.
 
 Each language community maintains its own membership.
 
@@ -159,33 +155,37 @@ Each language community maintains its own membership.
 ### [Intl](https://github.com/nodejs/Intl)
 
 The Intl Working Group is dedicated to support and improvement of
-Internationalization (i18n) and Localization (l10n) in Node. Its responsibilities are:
+Internationalization (i18n) and Localization (l10n) in Node.
 
-1. Functionality & compliance (standards: ECMA, Unicode…)
-2. Support for Globalization and Internationalization issues that come up in the tracker
-3. Guidance and Best Practices
-4. Refinement of existing `Intl` implementation
+Responsibilities include:
+* Ensuring functionality & compliance (standards: ECMA, Unicode…)
+* Supporting Globalization and Internationalization issues that come up
+  in the tracker
+* Communicating guidance and best practices
+* Refining the existing `Intl` implementation
 
-The Intl WG is not responsible for translation of content. That is the responsibility of the specific [i18n](#i18n) group for each language.
+The Intl Working Group is not responsible for translation of content. That is the
+responsibility of the specific [i18n](#i18n) group for each language.
 
 ### [Evangelism](https://github.com/nodejs/evangelism)
 
-The evangelism working group promotes the accomplishments
+The Evangelism Working Group promotes the accomplishments
 of Node.js and lets the community know how they can get involved.
 
-Their responsibilities are:
-* Project messaging.
-* Official project social media.
-* Promotion of speakers for meetups and conferences.
-* Promotion of community events.
+Responsibilities include:
+* Facilitating project messaging.
+* Managing official project social media.
+* Handling the promotion of speakers for meetups and conferences.
+* Handling the promotion of community events.
 * Publishing regular update summaries and other promotional
-content.
+  content.
 
 ### [HTTP](https://github.com/nodejs/http)
 
-The HTTP working group is chartered for the support and improvement of the
-HTTP implementation in Node. Its responsibilities are:
+The HTTP Working Group is chartered for the support and improvement of the
+HTTP implementation in Node.js.
 
+Responsibilities include:
 * Addressing HTTP issues on the Node.js issue tracker.
 * Authoring and editing HTTP documentation within the Node.js project.
 * Reviewing changes to HTTP functionality within the Node.js project.
@@ -195,41 +195,25 @@ HTTP implementation in Node. Its responsibilities are:
 * Messaging about the future of HTTP to give the community advance notice of
   changes.
 
-### [Roadmap](https://github.com/nodejs/roadmap)
-
-The roadmap working group is responsible for user community outreach
-and the translation of their concerns into a plan of action for Node.js.
-
-The final [ROADMAP](./ROADMAP.md) document is still owned by the TC and requires
-the same approval for changes as any other project asset.
-
-Their responsibilities are:
-* Attract and summarize user community needs and feedback.
-* Find or potentially create tools that allow for broader participation.
-* Create Pull Requests for relevant changes to [Roadmap.md](./ROADMAP.md)
-
-
 ### [Docker](https://github.com/nodejs/docker-iojs)
 
-The Docker working group's purpose is to build, maintain, and improve official
-Docker images for the `Node.js` project.
+The Docker Working Group's purpose is to build, maintain, and improve official
+Docker images for the Node.js project.
 
-Their responsibilities are:
-* Keep the official Docker images updated in line with new `Node.js` releases.
+Responsibilities include:
+* Keeping the official Docker images updated in line with new Node.js releases.
 * Decide and implement image improvements and/or fixes.
 * Maintain and improve the images' documentation.
 
-
 ### [Addon API](https://github.com/nodejs/nan)
 
 The Addon API Working Group is responsible for maintaining the NAN project and
 corresponding _nan_ package in npm. The NAN project makes available an
-abstraction layer for native add-on authors for both Node.js and Node.js,
+abstraction layer for native add-on authors for Node.js,
 assisting in the writing of code that is compatible with many actively used
-versions of Node.js, Node.js, V8 and libuv.
-
-Their responsibilities are:
+versions of Node.js, V8 and libuv.
 
+Responsibilities include:
 * Maintaining the [NAN](https://github.com/nodejs/nan) GitHub repository,
   including code, issues and documentation.
 * Maintaining the [addon-examples](https://github.com/nodejs/node-addon-examples)
@@ -247,48 +231,46 @@ The current members can be found in their
 
 ### [Benchmarking](https://github.com/nodejs/benchmarking)
 
-The purpose of the Benchmark working group is to gain consensus
-for an agreed set of benchmarks that can be used to:
+The purpose of the Benchmark Working Group is to gain consensus
+on an agreed set of benchmarks that can be used to:
 
-+ track and evangelize performance gains made between Node releases
-+ avoid performance regressions between releases
+* track and evangelize performance gains made between Node.js releases
+* avoid performance regressions between releases
 
-Its responsibilities are:
-
-+ Identify 1 or more benchmarks that reflect customer usage.
-   Likely need more than one to cover typical Node use cases
-   including low-latency and high concurrency
-+ Work to get community consensus on the list chosen
-+ Add regular execution of chosen benchmarks to Node builds
-+ Track/publicize performance between builds/releases
+Responsibilities include:
+* Identifying 1 or more benchmarks that reflect customer usage.
+  Likely will need more than one to cover typical Node.js use cases
+  including low-latency and high concurrency
+* Working to get community consensus on the list chosen
+* Adding regular execution of chosen benchmarks to Node.js builds
+* Tracking/publicizing performance between builds/releases
 
 ### [Post-mortem](https://github.com/nodejs/post-mortem)
 
-The Post-mortem Diagnostics working group is dedicated to the support
+The Post-mortem Diagnostics Working Group is dedicated to the support
 and improvement of postmortem debugging for Node.js. It seeks to
 elevate the role of postmortem debugging for Node, to assist in the
 development of techniques and tools, and to make techniques and tools
 known and available to Node.js users.
 
-Its responsibilities are:
-
-+ Defining and adding interfaces/APIs in order to allow dumps
-  to be generated when needed
-+ Defining and adding common structures to the dumps generated
-  in order to support tools that want to introspect those dumps
+Responsibilities include:
+* Defining and adding interfaces/APIs in order to allow dumps
+  to be generated when needed.
+* Defining and adding common structures to the dumps generated
+  in order to support tools that want to introspect those dumps.
 
 ### [Documentation](https://github.com/nodejs/docs)
 
-The Documentation working group exists to support the improvement of Node.js
+The Documentation Working Group exists to support the improvement of Node.js
 documentation, both in the core API documentation, and elsewhere, such as the
-Node.js website. Its intent is to work closely with Evangelism, Website, and
-Intl working groups to make excellent documentation available and accessible
+Node.js website. Its intent is to work closely with the Evangelism, Website, and
+Intl Working Groups to make excellent documentation available and accessible
 to all.
 
-Its responsibilities are:
-
+Responsibilities include:
 * Defining and maintaining documentation style and content standards.
-* Producing documentation in a format acceptable for the Website WG to consume.
+* Producing documentation in a format acceptable for the Website Working Group
+  to consume.
 * Ensuring that Node's documentation addresses a wide variety of audiences.
 * Creating and operating a process for documentation review that produces
   quality documentation and avoids impeding the progress of Core work.
@@ -298,8 +280,7 @@ Its responsibilities are:
 The Node.js Testing Working Group's purpose is to extend and improve testing of
 the Node.js source code.
 
-Its responsibilities are:
-
+Responsibilities include:
 * Coordinating an overall strategy for improving testing.
 * Documenting guidelines around tests.
 * Working with the Build Working Group to improve continuous integration.
diff --git a/benchmark/timers/timers-breadth.js b/benchmark/timers/timers-breadth.js
new file mode 100644
index 00000000000000..1101ee7dbf8907
--- /dev/null
+++ b/benchmark/timers/timers-breadth.js
@@ -0,0 +1,20 @@
+'use strict';
+var common = require('../common.js');
+
+var bench = common.createBenchmark(main, {
+  thousands: [500],
+});
+
+function main(conf) {
+  var N = +conf.thousands * 1e3;
+  var n = 0;
+  bench.start();
+  function cb() {
+    n++;
+    if (n === N)
+      bench.end(N / 1e3);
+  }
+  for (var i = 0; i < N; i++) {
+    setTimeout(cb, 1);
+  }
+}
diff --git a/benchmark/timers/timers-depth.js b/benchmark/timers/timers-depth.js
new file mode 100644
index 00000000000000..d5efc5c672d502
--- /dev/null
+++ b/benchmark/timers/timers-depth.js
@@ -0,0 +1,20 @@
+'use strict';
+var common = require('../common.js');
+
+var bench = common.createBenchmark(main, {
+  thousands: [1],
+});
+
+function main(conf) {
+  var N = +conf.thousands * 1e3;
+  var n = 0;
+  bench.start();
+  setTimeout(cb, 1);
+  function cb() {
+    n++;
+    if (n === N)
+      bench.end(N / 1e3);
+    else
+      setTimeout(cb, 1);
+  }
+}
diff --git a/benchmark/timers/timers.js b/benchmark/timers/timers.js
deleted file mode 100644
index 13b18fffc5ead7..00000000000000
--- a/benchmark/timers/timers.js
+++ /dev/null
@@ -1,41 +0,0 @@
-'use strict';
-var common = require('../common.js');
-
-var bench = common.createBenchmark(main, {
-  thousands: [500],
-  type: ['depth', 'breadth']
-});
-
-function main(conf) {
-  var n = +conf.thousands * 1e3;
-  if (conf.type === 'breadth')
-    breadth(n);
-  else
-    depth(n);
-}
-
-function depth(N) {
-  var n = 0;
-  bench.start();
-  setTimeout(cb);
-  function cb() {
-    n++;
-    if (n === N)
-      bench.end(N / 1e3);
-    else
-      setTimeout(cb);
-  }
-}
-
-function breadth(N) {
-  var n = 0;
-  bench.start();
-  function cb() {
-    n++;
-    if (n === N)
-      bench.end(N / 1e3);
-  }
-  for (var i = 0; i < N; i++) {
-    setTimeout(cb);
-  }
-}
diff --git a/configure b/configure
index 02e926d4b3cf29..d33760dcf37e16 100755
--- a/configure
+++ b/configure
@@ -1,5 +1,10 @@
 #!/usr/bin/env python
 
+import sys
+if sys.version_info[0] != 2 or sys.version_info[1] not in (6, 7):
+  sys.stdout.write("Please use either Python 2.6 or 2.7\n")
+  sys.exit(1)
+
 import errno
 import optparse
 import os
@@ -7,7 +12,6 @@ import pprint
 import re
 import shlex
 import subprocess
-import sys
 import shutil
 import string
 
@@ -59,6 +63,11 @@ parser.add_option('--prefix',
     default='/usr/local',
     help='select the install prefix [default: %default]')
 
+parser.add_option('--coverage',
+    action='store_true',
+    dest='coverage',
+    help='Build node with code coverage enabled')
+
 parser.add_option('--debug',
     action='store_true',
     dest='debug',
@@ -443,7 +452,7 @@ def pkg_config(pkg):
           shlex.split(pkg_config) + ['--silence-errors', flag, pkg],
           stdout=subprocess.PIPE)
       val = proc.communicate()[0].strip()
-    except OSError, e:
+    except OSError as e:
       if e.errno != errno.ENOENT: raise e  # Unexpected error.
       return (None, None, None)  # No pkg-config/pkgconf installed.
     retval += (val,)
@@ -479,12 +488,12 @@ def get_version_helper(cc, regexp):
     proc = subprocess.Popen(shlex.split(cc) + ['-v'], stdin=subprocess.PIPE,
                             stderr=subprocess.PIPE, stdout=subprocess.PIPE)
   except OSError:
-    print '''Node.js configure error: No acceptable C compiler found!
+    print('''Node.js configure error: No acceptable C compiler found!
 
         Please make sure you have a C compiler installed on your system and/or
         consider adjusting the CC environment variable if you installed
         it in a non-standard prefix.
-        '''
+        ''')
     sys.exit()
 
   match = re.search(regexp, proc.communicate()[1])
@@ -510,12 +519,12 @@ def get_gas_version(cc):
                             stdin=subprocess.PIPE, stderr=subprocess.PIPE,
                             stdout=subprocess.PIPE)
   except OSError:
-    print '''Node.js configure error: No acceptable C compiler found!
+    print('''Node.js configure error: No acceptable C compiler found!
 
         Please make sure you have a C compiler installed on your system and/or
         consider adjusting the CC environment variable if you installed
         it in a non-standard prefix.
-        '''
+        ''')
     sys.exit()
 
   match = re.match(r"GNU assembler version ([2-9]\.[0-9]+)",
@@ -570,12 +579,12 @@ def cc_macros(cc=None):
                          stdout=subprocess.PIPE,
                          stderr=subprocess.PIPE)
   except OSError:
-    print '''Node.js configure error: No acceptable C compiler found!
+    print('''Node.js configure error: No acceptable C compiler found!
 
         Please make sure you have a C compiler installed on your system and/or
         consider adjusting the CC environment variable if you installed
         it in a non-standard prefix.
-        '''
+        ''')
     sys.exit()
 
   p.stdin.write('\n')
@@ -632,7 +641,7 @@ def host_arch_cc():
     '__MIPSEL__'  : 'mipsel',
     '__mips__'    : 'mips',
     '__PPC64__'   : 'ppc64',
-    '__PPC__'     : 'ppc',
+    '__PPC__'     : 'ppc64',
     '__x86_64__'  : 'x64',
     '__s390__'    : 's390',
     '__s390x__'   : 's390x',
@@ -802,7 +811,14 @@ def configure_node(o):
   o['variables']['node_use_v8_platform'] = b(not options.without_v8_platform)
   o['variables']['node_use_bundled_v8'] = b(not options.without_bundled_v8)
   node_module_version = getmoduleversion.get_version()
-  shlib_suffix = '%s.dylib' if sys.platform == 'darwin' else 'so.%s'
+
+  if sys.platform == 'darwin':
+    shlib_suffix = '%s.dylib'
+  elif sys.platform.startswith('aix'):
+    shlib_suffix = '%s.a'
+  else:
+    shlib_suffix = 'so.%s'
+
   shlib_suffix %= node_module_version
   o['variables']['node_module_version'] = int(node_module_version)
   o['variables']['shlib_suffix'] = shlib_suffix
@@ -815,6 +831,11 @@ def configure_node(o):
   if options.use_xcode and options.use_ninja:
     raise Exception('--xcode and --ninja cannot be used together.')
 
+  if options.coverage:
+    o['variables']['coverage'] = 'true'
+  else:
+    o['variables']['coverage'] = 'false'
+
 def configure_library(lib, output):
   shared_lib = 'shared_' + lib
   output['variables']['node_' + shared_lib] = b(getattr(options, shared_lib))
@@ -822,26 +843,26 @@ def configure_library(lib, output):
   if getattr(options, shared_lib):
     (pkg_libs, pkg_cflags, pkg_libpath) = pkg_config(lib)
 
-    if pkg_cflags:
+    if options.__dict__[shared_lib + '_includes']:
+      output['include_dirs'] += [options.__dict__[shared_lib + '_includes']]
+    elif pkg_cflags:
       output['include_dirs'] += (
           filter(None, map(str.strip, pkg_cflags.split('-I'))))
-    elif options.__dict__[shared_lib + '_includes']:
-      output['include_dirs'] += [options.__dict__[shared_lib + '_includes']]
 
     # libpath needs to be provided ahead libraries
-    if pkg_libpath:
-      output['libraries'] += [pkg_libpath]
-    elif options.__dict__[shared_lib + '_libpath']:
+    if options.__dict__[shared_lib + '_libpath']:
       output['libraries'] += [
           '-L%s' % options.__dict__[shared_lib + '_libpath']]
+    elif pkg_libpath:
+      output['libraries'] += [pkg_libpath]
 
     default_libs = getattr(options, shared_lib + '_libname')
     default_libs = map('-l{0}'.format, default_libs.split(','))
 
-    if pkg_libs:
-      output['libraries'] += pkg_libs.split()
-    elif default_libs:
+    if default_libs:
       output['libraries'] += default_libs
+    elif pkg_libs:
+      output['libraries'] += pkg_libs.split()
 
 
 def configure_v8(o):
@@ -904,7 +925,7 @@ def configure_winsdk(o):
 
 def write(filename, data):
   filename = os.path.join(root_dir, filename)
-  print 'creating ', filename
+  print('creating %s' % filename)
   f = open(filename, 'w+')
   f.write(data)
 
@@ -924,7 +945,7 @@ def glob_to_var(dir_base, dir_sub, patch_dir):
           patchfile = '%s/%s/%s' % (dir_base, patch_dir, file)
           if os.path.isfile(patchfile):
             srcfile = '%s/%s' % (patch_dir, file)
-            print 'Using version-specific floating patch %s' % patchfile
+            print('Using version-specific floating patch %s' % patchfile)
         list.append(srcfile)
     break
   return list
@@ -939,8 +960,8 @@ def configure_intl(o):
   def icu_download(path):
     # download ICU, if needed
     if not os.access(options.download_path, os.W_OK):
-      print 'Error: cannot write to desired download path. ' \
-            'Either create it or verify permissions.'
+      print('Error: cannot write to desired download path. ' \
+            'Either create it or verify permissions.')
       sys.exit(1)
     for icu in icus:
       url = icu['url']
@@ -951,16 +972,16 @@ def configure_intl(o):
         if nodedownload.candownload(auto_downloads, "icu"):
           nodedownload.retrievefile(url, targetfile)
       else:
-        print ' Re-using existing %s' % targetfile
+        print(' Re-using existing %s' % targetfile)
       if os.path.isfile(targetfile):
         sys.stdout.write(' Checking file integrity with MD5:\r')
         gotmd5 = nodedownload.md5sum(targetfile)
-        print ' MD5:      %s  %s' % (gotmd5, targetfile)
+        print(' MD5:      %s  %s' % (gotmd5, targetfile))
         if (md5 == gotmd5):
           return targetfile
         else:
-          print ' Expected: %s      *MISMATCH*' % md5
-          print '\n ** Corrupted ZIP? Delete %s to retry download.\n' % targetfile
+          print(' Expected: %s      *MISMATCH*' % md5)
+          print('\n ** Corrupted ZIP? Delete %s to retry download.\n' % targetfile)
     return None
   icu_config = {
     'variables': {}
@@ -980,7 +1001,7 @@ def configure_intl(o):
   with_icu_source = options.with_icu_source
   have_icu_path = bool(options.with_icu_path)
   if have_icu_path and with_intl != 'none':
-    print 'Error: Cannot specify both --with-icu-path and --with-intl'
+    print('Error: Cannot specify both --with-icu-path and --with-intl')
     sys.exit(1)
   elif have_icu_path:
     # Chromium .gyp mode: --with-icu-path
@@ -1008,8 +1029,8 @@ def configure_intl(o):
     o['variables']['v8_enable_i18n_support'] = 1
     pkgicu = pkg_config('icu-i18n')
     if pkgicu[0] is None:
-      print 'Error: could not load pkg-config data for "icu-i18n".'
-      print 'See above errors or the README.md.'
+      print('Error: could not load pkg-config data for "icu-i18n".')
+      print('See above errors or the README.md.')
       sys.exit(1)
     (libs, cflags, libpath) = pkgicu
     # libpath provides linker path which may contain spaces
@@ -1035,17 +1056,17 @@ def configure_intl(o):
   # --with-icu-source processing
   # first, check that they didn't pass --with-icu-source=deps/icu
   if with_icu_source and os.path.abspath(icu_full_path) == os.path.abspath(with_icu_source):
-    print 'Ignoring redundant --with-icu-source=%s' % (with_icu_source)
+    print('Ignoring redundant --with-icu-source=%s' % with_icu_source)
     with_icu_source = None
   # if with_icu_source is still set, try to use it.
   if with_icu_source:
     if os.path.isdir(icu_full_path):
-      print 'Deleting old ICU source: %s' % (icu_full_path)
+      print('Deleting old ICU source: %s' % icu_full_path)
       shutil.rmtree(icu_full_path)
     # now, what path was given?
     if os.path.isdir(with_icu_source):
       # it's a path. Copy it.
-      print '%s -> %s' % (with_icu_source, icu_full_path)
+      print('%s -> %s' % (with_icu_source, icu_full_path))
       shutil.copytree(with_icu_source, icu_full_path)
     else:
       # could be file or URL.
@@ -1069,7 +1090,8 @@ def configure_intl(o):
         os.rename(tmp_icu, icu_full_path)
         shutil.rmtree(icu_tmp_path)
       else:
-        print ' Error: --with-icu-source=%s did not result in an "icu" dir.' % with_icu_source
+        print(' Error: --with-icu-source=%s did not result in an "icu" dir.' % \
+               with_icu_source)
         shutil.rmtree(icu_tmp_path)
         sys.exit(1)
 
@@ -1078,22 +1100,22 @@ def configure_intl(o):
   # ICU source dir relative to root
   o['variables']['icu_path'] = icu_full_path
   if not os.path.isdir(icu_full_path):
-    print '* ECMA-402 (Intl) support didn\'t find ICU in %s..' % (icu_full_path)
+    print('* ECMA-402 (Intl) support didn\'t find ICU in %s..' % icu_full_path)
     # can we download (or find) a zipfile?
     localzip = icu_download(icu_full_path)
     if localzip:
       nodedownload.unpack(localzip, icu_parent_path)
   if not os.path.isdir(icu_full_path):
-    print ' Cannot build Intl without ICU in %s.' % (icu_full_path)
-    print ' (Fix, or disable with "--with-intl=none" )'
+    print(' Cannot build Intl without ICU in %s.' % icu_full_path)
+    print(' (Fix, or disable with "--with-intl=none" )')
     sys.exit(1)
   else:
-    print '* Using ICU in %s' % (icu_full_path)
+    print('* Using ICU in %s' % icu_full_path)
   # Now, what version of ICU is it? We just need the "major", such as 54.
   # uvernum.h contains it as a #define.
   uvernum_h = os.path.join(icu_full_path, 'source/common/unicode/uvernum.h')
   if not os.path.isfile(uvernum_h):
-    print ' Error: could not load %s - is ICU installed?' % uvernum_h
+    print(' Error: could not load %s - is ICU installed?' % uvernum_h)
     sys.exit(1)
   icu_ver_major = None
   matchVerExp = r'^\s*#define\s+U_ICU_VERSION_SHORT\s+"([^"]*)".*'
@@ -1103,7 +1125,7 @@ def configure_intl(o):
     if m:
       icu_ver_major = m.group(1)
   if not icu_ver_major:
-    print ' Could not read U_ICU_VERSION_SHORT version from %s' % uvernum_h
+    print(' Could not read U_ICU_VERSION_SHORT version from %s' % uvernum_h)
     sys.exit(1)
   icu_endianness = sys.byteorder[0];
   o['variables']['icu_ver_major'] = icu_ver_major
@@ -1130,8 +1152,8 @@ def configure_intl(o):
   # this is the icudt*.dat file which node will be using (platform endianness)
   o['variables']['icu_data_file'] = icu_data_file
   if not os.path.isfile(icu_data_path):
-    print ' Error: ICU prebuilt data file %s does not exist.' % icu_data_path
-    print ' See the README.md.'
+    print(' Error: ICU prebuilt data file %s does not exist.' % icu_data_path)
+    print(' See the README.md.')
     # .. and we're not about to build it from .gyp!
     sys.exit(1)
   # map from variable name to subdirs
diff --git a/doc/api/assert.md b/doc/api/assert.md
index 875b4ee5f4cf94..62d76b659cc709 100644
--- a/doc/api/assert.md
+++ b/doc/api/assert.md
@@ -271,7 +271,7 @@ assert.notDeepEqual(obj1, obj3);
   // AssertionError: { a: { b: 1 } } notDeepEqual { a: { b: 1 } }
 
 assert.notDeepEqual(obj1, obj4);
-  // OK, obj1 and obj2 are not deeply equal
+  // OK, obj1 and obj4 are not deeply equal
 ```
 
 If the values are deeply equal, an `AssertionError` is thrown with a `message`
@@ -339,7 +339,7 @@ assert.notStrictEqual(1, 2);
   // OK
 
 assert.notStrictEqual(1, 1);
-  // AssertionError: 1 != 1
+  // AssertionError: 1 !== 1
 
 assert.notStrictEqual(1, '1');
   // OK
diff --git a/doc/api/buffer.md b/doc/api/buffer.md
index 7871a788540e3a..7035fa254e77d9 100644
--- a/doc/api/buffer.md
+++ b/doc/api/buffer.md
@@ -522,7 +522,7 @@ A `TypeError` will be thrown if `size` is not a number.
 
 * `string` {String}
 * `encoding` {String} Default: `'utf8'`
-* Return: {Number}
+* Returns: {Number}
 
 Returns the actual byte length of a string. This is not the same as
 [`String.prototype.length`][] since that returns the number of *characters* in
@@ -546,7 +546,7 @@ added: v0.11.13
 
 * `buf1` {Buffer}
 * `buf2` {Buffer}
-* Return: {Number}
+* Returns: {Number}
 
 Compares `buf1` to `buf2` typically for the purpose of sorting arrays of
 Buffers. This is equivalent is calling [`buf1.compare(buf2)`][].
@@ -563,7 +563,7 @@ added: v0.7.11
 
 * `list` {Array} List of Buffer objects to concat
 * `totalLength` {Number} Total length of the Buffers in the list when concatenated
-* Return: {Buffer}
+* Returns: {Buffer}
 
 Returns a new Buffer which is the result of concatenating all the Buffers in
 the `list` together.
@@ -692,7 +692,7 @@ A `TypeError` will be thrown if `str` is not a string.
 ### Class Method: Buffer.isBuffer(obj)
 
 * `obj` {Object}
-* Return: {Boolean}
+* Returns: {Boolean}
 
 Returns 'true' if `obj` is a Buffer.
 
@@ -702,7 +702,7 @@ added: v0.9.1
 -->
 
 * `encoding` {String} The encoding string to test
-* Return: {Boolean}
+* Returns: {Boolean}
 
 Returns true if the `encoding` is a valid encoding argument, or false
 otherwise.
@@ -737,7 +737,7 @@ added: v0.11.13
 -->
 
 * `otherBuffer` {Buffer}
-* Return: {Number}
+* Returns: {Number}
 
 Compares two Buffer instances and returns a number indicating whether `buf`
 comes before, after, or is the same as the `otherBuffer` in sort order.
@@ -773,7 +773,7 @@ console.log(buf2.compare(buf3));
 * `targetStart` {Number} Default: 0
 * `sourceStart` {Number} Default: 0
 * `sourceEnd` {Number} Default: `buffer.length`
-* Return: {Number} The number of bytes copied.
+* Returns: {Number} The number of bytes copied.
 
 Copies data from a region of this Buffer to a region in the target Buffer even
 if the target memory region overlaps with the source.
@@ -815,7 +815,7 @@ console.log(buf.toString());
 added: v1.1.0
 -->
 
-* Return: {Iterator}
+* Returns: {Iterator}
 
 Creates and returns an [iterator][] of `[index, byte]` pairs from the Buffer
 contents.
@@ -840,7 +840,7 @@ added: v1.0.0
 -->
 
 * `otherBuffer` {Buffer}
-* Return: {Boolean}
+* Returns: {Boolean}
 
 Returns a boolean indicating whether `this` and `otherBuffer` have exactly the
 same bytes.
@@ -864,7 +864,7 @@ added: v0.5.0
 * `value` {String|Number}
 * `offset` {Number} Default: 0
 * `end` {Number} Default: `buffer.length`
-* Return: {Buffer}
+* Returns: {Buffer}
 
 Fills the Buffer with the specified value. If the `offset` and `end` are not
 given it will fill the entire Buffer. The method returns a reference to the
@@ -884,7 +884,7 @@ added: v1.5.0
 * `value` {String|Buffer|Number}
 * `byteOffset` {Number} Default: 0
 * `encoding` {String} Default: `'utf8'`
-* Return: {Number}
+* Returns: {Number}
 
 Operates similar to [`Array#indexOf()`][] in that it returns either the
 starting index position of `value` in Buffer or `-1` if the Buffer does not
@@ -922,7 +922,7 @@ utf16Buffer.indexOf('\u03a3', -4, 'ucs2');
 added: v1.1.0
 -->
 
-* Return: {Iterator}
+* Returns: {Iterator}
 
 Creates and returns an [iterator][] of Buffer keys (indices).
 
@@ -980,7 +980,7 @@ console.log(buf.length);
 
 * `offset` {Number} `0 <= offset <= buf.length - 8`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads a 64-bit double from the Buffer at the specified `offset` with specified
 endian format (`readDoubleBE()` returns big endian, `readDoubleLE()` returns
@@ -1008,7 +1008,7 @@ buf.readDoubleLE(1, true); // Warning: reads passed end of buffer!
 
 * `offset` {Number} `0 <= offset <= buf.length - 4`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads a 32-bit float from the Buffer at the specified `offset` with specified
 endian format (`readFloatBE()` returns big endian, `readFloatLE()` returns
@@ -1035,7 +1035,7 @@ buf.readFloatLE(1, true); // Warning: reads passed end of buffer!
 
 * `offset` {Number} `0 <= offset <= buf.length - 1`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads a signed 8-bit integer from the Buffer at the specified `offset`.
 
@@ -1058,7 +1058,7 @@ buf.readInt8(1);
 
 * `offset` {Number} `0 <= offset <= buf.length - 2`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads a signed 16-bit integer from the Buffer at the specified `offset` with
 the specified endian format (`readInt16BE()` returns big endian,
@@ -1083,7 +1083,7 @@ buf.readInt16LE(1);
 
 * `offset` {Number} `0 <= offset <= buf.length - 4`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads a signed 32-bit integer from the Buffer at the specified `offset` with
 the specified endian format (`readInt32BE()` returns big endian,
@@ -1114,7 +1114,7 @@ added: v1.0.0
 * `offset` {Number} `0 <= offset <= buf.length - byteLength`
 * `byteLength` {Number} `0 < byteLength <= 6`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads `byteLength` number of bytes from the Buffer at the specified `offset`
 and interprets the result as a two's complement signed value. Supports up to 48
@@ -1138,7 +1138,7 @@ Setting `noAssert` to `true` skips validation of the `offset`. This allows the
 
 * `offset` {Number} `0 <= offset <= buf.length - 1`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads an unsigned 8-bit integer from the Buffer at the specified `offset`.
 
@@ -1159,7 +1159,7 @@ buf.readUInt8(1);
 
 * `offset` {Number} `0 <= offset <= buf.length - 2`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads an unsigned 16-bit integer from the Buffer at the specified `offset` with
 specified endian format (`readUInt16BE()` returns big endian,
@@ -1192,7 +1192,7 @@ buf.readUInt16LE(2);
 
 * `offset` {Number} `0 <= offset <= buf.length - 4`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads an unsigned 32-bit integer from the Buffer at the specified `offset` with
 specified endian format (`readUInt32BE()` returns big endian,
@@ -1221,7 +1221,7 @@ added: v1.0.0
 * `offset` {Number} `0 <= offset <= buf.length - byteLength`
 * `byteLength` {Number} `0 < byteLength <= 6`
 * `noAssert` {Boolean} Default: false
-* Return: {Number}
+* Returns: {Number}
 
 Reads `byteLength` number of bytes from the Buffer at the specified `offset`
 and interprets the result as an unsigned integer. Supports up to 48
@@ -1245,7 +1245,7 @@ Setting `noAssert` to `true` skips validation of the `offset`. This allows the
 
 * `start` {Number} Default: 0
 * `end` {Number} Default: `buffer.length`
-* Return: {Buffer}
+* Returns: {Buffer}
 
 Returns a new Buffer that references the same memory as the original, but
 offset and cropped by the `start` and `end` indices.
@@ -1290,7 +1290,7 @@ buf.slice(-5, -2).toString();
 * `encoding` {String} Default: `'utf8'`
 * `start` {Number} Default: 0
 * `end` {Number} Default: `buffer.length`
-* Return: {String}
+* Returns: {String}
 
 Decodes and returns a string from the Buffer data using the specified
 character set `encoding`.
@@ -1315,7 +1315,7 @@ buf.toString(undefined,0,5);
 added: v0.9.2
 -->
 
-* Return: {Object}
+* Returns: {Object}
 
 Returns a JSON representation of the Buffer instance.  [`JSON.stringify()`][]
 implicitly calls this function when stringifying a Buffer instance.
@@ -1344,7 +1344,7 @@ console.log(copy.toString());
 added: v1.1.0
 -->
 
-* Return: {Iterator}
+* Returns: {Iterator}
 
 Creates and returns an [iterator][] for Buffer values (bytes). This function is
 called automatically when the Buffer is used in a `for..of` statement.
@@ -1380,7 +1380,7 @@ for (var value of buf) {
 * `offset` {Number} Default: 0
 * `length` {Number} Default: `buffer.length - offset`
 * `encoding` {String} Default: `'utf8'`
-* Return: {Number} Numbers of bytes written
+* Returns: {Number} Numbers of bytes written
 
 Writes `string` to the Buffer at `offset` using the given `encoding`.
 The `length` parameter is the number of bytes to write. If the Buffer did not
@@ -1401,7 +1401,7 @@ console.log(`${len} bytes: ${buf.toString('utf8', 0, len)}`);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 8`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` with specified endian
 format (`writeDoubleBE()` writes big endian, `writeDoubleLE()` writes little
@@ -1434,7 +1434,7 @@ console.log(buf);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 4`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` with specified endian
 format (`writeFloatBE()` writes big endian, `writeFloatLE()` writes little
@@ -1466,7 +1466,7 @@ console.log(buf);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 1`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset`. The `value` should be a
 valid signed 8-bit integer.  Behavior is not defined when `value` is anything
@@ -1493,7 +1493,7 @@ console.log(buf);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 2`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` with specified endian
 format (`writeInt16BE()` writes big endian, `writeInt16LE()` writes little
@@ -1521,7 +1521,7 @@ console.log(buf);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 4`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` with specified endian
 format (`writeInt32BE()` writes big endian, `writeInt32LE()` writes little
@@ -1553,7 +1553,7 @@ added: v1.0.0
 * `offset` {Number} `0 <= offset <= buf.length - byteLength`
 * `byteLength` {Number} `0 < byteLength <= 6`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` and `byteLength`.
 Supports up to 48 bits of accuracy. For example:
@@ -1582,7 +1582,7 @@ Behavior is not defined when `value` is anything other than an integer.
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 1`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset`. The `value` should be a
 valid unsigned 8-bit integer.  Behavior is not defined when `value` is anything
@@ -1612,7 +1612,7 @@ console.log(buf);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 2`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` with specified endian
 format (`writeUInt16BE()` writes big endian, `writeUInt16LE()` writes little
@@ -1647,7 +1647,7 @@ console.log(buf);
 * `value` {Number} Bytes to be written to Buffer
 * `offset` {Number} `0 <= offset <= buf.length - 4`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` with specified endian
 format (`writeUInt32BE()` writes big endian, `writeUInt32LE()` writes little
@@ -1681,7 +1681,7 @@ console.log(buf);
 * `offset` {Number} `0 <= offset <= buf.length - byteLength`
 * `byteLength` {Number} `0 < byteLength <= 6`
 * `noAssert` {Boolean} Default: false
-* Return: {Number} The offset plus the number of written bytes
+* Returns: {Number} The offset plus the number of written bytes
 
 Writes `value` to the Buffer at the specified `offset` and `byteLength`.
 Supports up to 48 bits of accuracy. For example:
diff --git a/doc/api/child_process.md b/doc/api/child_process.md
index b596b2547d3f6d..7b4e3a70a73077 100644
--- a/doc/api/child_process.md
+++ b/doc/api/child_process.md
@@ -135,7 +135,7 @@ added: v0.1.90
   * `error` {Error}
   * `stdout` {String|Buffer}
   * `stderr` {String|Buffer}
-* Return: {ChildProcess}
+* Returns: {ChildProcess}
 
 Spawns a shell then executes the `command` within that shell, buffering any
 generated output.
@@ -212,7 +212,7 @@ added: v0.1.91
   * `error` {Error}
   * `stdout` {String|Buffer}
   * `stderr` {String|Buffer}
-* Return: {ChildProcess}
+* Returns: {ChildProcess}
 
 The `child_process.execFile()` function is similar to [`child_process.exec()`][]
 except that it does not spawn a shell. Rather, the specified executable `file`
@@ -258,7 +258,7 @@ added: v0.5.0
     [`stdio`][] for more details (default is false)
   * `uid` {Number} Sets the user identity of the process. (See setuid(2).)
   * `gid` {Number} Sets the group identity of the process. (See setgid(2).)
-* Return: {ChildProcess}
+* Returns: {ChildProcess}
 
 The `child_process.fork()` method is a special case of
 [`child_process.spawn()`][] used specifically to spawn new Node.js processes.
@@ -269,7 +269,7 @@ allows messages to be passed back and forth between the parent and child. See
 
 It is important to keep in mind that spawned Node.js child processes are
 independent of the parent with exception of the IPC communication channel
-that is established between the two. Each process has it's own memory, with
+that is established between the two. Each process has its own memory, with
 their own V8 instances. Because of the additional resource allocations
 required, spawning a large number of child Node.js processes is not
 recommended.
@@ -776,7 +776,7 @@ added: v0.1.90
 * `signal` {String}
 
 The `child.kill()` methods sends a signal to the child process. If no argument
-is given, the process will be sent the `'SIGTERM'` signal. See `signal(7)` for
+is given, the process will be sent the `'SIGTERM'` signal. See signal(7) for
 a list of available signals.
 
 ```js
@@ -852,7 +852,7 @@ added: v0.5.9
 * `message` {Object}
 * `sendHandle` {Handle}
 * `callback` {Function}
-* Return: {Boolean}
+* Returns: {Boolean}
 
 When an IPC channel has been established between the parent and child (
 i.e. when using [`child_process.fork()`][]), the `child.send()` method can be
diff --git a/doc/api/cluster.md b/doc/api/cluster.md
index 0c34aae6b76939..aca07a9b6e0248 100644
--- a/doc/api/cluster.md
+++ b/doc/api/cluster.md
@@ -144,7 +144,7 @@ added: v0.11.2
 -->
 
 * `code` {Number} the exit code, if it exited normally.
-* `signal` {String} the name of the signal (eg. `'SIGHUP'`) that caused
+* `signal` {String} the name of the signal (e.g. `'SIGHUP'`) that caused
   the process to be killed.
 
 Similar to the `cluster.on('exit')` event, but specific to this worker.
@@ -390,7 +390,7 @@ added: v0.7.0
 * `message` {Object}
 * `sendHandle` {Handle}
 * `callback` {Function}
-* Return: Boolean
+* Returns: Boolean
 
 Send a message to a worker or master, optionally with a handle.
 
@@ -466,7 +466,7 @@ added: v0.7.9
 
 * `worker` {cluster.Worker}
 * `code` {Number} the exit code, if it exited normally.
-* `signal` {String} the name of the signal (eg. `'SIGHUP'`) that caused
+* `signal` {String} the name of the signal (e.g. `'SIGHUP'`) that caused
   the process to be killed.
 
 When any of the workers die the cluster module will emit the `'exit'` event.
diff --git a/doc/api/console.md b/doc/api/console.md
index cd546281464d33..4de1c096430d16 100644
--- a/doc/api/console.md
+++ b/doc/api/console.md
@@ -184,7 +184,7 @@ added: v0.1.100
 
 Prints to `stderr` with newline. Multiple arguments can be passed, with the
 first used as the primary message and all additional used as substitution
-values similar to `printf(3)` (the arguments are all passed to
+values similar to printf(3) (the arguments are all passed to
 [`util.format()`][]).
 
 ```js
@@ -213,7 +213,7 @@ added: v0.1.100
 
 Prints to `stdout` with newline. Multiple arguments can be passed, with the
 first used as the primary message and all additional used as substitution
-values similar to `printf(3)` (the arguments are all passed to
+values similar to printf(3) (the arguments are all passed to
 [`util.format()`][]).
 
 ```js
diff --git a/doc/api/crypto.md b/doc/api/crypto.md
index 177d1bd107597c..5a471ef8dad423 100644
--- a/doc/api/crypto.md
+++ b/doc/api/crypto.md
@@ -311,7 +311,7 @@ added: v1.0.0
 -->
 
 When using an authenticated encryption mode (only `GCM` is currently
-supported), the `cipher.setAAD()` method sets the value used for the
+supported), the `decipher.setAAD()` method sets the value used for the
 _additional authenticated data_ (AAD) input parameter.
 
 ### decipher.setAuthTag(buffer)
@@ -910,8 +910,8 @@ of two ways:
 - Using the [`verify.update()`][] and [`verify.verify()`][] methods to verify
   the signature.
 
-  The [`crypto.createSign()`][] method is used to create `Sign` instances.
-  `Sign` objects are not to be created directly using the `new` keyword.
+The [`crypto.createVerify()`][] method is used to create `Verify` instances.
+`Verify` objects are not to be created directly using the `new` keyword.
 
 Example: Using `Verify` objects as streams:
 
@@ -1405,7 +1405,6 @@ keys:
 * `padding` : An optional padding value, one of the following:
   * `constants.RSA_NO_PADDING`
   * `constants.RSA_PKCS1_PADDING`
-  * `constants.RSA_PKCS1_OAEP_PADDING`
 
 All paddings are defined in the `constants` module.
 
diff --git a/doc/api/debugger.md b/doc/api/debugger.md
index 6ddaf9c92a06a0..00eb1f0ffdaff5 100644
--- a/doc/api/debugger.md
+++ b/doc/api/debugger.md
@@ -4,10 +4,10 @@
 
 <!-- type=misc -->
 
-Node.js includes a full-featured out-of-process debugging utility accessible
-via a simple [TCP-based protocol][] and built-in debugging client. To use it,
-start Node.js with the `debug` argument followed by the path to the script to
-debug; a prompt will be displayed indicating successful launch of the debugger:
+Node.js includes an out-of-process debugging utility accessible via a
+[TCP-based protocol][] and built-in debugging client. To use it, start Node.js
+with the `debug` argument followed by the path to the script to debug; a prompt
+will be displayed indicating successful launch of the debugger:
 
 ```
 $ node debug myscript.js
diff --git a/doc/api/dns.md b/doc/api/dns.md
index 933e9e8479e9b6..406f1548e8393b 100644
--- a/doc/api/dns.md
+++ b/doc/api/dns.md
@@ -256,7 +256,7 @@ added: v0.1.90
 Uses the DNS protocol to resolve name server records (`NS` records) for the
 `hostname`. The `addresses` argument passed to the `callback` function will
 contain an array of name server records available for `hostname`
-(e.g., `['ns1.example.com', 'ns2.example.com']`).
+(e.g. `['ns1.example.com', 'ns2.example.com']`).
 
 ## dns.resolveSoa(hostname, callback)
 <!-- YAML
@@ -394,14 +394,14 @@ Under the hood, [`dns.lookup()`][] uses the same operating system facilities
 as most other programs. For instance, [`dns.lookup()`][] will almost always
 resolve a given name the same way as the `ping` command. On most POSIX-like
 operating systems, the behavior of the [`dns.lookup()`][] function can be
-modified by changing settings in `nsswitch.conf(5)` and/or `resolv.conf(5)`,
+modified by changing settings in nsswitch.conf(5) and/or resolv.conf(5),
 but note that changing these files will change the behavior of _all other
 programs running on the same operating system_.
 
 Though the call to `dns.lookup()` will be asynchronous from JavaScript's
-perspective, it is implemented as a synchronous call to `getaddrinfo(3)` that
+perspective, it is implemented as a synchronous call to getaddrinfo(3) that
 runs on libuv's threadpool. Because libuv's threadpool has a fixed size, it
-means that if for whatever reason the call to `getaddrinfo(3)` takes a long
+means that if for whatever reason the call to getaddrinfo(3) takes a long
 time, other operations that could run on libuv's threadpool (such as filesystem
 operations) will experience degraded performance. In order to mitigate this
 issue, one potential solution is to increase the size of libuv's threadpool by
@@ -412,7 +412,7 @@ setting the `'UV_THREADPOOL_SIZE'` environment variable to a value greater than
 ### `dns.resolve()`, `dns.resolve*()` and `dns.reverse()`
 
 These functions are implemented quite differently than [`dns.lookup()`][]. They
-do not use `getaddrinfo(3)` and they _always_ perform a DNS query on the
+do not use getaddrinfo(3) and they _always_ perform a DNS query on the
 network. This network communication is always done asynchronously, and does not
 use libuv's threadpool.
 
diff --git a/doc/api/fs.md b/doc/api/fs.md
index 0668f1e24f3cd5..d20024419cb247 100644
--- a/doc/api/fs.md
+++ b/doc/api/fs.md
@@ -212,13 +212,13 @@ page.
 The times in the stat object have the following semantics:
 
 * `atime` "Access Time" - Time when file data last accessed.  Changed
-  by the `mknod(2)`, `utimes(2)`, and `read(2)` system calls.
+  by the mknod(2), utimes(2), and read(2) system calls.
 * `mtime` "Modified Time" - Time when file data last modified.
-  Changed by the `mknod(2)`, `utimes(2)`, and `write(2)` system calls.
+  Changed by the mknod(2), utimes(2), and write(2) system calls.
 * `ctime` "Change Time" - Time when file status was last changed
-  (inode data modification).  Changed by the `chmod(2)`, `chown(2)`,
-  `link(2)`, `mknod(2)`, `rename(2)`, `unlink(2)`, `utimes(2)`,
-  `read(2)`, and `write(2)` system calls.
+  (inode data modification).  Changed by the chmod(2), chown(2),
+  link(2), mknod(2), rename(2), unlink(2), utimes(2),
+  read(2), and write(2) system calls.
 * `birthtime` "Birth Time" -  Time of file creation. Set once when the
   file is created.  On filesystems where birthtime is not available,
   this field may instead hold either the `ctime` or
@@ -226,7 +226,7 @@ The times in the stat object have the following semantics:
   value may be greater than `atime` or `mtime` in this case. On Darwin
   and other FreeBSD variants, also set if the `atime` is explicitly
   set to an earlier value than the current `birthtime` using the
-  `utimes(2)` system call.
+  utimes(2) system call.
 
 Prior to Node v0.12, the `ctime` held the `birthtime` on Windows
 systems.  Note that as of v0.12, `ctime` is not "creation time", and
@@ -503,7 +503,9 @@ default value of 64 kb for the same parameter.
 
 `options` can include `start` and `end` values to read a range of bytes from
 the file instead of the entire file.  Both `start` and `end` are inclusive and
-start at 0. The `encoding` can be any one of those accepted by [`Buffer`][].
+start counting at 0. If `fd` is specified and `start` is omitted or `undefined`,
+`fs.createReadStream()` reads sequentially from the current file position.
+The `encoding` can be any one of those accepted by [`Buffer`][].
 
 If `fd` is specified, `ReadStream` will ignore the `path` argument and will use
 the specified file descriptor. This means that no `'open'` event will be emitted.
diff --git a/doc/api/http.md b/doc/api/http.md
index 17dd39c76ccfae..8b99ba5256735a 100644
--- a/doc/api/http.md
+++ b/doc/api/http.md
@@ -510,7 +510,7 @@ with a 100 Continue as appropriate.
 
 Handling this event involves calling [`response.writeContinue()`][] if the client
 should continue to send the request body, or generating an appropriate HTTP
-response (e.g., 400 Bad Request) if the client should not continue to send the
+response (e.g. 400 Bad Request) if the client should not continue to send the
 request body.
 
 Note that when this event is emitted and handled, the `'request'` event will
@@ -755,7 +755,7 @@ This method adds HTTP trailing headers (a header but at the end of the
 message) to the response.
 
 Trailers will **only** be emitted if chunked encoding is used for the
-response; if it is not (e.g., if the request was HTTP/1.0), they will
+response; if it is not (e.g. if the request was HTTP/1.0), they will
 be silently discarded.
 
 Note that HTTP requires the `Trailer` header to be sent if you intend to
diff --git a/doc/api/https.md b/doc/api/https.md
index 4c515a09b605ae..a5ff6afbd6f4aa 100644
--- a/doc/api/https.md
+++ b/doc/api/https.md
@@ -158,11 +158,11 @@ var req = https.request(options, (res) => {
     process.stdout.write(d);
   });
 });
-req.end();
 
 req.on('error', (e) => {
   console.error(e);
 });
+req.end();
 ```
 
 The options argument has the following options
@@ -192,8 +192,7 @@ The options argument has the following options
  - `false`: opts out of connection pooling with an Agent, defaults request to
    `Connection: close`.
 
-The following options from [`tls.connect()`][] can also be specified. However, a
-[`globalAgent`][] silently ignores these.
+The following options from [`tls.connect()`][] can also be specified:
 
 - `pfx`: Certificate, Private key and CA certificates to use for SSL. Default `null`.
 - `key`: Private key to use for SSL. Default `null`.
diff --git a/doc/api/modules.md b/doc/api/modules.md
index dd02fc372a6887..f5dba78dac84b1 100644
--- a/doc/api/modules.md
+++ b/doc/api/modules.md
@@ -6,16 +6,18 @@
 
 Node.js has a simple module loading system.  In Node.js, files and modules
 are in one-to-one correspondence (each file is treated as a separate module).
-As an example, `foo.js` loads the module `circle.js` in the same directory.
 
-The contents of `foo.js`:
+As an example, consider a file named `foo.js`:
 
 ```js
 const circle = require('./circle.js');
 console.log(`The area of a circle of radius 4 is ${circle.area(4)}`);
 ```
 
-The contents of `circle.js`:
+On the first line, `foo.js` loads the module `circle.js` that is in the same
+directory as `foo.js`.
+
+Here are the contents of `circle.js`:
 
 ```js
 const PI = Math.PI;
@@ -23,7 +25,6 @@ const PI = Math.PI;
 exports.area = (r) => PI * r * r;
 
 exports.circumference = (r) => 2 * PI * r;
-
 ```
 
 The module `circle.js` has exported the functions `area()` and
@@ -181,9 +182,9 @@ NODE_MODULES_PATHS(START)
 3. let DIRS = []
 4. while I >= 0,
    a. if PARTS[I] = "node_modules" CONTINUE
-   c. DIR = path join(PARTS[0 .. I] + "node_modules")
-   b. DIRS = DIRS + DIR
-   c. let I = I - 1
+   b. DIR = path join(PARTS[0 .. I] + "node_modules")
+   c. DIRS = DIRS + DIR
+   d. let I = I - 1
 5. return DIRS
 ```
 
@@ -529,34 +530,51 @@ const x = require('./x');
 console.log(x.a);
 ```
 
-#### exports alias
+#### exports shortcut
 <!-- YAML
 added: v0.1.16
 -->
 
-The `exports` variable that is available within a module starts as a reference
-to `module.exports`. As with any variable, if you assign a new value to it, it
-is no longer bound to the previous value.
+The `exports` variable is available within a module's file-level scope, and is
+assigned the value of `module.exports` before the module is evaluated.
+
+It allows a shortcut, so that `module.exports.f = ...` can be written more
+succinctly as `exports.f = ...`. However, be aware that like any variable, if a
+new value is assigned to `exports`, it is no longer bound to `module.exports`:
+
+```js
+module.exports.hello = true; // Exported from require of module
+exports = { hello: false };  // Not exported, only available in the module
+```
+
+When the `module.exports` property is being completely replaced by a new
+object, it is common to also reassign `exports`, for example:
+
+```js
+module.exports = exports = function Constructor() {
+    // ... etc.
+```
 
 To illustrate the behavior, imagine this hypothetical implementation of
-`require()`:
+`require()`, which is quite similar to what is actually done by `require()`:
 
 ```js
 function require(...) {
-  // ...
+  var module = { exports: {} };
   ((module, exports) => {
-    // Your module code here
-    exports = some_func;        // re-assigns exports, exports is no longer
-                                // a shortcut, and nothing is exported.
-    module.exports = some_func; // makes your module export 0
+    // Your module code here. In this example, define a function.
+    function some_func() {};
+    exports = some_func;
+    // At this point, exports is no longer a shortcut to module.exports, and
+    // this module will still export an empty default object.
+    module.exports = some_func;
+    // At this point, the module will now export some_func, instead of the
+    // default object.
   })(module, module.exports);
-  return module;
+  return module.exports;
 }
 ```
 
-As a guideline, if the relationship between `exports` and `module.exports`
-seems like magic to you, ignore `exports` and only use `module.exports`.
-
 ### module.filename
 <!-- YAML
 added: v0.1.16
@@ -601,7 +619,7 @@ added: v0.5.1
 -->
 
 * `id` {String}
-* Return: {Object} `module.exports` from the resolved module
+* Returns: {Object} `module.exports` from the resolved module
 
 The `module.require` method provides a way to load a module as if
 `require()` was called from the original module.
diff --git a/doc/api/process.md b/doc/api/process.md
index 7967354face764..7279c33a2935a6 100644
--- a/doc/api/process.md
+++ b/doc/api/process.md
@@ -938,7 +938,7 @@ added: v0.5.9
 * `message` {Object}
 * `sendHandle` {Handle object}
 * `callback` {Function}
-* Return: {Boolean}
+* Returns: {Boolean}
 
 When Node.js is spawned with an IPC channel attached, it can send messages to its
 parent process using `process.send()`. Each will be received as a
diff --git a/doc/api/readline.md b/doc/api/readline.md
index 5e890c12852439..19923009345762 100644
--- a/doc/api/readline.md
+++ b/doc/api/readline.md
@@ -207,7 +207,7 @@ added: v0.7.5
 **This does not work on Windows.**
 
 Emitted whenever the `input` stream is sent to the background with `^Z`,
-respectively known as `SIGTSTP`, and then continued with `fg(1)`. This event
+respectively known as `SIGTSTP`, and then continued with fg(1). This event
 only emits if the stream was not paused before sending the program to the
 background.
 
diff --git a/doc/api/repl.md b/doc/api/repl.md
index 6d10f40d7eb60a..9863b9bfce60c9 100644
--- a/doc/api/repl.md
+++ b/doc/api/repl.md
@@ -359,7 +359,7 @@ connect to a long-running Node.js process without restarting it.
 For an example of running a "full-featured" (`terminal`) REPL over
 a `net.Server` and `net.Socket` instance, see: https://gist.github.com/2209310
 
-For an example of running a REPL instance over `curl(1)`,
+For an example of running a REPL instance over curl(1),
 see: https://gist.github.com/2053342
 
 [`readline.prompt`]: readline.html#readline_rl_prompt_preservecursor
diff --git a/doc/api/stream.md b/doc/api/stream.md
index 34ab5d964d9ea8..62e5190330610d 100644
--- a/doc/api/stream.md
+++ b/doc/api/stream.md
@@ -254,7 +254,7 @@ end
 
 #### readable.isPaused()
 
-* Return: {Boolean}
+* Returns: {Boolean}
 
 This method returns whether or not the `readable` has been **explicitly**
 paused by client code (using [`stream.pause()`][stream-pause] without a
@@ -272,7 +272,7 @@ readable.isPaused() // === false
 
 #### readable.pause()
 
-* Return: `this`
+* Returns: `this`
 
 This method will cause a stream in flowing mode to stop emitting
 [`'data'`][] events, switching out of flowing mode. Any data that becomes
@@ -382,7 +382,7 @@ event has been triggered will return `null`. No runtime error will be raised.
 
 #### readable.resume()
 
-* Return: `this`
+* Returns: `this`
 
 This method will cause the readable stream to resume emitting [`'data'`][]
 events.
@@ -403,7 +403,7 @@ readable.on('end', () => {
 #### readable.setEncoding(encoding)
 
 * `encoding` {String} The encoding to use.
-* Return: `this`
+* Returns: `this`
 
 Call this function to cause the stream to return strings of the specified
 encoding instead of Buffer objects. For example, if you do
diff --git a/doc/api/tls.md b/doc/api/tls.md
index 4d836b5e7f7be1..9c650ad9bbec5e 100644
--- a/doc/api/tls.md
+++ b/doc/api/tls.md
@@ -365,7 +365,7 @@ port value of zero will assign a random port.
 This function is asynchronous. The last parameter `callback` will be called
 when the server has been bound.
 
-See `net.Server` for more information.
+See [`net.Server`][] for more information.
 
 ### server.maxConnections
 <!-- YAML
diff --git a/doc/api_assets/style.css b/doc/api_assets/style.css
index 1e82464cc93b79..c187079a26f98e 100644
--- a/doc/api_assets/style.css
+++ b/doc/api_assets/style.css
@@ -274,6 +274,7 @@ pre {
 
 pre > code {
   font-size: .8em;
+  padding: 0;
 }
 
 pre + h3 {
diff --git a/doc/ctc-meetings/2015-10-28.md b/doc/ctc-meetings/2015-10-28.md
deleted file mode 100644
index 5efe94454ad3f8..00000000000000
--- a/doc/ctc-meetings/2015-10-28.md
+++ /dev/null
@@ -1,276 +0,0 @@
-# Node Foundation CTC Meeting 2015-10-28
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/ctc-meeting-2015-10-28
-* **GitHub Issue**: https://github.com/nodejs/node/issues/3561
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1GsTF3no6bimA20hi9i5aTBudBSM8jzPvuODR01hOltc>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1ad8Xlza_B-iWexdlAd1Z5muzBy_HH88t_iSD31OUepA>_
-
-## Present
-
-* Rod Vagg (CTC)
-* Brian White (CTC)
-* James Snell (CTC)
-* Chris Dickinson (CTC)
-* Ben Noordhuis (CTC)
-* Jeremiah Senkpiel (CTC)
-* Trevor Norris (CTC)
-* Alexis Campailla (CTC)
-* Mikeal Rogers (observer)
-* Shigeki Ohtsu (CTC)
-* Seth Thompson (observer)
-* Bert Belder (CTC)
-* Fedor Indutny (CTC)
-* Ben Noordhuis (CTC)
-* Colin Ihrig (CTC)
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node
-
-* Load JSON-LD in the same way as JSON [#3502](https://github.com/nodejs/node/pull/3502)
-* fs: decode filenames using UTF-8 in fs.watch [#3401](https://github.com/nodejs/node/pull/3401)
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-
-## Minutes
-
-### Review of previous meeting
-
-* governance: add new collaborators #VIII [#3472](https://github.com/nodejs/node/issues/3472)
-* detect "full-icu" module [#3460](https://github.com/nodejs/node/issues/3460)
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-* node: deprecate public access to `process.binding` [#2768](https://github.com/nodejs/node/pull/2768)
-* node: make listen address configurable [#3316](https://github.com/nodejs/node/pull/3316)
-
-### Standup
-
-* Rod Vagg (CTC): Traveling, rc for v5.x, going to put another rc out today, comfortable with it getting released tomorrow. If it slips we’ll put it off until next week. Just need to do more smoke testing on this.
-* Brian White (CTC): Not a whole lot this week — triaging, responding to issues.
-* James Snell (CTC): Getting HTTP parser up to v2.6; getting 4.2.2 LTS update ready to go. open issue on LTS repo, would love eyes on it, to verify that the commits going into 4.2.2 look good. (https://github.com/nodejs/LTS/issues/50) working with Miles on getting CITGM updated.
-* Chris Dickinson (CTC): Some silly build stuff
-* Jeremiah Senkpiel (CTC): Not much — computer was dead since last Friday, ): but repaired now.
-* Trevor Norris (CTC): Bugs and issues — couple of outstanding PRs around asyncwrap, one done at Fedor’s request to make AsyncWrap public, in order to make JSStream class public
-* Alexis Campailla (CTC): Meetings; first API WG meeting, defining scope of the work for the WG, we want to address engine abstraction and native module API and some performance issues; small work in CI to add diagnostics; progress on module build service, going to post finding soon to get feedback
-* Mikeal Rogers (observer): getting a lot of interest on a certification program for node, for alternative implementations, looking at notes for API WG (thanks for taking great notes! that was awesome) I reached out to a few people that may contribute as well
-* Seth Thompson (observer): No updates this week.
-* Bert Belder (CTC): nothing noteworthy
-* Ben Noordhuis (CTC): Fixed debugger bugs, reviewed a lot of pull requests.
-* Colin Ihrig (CTC): Trying to help out with issue tracker, anticipate in another week ½ I should have significantly more time to work on core.
-
-### Load JSON-LD in the same way as JSON [#3502](https://github.com/nodejs/node/pull/3502)
-
-* adds .jsonld files to require.extensions so that they’d load using json loader
-
-Rod: I raised this to CTC. I see this as a slippery slope, adding anything more to require.extensions. I don’t see how this won’t turn into XML — turns into bloat in formats that folks want to support. My preference would be to let the ecosystem figure this out and let folks write their own JSON loaders.
-
-Jeremiah: also probably belongs in npm
-
-James: .jsonld is just a json file with a special syntax internally. I have a module that loads it. It’s very easy to work around. Rename the file to use a json extension. I don’t see the harm in landing it, but if we don’t want to go that route,
-
-Mikeal: is the patch to add the extension or to give you your own serializer (extension)
-
-Bert: It seems harmless, but 6 months from now what if someone shows up and says “hey you’re not validating it properly” and then we have to add a validator … I’m very sensitive to slippery slope argument
-
-Alexis: Is it a different syntax?
-
-Bert: is every json document a valid jsonld document?
-
-James: no.
-
-Mikeal: we’re using a parser from npm, are we going to get a war between parsers, swapping them out?
-
-James: this doesn’t do any special parsing for jsonld, it just aliases json and uses the existing process.
-
-Trevor: the problem is what it opens us up to. invariably this leads to more PRs. this patch I don’t have a problem with, but I have a problem with this kind of patch in the future
-
-Bert: I think we’re reaching consensus here, which is: reject this patch. is anyone here strongly in favor.
-
-Ben: not in favor. one argument is jsonld is now a standard. but I too am sensitive to the slippery slope argument, so I’m perfectly fine with rejecting it.
-
-James: when rejecting it, it would be worthwhile to note how to work around it. I can do this.
-
-Jeremiah: require.extensions is not going to change anytime soon, so folks can write their own.
-
-Bert: I think we can go to the next issue.
-
-### fs: decode filenames using UTF-8 in fs.watch [#3401](https://github.com/nodejs/node/pull/3401)
-
-See also [#3519](https://github.com/nodejs/node/issues/3519)
-
-Bert: this is Ben’s issue.
-
-Ben: I wouldn’t say it’s my issue, but I’ve been involved
-the thing is that filenames are frequently (but not always) utf8, the problem is now that node in one or two places it doesn’t encode utf8 [Ben, post meeting addition: For background: I thought we had some file logic baked into node::Environment and the dtrace/etw/lttng/systemtap subsystems but turns out that's not the case.]
-
-Bert: where else are we encoding differently?
-
-Ben: I can answer this in a few seconds. At least, I think there are more places. Maybe I’m mistaken, also a possibility!
-
-Jeremiah: I think someone else said it was only fs.watch too.
-
-Bert: I’ve seen the discussion but I haven’t commented. I think there’s a problem with assuming that all files are all utf8, but it seems inconsequential to assume this everywhere but this one place
-
-Ben: this is not the best issue to link to, I agree it’s inconsistent to do utf8 in most places and latin1 in only one place. There’s a link to another issue 3519. my beef with the PR is not that it’s a terrible fix, it’s more that decoding to utf8 is not always the right thing to do because not all fs are utf-8. If we’re going to do this it has to be a semver major, and if we’re going to do a semver major, then it may as well be a full fix, which I’ve outlined in 3519.
-
-Bert: there’s actually some discussions we need to have around these things. Your suggestion is to not land this PR, and instead fix this the right way. Do you think it’s likely that 3519 will see attention any time soon?
-
-Ben: It’s on my todo list. I should mention that the way node deals with file names has been a thorn in my side for a long time now, I’ve been planning to do something about it for a long time, so take this as you will.
-
-Bert: my question is: do we take this PR now, ahead of
-
-Bert: customizable decoding
-
-Mikeal: is the other one going to be a breaking change?
-
-Ben: yes
-
-Bert: or it could be a bugfix?
-
-Mikeal: so it would make sense to buffer as many changes around that as possible.
-
-Jeremiah: we could land the semver-major fix on master which would go into 6.x, then if we have time before 6.x we could do the proper fix. maybe that keeps us from fixing it entirely though?
-
-Ben: that’s my problem, it’s a bandaid that lets us truck on for a another couple of years.
-
-James?: I don’t really like quick fixes, but …
-
-Trevor: on the fs doc page, a lot of those calls reference the system level call, on unix do those use utf8
-
-Ben: how do you mean?
-
-Trevor: for example, stat, first arg is char* pathname, if i were to take a utf8 string and read that in… what encoding does it use?
-
-Ben: syscall is agnostic. kernel treats as string of bytes. in node, we call fs.stat in javascript, string is decoded to utf8, then passed on to the kernel.
-
-Trevor: if i have a file that’s latin1, I’d have to turn that into a buffer as a binary buffer then tostring it to a utf8 string in order for the file to be open?
-
-[multiple people are talking]
-
-Ben: yes.
-
-Ben: sometimes it’s not possible to open files with funny characters in their names.
-
-Trevor: if there were a file with invalid utf8 characters it’d be impossible to open those, right?
-
-Ben: yep.
-
-James: I’m not a fan of the quick fix. I am okay with incremental so long as the larger task gets done, but …
-
-Bert: I am in favor of the quick fix, it restores consistency in the way node does things. practically speaking, almost all fs are going to be utf-8. it fixes the problem where fs.watch tells you “hey a file changed” but you go to look and the file’s not there due to the encoding scheme. I’d like to make a little improvement. the problem has been known since at least 2011, and we’ve never gotten around to it. I would not be surprised if it takes another 4 years for someone to take a stab at it.
-
-Brian: is it possible to get the user’s LOCALE and convert to that before sending it off?
-
-Ben: that’s worse than what we have now.
-
-James: the LOCALE often lies.
-
-Bert: are we going to land the patch to fs.watch? I’d like to have a quick references.
-
-Trevor: it’s not going to land in 5, we could leave it open until near v6 and land it then if no one is able to get around to the full fix. there’s 5-6 months between 5 and 6…
-
-Rod: that sounds like a nice compromise.
-
-### WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-
-Rod: I left this on because I thought it’d be nice to get a report from the WG on how it went.
-
-James: [cd: I am missing folk here]: Jeremiah, Eran Hammer, Doug Wilson, Myles Borins Brian White, Patrick Mueller, and myself.
-
-We talked about the charter. Looking into what improvements can be made to better support the ecosystem. Making existing impl hookable so that modules could swap out parts of the implementation with their own. Like replacing the parser, or header specific handling. The charter covers that aspect of it, but emphasizes that existing systems are not broken. We have a number of issues that we’ve created to start discussing these. I’ll get these into the doc.
-
-That’s the short version. Still really early to tell what all will come of it and what kind of schedule it’ll be on. 5th, at [cd: TIME?]
-We’ll be drawing up a charter and bringing it back to this group.
-
-Any other questions?
-
-Rod: could we get a report on the API WG?
-
-Trevor: the discussion was mainly around the native api. it went in a direction I wasn’t expecting. I explained my JS API proposal, then it went into a module discussion. ABI compat is straight out, it went in the direction of NAN (API compat, but occasional recompiles). Some discussion arose around abstracting node, like v8 completely. to replace with another VM. How do you handle specific difference like features that are available in one vm or another? or JS features that are/aren’t available between VMs. To target all vms, you end up having to use ES5. I was kind of losing where they were going with it. there are a lot of smart people. We’ll just have to have a discussion about feasibility.
-
-Ben: Was there any talk about who’s going to do the actual work?
-
-Trevor: No — it was more theoretical. It was more like the ES committee — develop features then say “go make these.” IF I bring it up I’m sure I can get some solid answers.
-
-Alexis: I’m trying to push for the Chakra folks to do some of this work.
-
-Mikeal: [cd: sorry, I missed this.]
-
-Rod: What companies are involved? Did MS show up?
-
-Trevor: Yes, I think so. JXCore, IBM was there, can’t remember offhand.
-
-Bert: JXCore is also secretly MS?
-
-Alexis: Not a secret! They’re on contract for an industrial IoT project.
-
-Alexis: IBM was there, Nodesource.
-
-Mikeal: Looking for someone from samsung’s jerryscript team to join.
-
-Trevor: My initial proposal was to get something usable. I’ll be out of there if it turns into WASM — if it blows up in size.
-
-Mikeal: The whole point is to be smaller than the current API, right?
-
-Bert: Well, not smaller, but … let’s not talk about technical issues
-
-Alexis: We’ve discussed multiple approaches, and we can tackle the problem from multiple sides. Trevor is tackling it by reducing the size of core. The approach I want to take is FFI interface into native modules. All of these approaches can help us tackle this huge beast into a manageable problem. They’re not competing solutions.
-
-Bert: We want to avoid scope creep. If the WG comes up with a HUGE proposal with 20 points of view, then no one will ever go do it.
-
-Trevor: I want to simplify the JS API, and get it to a point where all of the existing api can sit on top of it. If someone wants to do the work of replacing V8, they’ll have a clean entry point into the JS. And then write a set of compliance tests that specify what every entry point does. Writing a bunch for native code without JS tests to back it up would be futile.
-
-Bert: Restricting it to API design, that in theory, the sort of design goal, is for the API to be sufficient for Node to use.
-
-Alexis: This would include the native module api?
-
-Rod: It sounds like HTTP attacked charter first, maybe the API WG needs to do the same, to combat growth of scope. Maybe anyone else on this call that wants to could join and try to define scope? Is there another call scheduled, Trevor?
-
-Trevor: we’re still collecting times. I’ll mention the ctc in the issue.
-
-Rod: we should make a new @ctc GH group.
-
-Bert: which is going to be more fun?
-
-Rod: The CTC
-
-Bert: when are we going to split up?
-
-Rod: Mikeal is organizing another meeting.
-
-Mikeal: It’s tomorrow at this time slot.
-
-### node-gyp: Windows users are not happy. [node-gyp#629](https://github.com/nodejs/node-gyp/issues/629)
-
-
-Jeremiah: Do we want to talk about the windows issue?
-
-Rod?: it kind of contains all of the windows problems.
-
-Alexis: I was asking about guidance on this.
-
-Rod: there’s a strategy of giving folks a place to vent, keeping it from spilling over elsewhere. Without this issue, it might explode into a bunch more issues.
-
-Alexis: We’re working on a module build service. The other thing is that MS is going to release a smaller SKU of the compiler, that might be able to be included with node-gyp.
-
-Rod: Next visual studio is going to be shipping with clang.
-
-Trevor: Yes for AST stuff. [cd: might have gotten this wrong]
-
-Rod: Alexis, you should post in there, but I think it’s going to always catch folks googling for the problem. I’m not sure you can resolve it by closing or locking it. Folks will go there and not see a proper resolution.
-
-Mikeal: make sure there are issues for everything in the thread, then close and lock. Make sure there are resolutions (even if it’s “move hte conversation”).
-
-Rod: I’m happy for Alexis to take the lead on this.
-
-Rod: Maybe change the title to “Windows users are happy?”
-
-Alexis: Maybe change to “Unix users are unhappy.”
-
-Rod: that’d be an epic troll.
-
-## Next Meeting
-
-November 4, 2015
diff --git a/doc/ctc-meetings/2016-05-04.md b/doc/ctc-meetings/2016-05-04.md
deleted file mode 100644
index 3b5abb7ad98901..00000000000000
--- a/doc/ctc-meetings/2016-05-04.md
+++ /dev/null
@@ -1,192 +0,0 @@
-# Node Foundation CTC Meeting 2016-05-04
-
-## Links
-
-* **Audio Recording**: https://www.youtube.com/watch?v=3M95wsWs7qQ
-* **GitHub Issue**: https://github.com/nodejs/node/issues/6567
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1eP0HyB452ZmoMlljCXJNyWO-BZyhzo9j6kNn17sDCEg>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/16t1um6sXBlFZT2aCLqnlwumcEcM2K-_xeEFnnsA_rBQ>_
-
-## Present
-
-* Bradley Farias @bmeck (observer/modules EPS/GoDaddy)
-* Brian Terlson @bterlson (observer/modules EPS/tc39/Microsoft)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* James M Snell @jasnell (CTC)
-* Josh Gavant (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Rod Vagg @rvagg (CTC)
-* Seth Thompson (observer/Google)
-* Shigeki Ohtsu @shigeki (CTC)
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* Revert 5950 [#6537](https://github.com/nodejs/node/pull/6537)
-* src: refactor constants, deprecate require('constants') [#6534](https://github.com/nodejs/node/pull/6534)
-* doc: refactor the changelog by version [#6503](https://github.com/nodejs/node/pull/6503)
-* Request for discussion of https://github.com/dherman/defense-of-dot-js vs EPS on modules
-
-
-
-## Standup
-
-* Сковорода Никита Андреевич:
-    * Nothing too significant, some comments (as usual).
-
-* Colin Ihrig:
-    * A few PRs
-    * Reviewing issues and PRs
-
-* Evan Lucas:
-  * Submitted a doc and util pr.
-  * Working on a http bug.
-  * Been trying to help some packages get updated to work with v6.
-  * Left some comments on a few issues.
-  * Have been working on a commit validator tool.
-
-* Jeremiah Senkpiel:
-    * v6 Breaking changes doc
-    * working on v6.1.0 release
-    * assorted PRs, Issues, EPs -- done a bunch of reviews
-
-* James M Snell:
-  * v6 Release
-  * Fixed 2 util.inspect bugs (proxy and array length)
-  * Helped troubleshoot buffer indexOf/lastIndexOf bug
-  * Troubleshooting 5950 issues
-  * Work on error code refactoring
-  * Work on constants refactoring
-  * Work on changelog refactoring
-  * Ongoing http implementation security / spec compliance review
-  * Working on compliance follow ups from vm summit
-  * Investigating possible alternative solutions for stdout/stderr
-    non-blocking issues
-
-* Josh Gavant:
-  * Testing use of trace-event macros, designing tracing module, reviewing AsyncWrap and alternatives.
-
-* Michael Dawson:
-  * Investigated ppc be release machine issues
-  * validating be build from nightly release job
-  * AsyncWrap EP review
-  * switched benchmarking vof v6 over to new v6 branch
-  * wrote/submitted stable ABI module EP
-  * misc reviews/lands
-
-* Brian White:
-  * Worked on http server code refactor and other http performance improvements
-  * Reviewed PRs/issues
-
-* Rod Vagg:
-  * Time off, now catching up
-
-* Seth Thompson:
-  * continue to work on getting v8 inspector to work with node
-  * meeting with Ali as he.s visiting in person
-
-* Shigeki Ohtsu:
-    * Upgrading openssl and reviewing one PR for GCM IV
-
-* Steven R Loomis:
-    * turn/rebase/clean ci for https://github.com/nodejs/node/pull/6088 ( checkin ICU into master ) and https://github.com/nodejs/node/pull/4253 ( v8BreakIterator to throw error rather than fatal crash
-    * opened Doodle poll to get Intl WG going again (monthly) https://github.com/nodejs/Intl/issues/33
-
-* Trevor Norris:
-    * Don't abort on access of invalid pointer returned by Unwrap PR
-    * Tuning the AsyncWrap EP and writing patches as result
-
-* Rich Trott:
-  * Added undocumented-for-now -F flag to jslint.js to automatically fix lint issues. Dog-fooding it right now. Give it a shot if you.re brave.
-  * Open PR to have `known_issues` tests run via CI and `make test`. PTAL. https://github.com/nodejs/node/pull/6559
-  * Assessments for long-dormant issues.
-
-* Bradley Farias:
-  * Investigated counter proposal details to node EP for modules
-  * Started test framework for modules EP
-
-
-## Review of last meeting
-
-
-* governance: add new collaborators XII [#6282](https://github.com/nodejs/node/issues/6282)
-* doc: doc-only deprecation for util.log() [#6161](https://github.com/nodejs/node/pull/6161)
-* Check (small) ICU into repo [#6088](https://github.com/nodejs/node/pull/6088)
-* doc, tls: deprecate createSecurePair [#6063](https://github.com/nodejs/node/pull/6063)
-* Planning for v6 [#5766](https://github.com/nodejs/node/issues/5766)
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-* ES6 Modules detection update / https://github.com/nodejs/node-eps/issues/13
-
-
-## Minutes
-
-### Revert 5950 [#6537](https://github.com/nodejs/node/pull/6537)
-* James: Bug picked up in v6 for symlinked peer dependencies, our tests/CI didn.t pick it up unfortunately. Proposal is to revert the change and review it after adding some tests for this.
-* Rod: there was some discussion about a revert being semver major
-* Jeremiah: not optimal, reverting is technically a semver-major
-* Rod: does anyone have an objection to a revert at this stage?
-* Jeremiah: I believe some of the new behaviour was useful, is there a path to reintroducing it?
-* James: least invasive route would be to add the new behaviour behind a flag, there are some other approaches being investigated. The folks who proposed this change in the first place are behind the reversion at this stage.
-
-### Request for discussion of https://github.com/dherman/defense-of-dot-js vs EPS on modules
-
-
-* Bradley: we merged our proposal last week and afterward a counter-proposal (that we.ve been waiting on for many weeks) showed up. The proposal is a package.json-based solution. It does address all of the major use-cases of Node and it does this in slightly different ways than we.ve seen before. It.s still lacking some existing behaviour of CJS files (you can.t detect some filepaths for CJS), e.g. ~/.config.js. It introduces a path-expansion mechanism. You add a module.root to your package.json. I still have concerns about this but it.s much better than the previous ones based on package.json. I.ll be having a more in-depth conversation with Brian Terlson (TC39/Microsoft), if anyone wants to join.
-* Jeremiah: is the main downside of the file extension about sharing files from servers that aren.t configured for it?
-* Bradley: yes, the main concern is about firewalls and configs that block transmission of the new files.
-* Rod: can you help us empathise with the sentimentality around the file extension, are there objective problems that we are not picking up on?
-* Bradley: there.s a concern . _something about a lodash example_ . shell scripts not finding the new files with *.js.
-* Brian Terlson: there.s an expectation that JavaScript is contained in a .js file and we.re in a nice place now that this is true with some minor exceptions. For TypeScript we.d have to add a .mts and .mtsx extension.
-* Rod: _asking about the sentimentality again_
-* Brian Terlson: that.s a mischaracterisation of the defense of .js proposal
-* Jeremiah: there will be developer friction either way
-* Brian Terlson: but friction will be limited to node developers as opposed to all javascript developers
-* Rod: what state is standard ?
-* Bradley: Some pieces still have minor changes going on but mostly locked down.
-* Brian Terlson: we have been thinking about all of these kinds of things during the whole process. I don.t think spec changes are off the table, TC39 could reconsider some aspects of the spec to improve matters. No promises, but don.t feel like you shouldn.t bring it up because we.re so late in process.
-* Bradley: forward detection is the main problem. Have examples of specifics.  As long as implicit strict mode is enforced we are going to have a hard time.
-Rod: what.s the path forward ? On our side seems like strong preference is still on the file extension side.
-* Bradley: Either way was ecosystem effects. Personally towards file extensions, most response on social media is either .better than nothing. or .don.t like file extension but not pushing for package.json either..  Will discuss further with Brian and others from Microsoft.
-* Rod: EP does not mean it is final, but it does mean it is the preferred way forward and CTC members would have to be convinced otherwise.
-* Bradley: likely need longer discussion in next week or so either way.
-
-
-### src: refactor constants, deprecate require('constants') [#6534](https://github.com/nodejs/node/pull/6534)
-* James: recent PR asking to add new constant.  They are mentioned in the docs in a few places, but not well documented.  Figured should take a run at documenting and refactoring to make it make more sense. Cleans up the structure and properly documents.  Would it be semver major since we have never documented before ?
-* Jeremiah: marked as semver major because it was deprecating existing constants.
-* James: hard deprecation pretty much blows up everything as npm uses them ,etc. Thats why it is a soft deprecation.
-* Jerimiah: we should find way to document
-* James: add to release notes saying to use the new versions.
-* Rich: Move discussion back to github
-* Rod: Any objection to doing this, want consensus before we spend a lot of time doing it.
-
-
-### doc: refactor the changelog by version [#6503](https://github.com/nodejs/node/pull/6503)
-
-* James: changelog grew to point where it is no longer visible/usable on github.  To make it at least visible it was temporarily split out into an archive.  This PR is to split it out by version instead.  Each version release would link to the individual version change log.  One at top level becomes an index to the version specific ones.  Acceptable or do we need another approach?  Archive for io.js release and before v.10.  Should not add too much additional work to release process.
-* Rod: maybe io.js ones should be in separate files as well instead archive.
-* Jeremiah: io.js v1 has particularly large set of changes
-* James: any major objections ?
-* Rod: take it back to github, roll forward unless objections on github.
-
-### Q/A on public fora
-* call for questions on public channels.
-* no existing ones so far.
-* will wait a few minutes to see if any come in
-* ok moving on.
-
-
-## Next Meeting
-
-2016-05-11
diff --git a/doc/ctc-meetings/2016-06-15.md b/doc/ctc-meetings/2016-06-15.md
deleted file mode 100644
index 87fc0dc243d3a2..00000000000000
--- a/doc/ctc-meetings/2016-06-15.md
+++ /dev/null
@@ -1,174 +0,0 @@
-# Node Foundation CTC Meeting 2016-06-15
-
-## Links
-
-* **Audio Recording**: https://www.youtube.com/watch?v=qWX8i9SKatQ
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7307
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1e7JdFHVtMtW9_o0Gi3NNz6g7TK50q4u9LYKFzBeHOQ8>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1G_sywyzJFPDzLv-KiG21L_4cIAP9_awQnP00ox8Nyiw>_
-
-## Present
-
-* Bradley Meck @bmeck (observer/GoDaddy)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Chris Dickinson @chrisdickinson (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* John-David Dalton @jdalton (observer/Microsoft)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Alexis Campailla @orangemocha (CTC)
-* Rod Vagg @rvagg (CTC)
-* Rich Trott @Trott (CTC)
-* Trevor Norris @trevnorris (CTC)
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* url: return valid file: urls fom url.format() [#7234](https://github.com/nodejs/node/pull/7234)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-### Standup
-
-* Bradley Meck @bmeck
-    * fleshing out a proposal for if we could disambiguate the grammars for Script and Module.
-
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-    * some issue/PRs reviews
-
-* Chris Dickinson @chrisdickinson (CTC)
-      * NodeConf
-      * modules.guide
-
-* Evan Lucas @evanlucas (CTC)
-    * Preparing for security release
-
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-    * (Previous week: fixed the primary OS X stdio bug)
-    * NodeConf
-
-* Fedor Indutny @indutny (CTC)
-    * fixing bugs, reviewing PRs, working on llnode
-
-* Josh Gavant @joshgav
-    * debug protocol stuff
-
-* Michael Dawson @mhdawson (CTC)
-    * Still chasing PPC machine issues
-    * AIX/malloc(0) issue
-    * ABI stable module API work with Stefan/Ian, filling in Nan examples
-    * Input on some benchmarking related PRs
-    * Other misc reviews/lands
-    * Keeping up with issues
-
-* Brian White @mscdex (CTC)
-	* Landed some old PRs
-    * Submitting PRs to fix some regressions
-    * Reviewed PRs and issues
-
-* Ali Ijaz Sheikh @ofrobots (CTC)
-    * More work on v8_inspector
-    * Starting to look at backporting some V8 fixes for LTS
-
-* Alexis Campailla @orangemocha (CTC)
-    * Landed a fix for node-gyp, broke with VS update 3
-
-* Rod Vagg @rvagg (CTC)
-    * Alpine Linux in CI
-    * Security release hoo haa
-    * Reviews & discussions
-    * Electron / Node relationship
-    * New CTC repo
-    * Jenkins upkeep
-
-* Rich Trott @Trott (CTC)
-    * Setting up the next onboarding
-    * Facilitated a session on releases at NodeConf. Will share notes with Build WG, LTS WG, and people who can sign releases.
-
-* Trevor Norris @trevnorris (CTC)
-    * Finished updating AsyncWrap EP and now investigating proposed implementation.
-    * Helping identify old issue in Atom editor in regards to writing to disk.
-
-
-### Review of last meeting
-* Tracking issue: stdio problems [#6980](https://github.com/nodejs/node/issues/6980)
-* module: expose `Module._runInThisContext` [#6288](https://github.com/nodejs/node/pull/6288)
-
-
-## Minutes
-
-
-### url: return valid file: urls from url.format() [#7234](https://github.com/nodejs/node/pull/7234)
-
-@trott: semver-major change, needs approval from CTC.
-Real fix will be @jasnell’s HTTP compliance work.
-
-In browsers `file:/home/joshgav/myfile.txt` is auto-corrected to `file:///home/joshgav/myfile.txt` (i.e. slashes are prepended to the path and hostname is an empty string). This change institutes the same in Node.js.
-
-Are there other protocols which require additional slashes (`//`) if hostname isn’t specified? Yes, but hard to heuristically determine if needed.
-
-
-### http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-Replace headers object ({}) in req/res with StorageObject, which doesn’t delegate to Object.prototype. But this will break anyone using regular `Object` methods on header props.
-
-@trevnorris: Why don’t we intercept calls to properties with checks to an internal dictionary of actual headers? If the key isn’t there, then try to call Object.prototype.
-
-How would that effect perf?
-
-It’s the right decision because otherwise can’t use headers with certain names like `__proto__`.
-
-Better to do a deprecation cycle. How? Insert something (proxy) between actual call to property, would issue deprecation warning first. This would be temporary, eventually this interceptor/proxy would go away.
-
-
-### ES6 Modules [node-eps/002-es6-modules.md](https://github.com/nodejs/node-eps/blob/master/002-es6-modules.md)
-
-Need to disambiguate ES6 modules and regular scripts (which include CJS modules). Cannot determine if file is module, script, etc. from code itself. For this reason Node decided to use `.mjs` extension for ES6 modules.
-
-New proposal: If `import` or `export` keywords are in module code, then use module goal. So no need for extra metadata or file extension. But would have to parse file to check for presence of these keywords.
-
-https://github.com/bmeck/UnambiguousJavaScriptGrammar
-replaces https://github.com/nodejs/node-eps/blob/master/002-es6-modules.md#51-determining-if-source-is-an-es-module
-
-This would be part of ECMA262 so browsers would do the same, but needs to be ironed out in TC39. On [agenda][TC39 Agenda] for 7/26 TC39 meeting.
-
-[TC39 Agenda]: https://github.com/tc39/agendas/blob/master/2016/07.md
-
-What if nothing is imported or exported? Could do `export default null` to export nothing.
-
-Starting off, preferred goal when preparing code would be CommonJS/script, later on could change to ES6/module.
-
-Caching is more feasible.
-
-Provides more seamless flow from CJS to ES6 in the future.
-
-Will packaging tools need to implement parsing logic too to package properly? Yes, but there are possibilities listed in the repo.
-
-What other differences between scripts and modules?
-- `await` keyword only in modules according to ECMA262
-- `modules.root` in package.json is intended to allow mirrored directory structure for use with ES6; but technically all it does is redirect file system calls and it could be used for other purposes, so it’s not reliable.
-
-Purpose of modules.root - allows redirection within a module, e.g. `module/file.js` doesn’t necessarily resolve to `./file.js` within the directory, could be redirected to `${module.root}/file.js`. This allows side-by-side CJS and ES6 among other things.
-
-What about for human reading? How can people differentiate at a glance between CJS and ES6?
-- `import`’s are generally at the top, `export`s at the bottom. If you see `import` it’s an ES6 module.
-
-How are browsers dealing with this? Older browsers which encounter `<script type=”module”>` and don’t recognize the type will skip it. Loading is asynchronous by default.
-
-Are browsers concerned about transition period from CJS to ES6? How do they load older scripts, e.g. jQuery?
-
-**Should Node move this forward as alternative to `.mjs` proposal?**
-
-TBD. What does TC39 think of this? It’s on agenda for next F2F (see above).
-
-
-### Q/A on public fora
-None.
-
-## Next Meeting
-2016-06-22
diff --git a/doc/ctc-meetings/2016-06-22.md b/doc/ctc-meetings/2016-06-22.md
deleted file mode 100644
index 9e87b13b539fb3..00000000000000
--- a/doc/ctc-meetings/2016-06-22.md
+++ /dev/null
@@ -1,151 +0,0 @@
-# Node Foundation CTC Meeting 2016-06-22
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7366
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1X9PTcpYgTKJO-PRKOLBrL4fIV-7XDR0x71FAxJWn0II>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1e7JdFHVtMtW9_o0Gi3NNz6g7TK50q4u9LYKFzBeHOQ8>_
-
-## Present
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Chris Dickinson @chrisdickinson (CTC)
-* Evan Lucas @evanlucas (CTC)
-* James M Snell @jasnell (CTC)
-* John-David Dalton @jdalton (observer/Lodash/Microsoft)
-* Yuval Brik @jhamhader (observer)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Shigeki Ohtsu @shigeki (CTC)
-* Steven R. Loomis @srl295 (observer/IBM/ICU)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-
-## Standup
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-    * Need for APM / JIT Cache hooks investigation
-    * Investigation into VM support for V8 and ES Modules
-* Chris Dickinson @chrisdickinson (CTC)
-    * Keeping track of ES Modules proposals
-    * tooling gn to be npm installable
-* Evan Lucas @evanlucas (CTC)
-    * working on security fixes
-    * looking for ways to streamline landing commits
-* James M Snell @jasnell (CTC)
-    * Vacation last week (worked on an experimental http/2 impl)
-    * Working on WHATWG URL implementation
-    * Various other performance related and doc PRs
-    * And a heads up.. Will be on vacation again the 2nd and 3rd weeks of July.
-* John-David Dalton @jdalton (observer/Lodash/Microsoft)
-    * Retooled proposal to simplify it and make it more generic so it will work with things other than just script and module
-    * Babel now supports export {} and therefore supports Unambiguous Modules proposal
-    * Pinged some v8 devs to ask about impact there
-    * Met with TypeScript folks too to discuss things that are a bit out of the scope of Unambiguous JavaScript but still modules
-    * Initial round of feedback on Unambiguous JavaScript. Will be in JavaScript Weekly tomorrow.
-* Josh Gavant @joshgav (observer/Microsoft)
-    * hacking on inspector and tracing stuff
-    * es6 modules a bit
-    * monitoring issues, PRs, etc.
-* Michael Dawson @mhdawson (CTC)
-    * Chasing PPC machine issues
-    * Chasing new AIX machines (expect this month)
-    * Contributing to ABI stable module API PoC (NaN examples 1-8 now work)
-    * Misc reviews/commenting
-    * misc PRs/lands
-    * Keeping up with issues
-* Brian White @mscdex (CTC)
-    * Reviewing PRs/issues
-* Shigeki Ohtsu @shigeki (CTC)
-    * Reviewing just one PR for root cert update.
-* Steven R. Loomis @srl295 (observer/IBM/ICU)
-    * helping @jasnell (a little) with https://github.com/nodejs/node/pull/7355
-* Trevor Norris @trevnorris (CTC)
-    * Additional work on the AsyncWrap EP
-    * Misc PR reviews
-* Rich Trott @Trott (CTC)
-    * CO: Continuous Onboarding (welcome @RReverser!)
-    * CI: Investigating and fixing flaky tests as time allows
-* Ali Ijaz Sheikh @ofrobots(CTC)
-    * Working on FFI, and other miscellaneous things.
-
-
-## Minutes
-
-### Review of last meeting
-
-* url: return valid file: urls fom url.format() [#7234](https://github.com/nodejs/node/pull/7234)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-* ES6 Modules
-
-### fs.realpath
-
-- https://github.com/nodejs/node/issues/7175
-- https://github.com/nodejs/CTC/issues/9
-- https://github.com/nodejs/node/issues/7192
-- https://github.com/nodejs/node/issues/7044
-- https://github.com/nodejs/node/issues/7294
-
-When we made changes to rely on libuv realpath it was a semver-major change which introduced new errors and removed `cache` argument. This broke some ecosystem modules, notably `glob`. Also broke some path-related stuff in Windows.
-
-We chose libuv realpath because it’s much more performant.
-
-Options:
-- Revert to old behavior. Would lose perf gains. Would be semver-major change.
-- Add new method e.g. `realpath2` which uses old behavior.
-- **Keep new behavior and add logic in Node to handle new/unexpected errors.**
-
-@jasnell - We did a semver-major revert for the symlink issue.<br />
-@trevnorris - No need to revert, just handle the errors.<br />
-@jasnell - Do we really know what the errors are so we can be sure we’re handling all of them?<br />
-@trevnorris - we can compare to old impl.<br />
-@jasnell - Add an option to the options object to suppress errors, turn on by default.<br />
-
-**@trevnorris will work on option 3.**
-
-Post-mortem: https://github.com/nodejs/CTC/issues/9
-- Postpone till Rod is present.
-- @jasnell - We didn’t follow typical deprecation path for `cache` parameter change.
-
-
-### ES6 modules
-
-- https://github.com/bmeck/UnambiguousJavaScriptGrammar
-
-- Any code with `import` or `export` is a module, otherwise a script.
-- `modules.root` aspect removed, so “fat packages” (i.e. incl. both ES6 and CJS) are not addressed. Recommendation is to use one or the other and transpile as needed. Or discuss `modules.root` separately.
-- Users can explicitly specify module goal in package.json. This way even if dev removes all `import/export` from their code it’s still treated as a module.
-- TC39 could provide a “recommendation” or endorsement supporting this. They may suggest a spec extension.
-
-@bradleymeck - still need modules.root for fat packages.
-
-What about bytecode caching? Provide hooks to allow user to handle as desired. That means caching is in userland. Might split this into separate proposal.
-
-@trevnorris analyzed perf hit of double parsing and found max 25% perf hit.
-
-In-band detection (from the code itself) is preferable to out-of-band detections (e.g. package.json, file extension).
-
-CJS and ES6 semantic interoperability: Bradley is working on this, working with WHATWG Loader spec and V8.
-- `this` value
-- live bindings for getters (get updated values) (?)
-- immutability - hooks for APM providers to wrap original functions. To be handled by WHATWG Loader spec.
-
-**@jdalton - How do we finalize consensus on this?**
-- **PR to change [node-eps:/002-es6-modules.md](https://github.com/nodejs/node-eps/blob/master/002-es6-modules.md)**
-
-### Q/A on public fora
-None.
-
-### Next Meeting
-2016-06-29
diff --git a/doc/ctc-meetings/2016-06-29.md b/doc/ctc-meetings/2016-06-29.md
deleted file mode 100644
index 859cdc1df27c59..00000000000000
--- a/doc/ctc-meetings/2016-06-29.md
+++ /dev/null
@@ -1,187 +0,0 @@
-# Node Foundation CTC Meeting 2016-06-29
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7474
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1a19l2ICQHCw2w6cM4AayRM8QX8cIrgnHXCtzmuxfWuM>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1X9PTcpYgTKJO-PRKOLBrL4fIV-7XDR0x71FAxJWn0II>_
-
-## Present
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* James M Snell @jasnell (CTC)
-* John-David Dalton @jdalton (observer/Lodash/Microsoft)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Rod Vagg @rvagg (CTC)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* New Buffer API backport to v4.x [#7475](https://github.com/nodejs/node/pull/7475)
-* child_process: validate fork/execFile arguments [#7399](https://github.com/nodejs/node/pull/7399)
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-* repl: Default `useGlobal` to false in CLI REPL. [#5703](https://github.com/nodejs/node/pull/5703)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-### nodejs/LTS
-
-* Mention odd-number release has eight months support as Current. [#113](https://github.com/nodejs/LTS/issues/113)
-
-### nodejs/node-eps
-
-* AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-## Standup
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Trying to gather all stakeholders in ES Module implementations into a meeting
-  * Back and forth with V8 about details of CJS bridge
-* John-David Dalton @jdalton (observer/Lodash/Microsoft)
-  * Dropped caching from unambiguous JS proposal
-  * PR to Node EPS repo
-  * Discussed with V8 (Adam Klein) and Chakra about adding the API, no blockers
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Filed #7475 to backport new Buffer API to 4.x LTS
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewing issues and PRs. Made a couple libuv PRs.
-* Evan Lucas @evanlucas (CTC)
-  * Merged pr to allow passing prompt to readline
-  * Merged pr that prints experimental warning when using inspector
-  * Worked on v6.x branch a little
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Was away a bit adjusting to Europe.
-  * Misc PRs/Issues work.
-  * Also working to resolve https://github.com/nodejs/node/issues/5426 (ages old timers issue)
-* Josh Gavant @joshgav (observer/Microsoft)
-  * Scheduled next Diag WG meeting (7/13 12 Pacific) (https://github.com/nodejs/diagnostics/issues/60)
-  * “Inspector Gateway” proposal (https://github.com/nodejs/node/issues/7393)
-  * Module discussions
-* Michael Dawson @mhdawson (CTC)
-  * Testing problematic PPC machine after move to new node, adding back to regular CI runs
-  * Working on ABI stable API prototype with Ian/Sampson
-  * Post mortem work with Richard C
-  * Misc PR reviews/lands
-  * Adding linuxOne to master test jobs in CI (since 5.1 landed there)
-  * LTS, Build WG meetings
-  * Starting to work on presentations for upcoming conferences
-* Brian White @mscdex (CTC)
-  * Landed a fix for a StringDecoder regression
-  * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Busy with non-Node stuff mostly.
-* Rod Vagg @rvagg (CTC)
-  * Chat with Electron team
-  * Foundation board meeting
-  * npm publish bug hunt
-  * node-gyp release, fix for latest MSVS 2015 release
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-  * regrets for this meeting- nothing to add at this point(hopefully soon)
-* Trevor Norris @trevnorris (CTC)
-  * working on solution for user API for AsyncWrap (?)
-* Rich Trott @Trott (CTC)
-  * child_process fixes
-  * examining https://node-core-coverage.addaleax.net/ results (thanks, @addaleax!)
-  * re-certifying flaky tests
-
-## Minutes
-
-### child_process: validate fork/execFile arguments [#7399](https://github.com/nodejs/node/pull/7399)
-
-@trott: Semver-major change requires review.
-
-@trott: fixing a bug that James filed some time ago - if nonsensical arguments are passed to these methods they silently ignore those arguments. Rich and James think it should throw if you give it garbage.
-
-@nodejs/ctc: No objections.
-
-### Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-
-@trevnorris was to work on capturing new errors and handling them. Discovered that all fs methods suffer same issue. Trevor has idea on how to handle it, will submit PR in the next day or two.
-
-@bzoz understands Windows issues and will address them.
-
-### buffer: backport --zero-fill-buffers command line option [#5745](https://github.com/nodejs/node/pull/5745)
-
-See also [#7475](https://github.com/nodejs/node/pull/7475).
-
-Backport to v4. Was discussed and CTC thought it wasn’t a good idea, but want to revisit now. What was previous issue? @Fishrock123 - another change, possibly security-related, blocked it.
-
-@rvagg: Same objections as backport to 0.12, should be treated the same.
-
-@nodejs/ctc: No objections currently. This is relevant to security.
-
-### repl: Default `useGlobal` to false in CLI REPL. [#5703](https://github.com/nodejs/node/pull/5703)
-
-* Some discussion in the original issue: https://github.com/nodejs/node/issues/5659#issuecomment-195543607
-* Moving back to GitHub.
-
-### Mention odd-number release has eight months support as Current. [lts#113](https://github.com/nodejs/LTS/issues/113)
-
-* Current state is that Current (formerly Stable) branch is supported for **two** months after next release but some people think it’s **three** months. For example, v5 is supported till end of June 2016. But we’d like this to be stated clearly.
-
-@mhdawson: discussion in last LTS meeting but it’s not in the scope of the LTS WG’s work so it’s up to the CTC. Is it Current+2 or Current+3?
-
-@nodejs/ctc: Previous Current version is supported for two months after next version is released.
-
-@rvagg: v5 is still heavily used.
-
-@Fishrock123: npm metrics also show high usage of v5, not much decline.
-
-Need to make clear that people need to upgrade. Should we push this harder or adjust to usage pattern?
-
-@nodejs/ctc: Stick with plan to stop supporting v5 shortly.
-
-Metrics: https://nodejs.org/metrics/summaries/version.png
-
-
-### AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-
-@Fishrock123 - responses have been primarily positive, time for CTC to consider.
-
-@rvagg - Goal is to raise awareness amongst CTC today, vote on it next week.
-
-@rvagg - currently marked as experimental. We should associate a message/warning with experimental API usage. EPs are for experimental APIs.
-
-@trevnorris - AsyncWrap cannot track callbacks from native addons. Also investigating why sometimes messages are dropped (?).
-
-### replace section 5.1 with unambiguous JavaScript grammar  [node-eps#33](https://github.com/nodejs/node-eps/pull/33)
-
-@jdalton wants to get agreement from Node.js CTC so that he can proceed to browser vendors.
-
-TC39 may want to add other “goals” for files in addition to module and script such as asm.js, “frozen realms”.
-
-@rvagg: If we go with `.mjs` we’d have to have extensions for new parse goals too...
-
-@rvagg: We prefer a spec change in TC39/ES262 or an acknowledgement at least. @jdalton will add that caveat into the PR.
-
-@Fishrock123: What about avoiding double parsing?
-@bmeck: Chakra said maybe, V8 said probably not. @trevnorris did benchmarks and they weren’t too bad.
-
-`module.root` for fat packages? With .mjs it wasn’t needed, people would include .js and .mjs files; but with new proposal it is needed. However `module.root` isn’t foolproof because people could use it for general redirection/hiding of package internals instead of only for ES6 modules.
-
-@rvagg: Let’s slate for vote on Wednesday 7/6, those who are unavailable can vote in the issues.
-
-## Q/A on public fora
-
-None.
-
-## Next Meeting
-
-* AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-* replace section 5.1 with unambiguous JavaScript grammar.
-[node-eps#33](https://github.com/nodejs/node-eps/pull/33)
-
-CTC: 2016-07-06
diff --git a/doc/ctc-meetings/2016-07-06.md b/doc/ctc-meetings/2016-07-06.md
deleted file mode 100644
index 232b83b9c7d6bf..00000000000000
--- a/doc/ctc-meetings/2016-07-06.md
+++ /dev/null
@@ -1,150 +0,0 @@
-# Node Foundation CTC Meeting 2016-07-06
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7558
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1NWIKwYxDTApvc9Xbq5JTMorRPKIBuBKAA0zcjm8K_II>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1a19l2ICQHCw2w6cM4AayRM8QX8cIrgnHXCtzmuxfWuM>_
-
-## Present
-
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* James Snell @jasnell (CTC)
-* John-David Dalton @jdalton (observer/Microsoft)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Alexis Campailla @orangemocha (CTC)
-* Shigeki Ohtsu @shigeki (CTC)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-    * Nothing significant.
-* Colin Ihrig @cjihrig (CTC)
-    * Reviewed issues. Reviewed pull requests. Opened a couple PRs
-* Evan Lucas @evanlucas (CTC)
-    * Commented on a few issues, not much else
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-    * v6.3.0 Release, most difficult to date, lots of merge conflicts.
-    * Various PR / Issue review
-* John-David Dalton @jdalton (observer/Microsoft)
-    * Another round of questions with Chakra dev about Unambiguous JS Grammar confirming difficulty level of API is not significant
-    * Updated Unambiguous JS Grammar based on feedback
-* Josh Gavant @joshgav (observer/Microsoft)
-    * Out for July 4th holiday.
-* Michael Dawson @mhdawson (CTC)
-    * Added linuxOne to regression tests/watched for issues, all looks good, next step is to add to nightly releases
-    * Chasing down AIX build breaks test failures
-    * Continued work on ABI stable module API and scheduling of next WG meeting
-    * misc PR/Issue reviews/pull requests
-    * post-mortem work and scheduling of next meeting
-    * small update to benchmark graphs
-    * keeping up to date with issues
-* Brian White @mscdex (CTC)
-    * Started the process of rebasing the old js http parser onto master to see how it compares to the current http implementation
-    * Reviewed PRs, commented on issues
-* Alexis Campailla @orangemocha (CTC)
-    * Nothing to report (was out on vacation)
-* Shigeki Ohtsu @shigeki (CTC)
-    * Reviewed only one PR for crypto doc
-* Trevor Norris @trevnorris (CTC)
-    * Updated AsyncWrap EP
-    * fs.realpath() deep symlink PR
-* Rich Trott @Trott (CTC)
-    * Onboarded @bzoz
-    * Fixing test-net-write-slow on FreeBSD (PR #7555)
-* James M Snell @jasnell (CTC)
-    * WHATWG http implementation
-    * Closing up other business before going on vacation for a week
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484)
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-
-### nodejs/node-eps
-
-* Replace section 5.1 with unambiguous JavaScript grammar. [#33](https://github.com/nodejs/node-eps/pull/33)
-* AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-## Previous Meeting
-
-* New Buffer API backport to v4.x [#7475](https://github.com/nodejs/node/pull/7475)
-
-    * New PR: https://github.com/nodejs/node/pull/7562
-
-* child_process: validate fork/execFile arguments [#7399](https://github.com/nodejs/node/pull/7399)
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-* repl: Default `useGlobal` to false in CLI REPL. [#5703](https://github.com/nodejs/node/pull/5703)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-* Mention odd-number release has eight months support as Current. [#113](https://github.com/nodejs/LTS/issues/113)
-* AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-## Minutes
-
-### build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484) (@jasnell)
-
-Consider v6 and v7 separately. All agree on moving to VS 2015 for v7. Only question is v6 prior to LTS. We need more info to make decision on v6.
-
-If we stay with 2013 for v6 we’ll have to support it for the entire lifetime of v6 LTS. But it needs to still be possible to build native addons with 2013.
-
-@jasnell - Our recommendation is to build native addons with VS 2015 unless it doesn’t work (e.g. in [node-sass#1283](https://github.com/sass/node-sass/issues/1283).
-
-@orangemocha - No problem building `node.exe` with VS 2015 in v7. But dropping support for 2013 would break some modules (breaking change) due to ABI incompatibilities, so it might not be appropriate for v6. Need more time to assess impact.
-
-### Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-
-@trevnorris - fix is working, test in development. Comment further in the PR.
-
-### Replace section 5.1 with unambiguous JavaScript grammar. [#33](https://github.com/nodejs/node-eps/pull/33)
-
-@jdalton added line stating explicitly that the .mjs proposal is still possible.
-
-Vote taken in favor of merging this PR. Alexis officially abstained.
-
-### AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-See also [#7565](https://github.com/nodejs/node/issues/7565), which questions whether AsyncWrap should exist (from @bnoordhuis).
-
-@jasnell - Error handling should be addressed.
-
-@trott - A vote for the EP means “*if* we implement, this is what the JavaScript API will look like” and not necessarily “we intend to implement this.”
-
-@trevnorris - Correct. Confirm the API, then more work is needed on implementation, e.g. to include info on promises.
-
-@trevnorris - biggest missing chunk is public C++ API. Trouble is that it requires exposing some things which are not currently in public headers.
-
-@trevnorris - Goal is to include this as experimental in v6 before LTS. But still waiting on additional hooks into promises from V8.
-
-@Fishrock123 - AsyncWrap is best bet for CLS across async activities, replaces deprecated domains.
-
-Vote: 7-8 ayes, 0 opposed, 0 abstentions.
-
-
-## Q/A on public fora
-
-None.
-
-## Next Meeting
-
-* Move to VS 2015 for release build in v6? Is this a breaking change?
-
-## Upcoming TLP & WG Meetings
-
-* CTC: 2016-07-13
-* TSC: 2016-07-14
-* Diagnostics: 2016-07-13
-* Post-Mortem: [nodejs/post-mortem#31](https://github.com/nodejs/post-mortem/issues/31)
-* LTS:
-* Build:
diff --git a/doc/ctc-meetings/2016-07-13.md b/doc/ctc-meetings/2016-07-13.md
deleted file mode 100644
index 0c38f3b066a13a..00000000000000
--- a/doc/ctc-meetings/2016-07-13.md
+++ /dev/null
@@ -1,236 +0,0 @@
-# Node Foundation CTC Meeting 2016-07-13
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7707
-* [Minutes Google Doc](https://docs.google.com/document/d/1fP9_ZNcPoFh2VWCgUFu9-rDiDcMP88vhCC_oX6Aj528)
-* _[Previous Minutes Google Doc](https://docs.google.com/document/d/1NWIKwYxDTApvc9Xbq5JTMorRPKIBuBKAA0zcjm8K_II)_
-
-## Present
-
-* Anna Henningsen @addaleax (observer)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Ben Noordhuis @bnoordhuis (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Fedor Indutny @indutny (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Alexis Campailla @orangemocha (CTC)
-* Rod Vagg @rvagg (CTC)
-* Stephen Loomis @srl295 (observer/ICU)
-* Myles Borins @TheAlphaNerd (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (observer)
-  * PRs & issues
-  * Some v4.x backports
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Bad news from V8/Chakra. Can’t do property hoisting for Babel like CJS interop.
-  * Figuring out hooks for creating Modules in older Node versions
-* Ben Noordhuis @bnoordhuis (CTC)
-  * Back-porting patches
-  * Moving stuff over from malloc() to new[] because of AIX
-  * ABI compatibility tool
-  * PRs & issues, of course - how could I forget?
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewed issues and PRs
-  * Opened a few PRs
-* Evan Lucas @evanlucas (CTC)
-  * Simple doc fix
-  * Working on cherry-picking into v6.x
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Fixed a TTY test that was silently failing for over a year
-  * misc PR & issue work
-* Fedor Indutny @indutny (CTC)
-  * Various GYP-related tooling
-  * Code reviews, and fixing issues
-* Josh Gavant @joshgav (observer/Microsoft)
-  * Diagnostics WG meeting
-  * debugging docs
-* Michael Dawson @mhdawson (CTC)
-  * Added LinuxOne to v8 tests in CI
-  * Involvement on some AIX issues
-  * Working on ABI stable API, API WG meeting this week
-  * Re-scheduled post-mortem WG meeting for next week, LTS and diagnostic WG meetings
-  * misc reviews/lands and keeping up on issues
-* Brian White @mscdex (CTC)
-  * Worked on PR to check for accidental git conflict markers when linting in CI
-  * Backported some commits to v4.x
-  * Reviewed PRs and commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Back from vacation, buried in email (sorry for late responses!)
-* Alexis Campailla @orangemocha (CTC)
-  * Investigating ABI incompatibilities. Preparing to drop VS 2013.
-  * Reviewed miscellaneous Windows issues.
-  * Resumed work on a PR for case normalization of the module cache on Windows
-* Rod Vagg @rvagg (CTC)
-  * LTS README rework
-* Steven Loomis @srl295 (observer/ICU)
-  * not much here, just trying to keep an eye on issues/PRs
-* Myles Borins @TheAlphaNerd (observer)
-  * Working on v4.5.0 release https://github.com/nodejs/node/pull/7688
-  * CITGM Enhancements (XML + Queue)
-  * Working with V8 team to improve workflow for managing floated commits https://github.com/nodejs/LTS/issues/111
-* Trevor Norris @trevnorris (CTC)
-  * Working fix for one of the realpath bugs
-  * Backporting for v4.x
-  * Working on AsyncWrap implementation details
-* Rich Trott @Trott (CTC)
-  * Trying to handle flaky test outbreak on FreeBSD in CI
-  * Various ESLint updates/improvements
-  * Banging my head against test-tick-processor flakiness which is easily the longest-standing flaky test.
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/pull/7484)
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/pull/7175)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-
-## Previous Meeting
-
-### build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484) (@jasnell)
-
-To be discussed again.
-
-### Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-
-@trevnorris was to complete changes, to be discussed again.
-
-### Replace section 5.1 with unambiguous JavaScript grammar. [#33](https://github.com/nodejs/node-eps/pull/33)
-
-@jdalton’s proposal was merged.
-
-### AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-API was accepted, implementation TBD before October.
-
-
-## Minutes
-
-### build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484)
-
-@orangemocha: Decision to drop in v7 isn’t controversial. Will need to add tests for modules compiled with 2013 used with Node compiled with 2015.
-
-@orangemocha: Main question is switching in v6 before LTS. Is it a breaking change?
-
-Issue with node-sass module only comes up on Windows XP so can be discounted.
-
-No way to be sure if user modules compiled with 2013 might be incompatible with Node compiled with 2015. Have to run tests. Will CITGM provide sufficient testing?
-
-@myles: may not be enough native modules in CITGM to provide confidence.
-
-@Fishrock123: be sure to also test on pre-gyp’ed modules.
-
-@orangemocha: we may never have complete confidence that this isn’t a breaking change, but node-sass is the only issue ever reported.
-
-@orangemocha: Should we support modules built with 2013 in v7?
-@rvagg: need to include that in tests.
-
-**Next steps**: Run tests with modules compiled with 2013 to see if there are issues. Keep on agenda for next week and check on progress.
-
-### Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/pull/7175)
-
-* ELOOP fix: https://github.com/nodejs/node/pull/7548
-* Windows PR: https://github.com/nodejs/node/pull/7559 (see also https://github.com/nodejs/node/issues/7192)
-
-ELOOP issue has been resolved. Windows problem being addressed in another PR. May have to use JS impl for Windows.
-
-@rvagg: If libuv can’t handle the realpath issue for Windows what should we do?
-
-@orangemocha: We’re using the JS impl for Windows.
-
-@trevnorris: we can use the libuv impl and defer to the JS impl if the libuv impl throws unexpectedly.
-
-@rvagg: should we just revert? How common is the case where this provides a speed-up?
-
-@trevnorris: keep both libuv and js impl for now.
-
-**Next steps**: All please review #7548 and #7559.
-
-### http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-@mscdex: Prevent clash of header names with properties inherited from Object (e.g., `__proto__`). An object with a null prototype is already being used for the same purpose in `querystring.parse` since v6 release.
-
-@mscdex: Some have suggested cherry-picking some methods from Object such as `toString`:
-
-  * So that object can be inspected.
-  * To ensure backward compatibility.
-
-@mscdex: An eventual goal may be to store headers in an ES6 Map instead of on a plain object, but that will change the API considerably.
-
-@evanlucas: we should follow what we did with query string parameters.
-
-@rvagg: first need to review as some opposition to that.
-
-**Next steps**: All review PR.
-
-### proposal: WHATWG URL standard implementation [node-eps#28](https://github.com/nodejs/node-eps/pull/28)
-
-@trevnorris: Some discussion about supporting unregistered schemes (e.g. `chrome://`). We should support them, Chrome supports them.
-
-@trevnorris: `url.parse` can handle incomplete URLs (e.g. no scheme).
-
-@rvagg: Most important question is should `URL` be a global? There would be a `url` module and a different `URL` global.
-
-@fishrock123: there would be a transition period and then functionality would be in `URL`
-
-@rvagg: new impl is quite different from existing `url` module. Would like to see a diff. Migration will be difficult.
-
-**Next steps**: Waiting for @jasnell to return. Review again next week.
-
-### v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-@thealphanerd:
-
-* Would like to include libuv v1.9.1.
-* Would like very extensive testing prior to release to exclude breaking changes.
-
-How can we best test?
-
-@rvagg: Promote the RC on social media.
-
-@thealphanerd: npm could help test, Myles will reach out.
-
-@rvagg: Heroku? (Hunter Loftis) Travis CI? Probably not because it depends on nvm which doesn’t do RC’s yet.
-
-@thealphanerd: will talk with @ljharb about nvm support for RCs.
-
-**Next steps**: @thealphanerd will ping all to test RC.
-
-### ES Modules update
-
-@bmeck: named imports from CJS modules (e.g. `import {use, route} from "express"` or `import {readFile, readFileSync} from "fs"`) can’t work.
-
-Updates to come on the topic via: https://github.com/nodejs/node-eps/issues/26
-
-## Q/A on public fora
-
-## Upcoming Meetings
-
-* CTC: 2016-07-20
-* TSC: 2016-07-14
-* Diagnostics: 2016-08-03
-* Post-Mortem: 2016-07-18
-* API: 2016-07-14
-* LTS: 2016-07-25
-* Build: 2016-07-19
diff --git a/doc/ctc-meetings/2016-07-20.md b/doc/ctc-meetings/2016-07-20.md
deleted file mode 100644
index 02f16ae2ac24ca..00000000000000
--- a/doc/ctc-meetings/2016-07-20.md
+++ /dev/null
@@ -1,202 +0,0 @@
-# Node Foundation CTC Meeting 2016-07-20
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7809
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1Gr1XX-DuzgGXON5uAzrZHjWwXoQ4AIJEAJ2DK5jNmp4>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1fP9_ZNcPoFh2VWCgUFu9-rDiDcMP88vhCC_oX6Aj528>_
-
-## Present
-
-* Anna Henningsen @addaleax (observer)
-* Ben Noordhuis @bnoordhuis (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Julien Gilli @misterdjules (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Alexis Campailla @orangemocha (CTC)
-* Rod Vagg @rvagg (CTC)
-* Seth Thompson @s3ththompson (observer/Google)
-* Shigeki Ohtsu @shigeki (CTC)
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-* Myles Borins @TheAlphaNerd (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (observer)
-  * Issues & PRs
-  * looking into porting JS-based realpath to C
-* Ben Noordhuis @bnoordhuis (CTC)
-  * The usual (PR review and comment)
-  * Updating code base to do less manual memory management. PR coming soon.
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Some initial work on docs linting.
-  * Some comments on issues and PRs.
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewed issues and PRs
-  * Opened PRs
-* Evan Lucas @evanlucas (CTC)
-  * working on v6.3.1 release
-  * working on repl bugfix
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Did some timers review for https://github.com/nodejs/node/commit/5aac4c42da104c30d8f701f1042d61c2f06b7e6c
-  * Clearing out some other old stuff I’ve assigned myself to
-* Josh Gavant @joshgav (observer/Microsoft)
-  * Internal Microsoft work.
-* Michael Dawson @mhdawson (CTC)
-  * Misc issues with PPC machines, added new PPC
-    machines from newer openstack
-  * Working with Ian/Sampson on ABI stable abi, status
-    update at API WG meeting
-  * Working with Richard/Howard on post-mortem activities,
-    post-mortem WG meeting this week.
-  * Misc reviews/lands
-  * Reading/keeping up/commenting on issues
-  * Getting ready for Node Summit talk.
-* Julien Gilli @misterdjules (CTC)
-  * Looking forward to getting more involved again
-  * Investigating timers bug. Looking for someone to mentor on it
-  * Reviewing and commenting on pull requests
-* Brian White @mscdex (CTC)
-  * Diving deep into reworking API docs
-  * Reviewing PRs, commenting on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * shepherding some V8 backports, v8_inspector license issue and roll
-* Alexis Campailla @orangemocha (CTC)
-  * Nothing to report.
-* Rod Vagg @rvagg (CTC)
-  * Usual administrative stuff, some build maintenance
-* Seth Thompson @s3ththompson (observer/Google)
-  * Setting priorities for the next quarter.
-  * Team is continuing work on v8_inspector.
-  * Migrating v8_inspector into V8 itself.
-* Shigeki Ohtsu @shigeki (CTC)
-  * Nothing special. Working internal jobs.
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-  * Nodesummit prep…
-* Myles Borins @TheAlphaNerd (observer)
-  * v4.5.0-rc.2 released
-  * Email sent to npm team
-* Trevor Norris @trevnorris (CTC)
-  * realpath fix
-* Rich Trott @Trott (CTC)
-  * CTC governance doc updates
-  * onboarded @andrasq, will set up something with @princejwesley next, open to other nominations for after that
-  * eliminating more flaky tests (IT NEVER ENDS!!!!11!!!)
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* [meta] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-## Previous Meeting
-
-* build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/pull/7484)
-
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/pull/7175)
-
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-## Minutes
-
-### [meta] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-
-@rvagg: some discussion of reversion to v5 behavior, i.e. JS implementation rather than libuv implementation.
-
-@trevnorris: looks like everybody’s leaning towards a full revert (or at least a partial revert). I don’t like this plan but will go along.
-
-@addaleax: Unfortunate to have to do full revert for *nix systems. But having alternate impl for Windows increases maintenance costs.
-
-As part of the new implementation, the `cache` parameter was removed from the method. It was created to improve perf for the JS impl but is considered less necessary since the native impl performs better anyway.
-
-Should we reinstate the `cache` parameter as part of the revert? Would this be a semver-major again? Does caching in the JS impl provide a significant perf benefit?
-
-@addaleax: Benchmarking fs perf will show how much benefit the caching capability in libuv provides.
-
-@mhdawson: we run two benchmarks nightly: one with caching and one without.
-
-@orangemocha: It seems okay to have two impl’s, one for Windows and one for *nix, increased maintenance surface isn’t a concern, libuv manages libuv impl.
-
-@rvagg: As we move v6 to LTS it would be best to have a known-good implementation. So would prefer a full revert, then fix libuv impl independently, then re-integrate.
-
-@thealphanerd: Could we provide both interfaces? Revert the primary one to original behavior and add a second one with libuv behavior?
-
-@rvagg: Still doesn’t address breaking change in Windows.
-
-@fishrock123: also in favor of reverting. This has been going on for a long time, best to revert and then fix.
-
-@orangemocha: should not compromise correctness for performance.
-
-@trevnorris: caching could be separated from fs API. For example, it could be part of `module` module.
-
-@rvagg: This is why I’m in favor of a full reversion. These other discussions may continue for a month and we need to correct problem now.
-
-@thealphanerd: do we have a list of the original bugs the libuv patch addressed?
-
-@saghul has a list.
-
-@rvagg: back to github for now.
-
-**Next steps**: continue discussion in GH.
-
-### v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-@thealphanerd is raising visibility for tests and feedback.
-
-@misterdjules may have some testers.
-
-### http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-@rvagg: Need choices to vote on.
-
-@ofrobots: Wants to explore more options including `map` so wait for vote. If the goal is to go to a map why don’t we do that now?
-
-@Fishrock123: Because community has taken dependencies on it being an object.
-
-@ofrobots: headers end up with “megamorphic IC’s” so wants to research further.
-
-@Fishrock123: We are fixing this because header names like `__proto__` conflict with default object properties.
-
-We should really just make an API for headers.
-
-@rvagg: We’ll come back to this next week. Prepare wording for vote if ready.
-
-**Next steps**: List available options and conduct vote next week.
-
-
-## Q/A on public fora
-
-None.
-
-## Upcoming Meetings
-
-* CTC: 2016-07-27
-* TSC: 2016-07-28
-* Build: 2016-08-07
-* LTS: 2016-07-25
-* Diagnostics: 2016-08-03
-* Post-Mortem: August
-* API: August
diff --git a/doc/ctc-meetings/2016-07-27.md b/doc/ctc-meetings/2016-07-27.md
deleted file mode 100644
index d0b19393865f5b..00000000000000
--- a/doc/ctc-meetings/2016-07-27.md
+++ /dev/null
@@ -1,237 +0,0 @@
-# Node Foundation CTC Meeting 2016-07-27
-
-## Links
-
-* **Audio Recording**: https://www.youtube.com/watch?v=QAufnqo4ElY
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7881
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1rHxRb-ImjwFPOCOapgRDLdhqr4LJvie7eDNPOnDu2UA>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1Gr1XX-DuzgGXON5uAzrZHjWwXoQ4AIJEAJ2DK5jNmp4>_
-
-## Present
-
-* Anna Henningsen @addaleax (observer)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Fedor Indutny @indutny (CTC)
-* James M Snell @jasnell (CTC)
-* Julien Gilli @misterdjules (CTC)
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-* Brian White @mscdex (CTC)
-* Alexis Campailla @orangemocha (CTC)
-* Rod Vagg @rvagg (CTC)
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-* William Kapke @williamkapke (observer)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (observer)
-    * Issues & PRs
-    * Some realpath work
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-    * Mostly comments and reviews, nothing significant
-* Fedor Indutny @indutny (CTC)
-    * Issues, PRs, Direct-to-BIO experiments
-* James M Snell @jasnell (CTC)
-    * Glorious vacation …
-    * Catching up
-    * Small clarification PR for IRC moderation
-* Julien Gilli @misterdjules (CTC)
-    * PR reviews, especially https://github.com/nodejs/node/pull/7827, which looks like a very solid first contribution from a new contributor.
-* Brian White @mscdex (CTC)
-    * Continued reworking of API docs
-    * Reviewed PRs, commented on issues
-* Alexis Campailla @orangemocha (CTC)
-    * Investigating issues related to fs.realPath
-    * Investigating binary compatibility between Node and native modules compiled with different VS versions
-    * Working with team on various Windows issues in Node and libuv
-* Rod Vagg @rvagg (CTC)
-    * NodeSummit / travel, Node v5 blog post nearly ready to post, bug in require() (still need to post in nodejs/node)
-    * Steven R Loomis @srl295 (observer/IBM/ICU)
-    * @ NodeSummit / prep… thinking about how to keep an eye on upcoming v8 changes. Did some more work on https://github.com/nodejs/node/issues/3460 (detect full-icu module).
-* Trevor Norris @trevnorris (CTC)
-    * NodeSummit talk
-    * fs.realpath()
-    * Prepping AsyncWrap, target end of August
-* Rich Trott @Trott (CTC)
-    * Updating governance text and whatnot
-    * Flaky tests
-    * NodeSummit talk
-* William Kapke @williamkapke (Observer)
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* Role of CTC in semver-major changes needs clarification [#7848](https://github.com/nodejs/node/issues/7848)
-* Revert fs changes [#7846](https://github.com/nodejs/node/pull/7846)
-* doc: add information about CTC quorum rules [#7813](https://github.com/nodejs/node/pull/7813)
-* meta: provide example activities [#7744](https://github.com/nodejs/node/pull/7744)
-* meta: realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-* punycode: deprecate punycode module [#7552](https://github.com/nodejs/node/pull/7552)
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-### nodejs/post-mortem
-
-* Repositories to contribute collaboratively [#30](https://github.com/nodejs/post-mortem/issues/30)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-
-## Previous Meeting
-
-### nodejs/node
-
-* [meta] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-## Minutes
-
-
-### Role of CTC in semver-major changes needs clarification [#7848](https://github.com/nodejs/node/issues/7848)
-
-
-
-
-### Revert fs changes [#7846](https://github.com/nodejs/node/pull/7846)
-
-
-James: has to do with recent changes - making callback mandatory on all async functions apparently _broke the planet_, quite a few modules broke including a number used by npm, so `npm set` failed to work for example.
-
-James: technically this should be viewed as a bugfix but we’ve already treated things involving errors as sensitive but this is on master and things a broken right now so suggesting that we revert this. Some alternatives are: not revert and get fixes in the ecosystem, revert and add warning.
-
-Rich: Myles endorsed [#7897](https://github.com/nodejs/node/pull/7897) as a better alternative to reverting as it includes a warning. What’s the preferred approach here James?
-
-James: revert, even though I don’t like it, we should revert and revisit.
-
-Trevor: the fact that it was allowed was a bad decision because throwing can lead to hard-to-debug situations. Reverting is the _only course of action_.
-
-Rod: wanted to clarify as a matter of culture - we should fix master as soon as we’re aware of breakage in the ecosystem and deal with things more cleanly as we can.
-
-Julien: multiple commits in the revert PR, we should have separate discussions about them.
-
-James: will ask on the PR that they be split into two.
-
-James: second question here is whether we want to emit a warning instead?
-
-Rod: the graceful-fs warnings are still widespread because lots of packages rely on very old versions and it’s taking a long time to get updates through the ecosystem. We have to be careful about (1) warning fatigue, (2) users not understanding the subtlety and interpreting warnings as errors. Would be good if we go a bit slower on moving to warnings.
-
-James: we could run with warnings off by default as a way of dealing warning fatigue but that’s another discussion we can have on GitHub.
-
-Rich: moving on, this can be done on Github.
-
-### doc: add information about CTC quorum rules [#7813](https://github.com/nodejs/node/pull/7813)
-
-Rich: there was a counter-proposal which seemed to be better so I updated to use Chalker’s alternative wording. **If anyone doesn’t want this to land please comment on it within the next 24 hours or so**. There hasn’t been too much discussion or disagreement.
-
-### meta: provide example activities [#7744](https://github.com/nodejs/node/pull/7744)
-
-Rich: Similar to the previous issue - have not got a whole lot of response, or a luke-warm response at least. Please comment in there if you have any problems with it, there are no negatives so it’ll land in the next 24 hours or so so please comment!
-
-### \[meta\] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-
-Trevor: ran some benchmarks in CI to see how much time it would take to require() with and without cache in realpath. Haven’t done Windows but on the others there was between 10% to 100%, which is between 30us to 300us difference per require().
-
-Alexis: [#7899](https://github.com/nodejs/node/pull/7899) reverts and also includes Myles’ reversions from the other fs issues.
-
-Trevor: probably should revert and leave cache out, we might take a small hit now in perf but will lead to greater potential in the future.
-
-Alexis: the cache was never a great API in the first place anyway.
-
-Trevor: propose we revert and leave the cache and introduce a better fix.
-
-Anna: agree with Trevor and Alexis.
-
-Rod: should we get benchmarks on Windows?
-
-Alexis: much more concerned about correctness than performance.
-
-Trevor: this is a short-term fix, so we shouldn’t have a problem bringing it in.
-
-Rich asked for disagreement with moving forward with reversion without cache? No disagreement. Need to comment on 7899, review & lgtm. Anna, Trevor or Alexis will move it forward.
-
-### v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-James: because this adds some semver-minor’s Myles is very concerned about stability.
-
-Julien: any ideas on how we might be able to get more testers for these?
-
-James: maybe in a week, will get some suggestions posted to the LTS repo that we can discuss.
-
-### punycode: deprecate punycode module [#7552](https://github.com/nodejs/node/pull/7552)
-
-James: this is a 3rd party dependency that we expose and there’s some fairly extensive usage out there but there is a newer version out there in npm that people should be using.
-
-Rich: no more comments? Please post on the repo.
-
-Rod: deprecation is fine but would really like a long deprecation cycle.
-
-James: how about soft deprecation in v7 and hard in v8?
-
-Rod: soft in v7 and revisit decision to hard prior to v8.
-
-Brian: if people build without ICU what would happen to punycode since we need it?
-
-James: This particular PR introduces a hard deprecation that moves it to internal/ and has a shim that exposes it, so we could still use it internally but just deprecate the external API.
-
-Brian: are we going to continue updating the non-ICU version for people going forward or just leave it?
-
-James: would prefer to just leave it as is.
-
-Chalker: on npm it has 5.7M downloads per month so people are already using it.
-
-James: clarify: soft deprecate now and revisit hard deprecation prior to v8?
-
-### http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-Rod: wanted to mention that Chris Dickinson expressed concerns on Twitter about us doing this same thing on querystring and that it was causing problems for him and didn’t like that it crept in to v6.
-
-James: Doug, from the express side, thinks this is a good decision and cleans up things for users. The querystring thing has
-
-… discussion tended towards accepting the change but CTC would like to solicit input from Chris Dickinson before getting it landed since he had raised some objections
-
-### Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-Mikeal Rogers: discussing the SPDX stuff and restoration of licenses in the files. Mikeal and Rod will take the lead on moving forward with this.
-
-### Repositories to contribute collaboratively [post-mortem#30](https://github.com/nodejs/post-mortem/issues/30)
-
-Move to TSC meeting
-
-### proposal: WHATWG URL standard implementation [node-eps#28](https://github.com/nodejs/node-eps/pull/28)
-
-James: Passing WHATWG tests except some intentional ones. Performance is slower than our own url impl because of tests we fail. Any objections to moving forward?
-
-Rod: we’re going to have two implementations, this seems like a difficult thing to agree on.
-
-James: would like to eventually deprecate existing url.parse.
-
-Rich: let’s move on because this will be a big conversation. Let’s have a brief conversation next week and slot a bigger discussion next week.
-
-## Q/A on public fora
-
-No questions.
-
-## Upcoming Meetings
-
-* CTC: 2016-08-03
-* TSC: 2016-07-28
-* Build: 2016-08-09
-* Diagnostics: 2016-08-03
-* Post-Mortem: August
-* API: August
diff --git a/doc/ctc-meetings/2016-08-03.md b/doc/ctc-meetings/2016-08-03.md
deleted file mode 100644
index 96884b42e1d381..00000000000000
--- a/doc/ctc-meetings/2016-08-03.md
+++ /dev/null
@@ -1,336 +0,0 @@
-# Node Foundation CTC Meeting 2016-08-03
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: https://github.com/nodejs/node/issues/7948
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1ufR5dNuN3JLmFPvCvLYGRa98_-eqy5yY3zJuTnT60K8/edit#heading=h.ncvpl89y747j>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1rHxRb-ImjwFPOCOapgRDLdhqr4LJvie7eDNPOnDu2UA>_
-
-
-## Present
-
-* Anna Henningsen @addaleax (observer)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Ben Noordhuis @bnoordhuis (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* James M Snell @jasnell (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Bert Belder @piscisaureus (CTC)
-* Saúl Ibarra Corretgé @saghul (observer)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (observer)
-  * Issues & PR review
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Went to TC39
-  * Modules are going to take a different direction
-* Ben Noordhuis @bnoordhuis (CTC)
-  * Nothing special.
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Working on the npm dataset rebuilding tool. Some comments on issues and PRs as usual.
-* Colin Ihrig @cjihrig (CTC)
-  * Was on vacation
-  * Reviewing issues and PRs since I've been back
-* Evan Lucas @evanlucas (CTC)
-  * A little cherry-picking to v6.x
-  * Working on getting commit validator running for PRs
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Mostly away, experimenting with nucleus-js.
-* James M Snell @jasnell (CTC)
-  * Node Summit
-  * Exploring the possibility of an HTTP/2 implementation in core
-  * Continued evaluation of the WHATWG URL implementation
-  * Foundation-y / TSC-y stuff
-  * Reviewing PRs, catching up still from vacation
-* Josh Gavant @joshgav (observer/Microsoft)
-  * internal stuff, vacation
-* Michael Dawson @mhdawson (CTC)
-  * Node Summit/catching up on issues after Node Summit
-  * Starting to add linuxOne release machine/jobs
-  * Adding new AIX machine from osuosl
-  * landed a few minutes PRs
-* Brian White @mscdex (CTC)
-  * Commenting on issues/PRs.
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Node Summit & internal stuff. Spent rest of time shepherding some backports.
-  * Planning on writing a proposal for managing V8 for LTS
-* Bert Belder @piscisaureus (CTC)
-  * Commented on an issue.
-* Rich Trott @Trott (CTC)
-  * CTC/governance documentation updates
-  * Onboarding (danbev postponed but we’ll get there, now scheduling with fhinkel, additional nominees welcome)
-  * fixed a flaky test, investigating others
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* CTC membership nomination: @addaleax [#7607](https://github.com/nodejs/node/issues/7607)
-
-* Revert fs changes [#7846](https://github.com/nodejs/node/pull/7846)
-
-* [meta] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-* build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484)
-
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-### other
-
-* doc: @piscisaureus has stepped-down from the CTC [#7969](https://github.com/nodejs/node/pull/7969)
-
-## Previous Meeting
-
-### nodejs/node
-
-* Role of CTC in semver-major changes needs clarification [#7848](https://github.com/nodejs/node/issues/7848)
-* Revert fs changes [#7846](https://github.com/nodejs/node/pull/7846)
-* doc: add information about CTC quorum rules [#7813](https://github.com/nodejs/node/pull/7813)
-* meta: provide example activities [#7744](https://github.com/nodejs/node/pull/7744)
-* meta: realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-* punycode: deprecate punycode module [#7552](https://github.com/nodejs/node/pull/7552)
-* Node 6 fs.realpath behavior changes [#7175](https://github.com/nodejs/node/issues/7175)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-### nodejs/post-mortem
-
-* Repositories to contribute collaboratively [#30](https://github.com/nodejs/post-mortem/issues/30)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-## Minutes
-
-### CTC membership nomination: @addaleax [#7607](https://github.com/nodejs/node/issues/7607)
-
-Unanimous `aye`.
-
-**Next steps**: @rvagg to merge.
-
----
-
-### Revert fs changes [#7846](https://github.com/nodejs/node/pull/7846)
-
-Reverts:
-https://github.com/nodejs/node/pull/7846
-https://github.com/nodejs/node/pull/7950
-
-Warn instead of throw when callback is omitted, as in v5:
-https://github.com/nodejs/node/pull/7897
-
-@bnoordhuis: This change makes omitting the callback an immediate error.
-
-@trott: What do we need to do to get those PRs to land?
-
-@addaleax: Myles split off one commit to [#7950](https://github.com/nodejs/node/pull/7950). Not controversial, was requested by CTC last week.
-This must be landed prior to #7846.
-
-@jasnell: Would like to see a CI and CITGM run and some additional testing to make sure we have exactly the right set of reverts. @jasnell will start it.
-
-@bnoordhuis: We need to print a deprecation warning [instead of throwing, when no callback].
-
-@addaleax: That’s the plan after the reverts have landed. @thefourtheye plans to work on it. [see #7897])
-
-@jasnell: process warning or deprecation warning? Will we use `util.printDeprecationWarning` or `process.emitWarning()`?
-Deprecation warning is semver-major, process warning is semver-minor or even patch.
-
-[It's `printDeprecationWarning`, see [here](https://github.com/thefourtheye/io.js/blob/8c65f7b6a253ab4e26ffe0de791dc41fcee92244/lib/fs.js#L48).]
-
-@addaleax: PR to print warning already opened. Could be used instead of reverting, but we agreed to revert last week and it blocks the realpath revert.
-
-@Fishrock123: Unbreaking a break and replacing with warning shouldn’t be semver-major.
-
-@trott: @jasnell’s PR on semver policies says it should be semver-major.
-
-@Fishrock123: Since we already changed it in the v6 transition let’s just change it to a deprecation.
-
-@trott: Let’s do the reverts (#7846, #7950), discuss deprecation warning separately in GH (#7897).
-
-OK with everybody.
-
-**Next steps**: Do the reverts (#7846, #7950). Continue discussion on throw -> warning in #7897.
-
----
-
-### [meta] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-
-@trott: Last week we concluded that Anna, Trevor, or Alexis would move it forward.
-
-@trott: Just the two reverts that are blocking.
-
-@addaleax: Yes.
-
-@saghul: Old JS impl did not resolve subst’ed drives. New libuv impl does. A test looks for the new behavior. ]
-
-@saghul: Some people are relying on the old JS impl behavior to shorten paths on Windows. What are the right semantics? Should `subst`ed drives resolve to original path or to shortened path?
-
-@piscisaureus: The whole reason we use realpath in `module` is to avoid a module being loaded multiple times via multiple symlinked paths. So the goal should be to always resolve to the true path.
-
-@piscisaureus: Path limit is 64k not likely to encounter.
-
-@saghul: There’s a test for the new code which expects realpath on a subst’ed drive to give the original path. We need to revert this test for reverted behavior.
-
-@addaleax: Reverting to fs JS impl would return to old behavior.
-
-@trott: Submit a PR to remove that test, or move to known issues tests.
-
-@piscisaureus: Leave the test to track changes in the future.
-
-@Fishrock123: Key is to revert to an impl the ecosystem is depending on. Discuss this in another PR in GitHub.
-
-@jasnell: It’s a revert of the internal impl, not the changed public API [i.e. so we have to consider it now.]
-
-What about reverting the removal of the `cache` option?
-
-@addaleax: Not including the `cache` option now would allow additional/alternate improvements in the future.
-
-@bnoordhuis: Are these changes to land in v7?
-
-@jasnell: The idea is to get these into *v6* before it goes LTS.
-
-* The realpath change would land in v6.
-* The other changes (revert throwing error on callback) is only in master and would not land in v6.
-* Are the realpath changes dependent on the others?
-* Only Myles’ changes conflict with realpath [see previous item].
-
-@jasnell: Do we have the steps lined up?
-
-@addaleax: Myles revert (#7846, #7950), then realpath revert.
-
-@? apply semver-major changes that were reverted, with deprecation warning.
-
-@chalker: Can we keep tests which were added? Revert removes some tests which aren’t actually related to changes.
-
-@piscisareus: Same as @saghul’s comment, and we agreed to keep the new tests. So yes we should keep them.
-
-**Next steps**:
-
-* Modify PR to keep tests related to new behavior for reference.
-* Apply Myles' reverts (#7846, #7950)
-* Apply `realpath` revert.
-* Discuss other items (e.g. throw -> deprecation, proper realpath for subst'ed drives, cache impl) in GH issues.
-
----
-
-### v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-@trott: Please test the RCs.
-
-@mhdawson and @jasnell: Building at IBM and not encountered anything.
-
----
-
-### build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484)
-
-@bnoordhuis: Based on @joaocgreis’s comment we can move from 2013 without trouble.
-
-@joshgav: @joaocgreis tested against many modules and with CITGM and encountered no problems.
-
-@piscisaureus: Can we wait for semver-major?
-
-@joshgav: Then we’ll be stuck with 2013 through out v6 LTS.
-
-@piscisaureus: Should we make another issue for v6?
-
-@jasnell: Let’s get this landed in master and test it out, then make a decision on putting in v6 before October.
-
-@trott: Getting pretty close, don’t want to be switching just a month before.
-
-**Next steps**:
-
-* Merge to master and test.
-* Determine in September if we can apply in v6.
-
----
-
-### http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-@chrisdickinson has concerns, @mscdex contacted. No response yet.
-
-@Fishrock123: Let’s remove `ctc-agenda` tag for next week.
-
-@jasnell: Plenty of discussion, heard from Doug Wilson that it’s a positive change. Would rather not hold up waiting for a response. Would be best to land before v7.
-
-@ofrobots: If we are going to change this we should have a plan for if/how we’ll get to maps.
-
-@Fishrock123: There are too many people currently depending on this being a regular object.
-
-@ofrobots: We shouldn’t break the ecosystem twice. We should target something with maps for v8 or longer timeframe.
-
-@Fishrock123: Motivation is ?
-
-Some feel we should wait for maps before making a breaking change. Jeremiah feels we should make an effective change now and not wait for an unknown future.
-
-@Fishrock123: We’ll need to provide both old and new APIs side by side, and that could be hard to do with maps.
-
-@ofrobots: We can delegate old API to a Proxy and add deprecation warnings on that handler.
-
-@?: Is Proxy performant enough?
-
-@ofrobots: For a deprecated path is it okay to take a performance hit?
-
-@evan: Okay with current change proposal (i.e. to not inherit from Object) as long as it’s considered semver-major.
-
-@jasnell will work on this.
-
-**Next steps**: Decide whether to merge this or wait for maps-based impl.
-
----
-
-### nodejs/node-eps proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-@trott: briefing now, longer discussion next week.
-
-@jasnell: Everyone keep reviewing it. Goal is to land as “experimental” in master, doesn’t have to go in v6.
-
-@trevnorris: -1 on global `URL` variable.
-
-@Fishrock123 also against new globals other than lang features.
-
-@jasnell: It’s a global in browsers. It can be removed, it’s in its own commit.
-
-**Next steps**: @nodejs/ctc review @jasnell's proposal. Discuss next week.
-
----
-
-### doc: @piscisaureus has stepped-down from the CTC [#7969](https://github.com/nodejs/node/pull/7969)
-
-@Fishrock123: submit PR to remove @piscisaureus and/or move to Collaborator.
-
----
-
-## Q/A on public fora
-
-No questions.
-
-## Upcoming Meetings
-
-* CTC: 2016-08-03
-* TSC: 2016-07-28
-* Build: 2016-08-07
-* LTS: 2016-07-25
-* Diagnostics: Sept
-* Post-Mortem: August
-* API: August
diff --git a/doc/ctc-meetings/2016-08-10.md b/doc/ctc-meetings/2016-08-10.md
deleted file mode 100644
index 06e3b5083a9d30..00000000000000
--- a/doc/ctc-meetings/2016-08-10.md
+++ /dev/null
@@ -1,281 +0,0 @@
-# Node Foundation CTC Meeting 2016-08-10
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8030](https://github.com/nodejs/node/issues/8030)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1L65L7qhX5MrGeFwrub4-Z8klrwxJym-Q8CIEZsedohE>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1ufR5dNuN3JLmFPvCvLYGRa98_-eqy5yY3zJuTnT60K8>_
-
-
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Ben Noordhuis @bnoordhuis (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-* James M Snell @jasnell (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Myles Borins @TheAlphaNerd (observer/IBM)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Issues/PR review
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Came up with overhauled plan for Module moving forward
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * A bit more work on the ecosystem detection tool
-  * Mostly comments, nothing significant
-  * Will file a docs linting PR soon — needs some final cleanup
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewing issues and PRs
-  * Working on the v6.4.0 release
-* Evan Lucas @evanlucas (CTC)
-  * some more commit validation work
-  * backport pr for worker.exitedAfterDisconnect to v4.x
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Nothing in particular
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-* James M Snell @jasnell (CTC)
-  * Going through PRs/Issues
-  * More exploration of possibility of HTTP/2 impl in core
-  * Other miscellaneous things
-* Josh Gavant @joshgav (observer/Microsoft)
-  * meetings notes
-  * review some issues
-* Michael Dawson @mhdawson (CTC)
-  * adding linxuOne release machine to the release CI, and getting linuxOne added to release job so that we get nightlies for that platform
-  * configuring new AIX machines from osuosl, adding to CI and validating with AIX build jobs that they look good.  Working to get added to regular regression jobs.
-  * Working on build wg, FIPs and post-mortem presentations for Node interactive Europe
-  * Landing a few PRs
-  * Reading/commenting on issues
-  * Participation in LTS and Build WGs
-  * ABI stable API PoC
-* Brian White @mscdex (CTC)
-  * Reviewing PRs, commenting on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * v8_inspector updates, V8 backports, writing up a doc on maintaining V8
-* Myles Borins @TheAlphaNerd (observer/IBM)
-  * v4.5.0 testing (potential regression)
-  * ABI Smoke Testing Job
-  * Landing V8 5.1 on v6.x
-  * junit reporters for CI with Johann
-* Trevor Norris @trevnorris (CTC)
-  * PR reviews
-  * Vacation most of the week
-* Rich Trott @Trott (CTC)
-  * onboarded @fhinkel
-  * minor work on tests
-  * ESLint update, minor indentation rule update
-* Steven Loomis (Observer)
-  * Asked me to pass on his regrets as he’s on vacation.
-  * He’s been working on more Intl related items.
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-* buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-* Revert "fs: add a temporary fix for re-evaluation support" [#6413](https://github.com/nodejs/node/pull/6413)
-* errors: add internal/errors module [#6573](https://github.com/nodejs/node/pull/6573)
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-### general
-
-* discussion: CommonJS and ES6 modules interoperability (<https://gist.github.com/bmeck/52ee45e7c34d1eac44ce8c5fe436d753>)
-
-
-## Previous Meeting
-
-### nodejs/node
-
-* CTC membership nomination: @addaleax [#7607](https://github.com/nodejs/node/issues/7607)
-* Revert fs changes [#7846](https://github.com/nodejs/node/pull/7846)
-* [meta] realpath issues in v6 [#7726](https://github.com/nodejs/node/issues/7726)
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-* build: drop support for VS 2013 in v7 [#7484](https://github.com/nodejs/node/issues/7484)
-  * New issue specifically for v6: [#7989](https://github.com/nodejs/node/issues/7989)
-* http: don't inherit from Object.prototype [#6102](https://github.com/nodejs/node/pull/6102)
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-## Minutes
-
-### v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-@thealphanerd: investigating problem with Bower, may delay release, if so will notify everyone.
-
-**Next steps**:
-
-* As above.
-
----
-
-### buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-
-@trevnorris: In the future the Buffer function will need to be a proper class so that `iterate` can return a buffer and so that users can inherit from Buffer.
-
-Enabling inheritance forces the use of `new`. Thus it will break anyone who uses `Buffer` without the `new` keyword.
-
-@evanlucas: Wasn’t there a way around that?
-Perhaps with use of @@species symbol, but still doesn’t remove the fact that we’ll need to remove the `new` keyword at some point.
-
-@addaleax: We could work around using `Reflect` API and check if call was made with `new` or not. There were perf concerns, @RReverser worked on something (see <https://github.com/nodejs/node/pull/7152#discussion_r74932064>).
-
-@evanlucas: Can we do that and just soft-deprecate not using `new`?
-
-@jasnell: We should absolutely *not* deprecate `new Buffer(...)`.
-
-@chalker: [Deprecating `new Buffer()` will force libraries to work around this in 0.10, 0.12, and LTS <4.4, doesn’t sound like a good thing to do now.
-
-**Next steps**:
-
-* Continue discussion in GitHub.
-* Finalize decision next week.
-
----
-
-### Revert "fs: add a temporary fix for re-evaluation support" [#6413](https://github.com/nodejs/node/pull/6413)
-
-Do we land the revert?
-
-@chalker: This is going to break modules, notably those which depend on `graceful-fs`, including `gulp` and `unzip` (there’s another unzip module people use, unzip is not updated for a long time and its usage is rapidly decreasing), other inactive modules.
-
-gulp will update `graceful-fs` Gulp v4. Gulp accounts for 42% of usage of `graceful-fs`. Gulp doesn’t want to update `graceful-fs` in v3 because it's a semver-major change, wants to wait for semver-major update till v4.
-
-@jasnell: If we keep it as is I don’t think the modules are going to get fixed.
-
-@thealphanerd: if gulp v3 isn’t updated then it will continue to cause problems for people through v7 lifetime. Can gulp do something to make this easier on the community?
-
-@thealphanerd will follow up with gulp project leads about updating `graceful-fs` in Gulp v3.
-
-@chalker: Old version of `graceful-fs` now includes its own message that it will be broken in Node v7. Would be best to live up to our commitment.
-
-**Next steps**:
-
-* Myles to follow up with Gulp about changes in v3, notify CTC as appropriate.
-* Finalize decision next week.
-
----
-
-### proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-Should `url` be a global or not?
-@jasnell: To start let’s just not make it a global.
-
-@jasnell: No need to include this in v6; include in master and in v7.
-
-First step is to decide to land this as an EP in Node-EPs. Then, consider implementation.
-
-@evanlucas: Will the similarity of these cause confusion?
-`require(‘url’).Url` and `require(‘url’).URL`.
-
-@jasnell: best answer is I’m not sure yet.
-
-@jasnell: We’ll move forward on the EP without the global.
-
-**Next steps**:
-
-* Remove global then land EP.
-* Continue work/review on impl.
-
----
-
-### errors: add internal/errors module [#6573](https://github.com/nodejs/node/pull/6573)
-
-@jasnell: This begins the process of changing errors implementation so that changes to their text are not semver-major.
-
-Do we want this to land in v7? If we do, it needs to be complete by the end of August.
-
-@Fishrock123: think about whether we can keep the syntax similar between js and c++.
-
-@jasnell: if additional work is needed for C errors we should not rush it.
-
-**Next steps**:
-
-* Review in GitHub.
-* Finalize next week.
-
----
-
-### Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-
-@thealphanerd: If we had a staging branch we’d avoid blocking releases due to problematic commits.
-
-@Fishrock123: You can already stage to `v6.x` but usually people don’t do that.
-
-@thealphanerd: Since it has the same function as `staging` it would be good to name them similarly.
-
-@bnoordhuis: it’s confusing that there are different ways to get PRs backported in different branches.
-
-@Fishrock123: Actual practices are not likely to change.
-
-**Next steps**:
-
-* Continue discussion in GH.
-* Keep on agenda.
-
----
-
-### discussion: CommonJS and ES6 modules interoperability (see <https://gist.github.com/bmeck/52ee45e7c34d1eac44ce8c5fe436d753>)
-
-@bmeck:
-
-* Cannot match babel’s semantics.
-* Cannot support named imports from CJS modules.
-
-We cannot match babel’s semantics so whatever happens in the future, at a minimum people who use babel to compile will have to change to use whatever Node is using for ES modules.
-
-There’s no real way for us to support named imports from CJS modules, so these will be imported as the `default` property only, so people will not be able to use just `readFile` from `fs`.
-
-Those 2 breakages mean we have to rethink this. First route was to match babel.
-
-@bmeck proposes Node does a hard break. Remove most of Node’s magic names.
-
-We’ll need a separate WHATWG `registry` object
-
-@bmeck: New features are going to be targeting the module grammar exclusively. For example, `await` is not a keyword in the script grammar and if it’s treated that way it’s a language extension. TC39 considers `script` somewhat legacy.
-
-**Next steps**:
-
-* Schedule a session specifically on modules.
-
----
-
-## Q/A on public fora
-
-Q: Regarding WHATWG URL, how will updates be handled - major, minor, bug fix?
-
-@jasnell: Still need to figure out process. Currently monitoring WHATWG to get a sense of their process. If their change is semver-major ours would presumably also be.
-
-## Upcoming Meetings
-
-* CTC: 2016-08-17
-* TSC: 2016-08-11
-* Build: Sept
-* LTS: Sept
-* Diagnostics: Sept
-* Post-Mortem: Sept
-* API: Sept
diff --git a/doc/ctc-meetings/2016-08-17.md b/doc/ctc-meetings/2016-08-17.md
deleted file mode 100644
index 99c93bfc031d46..00000000000000
--- a/doc/ctc-meetings/2016-08-17.md
+++ /dev/null
@@ -1,300 +0,0 @@
-# Node Foundation CTC Meeting 2016-08-17
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8125](https://github.com/nodejs/node/issues/8125)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/10fKK2lyZrxJ1Gt4zJvVSIsfmTGVD547vJJOp6eVKk-k>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1L65L7qhX5MrGeFwrub4-Z8klrwxJym-Q8CIEZsedohE>_
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Ben Noordhuis @bnoordhuis (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-* James M Snell @jasnell (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Julien Gilli @misterdjules (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Rod Vagg @rvagg (CTC)
-* Myles Borins @TheAlphaNerd (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Issues & PR review
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Modules - talks w/ transpilers about paths forward , looks like clean break / may not be able to support forward transpilation
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Comments on issues and PRs
-* Colin Ihrig @cjihrig (CTC)
-  * v6.4.0 release
-  * Reviewed issues and PRs
-* Evan Lucas @evanlucas (CTC)
-  * some small doc updates
-  * pr to revert \r\n change to util/repl
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * only a few PR/Issue comments
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-  * working on inclusivity strategies, stay tuned for issues in the next few days
-  * certification scoping: reach out to me if you’d like to be part of that
-* James M Snell @jasnell (CTC)
-  * PR review
-  * More investigation into HTTP/2
-  * Work on proposed icu module
-  * Some inclusivity related discussions
-* Josh Gavant @joshgav (observer/Microsoft)
-  * onboarded!
-  * internal work
-* Julien Gilli @misterdjules (CTC)
-  * soliciting feedback on testing release candidates from customers
-* Brian White @mscdex (CTC)
-  * Submitted a couple of small PRs
-  * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Auditing upstream bug fixes on V8
-* Rod Vagg @rvagg (CTC)
-  * Taking time off
-* Myles Borins @TheAlphaNerd (observer)
-  * Released v4.5.0
-  * Landed **fix** into graceful-fs
-  * continued research into how to minimize ecosystem breakage with fs changes
-  * continued work on V8 ABI testing for citgm
-  * New native modules included in citgm
-  * CI job in jenkins
-* Trevor Norris @trevnorris (CTC)
-  * Nothing of note
-* Rich Trott @Trott (CTC)
-  * Onboarding @joshgav
-  * ESLint updates and enabling of rules
-  * small tests to plug holes in test coverage (per @addaleax’s coverage web page https://node-core-coverage.addaleax.net/)
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* CTC membership nomination: @TheAlphaNerd [#8058](https://github.com/nodejs/node/issues/8058)
-* buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-* Revert "fs: add a temporary fix for re-evaluation support" [#6413](https://github.com/nodejs/node/pull/6413)
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-
-## Previous Meeting
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* v4.5.0 proposal [#7688](https://github.com/nodejs/node/pull/7688)
-
-  * @thealphanerd will investigate problem with Bower, may delay release, if so will notify everyone.
-
-* buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-
-  * Continue discussion in GitHub.
-  * Finalize decision next week.
-
-* Revert "fs: add a temporary fix for re-evaluation support" [#6413](https://github.com/nodejs/node/pull/6413)
-
-  * Myles to follow up with Gulp, notify CTC as appropriate.
-  * Finalize decision next week.
-
-* errors: add internal/errors module [#6573](https://github.com/nodejs/node/pull/6573)
-
-  * Review in GitHub.
-  * Finalize next week.
-  * **Decided not to discuss today, continue work in GH.**
-
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-
-  * Continue discussion in GH.
-  * Keep on agenda.
-
-### nodejs/node-eps
-
-* proposal: WHATWG URL standard implementation [#28](https://github.com/nodejs/node-eps/pull/28)
-
-  * Remove global than land EP.
-  * Continue work/review on impl.
-
-### general
-
-* discussion: CommonJS and ES6 modules interoperability (<https://gist.github.com/bmeck/52ee45e7c34d1eac44ce8c5fe436d753>)
-
-  * Schedule a session specifically on modules.
-
-
-## Minutes
-
-### CTC membership nomination: @TheAlphaNerd [#8058](https://github.com/nodejs/node/issues/8058)
-
-Generally we require attendance as an observer at least 4 times to ensure fit on both sides. Myles has already attended several meetings and all are comfortable.
-
-We will vote on this next week.
-
-**Next steps**:
-
-* Vote next week.
-
----
-
-### buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-
-In order to enable inheritance from Buffer, need to declare it as a class, which will then require `new` keyword to create a new Buffer.
-
-`new Buffer(...)` works in all versions.
-
-Options
-
-1. Keep as is - `Buffer(...)` would still work without `new`, and Buffer wouldn’t be subclassable.
-2. Deprecate creating a buffer without `new`. `Buffer(...)` would no longer work.
-3. Fully deprecate any use of Buffer constructor even without `new`. Neither `Buffer(...)` nor `new Buffer(...)` would work.
-
-@trevnorris: Another option is to retain UInt8Array constructor signatures as Buffer constructor signatures.
-
-@Fishrock123: We should deprecate use without `new`, but deprecating entire constructor isn’t reasonable due to ecosystem usage.
-
-@jasnell: It would be a hard deprecation warning, i.e. by default print a warning message.
-
-@trott: That would imply full removal in v9.x at the earliest.
-
-@trevnorris: ecosystem has to use workarounds to subclass Buffer. So this refactor is actually blocking use cases.
-
-@Fishrock123: We could differentiate between `require(‘buffer’).Buffer` and the global `Buffer`; imported Buffer would have deprecation, but Buffer as a global would not have that deprecation.
-
-@addaleax: No. The types should still match (behave the same).
-
-@jasnell: Separate into 2 PRs: one for deprecation of `Buffer()` without `new`, and another for complete deprecation of constructor, even with `new`.
-
-**Next steps**:
-
-* Separate into 2 PRs as above.
-* Discuss again next week.
-
----
-
-### Revert "fs: add a temporary fix for re-evaluation support" [#6413](https://github.com/nodejs/node/pull/6413)
-
-@thealphanerd: Making many patches in `graceful-fs` and concerned that will not scale.
-
-Previously graceful-fs put something through `vm` module. Then we used something in `internal/util` and it blew everything up. This happened near v6 release so we added this temporary fix.
-
-Now this temporary fix is blocking progress on other issues.
-
-We’ve had to patch `graceful-fs` several times, no guarantee that we won’t have to again. Each time it’s putting internal/util methods directly into graceful-fs.
-
-Gulp transitively relies on graceful-fs v3.
-
-Myles spoke to Blaine (head of gulp). Very reluctant to make a breaking change within v3 major release. Nothing seems to be broken, Myles ran tests, but not every possible workflow.
-
-[#8149](https://github.com/nodejs/node/issues/8149) opened by @isaacs to discuss benefits of `internal`, worth discussing this in that context.
-
-We want to move things to `internal` but we also don’t want to break gulp and the ecosystem (e.g. ember CLI).
-
-@Fishrock123: Why can’t we use the updated shim to make graceful-fs v2 and v3 work?
-
-Myles: More changes coming that will further break graceful-fs, such as [#6749](https://github.com/nodejs/node/pull/6749), the Errors PR James is working on, a PR to move StringToFlags to internal/fs.
-
-Reasons to stop treating graceful-fs specially:
-
-* We’ll need to patch graceful-fs v2 whenever we patch `internal/fs`.
-* New things could be added to `internal` in `nodejs/node` which we don’t expect to be relevant to the ecosystem but in fact will need to be added graceful-fs.
-
-@rvagg: Perhaps we should move slower, graceful-fs is an important module.
-
-@jasnell: Consider errors PR, helps us reduce inconsistencies and problems. We’d need alternate code in graceful-fs to do that.
-
-We are doing that currently with streams. I have to treat it special cause of the `readable-stream` module.
-
-It makes things significantly harder.
-
-@thealphanerd: Should we shim `process.binding('internal/*')` to intercept this call and return patched module when needed?
-
-@thealphanerd: Let’s add graceful-fs v3 to CITGM and ensure it keeps working.
-
-@jasnell: perhaps we should have our own `graceful-fs` module in core.
-
-@Fishrock123: Let’s backport all patches in graceful-fs v4 to v3 and v2.
-
-@Chalker: This is what gulp objects to, they can’t backport to make a semver-major change.
-
-@Fishrock123: If in fact it’s not breaking then they should backport them.
-
-@jasnell: We need to decide if we want to land before v7. This particular PR, if landed, would not break `graceful-fs` v3. (Myles: but it would break v2).
-
-@rvagg: I’d vote for slowing down on this. This group is not a primary group of Node users, they’re using for frontend toolchain. They aren’t used to dealing with Node and won’t know how to handle problems. Better for us to accept a little pain than to inflict on lots of users.
-
-@bnoordhuis: if not now when?
-
-@myles: graceful-fs v2 patch wouldn’t take a long time.
-
-A lot of people in ecosystem who don’t feel like we’re listening. There’s not much technical advantage to landing this. (We could update the patch to use an updated form of deprecation.)
-
-On the other hand, to land all the other fs fixes we need to land this.
-
-So if we’re going to land the rest, we should land this. Otherwise, hold.
-
-@jasnell: no consensus to land this before v7. Next possible time is v8.x (which becomes LTS).
-
-@thealphanerd: still possible to land in v7.
-
-@bnoordhuis: What might change in v8.x timeframe?
-
-@thealphanerd: more gulp v4 adoption, more ecosystem testing to see how to avoid breaking people.
-
-@trevnorris: will the ecosystem upgrade from v3 to v4?
-
-@thealphanerd: at least they’ll have the option to upgrade and be unbroken.
-
-**Next steps**:
-
-* Myles working with @isaacs to integrate a fix in graceful-fs@3 to address all these concerns, see <https://github.com/nodejs/node/pull/8245#issuecomment-242192458>.
-
----
-
-### Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-
-Deferred till next week.
-
----
-
-### Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-@rvagg to follow up with legal committee.
-
----
-
-### Modules Update (from Bradley)
-
-@jasnell will set up a Doodle for a meeting on modules.
-
----
-
-## Q/A on public channels
-
-Q: Where should the question of accepting creationix/nvm go?
-[TSC#96](https://github.com/nodejs/TSC/issues/96)
-
-@jasnell: TSC meeting, add to next week’s agenda.
-
-## Upcoming Meetings
-
-* CTC: 2016-08-24
-* TSC: 2016-08-25
-* Benchmarking: [Benchmarking#56](https://github.com/nodejs/benchmarking/issues/56)
-* Build:
-* LTS:
-* Diagnostics:
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-08-24.md b/doc/ctc-meetings/2016-08-24.md
deleted file mode 100644
index d68ec64768abb5..00000000000000
--- a/doc/ctc-meetings/2016-08-24.md
+++ /dev/null
@@ -1,328 +0,0 @@
-# Node Foundation CTC Meeting 2016-08-24
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8242](https://github.com/nodejs/node/issues/8242)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1mkOUQ-M3s6zV2ige00hj6IIlT5oGQcw1USeliRqRDSk>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/10fKK2lyZrxJ1Gt4zJvVSIsfmTGVD547vJJOp6eVKk-k>_
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Fedor Indutny @indutny (CTC)
-* James M Snell @jasnell (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Julien Gilli @misterdjules (CTC)
-* Brian White @mscdex (CTC)
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-* Rod Vagg @rvagg (CTC)
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-* Myles Borins @TheAlphaNerd (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Issues & PR review
-  * Couple of own PRs
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Started rewrite/overhaul of Module EP
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Comments on issues and PRs, nothing significant
-  * Started documenting my npm tooling
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Minor PR & Issue things
-  * Review of the Promises Warnings thing
-* Fedor Indutny @indutny (CTC)
-  * Reviewing PRs, nothing fancy
-* James M Snell @jasnell (CTC)
-  * PR review
-* Josh Gavant @joshgav (observer/Microsoft)
-  * Issue review, keep CTC notes in order
-* Michael Dawson @mhdawson (CTC)
-  * Away on vacation last week
-  * Fixed up problems with acme air benchmarks
-  * Investigated AIX machine issues (firewall problem)
-  * misc PR review/land
-  * catching up on issues
-  * starting to add new PPC machines (hopefully final set)
-* Julien Gilli @misterdjules (CTC)
-  * making libuv test suite pass on SmartOS
-* Brian White @mscdex (CTC)
-  * My continuing mission: to explore strange new deopts, to seek out new JS and new optimizations.
-  * Reviewing PRs, commenting on issues
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-  * Observing in prep for a newsletter on Node community with
-Node.js Foundation
-* Rod Vagg @rvagg (CTC)
-  * Taking it easy, some discussion, some meetings
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-  * Achievement unlocked: getting to CTC call
-* Myles Borins @TheAlphaNerd (observer)
-  * (on vacation)
-* Trevor Norris @trevnorris (CTC)
-  * async wrap; considering changing the name of public API require.
-* Rich Trott @Trott (CTC)
-  * Multiple issues causing CI yellow and red this week. Will file an issue for next meeting for things we may wish to do differently.
-  * Helped three first-time contributors get their first commits in. (Well, two of them so far.) Some documentation changes have/will come from this.
-  * Lots of small PRs to refactor tests.
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* CTC membership nomination: @TheAlphaNerd [#8058](https://github.com/nodejs/node/issues/8058)
-* buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-* fs: don't alter user provided `options` object [#7831](https://github.com/nodejs/node/pull/7831)
-* fs: undeprecate existsSync; use access instead of stat for performance [#7455](https://github.com/nodejs/node/pull/7455)
-* doc: add Google Analytics tracking. [#6601](https://github.com/nodejs/node/pull/6601)
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-### nodejs/api
-
-* Landing node-eps for ABI stable module and location for PoC code [#28](https://github.com/nodejs/api/issues/28)
-
-
-## Previous Meeting
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-* CTC membership nomination: @TheAlphaNerd [#8058](https://github.com/nodejs/node/issues/8058)
-  * vote next week
-* buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/issues/7152)
-  * separate into 2 PRs (one for deprecation without `new`, one for deprecation even with `new`)
-  * revisit next week
-* Revert "fs: add a temporary fix for re-evaluation support" [#6413](https://github.com/nodejs/node/6413)
-  * Discussion continuing in GitHub.
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/6306)
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/3979)
-
-
-## Minutes
-
-### CTC membership nomination: @TheAlphaNerd [#8058](https://github.com/nodejs/node/issues/8058)
-
-@trott: Any objections?
-
-Vote: Unanimous yes. No “nos” or official “abstains.”
-
-**Next steps**:
-
-* @rvagg to onboard @thealphanerd.
-
----
-
-### buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-
-@addaleax: See <https://github.com/nodejs/node/pull/7152#issuecomment-241355246>
-
-@jasnell and @rvagg both posted following @addaleax, she agrees.
-
-@addaleax: Not in favor of dropping constructors which don’t match UInt8Array constructors.
-
-@jasnell: What is the use case that requires `Buffer` be subsclassable?
-
-@trevnorris: It cleans up the code if we can extend directly from UInt8Array. Also, community members have requested the ability to extend Buffer.
-
-@addaleax: We could work around that, we could export something from `require(‘Buffer’)` which is subclassable.
-
-@trevnorris: But your constructor name won’t be right.
-
-@addaleax: I posted a proof of concept, I think everything is going to be right, needs perf evaluation.
-
-@trott: One issue is whether and when to deprecate `Buffer` without `new` keyword. Any dissent on that?
-
-@jasnell: Haven’t seen any dissent.
-
-@trott: Can we finalize on that?
-
-@trevnorris: to extend from UInt8Array all we need to do is deprecate `Buffer` without `new`.
-
-@jasnell: We all agree about removing `new` - hard deprecation.
-
-@joshgav: Can you clarify what is meant by “soft” and “hard” deprecation?
-@jasnell: "soft" means documentation only. "hard" means throw an error by default, or with command-line flag print a warning instead.
-
-@trott: Other question re deprecating constructors with `new` is not as clear. Do we need to figure this out now?
-
-@jasnell: Recommend waiting, it’s more nuanced.
-
-@addaleax: I agree. Maybe in v8.x.
-
-@trevnorris: We can’t flatly deprecate all use cases of `new Buffer(...)`.
-
-**Next steps**:
-
-* Land hard deprecation of `Buffer` without `new` now.
-* Other conversation continue in GH, remove ctc-agenda label.
-
----
-
-### fs: don't alter user provided `options` object [#7831](https://github.com/nodejs/node/pull/7831)
-
-@FishRock123: while using `util._extend` would be a semver-major break, does it actually break anything?
-
-@indutny: It’s just a side effect, not major.
-
-@FishRock123: should still be a semver-major change, but not something to worry about.
-
-@rvagg: We’ve landed these types of changes in the past without waiting for semver-major.
-
-@indutny takes back his words, it’s semver-major.
-
-@trott: Seems pretty low risk for a semver-major.
-
-@indutny: yes
-
-@trott: post comments in GH if you have concerns, otherwise semver-major change is okay. What else?
-
-@rvagg: This is just due diligence, there’s already use of utils._extend(...) in there.
-
-@chalker: why did we have a test which passed an `Object.create()`-ed options object to it? [No objections].
-
-**Next steps**:
-
-* CTC approved semver-major change. Remove ctc-agenda, continue with usual process.
-
----
-
-### fs: undeprecate existsSync; use access instead of stat for performance [#7455](https://github.com/nodejs/node/pull/7455)
-
-Action requested: Is it okay to undeprecate existsSync()?
-
-@Fishrock123: There is a use case for a file which exists but has no content - `.git/rebase-apply/rebasing`. Existence itself is a flag.
-
-Also includes change to use `fs.access`, I don’t think that’s reasonable.
-
-@rvagg: only undeprecates `existsSync`, not `exists`.
-
-@chalker: I’d be okay with that.
-
-@trott: Postpone till next week to allow for review?
-
-**Next steps**:
-
-* First item on next week’s agenda.
-
----
-
-### doc: add Google Analytics tracking. [#6601](https://github.com/nodejs/node/pull/6601)
-
-@FishRock123: Was this fixed to not include GA for local usage?
-
-@chalker: Ben isn’t here and has opinions.
-
-@rvagg: Marketing and web site team want analytics to understand how docs are used. The objections are about user privacy, and there was a suggestion that we manage our own analytics. But there was a non-trivial cost.
-
-@rvagg: Only for the online docs, not the tarball etc. I’m okay with this.
-
-@trott: It’s a legitimate need for access, I have no concerns.
-
-@trevnorris: Is this to put analytics tracking inside the docs repo?
-
-@Fishrock123: PR replaces a line and puts in the GA link/script.
-
-@rvagg: Has to be included via a special flag to make. Will only be set when building for web site.
-
-@misterdjules: A DNT flag has been added too, that may address some concerns.
-
-@Chalker: DNT flag makes this acceptable. What will we use the stats for? To improve docs?
-
-See <https://github.com/nodejs/node/pull/6601#issuecomment-224002869>
-
-@rvagg: My only concern is moving forward without @bnoordhuis, who was the main holdout based on strong privacy objections.
-
-@indutny: I don’t like the idea of being tracked. Considering that other parts of web site do tracking it may be more acceptable. An important question is what people will have access to these statistics? Has it been made clear?
-
-@rvagg: Good question. Probably at least @mikeal.
-
-@trott: Raise these questions in GitHub. We’ll put this back on the agenda for a quick resolution next week.
-
-**Next steps**:
-
-* Raise above questions and discuss in GH.
-* Review for quick resolution next week.
-
----
-
-### Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-
-Defer to next week when @thealphanerd is back.
-
-**Next steps**:
-
-* Defer to next week.
-
----
-
-### Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-
-@rvagg has action to follow up, particularly on LICENSE file.
-
-**Next step**:
-
-* @rvagg to remove `ctc-agenda` label
-
----
-
-### Landing node-eps for ABI stable module and location for PoC code [#28](https://github.com/nodejs/api/issues/28)
-
-@mhdawson: EP has a view of what we’re trying to do, it’s definitely not the final version. But having it only as a PR makes it harder for others to collaborate on it. Can we merge it in draft status? Or perhaps move to another forum where we can collaborate more easily?
-
-@misterdjules: Node-EPs repo says it’s okay to commit a draft.
-
-@mhdawson: Then I’ll do that.
-
-@mhdawson: Progress on POC code in a personal GitHub org, would like to put somewhere more visible, such as a repo in github.com/nodejs, or a branch in github.com/nodejs/node.
-
-@Fishrock123: Maybe we should consolidate all experimental stuff (e.g. this, HTTP/2) in a nodejs/experimental repo?
-
-@misterdjules: Are there concerns with new branches on main repo?
-
-@Fishrock123: If there will be a lot of PRs and issues related to this branch it may block up the issue tracker.
-
-@mhdawson: Issues will continue in nodejs/api repo.
-
-@indutny: I don’t want to establish a precedent of having experimental branches in main repo. We had problems in past with cleaning these up. Having in a separate repo should simplify things.
-
-@mhdawson: Would nodejs/node-experimental make sense, with different branches for different features?
-
-@misterdjules: better not to centralize a lot of unrelated branches in a single repo.
-
-@jasnell: do the same as I did for HTTP/2 repo, fork from nodejs/node into a new repo within github.com/nodejs.
-
-@mhdawson: I’ll create another repo within github.com/nodejs.
-
-**Next steps**:
-
-* @mhdawson to commit draft to Node-EPs repo.
-* @mhdawson to create another repo for ABI-stable work.
-
-### Other:
-
-Modules meeting: <http://doodle.com/poll/s4gcm28vmrdd3bqd>
-
-## Q/A on public channels
-
-None
-
-## Upcoming Meetings
-
-* CTC: 2016-08-31
-* TSC: 2016-08-25
-* Benchmarking: [Benchmarking#56](https://github.com/nodejs/benchmarking/issues/56)
-* Build:
-* LTS:
-* Diagnostics:
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-08-31.md b/doc/ctc-meetings/2016-08-31.md
deleted file mode 100644
index 0b73e07ef635d6..00000000000000
--- a/doc/ctc-meetings/2016-08-31.md
+++ /dev/null
@@ -1,315 +0,0 @@
-# Node Foundation CTC Meeting 2016-08-31
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8330](https://github.com/nodejs/node/issues/8330)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1qYUOfiiytaZ0-YZVZ1NZX9O-4SE28QNooapOdcjlPqA>
-* _Previous Minutes Google Doc_: <https://docs.google.com/document/d/1mkOUQ-M3s6zV2ige00hj6IIlT5oGQcw1USeliRqRDSk>
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Fedor Indutny @indutny (CTC)
-* James M Snell @jasnell (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-* Rod Vagg @rvagg (CTC)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Couple of own PRs
-  * Segfault issue in V8
-  * Issues & PR review
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Going around sorting out the modules rewrite / explaining to people
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Some work on the npm codesearch tool
-  * Usual comments on issues and PRs
-* Evan Lucas @evanlucas (CTC)
-  * v6.5.0 release
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Module discussions
-  * Reviewing promises warning & other PRs.
-  * Discovered more odd stdio related quirks.
-* Fedor Indutny @indutny (CTC)
-  * Issues and PRs, nothing new
-* Josh Gavant @joshgav (observer/Microsoft)
-  * Some work on debugging docs.
-  * Plan next Diag WG meeting.
-* Michael Dawson @mhdawson (CTC)
-  * Addons on test issues on AIX
-  * Adding PPC machines from new cluster at OSUOSL
-  * Adding AIX machines from OSUOSL
-  * Adding linxuOne machine to release CI
-  * Initial discussion on codecoverage.nodejs.org
-  * Preparing for Node Interactive presentations (build WG update
-    Post-mortem WG update)
-  * General PR review/land/keeping up with issues
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-  * board meeting stuff from Monday
-  * getting things together for TC39 meeting
-* Brian White @mscdex (CTC)
-  * Landed a couple of old PRs
-  * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * V8 5.1 and 5.4 related issues.
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-  * Observing for the Node.js Foundation newsletter
-* Rod Vagg @rvagg (CTC)
-  * Node Foundation Board business (incl Board meeting), lots of Build WG work incl major ARM cluster cleanup, OSX resource chasing, clang 3.4.1 CI node, blog post
-* Trevor Norris @trevnorris (CTC)
-  * Finishing async_hooks implementation
-  * Few PR reviews
-  * Posted issue about --prof not working on win x64 (when processing isolate*.log w/ --prof-process)
-* Rich Trott @Trott (CTC)
-  * Onboarded @lpinca and @danbev
-  * Helped a few first-time and second-time committers, looking to do that more
-  * Trying to get CI green again, even ventured into C++/crypto land for a tiny change. #OutOfMyComfortZone Please review: https://github.com/nodejs/node/pull/8352
-* James M Snell @jasnell (CTC)
-  * prs, issues, doc updates
-  * Preparing for v7
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* Process for determining supported platforms [#8265](https://github.com/nodejs/node/issues/8265)
-* child_process, win: fix shell spawn with AutoRun [#8063](https://github.com/nodejs/node/pull/8063)
-* fs: undeprecate existsSync; use access instead of stat for performance [#7455](https://github.com/nodejs/node/pull/7455)
-* doc: add Google Analytics tracking. [#6601](https://github.com/nodejs/node/pull/6601)
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-* Move ecosystem detection tool to nodejs org [#7935](https://github.com/nodejs/node/issues/7935)
-
-### nodejs/node-eps
-
-* AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-
-## Previous Meeting Review
-
-* CTC membership nomination: @TheAlphaNerd [#8058](https://github.com/nodejs/node/issues/8058)
-  * @rvagg to onboard @thealphanerd.
-* buffer: hard-deprecate Buffer constructor [#7152](https://github.com/nodejs/node/pull/7152)
-  * Land hard deprecation of `Buffer` without `new` now.
-  * Other conversation continue in GH, remove ctc-agenda label.
-* fs: don't alter user provided `options` object [#7831](https://github.com/nodejs/node/pull/7831)
-  * CTC approved semver-major change. Remove ctc-agenda, continue with usual process.
-* fs: undeprecate existsSync; use access instead of stat for performance [#7455](https://github.com/nodejs/node/pull/7455)
-  * First item on next week’s agenda.
-* doc: add Google Analytics tracking. [#6601](https://github.com/nodejs/node/pull/6601)
-  * Raise above questions and discuss in GH.
-  * Review for quick resolution next week.
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-  * Defer to next week.
-* Seek legal advice on LICENSE and copyright blocks in code [#3979](https://github.com/nodejs/node/issues/3979)
-  * @rvagg to remove `ctc-agenda` label
-* Landing node-eps for ABI stable module and location for PoC code [#28](https://github.com/nodejs/api/issues/28)
-  * @mhdawson to commit draft to Node-EPs repo.
-  * @mhdawson to create another repo for ABI-stable work.
-
-## Minutes
-
-* fs: undeprecate existsSync; use access instead of stat for performance [#7455](https://github.com/nodejs/node/pull/7455)
-
-@Fishrock123: No further discussion from us this past week.
-Person who submitted PR analyzed `access` with F_OK flag but that didn’t reveal anything.
-If we are to undeprecate something it needs CTC signoff.
-
-@Trott: Is anyone strongly in favor?
-@trevnorris: No super compelling reason for leaving it out, especially since this is something which has had a lot of community push to keep in.
-
-@rvagg: This one needs a CTC or Collaborator champion to move it through, otherwise it will continue to be stalled.
-
-@joshgav: Should we have someone come and present the case to the CTC?
-@jasnell: That could be helpful.
-@Fishrock123: All the cases are laid out in the thread.
-
-@rvagg: Without a champion it won’t move forward. We need to ping collaborators and seek someone particularly interested.
-
-@trevnorris: Code and tests are there. Do we need someone to come and make the argument?
-@rvagg: Someone needs to come and do the convincing.
-@trevnorris: There are people religiously opposed to this, no argument could win them over. I don’t have time to make all those arguments.
-@mikeal: We can move to a vote then.
-
-@trott: Let’s ping nodejs/collaborators to see if anyone feels very strongly in favor of `existsSync` and see where that lands, then look at this again in a week. If no one stands up for the case than whether just or not it’s dead in the water.
-
-@rvagg: We can also have a vote here and just bring it down to proper voting.
-
-@addaleax: @williamkapke suggested discussing this at the Collaboration Summit.
-
-**Next steps**:
-
-* @trott to ping nodejs/collaborators in that thread.
-* If no response raise for vote next week or close.
-
-
-### doc: add Google Analytics tracking. [#6601](https://github.com/nodejs/node/pull/6601)
-
-@mikeal: People with access would be web site admin team and internal foundation employees.
-
-@trott: We wanted to wait for @bnoordhuis to give input. But he’s not here again this week. Should we table?
-
-@mikeal: No argument about value of this data, argument about which tool to use. But no alternative has been proposed.
-
-@rvagg: We gave warning that we’d come back to it this week. We’re back so now it’s time to vote.
-
-@indutny: My questions are answered, I don’t have any objections.
-
-@trott: Anyone opposed to moving to a vote?
-
-**Vote**:
-
-* Yes: 9 (Rich Trott, Ali Sheikh, Evan Lucas, Anna Henningsen, Fedor Indutny, Rod Vagg, James Snell, Michael Dawson, Trevor Norris)
-* No: 0
-* Abstain: 3 (Brian White, Сковорода Никита, Jeremiah Senkpiel)
-
-**Next steps**:
-
-* Merge!
-
-
-### Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-
-@trott: No rush, propose tabling another week to wait for @thealphanerd.
-
-@evanlucas: Myles made his position pretty clear. At first I didn’t care either way, but after the last release it was difficult to not have a staging branch to build out on. I had built binaries and then something was added and I had to go back.
-
-@jasnell: Most people who have done releases recently have come out in favor of this or at least not said absolutely not. We can try it and if it’s too much process we can go back to the way we’re doing it now.
-
-@rvagg: I like Myles argument about consistency and helping people onboard. Agree with James that this is up to those doing releases. If they want this, so be it.
-
-@Fishrock123: Consistency argument is reasonably compelling, but I thought that wasn’t the case.
-
-**Vote**:
-
-Aye: 11 (Jeremiah Senkpiel, Evan Lucas, Ali Sheikh, Anna Henningsen, Rich Trott, Rod Vagg, Trevor Norris, Brian White, Nikita, Fedor Indutny, Michael Dawson, James Snell)
-Nay: 0
-Abstain: 0
-
-**Next steps**:
-
-* Do this as proposed.
-
-
-### Process for determining supported platforms [#8265](https://github.com/nodejs/node/issues/8265)
-
-@rvagg: Build working group should build a list and we can start from there. Next Build WG meeting is in 3 weeks.
-
-@rvagg: Not just about platforms, but many permutations of plats and arch’s.
-
-**Next steps**:
-
-* Build WG will prepare initial list of supported platforms in their next meeting.
-* Then CTC will review and decide next steps.
-
-
-### child_process, win: fix shell spawn with AutoRun [#8063](https://github.com/nodejs/node/pull/8063)
-
-@joshgav: Someone filed a bug to not respect registered autorun programs in Windows cmd spawned from Node.
-
-@rvagg: Others asked what other runtimes do, e.g. Python.
-Seems to me if you have something in the autorun then we should respect that.
-
-@joshgav: Probably Microsoft would argue against bypassing something configured to autorun.
-
-@rvagg: We don’t have sufficient expertise here to decide. Was brought to CTC because it’s semver-major.
-
-**Next steps**:
-
-* Remove from CTC agenda.
-* @joshgav to check for opinions within Microsoft.
-* Ask @joaocgreis in GitHub for more explanation.
-
-
-### Move ecosystem detection tool to nodejs org [#7935](https://github.com/nodejs/node/issues/7935)
-
-@Chalker: Now it’s completely in JavaScript and it has documentation to allow people to use it, so I think it’s ready for moving in.
-
-@trott: In the issue I see only supportive voices. Any questions or concerns?
-
-@Fishrock123: Chris Dickinson (@chrisdickinson) did some work on making an indexer that could track code paths (?). Just an aside, it’d be nice to get his opinion.
-
-@Chalker: This doesn’t use any database, it uses plain text and json files compressed with lz4.
-
-@trott: Move to a vote?
-
-@rvagg: Who would take responsibility for this? Directly under CTC? It’s own maintenance group? For example if there are controversial issues to resolve are they resolved by the CTC.
-
-@Chalker: Not sure.
-
-@rvagg: CTC probably doesn’t want to own this, so probably needs its own team/WG, and that should be in the README at least.
-
-@mhdawson: Probably needs LICENSE, CONTRIBUTORS, etc. We’ve asked others to add those in, then open an issue in nodejs/tsc, then we move it over.
-
-@rvagg: That seems absolutely right. Prepare it and put it on TSC repo. Ping @williamkapke for help if you need.
-
-@mhdawson: Also node-report is an example of this exercise done recently, you can learn from that.
-
-@trott: Any objections to this?
-
-**Next steps**:
-
-* Prep repo for migration.
-* Open issue in nodejs/tsc.
-
-
-### AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-@trevnorris: Updated the EP some, updating again now. There was an API which was useless. Happy with progress, 80% of the way there. Will keep working on it, put up for review tomorrow morning. Other than that one change of removal of API it’s pretty much on point.
-
-@rvagg: There was a question about renaming the API.
-
-@trevnorris: The name ‘AsyncWrap’ is an implementation “leak”. So I’ve renamed it “async_hooks”. Want to verify that CTC is okay with name change.
-
-@Fishrock123: A lot of new things have been added since CTC last reviewed.
-
-@rvagg: Let’s bring this up again next week with a clear request for a vote.
-Where is the code for review?
-
-@trevnorris: cannot be done in pieces, it’s an all-or-none thing.
-
-@joshgav: Do we want this to land before v7?
-
-@Fishrock123: It’s semver-minor, so not a big deal.
-
-@trevnorris: Plan was to get this in before v6 goes LTS. When is that?
-
-@jasnell: mid to late October.
-
-**Next steps**:
-
-* Trevor to update all code and ask for vote on specific item(s).
-* CTC to review again once complete.
-
-
-## Q/A on public channels
-
-None.
-
-
-## Upcoming Meetings
-
-* CTC: 2016-09-07
-* TSC: 2016-09-08
-* Benchmarking: [Benchmarking#56](https://github.com/nodejs/benchmarking/issues/56)
-* Build:
-* LTS:
-* Diagnostics:
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-09-07.md b/doc/ctc-meetings/2016-09-07.md
deleted file mode 100644
index 15dfffcb1fe30f..00000000000000
--- a/doc/ctc-meetings/2016-09-07.md
+++ /dev/null
@@ -1,245 +0,0 @@
-# Node Foundation CTC Meeting 2016-09-07
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8425](https://github.com/nodejs/node/issues/8425)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1GRgBC5Dv5luqlRc6egtxmkrQULJXa3M3CqGqWfoogV8>
-* _Previous Minutes Google Doc_: <https://docs.google.com/document/d/1qYUOfiiytaZ0-YZVZ1NZX9O-4SE28QNooapOdcjlPqA>
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Julien Gilli @misterdjules (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Rod Vagg @rvagg (CTC)
-* Seth Thompson @s3ththompson (observer/Google)
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-* Myles Borins @TheAlphaNerd (CTC)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Issues & PR review
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Just emails around modules
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Some private ecosystem things
-* Evan Lucas @evanlucas (CTC)
-  * opened PR for adding back --harmony-proxies flag, not much else
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Working on v6.6.0
-  * issue & PRs, Async_Wrap review, some Timers PRs.
-* Fedor Indutny @indutny (CTC)
-  * Reviewing PRs & Fixing bugs (sorry for not joining you today)
-* Josh Gavant @joshgav (observer/Microsoft)
-  * Issues and PRs
-* Michael Dawson @mhdawson (CTC)
-  * Investigating and PRs to move AIX to green in CI
-  * Migration to new set of PPC machines
-  * Addition of linuxOne to nightlies
-  * Moved API work to nodejs/abi-stable-nodenodejs/abi-stable-node-addons-examples
-  * presentations for Node Interactive EU
-* Brian White @mscdex (CTC)
-  * Worked on finding improvements in http code
-  * Commented on issues, reviewed PRs
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Wrangle some V8 backports.
-  * Looking at performance w/ new ignition interpreter
-* Rod Vagg @rvagg (CTC)
-  * Raspberry Pi cluster hardware problems, blog post
-* Seth Thompson @s3ththompson (observer/Google)
-  * V8 team working on Ignition interpreter and V8 Inspector migration
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-  * PRs.
-* Myles Borins @TheAlphaNerd (CTC)
-  * Auditing commits for v4.x
-  * Modifying output of testrunner
-  * preparing for interactive EU
-* Trevor Norris @trevnorris (CTC)
-  * AsyncHook (formerly known as AsyncWrap); update embedder API to improve performance
-* Rich Trott @Trott (CTC)
-  * Backporting a few small commits to v4.x
-  * Updating Build and Onboarding docs based on contributor mentoring and onboarding activities
-  * A few test PRs designed to increase test coverage
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* src: add no-op for --harmony-proxies flag [#8395](https://github.com/nodejs/node/pull/8395)
-
-### nodejs/node-eps
-
-* AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-
-
-## Previous Meeting Review
-
-* Process for determining supported platforms [#8265](https://github.com/nodejs/node/issues/8265)
-  * Build WG will prepare initial list of supported platforms in their next meeting.
-  * Then CTC will review and decide next steps.
-
-* child_process, win: fix shell spawn with AutoRun [#8063](https://github.com/nodejs/node/pull/8063)
-  * Remove from CTC agenda.
-  * @joshgav to check for opinions within Microsoft.
-  * Ask @joaocgreis in GitHub for more explanation.
-
-* fs: undeprecate existsSync; use access instead of stat for performance [#7455](https://github.com/nodejs/node/pull/7455)
-  * @trott to ping nodejs/collaborators in that thread. If no response then [fix].
-
-* doc: add Google Analytics tracking. [#6601](https://github.com/nodejs/node/pull/6601)
-  * Merge!
-
-* Introduce staging branch for stable release streams [#6306](https://github.com/nodejs/node/issues/6306)
-  * Do this as proposed.
-
-* Move ecosystem detection tool to nodejs org [#7935](https://github.com/nodejs/node/issues/7935)
-  * Prep repo for migration.
-  * Open issue in nodejs/tsc.
-
-* AsyncWrap public API proposal [#18](https://github.com/nodejs/node-eps/pull/18)
-  * Trevor to update all code and ask for vote on specific item(s).
-  * CTC to review again once complete.
-
-
-## Minutes
-
-### src: add no-op for --harmony-proxies flag [#8395](https://github.com/nodejs/node/pull/8395)
-
-We upgraded to V8 5.1 in v6.5. That removed several flags, notably the --harmony-* flags. Many in the ecosystem have hard-coded these flags and as a result are getting errors since v6.5.
-
-@evanlucas added a PR to no-op those flags. There was quite a bit of resistance to that, as it implies that we apply semver semantics to experimental features.
-
-@addaleax: Does anyone have concrete reason to not no-op these flags?
-
-@trott: For clarity, do we mean to no-op them till the next semver-major release?
-
-@addaleax: Yes.
-
-@Fishrock123: This would only ever land in v6.
-
-@evanlucas: Some feel this should be floated on V8.
-
-@trevnorris: Could they?
-
-@ofrobots: Trivial to do it, but this is on 5.1 which is an abandoned upstream.
-
-@trevnorris: We were told we could re-open abandoned branches?
-
-@ofrobots: That’s correct.
-
-@? : Were the flags removed because their behavior is V8's default?
-
-@ofrobots: Yes, support was already there but flags had not yet been removed.
-
-@? : Other flags were removed too.
-
-@addaleax: Main issue is the --harmony flags, I haven’t seen the other flags as issues.
-
-@ofrobots: I’m supportive of adding no-ops for --harmony flags cause they break the ecosystem. Others no.
-
-@Fishrock123: What about strong mode flags?
-
-@ofrobots: Mainstream users are not likely to be using strong mode flags.
-
-@ofrobots: The ones recommended as no-ops I agree should be added back as no-ops.
-
-@rvagg: We can adopt a new policy if we want, for example state that when we upgrade V8 flags may change and you have to do feature detection to address that.
-
-@addaleax: Seems to be that’s what some people want in comments, but it seems that it might not be what people expect.
-
-@rvagg: Many flags unlikely to be used in real code, but some may be used in production code. Ones that are potentially usable in production code, sure.
-
-@trevnorris: Let’s re-add the no-ops and see if people raise issues about the others.
-It would be more pure to backport in V8, but I don’t see why floating it in Node would be an issue.
-
-@addaleax: @bnoordhuis was strongly -1 on floating a patch on V8, but didn’t give a reason.
-
-@misterdjules: what do we mean by floating a patch?
-
-@trevnorris: we don’t even have to let these through to V8, just catch it ourselves.
-
-@Fishrock123: That would be harder.
-
-@ChALkeR: perhaps warn in runtime on unsupported flags for next major?
-
-@rvagg: Colin and Ben had negative positions.
-Is proposal to ask Ali to move forward in V8?
-
-@addaleax: Not expecting a definite decision, hoping to hear from people who are -1. Would be happy if someone put together a PR with all the flags we want to no-op and discuss in next meeting if necessary.
-
-@trev: How long to get a patch on the V8 branch?
-
-@ofrobots: Probably not too long, dependent on me finding a half hour.
-This will be a patch we float on our downstream of V8 5.1. We are the de facto owners of this branch now.
-
-@rvagg: Open a PR, move discussion there, people with negatives can expand on them there.
-
-**Next steps**:
-
-* @ofrobots to float a patch on our branch of V8 5.1 and open a PR. Discussion to continue there.
-* Keep on agenda for next week just in case.
-
-
-### AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-
-@trevnorris: EP is near 100% ready, only thing likely to change is the native C++ API but after doing testing and implementation it’s where it needs to be for all of the goals set for it.
-
-@rvagg: We need to sign off on the EP. Can’t do that today, right?
-
-@trevnorris: No, but EP is there. I’ve updated it with code, examples, stuff like that.
-
-@rvagg: Will there be changes in node-eps#18 between now and next week?
-
-@trevnorris: No, unless some major change comes in.
-
-@trevnorris: No docs yet, Bradley has volunteered.
-
-@rvagg: There will eventually be a discussion of backporting to V4.
-
-@trevnorris: Discussion continues on promise side.
-
-@rvagg: cause we don’t have insight into the microtask queue?
-
-@trevnorris: Yes. It’s proceeding.
-
-@seththompson: V8 team is interested in helping with this. Looks like async/await won’t make cut for v7, gives us more time to work on the right thing here.
-
-**Next steps**:
-
-* Everyone read [node-eps#18](https://github.com/nodejs/node-eps/pull/18).
-* Vote next week on Node-EP.
-* Open a PR for implementation in nodejs/node.
-
-
-### Modules
-
-@bmeck: There were several concerns about the rewritten EP for ES6 module compat. Note that we haven’t merged that yet, people are welcome to comment in that issue.
-
-@rvagg: Those who are concerned should definitely get in touch with Bradley (@bmeck).
-
-
-## Q/A on public channels
-
-* Thanks for the heads-up on async/await.
-
-
-## Upcoming Meetings
-
-* CTC: 2016-09-14
-* TSC: 2016-09-08
-* Benchmarking: [Benchmarking#56](https://github.com/nodejs/benchmarking/issues/56)
-* Build: 2016-09-20
diff --git a/doc/ctc-meetings/2016-09-14.md b/doc/ctc-meetings/2016-09-14.md
deleted file mode 100644
index bb8645f65cf52f..00000000000000
--- a/doc/ctc-meetings/2016-09-14.md
+++ /dev/null
@@ -1,153 +0,0 @@
-# Node Foundation CTC Meeting 2016-09-14
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8506](https://github.com/nodejs/node/issues/8506)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1kW9wLdfojpIGbu3fQMrtr7S_RJFq8CWupoKnmtWw17Q>
-* _Previous Minutes Google Doc_: <https://docs.google.com/document/d/1GRgBC5Dv5luqlRc6egtxmkrQULJXa3M3CqGqWfoogV8>
-
-## Present
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Julien Gilli @misterdjules (CTC)
-* Brian White @mscdex (CTC)
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-* Rod Vagg @rvagg (CTC)
-* Seth Thompson @s3ththompson (observer/Google)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-    * Synched up with more people about ES Modules
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-    * Mostly nothing this week.
-* Evan Lucas @evanlucas (CTC)
-    * Commented on issues/prs
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-    * v6.6.0 Release WIP
-    * ES Modules discussions
-    * Misc PRs / Issues
-    * Async_Hooks review / Thinking
-* Josh Gavant @joshgav (observer/Microsoft)
-    * Diag WG activity
-    * modules discussion
-* Julien Gilli @misterdjules (CTC)
-    * Timers code reviews and investigating/fixing libuv bugs on SmartOS. Read Async Hooks EP.
-* Brian White @mscdex (CTC)
-    * Investigated UDP performance again for the purposes of a JS DNS resolver. With a few tweaks/optimizations, we can at least achieve performance very close to c-ares.
-    * Reviewed PRs, commented on issues
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-    * Observing, no update.
-* Rod Vagg @rvagg (CTC)
-    * Travel, administrative, board, TSC, meetings, yabba yabba
-* Seth Thompson @s3ththompson (observer/Google)
-    * v8_inspector move to v8 is almost done, builds in tree now
-    * continued discussion on microtask queue inspection here: https://bugs.chromium.org/p/v8/issues/detail?id=4643
-* Trevor Norris @trevnorris (CTC)
-    * async_hooks. submitted PR and updated EP.
-* Rich Trott @Trott (CTC)
-    * Onboarded @not-an-aardvark (with @addaleax’s help), @imyller, and @gibfahn
-    * ESLint update (replaced a custom rule with a built-in), test PRs, doc PRs
-    * A burst of first-time-contributor PRs landed, woo hoo
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-* AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-
-
-## Previous Meeting Review
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-* src: add no-op for --harmony-proxies flag [#8395](https://github.com/nodejs/node/pull/8395)
-
-    * @ofrobots to float a patch on our branch of V8 5.1 and open a PR. Discussion to continue there.
-    * Keep on agenda for next week just in case.
-
-* AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-
-    * Everyone read [node-eps#18](https://github.com/nodejs/node-eps/pull/18).
-    * Vote next week on Node-EP.
-    * Open a PR for code in nodejs/node.
-
----
-
-## Minutes
-
-### AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-
-PR: [#8531](https://github.com/nodejs/node/pull/8531)
-
-@trott: move to vote on the EP. Anything to discuss first?
-
-@rvagg: One thing Trevor adjusted since discussion - some desire to have hooks that execute on one execution branch. Trevor can describe.
-
-@trevnorris: if you were to enable a hook, run an async op, then disable the hook, any ops that took place during time when it was enabled will continue to have hooks called for them even after it’s disabled.
-
-This was okay, I could’ve managed it, but `nextTick` alone increases the amount of hooks to be processed 3x.
-
-**Votes**
-
-* Yes     - 7 - @rvagg, @evanlucas, @Chalker, @Fishrock123, @trevnorris, @mscdex, @trott
-* No      - 0
-* Abstain - 1 - @misterdjules
-
----
-
-### Other
-
-@Chalker: Perhaps we should discuss GitHub functionality changes, such as the review capability in the web interface.
-
-@trott: Open a PR to discuss. It could make fixing up the commit message simpler.
-
----
-
-## Q/A on public channels
-
-Q: @williamkapke: Live CTC meeting in Austin? [tsc#137](https://github.com/nodejs/tsc/issues/137)
-
-A: @rvagg: More people probably and a good time too.
-
-Q: What’s the status of ES6 modules? What’s the team’s personal opinion on that?
-
-@Fishrock123: Mostly kept up in Node-EP 002 and related PRs. Some of us and @bmeck will be going to TC39 meeting at end of Sept. and have materials prepared to discuss problems we’re facing.
-
-@trott: My personal opinion is that I hope we can work with TC39 and get alterations such that we can avoid `.mjs` extension, but if that doesn’t happen the `.mjs` extension isn’t ideal but I do believe that it’s better than other options.
-
-@rvagg: My personal opinion is that we are unfortunately trapped in a tough corner where TC39 has created a spec which has technical problems for Node and we’ve had difficulty getting them to hear our concerns. They’d like us to make changes on our side and that would be enough, but that’s quite complicated.
-
-We have many users who like the idea of modules, but they’re actually transpiled versions and not implemented by browsers.
-
-@trott: I’m optimistic that things will work out well. I have a lot of faith in Bradley, Jeremiah, et al.
-
-@Fishrock123: No browser / VM has this fully implemented yet. V8 would have to implement it first and it definitely won’t be done for Node.js v7.
-
-@bmeck: Chakra’s impl is basically done for `type=module` spec in the browser, but that would drastically change if we went to TC39 and they changed the behavior.
-
-@Chalker: Edge has modules in a preview release.
-
-@Fishrock123: That’s Chakra, yes.
-
-@rvagg: There will be a talk at Node Interactive Austin by Bradley, you should attend there. (CTC call at the same time, we might need to think about whether to have CTC call that day.)
-
-
-## Upcoming Meetings
-
-* CTC: 2016-09-21
-* TSC: 2016-09-22
-* Build: 2016-09-20
-* Diagnostics: 2016-09-21
-* Benchmarking: 2016-09-21? [Benchmarking#56](https://github.com/nodejs/benchmarking/issues/56)
-* LTS:
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-09-21.md b/doc/ctc-meetings/2016-09-21.md
deleted file mode 100644
index f46300536869d9..00000000000000
--- a/doc/ctc-meetings/2016-09-21.md
+++ /dev/null
@@ -1,218 +0,0 @@
-# Node Foundation CTC Meeting 2016-09-21
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8656](https://github.com/nodejs/node/issues/8656)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1-PS20PGCJQIi4_quBHqVgrQNJeJP10NH21wUelcMhfw>
-* _Previous Minutes Google Doc_: <https://docs.google.com/document/d/1kW9wLdfojpIGbu3fQMrtr7S_RJFq8CWupoKnmtWw17Q>
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Fedor Indutny @indutny (CTC)
-* James M Snell @jasnell (CTC)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Myles Borins @TheAlphaNerd (CTC)
-* Rich Trott @Trott (CTC)
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-* Seth Thompson (observer/Google)
-* Jenn Turner (observer/Node Foundation)
-* Josh Gavant (observer/Microsoft)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-    * Node Interactive EU
-    * In particular, Code & Learn
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-    * Filed some PRs regarding doc linting
-    * Some issue comments and PR reviews as usual
-* Evan Lucas @evanlucas (CTC)
-    * Working on an EP for exposing is* methods from core
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-    * async_hooks review
-    * v6.6.0 release
-* Fedor Indutny @indutny (CTC)
-    * PRs, regular/security issues, Node.js Interactive!
-* James M Snell @jasnell (CTC)
-    * Node Interactive EU/Collab summit
-    * Reviewing PRs (primarily from the code n learn)
-    * Preparing v7.0.0-beta1 (built now!)
-    * Preparing for TC-39 meeting next week
-    * Continued work on HTTP/2 plan
-* Michael Dawson @mhdawson (CTC)
-    * Node Interactive EU/Collaborators summit
-    * New PPC machines into CI
-    * Addition of LinuxOne and AIX to nightlies
-    * build WG meeting, benchmarking WG meeting
-    * Investigating an AIX issues
-    * Some work on ABI stable API
-    * Catching up on issues
-* Brian White @mscdex (CTC)
-    * Performance testing for various things
-    * Submitted PRs to improve setImmediate() and setTimeout()/setInterval() performance
-    * Submitted alternative PR to fix the malloc(0) compatibility issue introduced in node v6.6.0
-    * Worked on other various potential optimizations in core
-    * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-    * Mostly busy with internal stuff; work with some inspector PRs; finishing up V8 guide.
-* Myles Borins @TheAlphaNerd (CTC)
-    * Node Interactive EU / Collab Summit
-    * Work on new tap reporter
-    * Reviewing @ofrobots work on V8 guide
-    * LTS backporting work
-* Rich Trott @Trott (CTC)
-    * Onboarded @ak239 and @eugeneo
-    * assorted test, tools, and doc PRs
-    * https://github.com/nodejs/node/pull/8572 (Malloc and Calloc with size 0) to fix https://github.com/nodejs/node/issues/8571 (node::PBKDF2() Out of Memory) to land imminently, please take a look
-    * looking at the recent uptick in test failures, trying to figure out ways to fix it systemically and avoid it from recurring
-    * CTC meeting time proposal: more work than you think, trust me
-* Seth Thompson @s3ththompson (observer/Google)
-    * continued v8_inspector work
-
-## Agenda
-
-* deps: update V8 to 5.4 [node#8317](https://github.com/nodejs/node/pull/8317)
-* Scheduling Meetings [ctc#14](https://github.com/nodejs/CTC/issues/14)
-* Decide on what problem points for ES Modules we care about the most. [ctc#15](https://github.com/nodejs/CTC/issues/15)
-
-## Previous Meeting Review
-
-* AsyncWrap public API proposal [node-eps#18](https://github.com/nodejs/node-eps/pull/18)
-    * Merge.
-
-
-## Minutes
-
-@trott: removed the async_hooks EP from the agenda, if anybody has concerns, the place for that would be on Github, or if necessary the item can be put on the agenda again.
-
-### deps: update V8 to 5.4 [#8317](https://github.com/nodejs/node/pull/8317)
-
-@ofrobots: V8 5.4 is part of Chrome beta. Since we’re trying to release v7.x with V8 5.4 I think it would be best to land this in master now rather than close to release.
-
-Traditionally we’ve only landed V8 once it goes stable, but in this particular instance I think it’s important cause of 7.0 and this beta lining up so closely.
-
-@Fishrock123: Original reason why we only landed stable was because in io.js we were landing beta, but the V8 team warned us that things could change, and they did change.
-
-Did these things change on the V8 end? How is this different than yesterday?
-
-@ofrobots: Google is saying we shouldn’t *ship* a V8 beta. It’s in master so it can undergo testing, but we wouldn’t ship it. Things could change but it doesn’t matter cause it’s just in master, we’re not shipping it.
-
-@Fishrock123: Do RC’s count as shipping this? Some people will expect not much breakage between RC and release.
-
-@jasnell: We’ve had issues where things are broken in master and people complain cause it’s broken in master even if it doesn’t go to releases.
-
-@ofrobots: Purpose of an RC is to say this is what we think we’re going to ship, intention is not to change. With V8, we’ll also have the intention not to change. If a bug is found which breaks the web and a change needs to happen then it would happen.
-
-@Seth: We treat beta as an RC in that respect.
-
-@myles: Re what @jasnell said about things on master, it’s about things landing on master which are experience breaking. We’ve already been testing with 5.4. We should just be ready to revert if there’s an experience-breaking problem.
-
-@Fishrock123: Good arguments, but we’re changing what we’re doing where we took a particular stance because people had issues with it.
-
-@jasnell: We took that stance before we had the improved release model, with LTS. Risk was much greater then than now.
-
-@trott: Any other voices?
-
-@jasnell: @Fishrock123 is this something you absolutely want to see?
-
-@Fishrock123: If there’s a vote I’ll just abstain.
-
-@trott: Seems we have consensus and don’t need to vote.
-
-@Fishrock123: Might as well try it again and see if it works.
-
-@jasnell: If anything comes up, V8 team please give us a heads up as early as possible.
-
-@ofrobots: one change that’s going to happen, is that since Node is going to use V8 5.4, we’re going to get v8_inspector into v8 and out of separate deps folder. This will make build and maintenance easier for Node.
-
-**Next steps**:
-
-- Do this and keep a careful eye.
-- Evaluate after this cycle and decide what to do in the future.
-
----
-
-### Scheduling Meetings [ctc#14](https://github.com/nodejs/CTC/issues/14)
-
-@trott: Raising for CTC awareness.
-
----
-
-### Decide on what problem points for ES Modules we care about the most. [ctc#15](https://github.com/nodejs/CTC/issues/15)
-
-@Fishrock123: Majority of problems we can see so far are in EP #002, also in CTC#15.
-
-Bradley’s been at this for almost a year trying to get better support for us and nothing’s really moved from the spec end. I kind of doubt it will but would like to push in that direction.
-
-Would be good to find out what the CTC and Collaborators care about. Focus on CTC cause it’s easier to get overall decision with a smaller group. There’s a lot to talk about.
-
-Hard to know what opinion I should have.
-
-@trott: Is the question: Assuming the spec does not change, what should we do?
-
-@Fishrock123: If we want to push the spec to changing for better compatibility, what do we want to push? Pushing on everything would be basically rewriting the entire spec…
-
-@jasnell: Another aspect of this, conversations with TC39 at multiple levels, not just technical but also process. Try to help TC39 understand and care about the issues. If there’s something to change, it’s something they should care about also.
-
-@Fishrock123: Still comes back to this list of issues. What do we want to tackle the most?
-
-TC39 meeting next week, a couple people are going to that, context around what CTC cares about would be helpful.
-
-@jasnell: TC39 is 9/27-29. We should have a call just for CTC to make sure all are on same page beforehand.
-
-@Fishrock123: While I agree with that, we still need a consensus from the CTC on where to focus. Do we care about loading modules, REPLs, wrapping modules.
-
-@trott: Anything in particular?
-
-@jasnell: All are breaking issues.
-
-@Fishrock123: We don’t break modules, but if a module moves to ESM they could break downstream modules.
-
-@joshgav: In particular cannot change modules after import, breaks mocks and APMs.
-
-@Fishrock123: For example, `graceful-fs` might not work at all.
-
-@jasnell: What are our goals to come away from TC39 meeting?
-
-@Fishrock123:
-* TC39 showing some amount of care for our problems.
-* Communication of those problems and some cooperation.
-* Look at delaying shipping dates so we don’t have a browser vendor war which exacerbates our problems.
-
-@trott: Encourage everyone to read the issue carefully, ask a bunch of questions, know that date of TC39 meeting is coming and we need one clear set of priorities. Everyone that can have an informed opinion on this should educate themselves and participate.
-
-@jasnell: Talked with some of the members of TC39. What they articulated is that not to expect sweeping changes be made just because we ask for them.
-
-Instead describe why the current spec is a problem, and if there are aspects which are incorrect or can be improved, it’s on us to make those changes.
-
-We can’t expect them to care. Ideally they’d care already. But we have to have a proposal - this is why the module spec is broken, in terms of “we can’t implement it and this is why.”
-
-@thealphanerd: Conversations on Twitter, biggest sentiment from TC39 is that there are individuals who do care and want to work with us on it. If we approach with that narrative we’ll likely have more progress.
-
-@jasnell: Definite sentiment that we should be able to make this work, just a matter of making the right case.
-
----
-
-## Q/A on public channels
-
-None.
-
-
-## Upcoming Meetings
-
-* CTC: 2016-09-28
-* TSC: 2016-09-22
-* Build:
-* Diagnostics: 2016-09-28
-* Benchmarking: 2016-09-21
-* LTS:
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-09-28.md b/doc/ctc-meetings/2016-09-28.md
deleted file mode 100644
index 81f4fb4482f840..00000000000000
--- a/doc/ctc-meetings/2016-09-28.md
+++ /dev/null
@@ -1,302 +0,0 @@
-# Node Foundation CTC Meeting 2016-09-28
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8802](https://github.com/nodejs/node/issues/8802)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1ZsLMM29guCBPGh7KhuhZEq6YQCKybiTfTUIXajTBalM/>
-* _Previous Minutes Google Doc_: <https://docs.google.com/document/d/1-PS20PGCJQIi4_quBHqVgrQNJeJP10NH21wUelcMhfw>
-
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-* Rod Vagg @rvagg (CTC)
-* Seth Thompson @s3ththompson (observer/Google)
-* Myles Borins @TheAlphaNerd (CTC)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * The usual, issues and PR reviews
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Some issue and PR comments and reviews as usual.
-  * Some more work on docs linting.
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewing issues and PRs.
-  * Evan Lucas @evanlucas (CTC)
-  * v6.7.0 release
-  * More work on types eps
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * Issue / PR Review … general stuff
-  * Working towards ES Modules prototype implementations with Chris Dickinson
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-  * getting the Outreachy info on website
-* Josh Gavant @joshgav (observer/Microsoft)
-  * helping bring in some new MS contributors
-  * scheduled diag meeting for next week
-* Michael Dawson @mhdawson (CTC)
-  * Finishing off PPC migration
-  * Fixing AIX issues when building from node-private
-  * Some work on ABI-stable node
-  * Misc PR review/lands
-  * Keeping up with issues
-  * Post-mortem nodereport review
-* Brian White @mscdex (CTC)
-  * Worked on various performance improvements in node core
-  * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Looking at node+V8 (5.5) integration build failures that seem related to recent parser improvements
-  * Investigating performance with the new interpreter
-  * Working with @matthewloring on FFI
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-  * No update, just observing
-* Rod Vagg @rvagg (CTC)
-  * Security releases, supposed to be on vacation
-* Seth Thompson @s3ththompson (observer/Google)
-  * async/await landed in V8 Tip of Tree. on track to ship with V8 5.5
-  * expect a doc from V8 language team on promise hook API to allow microtask introspection in the near future
-* Myles Borins @TheAlphaNerd (CTC)
-  * issue / pr review
-  * helping with security release
-  * backporting inspector
-  * auditing v4 backlog
-  * really have to get to that tap reporter
-  * coming up with outreachy mentor project
-* Trevor Norris @trevnorris (CTC)
-  * AsyncHooks
-* Rich Trott @Trott (CTC)
-  * mentoring more first-time contributors (via Node Todo)
-  * doc, test PRs
-  * ramping up a tiny bit on Build WG stuff, but just a tiny bit
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/CTC
-
-* Scheduling Meetings [#14](https://github.com/nodejs/CTC/issues/14)
-
-### nodejs/node
-
-* meta: update NODE_MODULE_VERSION to 51 [#8808](https://github.com/nodejs/node/pull/8808)
-* General v7.0.0 / v6 LTS Planning / Discussion
-
-
-## Previous Meeting Review
-
-* deps: update V8 to 5.4 [#8317](https://github.com/nodejs/node/pull/8317)
-* Scheduling Meetings [#14](https://github.com/nodejs/CTC/issues/14)
-* Decide on what problem points for ES Modules we care about the most. [#15](https://github.com/nodejs/CTC/issues/15)
-
-
-## Minutes
-
-### Scheduling Meetings [ctc#14](https://github.com/nodejs/CTC/issues/14)
-
-@trott: This is a status report. Initial proposal was to dive in and start rotating meetings. Some were on board, some were concerned. Nikita started Google spreadsheet to figure things out.
-
-One proposal is to move back one hour (12pm Pacific) which would be a mild improvement for Ben and Nikita.
-
-Input received from NA and EU but not Asia and Australia. Once we have that information we can figure out what might work.
-
----
-
-### meta: update NODE_MODULE_VERSION to 51 [#8808](https://github.com/nodejs/node/pull/8808)
-
-`process.versions.modules` == 48 for v6.7.0.
-
-Set in build script, we bump this number for each semver-minor. We’d update to 49, but Electron has been bumping in between, so we need to go to 51.
-
-@thealphanerd: Had a way to do this in the past, but never landed a version of V8 on master [before a release]. So those using master cannot rely on this check.
-
-Proposal is to add this to master now and v7.x when released. But should we wait to bump till the actual release?
-
-@rvagg: If you’re using master, it’s been a bit “buyer beware” in the past.
-
-@thealphanerd: Node-pre-gyp uses the module version number to determine whether to pull the pre-built binary or to rebuild. So that’s causing problems.
-
-@ofrobots: Is there a disadvantage to doing this now?
-
-@rvagg: Doesn’t seem to be.
-
-@joshgav: Any concern that we’d have to bump again at v7.x release?
-
-@rvagg: We’ll just bump again.
-
-@addaleax: We should watch what Electron is doing cause they pull in every V8 version.
-
-@trevnorris: Could it happen that newer version of V8 has a lower module version number?
-
-@trott: if module version mapped to V8 version we could always be in sync.
-
-@ofrobots: Problem is that ABI is more than just V8. Also, we’re moving to a VM-neutral API/ABI in the future and that will remove the relationship to a V8 version.
-
-@rvagg: We should coordinate with Electron and draw from the same pool of numbers.
-
-@ofrobots: A good point for a bump would be when we bring a new V8 into master.
-
-@rvagg: This would make testing those nightlies easier.
-
-@trevnorris: Sounds to me that we can’t map reliably map a version of Node to a version of V8. So pulling from the same pool as Electron might be misleading to developers. If the number in Electron doesn’t match a Node version there would be a conflict.
-
-@rvagg: People are tracking which module versions map to what, so they could follow this too.
-
-@trevnorris: Maybe we can give Electron the minor numbers.
-
-@rvagg: NW.js also had a similar issue.
-
-@thealphanerd: Electron bumped to 5.1 in an ABI-breaking way, so we have two versions of Node ABIs out there, cause they needed to stay closer to Chromium.
-
-@rvagg: They don’t need to keep up with the latest version of V8.
-
-@thealphanerd: Let’s talk offline.
-
-@rvagg: Back to GitHub? Or do we need to decide now?
-
-@thealphanerd : PR has a lot of LGTMs, would like to see this land today or tomorrow so we can unbreak master.
-
-@ofrobots: Two points - one, what to do now; two, what to do going forward?
-
-Ali and Myles will work on a policy going forward.
-
-@rvagg: Might belong in LTS repo as we’ve been doing a lot of versioning stuff there.
-
-**Next steps**:
-
-* If there are objections raise them in the issue, otherwise ready to merge.
-
----
-
-### General v7.0.0 / v6 LTS Planning / Discussion
-
-@Fishrock123: Make sure all are in the loop.
-
-Throw v0.10 in too since it’s end of life at end of October.
-
-@rvagg: LTS map says *first* of October. Some people expect that cause the docs say that.
-
-@Fishrock123: We discussed keeping it alive till end of December like v0.12, cause that’s when OpenSSL is EOL’ed.
-
-@mhdawson: If the doc says Oct 1 what’s the downside to sticking with that?
-
-@rvagg: We may have communicated Oct 31 through some channels, so some people may expect that.
-
-Or perhaps when v7.x is first released.
-
-Having said that, it’s been >2 years, so people have had time to migrate.
-
-@rvagg: Originally 0.12 was slated for EOL in April 2017, we moved it back because of the OpenSSL issue.
-
-@Fishrock123: Official LTS policy is target date is when the next release/LTS is cut. That’s usually midway through month.
-
-@rvagg: Push to LTS WG to resolve ASAP.
-
-@rvagg: James pushing another beta later this week or early next week.
-
-@Fishrock123: v7.x is now on semver-major freeze.
-
-@rvagg: There are some semver-major commits in master which aren’t in v7 release.
-
-@Fishrock123: Might still need to update? Might have been left out by James intentionally?
-
-@thealphanerd: Not a ton of semver-major things on master. There are the V8 upgrades (patches), and a move of a method to fs/internal.
-
-Big one is npm@4 coming through the pipeline 1-2 weeks before Node release, should we include that.
-
-@rvagg: npm@3 had problems originally so we delayed. Should we do the same for npm@4?
-
-@addaleax: I’d feel comfortable with landing it. Kat said they aren’t concerned if 4 is included now or not.
-
-@Fishrock123: Things which are deprecated in v4 will still be deprecated (not removed) in v5, so we could bump all the way to v5 in a later release.
-
-@rvagg: We don’t have to synchronize all these dates to one, we can be flexible if needed.
-
-@thealphanerd: If we have a date other than late October it might be a good idea to offer a date.
-
-@ofrobots: Tentatively Oct 18 is the target stable date for V8 5.4. As tentative as usual, not clear till the last moment. Low chance that V8 will be moving a lot around Oct 18. Haven’t seen this date slip by more than 1-2 days. Very low chance that V8 will destablizie us.
-
-@thealphanerd: Oct 25 as a tentative date for v7.x?
-
-@rvagg: Ali and Seth, what’s the risk of setting that date now?
-
-@ofrobots: Close to Oct 18 I can highlight any potential risk.
-
-@rvagg: Let’s say that - 25th is tentative date, we’ll communicate if there’s any change. Any objections? (No.)
-
-That will also be the day we switch v6 to LTS.
-
-@thealphanerd: Doing release of v6 LTS earlier might be helpful so we have that out of the way for potential v7 issues.
-
-@rvagg: Discussion on this will move to LTS WG. Join the LTS WG on Monday to discuss.
-
-@thealphanerd: Could use someone to be responsible for v6 LTS, please volunteer.
-
-@rvagg: It’s been helpful to have a single person for v4 LTS, but we need to find a model that scales in the future.
-
-@Fishrock123: Would be helpful to schedule LTS a week earlier to avoid problems.
-
----
-
-### Supported platforms proposal from  Build WG [#488](https://github.com/nodejs/build/issues/488)
-
-Current proposal: <https://github.com/nodejs/build/issues/488#issuecomment-250155697>
-
-@trott should make a CTC agenda item next week?
-
-@rvagg: Give input on that issue before it comes to CTC. Build WG must review and sign off on as well.
-
-@rvagg: Some discussion about tiers, this affects OS vendors.
-
----
-
-### Other
-
-@thealphanerd: Node.js is going to be working with Outreachy project to help people from underrepresented groups get involved.
-
-We need projects for these people to work on in 3 months. If you can think of good parts of the project to assign… would love to hear your suggestions.
-
-@rvagg: GitHub thread?
-
-@hackygolucky: I’ll create a new one and ping @nodejs/collaborators.
-
-@rvagg: Are we getting a satisfactory response on the call for mentors?
-
-@hackygolucky: 5 primary mentors and a number of supplementals. 4 sponsors, which means we can accept 4 mentees.
-
-@rvagg: If someone wants to be a supplemental is that still open?
-
-@hackygolucky: Thread is still open: https://github.com/nodejs/education/issues/7
-
----
-
-## Q/A on public channels
-
-None.
-
----
-
-## Upcoming Meetings
-
-* CTC: 2016-10-05
-* TSC: 2016-10-06
-* Build: 2016-10-11
-* Diagnostics: 2016-10-05, 12pm Pacific
-* Benchmarking:
-* LTS: 2016-10-03
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-10-05.md b/doc/ctc-meetings/2016-10-05.md
deleted file mode 100644
index 1db805e235aabd..00000000000000
--- a/doc/ctc-meetings/2016-10-05.md
+++ /dev/null
@@ -1,311 +0,0 @@
-# Node Foundation CTC Meeting 2016-10-05
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#8915](https://github.com/nodejs/node/issues/8915)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1ZsLMM29guCBPGh7KhuhZEq6YQCKybiTfTUIXajTBalM/>
-* _Previous Minutes Google Doc_: <https://docs.google.com/document/d/1-PS20PGCJQIi4_quBHqVgrQNJeJP10NH21wUelcMhfw>
-
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-* Michael Dawson @mhdawson (CTC)
-* Julien Gilli @misterdjules (CTC)
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-* Rod Vagg @rvagg (CTC)
-* Seth Thompson @s3ththompson (observer/Google)
-* Myles Borins @TheAlphaNerd (CTC)
-* Sakthipriyan Vairamani @thefourtheye (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Nothing noteworthy
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Went to TC39, got late linking and re-linking fully discussed
-  * Working on live named imports talks and spec changes
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewing of issues and PRs.
-* Evan Lucas @evanlucas (CTC)
-  * Worked a little on improving the commit linter
-  * Submitted a PR improving process.nextTick perf by 10-20% in some cases
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * merged existsSync undeprecation
-  * other PRs & Issues
-* Tracy Hinds @hackygolucky (observer/Node.js Foundation)
-  * Outreachy application drive, issue open in the CTC repo
-  * Met last week to talk about code & lean @ Austin event
-* Michael Dawson @mhdawson (CTC)
-  * Miscellaneous PR review
-  * fix a v8 test issue
-  * ABI Stable API meeting, reviews, discussion
-  * Closed out PPC migration
-* Julien Gilli @misterdjules (CTC)
-  * Investigated SmartOS-specific issues.
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-  * Working on new budget for 2017 for the NF
-  * @ TC39 last week, very productive, looking for a way to be involved longer-term
-* Brian White @mscdex (CTC)
-  * Continued work on various optimizations in core
-  * Submitted a few misc. cleanup PRs
-  * Reviewed PRs, commented on issues
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-  * No update, observing
-* Rod Vagg @rvagg (CTC)
-  * Little build of build, little bit of LTS, little bit of NF work
-* Seth Thompson @s3ththompson (observer/Google)
-  * async await on track to ship
-  * V8 inspector work ongoing
-* Steven R Loomis @srl295 (observer/IBM/ICU)
-  * Regrets for today (and out next week) - ICU 58 will be out in a couple of weeks and will have an updated PR at that time…
-* Myles Borins @TheAlphaNerd (CTC)
-  * v4.x backporting
-  * define outreachy project
-  * fix regressions in citgm
-  * work on new communication plan for LTS dates
-* Sakthipriyan Vairamani @thefourtheye (observer)
-  * was sick for much of the week, so not much to report
-* Trevor Norris @trevnorris (CTC)
-  * Fix performance regressions from async hooks
-  * Almost finished bringing PR compliant with EP. Soon tests and proper API documentation will follow.
-  * Engaged with the V8 team regarding the MicrotaskQueue API (https://bugs.chromium.org/p/v8/issues/detail?id=4643#c19)
-* Rich Trott @Trott (CTC)
-  * CTC meeting rotation proposal
-  * 2FA for Collaborators
-  * miscellaneous issue tracker/commit activity
-* Josh Gavant @joshgav (observer)
-  * time away
-  * diagnostics WG meeting
-
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* doc: add supported platforms list [#8922](https://github.com/nodejs/node/pull/8922)
-* Intl: Consider deprecating Intl.v8BreakIterator [#8865](https://github.com/nodejs/node/issues/8865)
-* net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419)
-
-### nodejs/CTC
-
-* Scheduling Meetings [#14](https://github.com/nodejs/CTC/issues/14)
-
-
-## Previous Meeting Review
-
-* Scheduling Meetings [#14](https://github.com/nodejs/CTC/issues/14)
-* meta: update NODE_MODULE_VERSION to 51 [#8808](https://github.com/nodejs/node/pull/8808)
-  * If there are objections raise them in the issue, otherwise ready to merge.
-* General v7.0.0 / v6 LTS Planning / Discussion
-
-
-## Minutes
-
-### doc: add supported platforms list [#8922](https://github.com/nodejs/node/pull/8922)
-
-@johanbergstrom put this together in collaboration with libuv and v8 teams.
-
-@rvagg: Has everyone reviewed that would like to?
-
-We rely on a few dependencies that make us who we are — most importantly V8 and libuv. We therefore need to adopt their supported platforms and potentially add to their lists based on test and/or release coverage.
-
-@trott: Do we mean that we support whatever they support?
-
-@Fishrock123: Could be clarified. Intent is that we must start with what they offer and anything additional falls to us (Node).
-
-@rvagg: Our supported platform list is narrower than that of libuv and v8.
-
-@?: It should say we’re a subset due to the constraints.
-
-@rvagg: Removing that might be the way to go.
-
-Any objections to list as it stands?
-
-Applies to v6, probably the same for v7. Will need to be changed for v4.
-
-If there are concerns, raise in issue.
-
-**Next steps**:
-
-* Raise any concerns in issue.
-
----
-
-### Intl: Consider deprecating Intl.v8BreakIterator [#8865](https://github.com/nodejs/node/issues/8865)
-
-Want to move to a different API: `Intl.Segmentor`, so want to deprecate this one.
-
-@mikeal: We need to discourage community from using this API so we can move to a more standards-compliant implementation.
-
-@rvagg: We expose this API because V8 exposes it.
-
-@bmeck: APIs exposed by V8 can be removed…
-
-@rvagg: New API is before TC-39, could take a while. Also, what is the timeframe for removal?
-
-Is it possible this will be removed in 5.5 or 5.6, which may land in Node v7.x, in which case it would be a breaking change we’d have to polyfill.
-
-Or will it be removed later and we can include it in Node v8.x.
-
-@mikeal: V8 (Daniel) wants to remove this as soon as possible, but depends on TC-39.
-
-@bmeck: Also some small percentage of web uses this so not able to completely remove yet anyway.
-
-@seththompson: We wait till stage 3 at TC-39 to implement. As far as removing v8BreakIterator, we don’t necessarily rely on usage.
-
-Will investigate this further with Daniel.
-
-@rvagg: No problem with removing it, but need a signal as to when it will be removed.
-
-@seththompson: Dan is out of office through next week.
-
-**Next steps**:
-
-* Continue discussion in GitHub.
-
----
-
-### net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419)
-
-see also: <https://github.com/nodejs/node/pull/8294>
-
-@jasnell added this item, would be a semver-major change, can it be landed in v7.
-
-@rvagg: Adds error message when `.listen()` is called twice, EADDRINUSE.
-
-@addaleax: (#8294)[https://github.com/nodejs/node/pull/8294] documented that .listen() twice restarts the server. Does that conflict with this?
-
-@Fishrock123: When `close()` is called it resets the listen listener to `false`.
-
-@rvagg: Is this the only way to close?
-
-@addaleax: Might be…
-
-@rvagg: Will keep on agenda for James to discuss.
-
-@Fishrock123: Is anyone opposed to this?
-
-@evanlucas: Have we tested against the ecosystem?
-
-No, but it’s a poor usage anyway.
-
-@trott: delay until next week when James is here.
-
-@trevnorris: If you run this twice on the same server object, it overwrites the `_handle` property, orphaning the original handle.
-
-@mhdawson: Do they get a new handle to use?
-
-@trott: Put this into the issue.
-
-**Next steps**:
-
-* Discuss again next week.
-
----
-
-### Scheduling Meetings [#14](https://github.com/nodejs/CTC/issues/14)
-
-@trott: All possibilities are bad. Choosing the best of bad options. Hope to give proposed schedule a shot for 4 weeks and then evaluate. Or should we shoot this down and move on?
-
-@rvagg: To start next week, Oct 12?
-
-@trott: Yes.
-
-@rvagg: Any objections to next week: UTC 4:00pm, US Pacific 9am, US East 12 noon.
-
-Better for Europe and India.
-
-No.
-
-Next steps:
-
-* Do next week at new time.
-
----
-
-### General v7.0.0 / v6 LTS Planning / Discussion
-
-LTS group agreed to put out v6 LTS week of 10/17.
-
-Week after would be v7 final.
-
-@thealphanerd: We should do a release the week before v6 LTS to include all semver-minor changes we want in.
-
-@Fishrock123 will manage this release next week (10/10).
-
-@rvagg will manage v6 LTS the week after (10/17).
-
-@rvagg: What is status on V8 5.4 for 10/18?
-
-@seththompson: @ofrobots to confirm, no known problems.
-
-@rvagg: Still looking for someone to handle backports and releases for v6 LTS.
-
-@Fishrock123: We could switch Myles to v6 and someone else can pick up v4.
-
-@thealphanerd: As long as v4 is still “active” we have to go through everything. Some discussion of how to automate process.
-
-There will be more backports to v6, but also that stuff will be a lot clearer, if it can be backported.
-
-Would be good to come up with a better process for how things end up in staging. Instead of getting everything in there in the last minute.
-
-@Fishrock123: I disagree that if v4 is active it needs to have the same amount of activity all the way through. There has been an understanding that it would get more and more difficult to backport features, focus only on backporting security fixes.
-
-@thealphanerd: I found non-trivial number of items which would’ve been missed by automation.
-
-I’m a little bit uncomfortable with not auditing everything. Things that would get missed are more important than they sometimes seem.
-
-Myles, Evan, and Jeremiah to discuss tooling to help make auditing less work.
-
-@rvagg: Need to resolve Intl.v8BreakIterator for v7 - if we need to deprecate or remove it would be good to do so now.
-
-@SethThompson: Plan is to not deprecate anything until Intl.Segmentor reaches more conclusiveness in TC-39. But team would be fine if Node deprecates sooner.
-
-Current open issues for v7: https://github.com/nodejs/node/milestone/15
-
-@rvagg: We won’t have OpenSSL 1.1.0 in Node in the near future, but it may be possible to compile against it. This isn’t a blocker for v7, doesn’t require semver-major.
-
-@rvagg: Should we ship another version of 0.10 with npm updated to include updated license? Comment in LTS WG.
-
----
-
-## Q/A on public channels
-
-Alex: Can we get a comment on stability of v6 at this point?
-
-@rvagg: We’ll have a standard v6 release next Tuesday, and the following Tuesday we’ll drop to LTS and stability push will start. Expect it to be as stable as the v4 releases.
-
-If you’re planning to move to v6 LTS, it’s worth testing now.
-
-@Fishrock123: Not many new features in next week’s v6.x.x release. Some regressions early in v6 lifecycle, none now.
-
-@evanlucas: Regression in inspector.
-
-@rvagg: Inspector is still marked experimental for now. That may change in the v6 lifetime. But for now it shouldn’t be treated as stable as the other features.
-
----
-
-## Upcoming Meetings
-
-* CTC: 2016-10-12, 9am Pacific
-* TSC: 2016-10-06, 1pm Pacific
-* Build: 2016-10-11
-* Diagnostics: first week of November
-* Benchmarking:
-* LTS: 2016-10-17
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-10-12.md b/doc/ctc-meetings/2016-10-12.md
deleted file mode 100644
index 1b93d6e6f4e09b..00000000000000
--- a/doc/ctc-meetings/2016-10-12.md
+++ /dev/null
@@ -1,157 +0,0 @@
-# Node Foundation CTC Meeting 2016-10-12
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#9020](https://github.com/nodejs/node/issues/9020)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/16l9D_OvAkeG6JoM_HRomHcFl--FTB61quvIWo9QfsVw>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1qRJiogKTWvxiHQ3S16MIR7BlynbXZPjqWwPScUSI2Rg>_
-
-## Present
-
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-* Michael Dawson @mhdawson (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Shigeki Ohtsu @shigeki (CTC)
-* Sakthipriyan Vairamani @thefourtheye (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Nothing worth mentioning.
-    I was busy for the last week, catching up now.
-* Colin Ihrig @cjihrig (CTC)
-  * Issue and PR review. A few PRs for tests.
-* Evan Lucas @evanlucas (CTC)
-  * Opened a few PRs
-  * Some issue/pr review
-  * Wrote Chrome extension to make generating review metadata easier
-* Jeremiah Senkpiel @Fishrock123 (CTC)
-  * misc PRs / issues
-  * working with the ChakraCore team on ES Modules
-  * v6.8.0 Release
-* Michael Dawson @mhdawson (CTC)
-  * Misc review + land
-  * Back to working on adding nightly code coverage build
-  * ABI stable API PoC
-  * Keeping up to date on issues
-* Brian White @mscdex (CTC)
-  * Worked on improved string encoding/decoding performance
-  * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Travelling last week so not too much
-* Shigeki Ohtsu @shigeki (CTC)
-  * Review some PR and issues related to crypto.
-* Sakthipriyan Vairamani @thefourtheye (observer)
-  * catching up
-  * reviewing PRs and commenting
-* Trevor Norris (CTC)
-    * Finishing up implementing parentId for async hooks
-* Rich Trott @Trott (CTC)
-  * Issue and PR review
-  * governance discussions/issues
-  * Outreachy mentoring prep/work with applicants
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* governance: expand use of CTC issue tracker [#8945](https://github.com/nodejs/node/pull/8945)
-* doc: add supported platforms list [#8922](https://github.com/nodejs/node/pull/8922)
-* net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419)
-
-### nodejs/TSC
-
-* Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146)
-
-
-## Previous Meeting Review
-
-### nodejs/node
-
-* doc: add supported platforms list [#8922](https://github.com/nodejs/node/pull/8922)
-  * approved last week, if any objections comment now
-    on issue
-* Intl: Consider deprecating Intl.v8BreakIterator [#8865](https://github.com/nodejs/node/issues/8865)
-  * now closed so resolved
-* net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419)
-  * back on agenda for this week
-
-### nodejs/CTC
-
-* Scheduling Meetings [#14](https://github.com/nodejs/CTC/issues/14)
-  * resolved, new meeting schedule set for next month.
-
-## Minutes
-
-### governance: expand use of CTC issue tracker [#8945](https://github.com/nodejs/node/pull/8945)
-
-  * don't want to change decision making process without
-    putting through current process.
-  * ctc-review label would be useful.  For issues we need to
-    come to consensus but that we don't need to bring to meeting.
-    Still good to open issues in CTC repo.
-  * Comment from @thefourtheye that section on consensus
-    seeking model could use some clarification. Rich -> likely
-    out of scope for this change.
-  * This only applies to issues that don't need a vote, votes
-    mostly required when consensus cannot be achieved.
-  * Please add your comments or LTGM to the issue.
-
-### doc: add supported platforms list [#8922](https://github.com/nodejs/node/pull/8922)
-
-  * discussed last week and input provided by CTC.
-  * removed from CTC-agenda.
-
-
-### net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419)
-
-  * latest discussion in issue still around if there is
-    any other way to close socket.
-  * you will already get errors if you listen twice.
-  * Some discussion, but missing proponents so discussion
-    back into github issue.
-  * If you object to it going into 7 (even though semver major)
-    make sure to comment.
-
-
-###  Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146)
-  * Already discussed in TSC, here to discuss with those not in CTC.
-  * no strong opinions voiced beyond what is in issue.
-  * comments that we have gotten questions as to
-    why we have 2 bodies.
-
-
-### General v7.0.0 / v6 LTS Planning / Discussion
-
-
-* 2 weeks out from V7.0 - Jerimiah handling this one.
-* 6 days from LTS release - Rodd handling this one.
-* v6 Current release should go out today.
-
-
-### http: improve invalid character in header error message [9010](https://github.com/nodejs/node/pull/9010)
-
-* asked if this could go into 7, some discussion, take
-  ongoing discussion back to github
-
-## Q/A on public channels
-
-
-## Upcoming Meetings
-
-* CTC: 2016-10-19, 1pm Pacific
-* TSC: 2016-10-13, 1pm Pacific
-* Build: 2016-10-11
-* Diagnostics: first week of November
-* Benchmarking:
-* LTS: 2016-10-17
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-10-19.md b/doc/ctc-meetings/2016-10-19.md
deleted file mode 100644
index 8fbaa1dfa906d6..00000000000000
--- a/doc/ctc-meetings/2016-10-19.md
+++ /dev/null
@@ -1,202 +0,0 @@
-# Node Foundation CTC Meeting 2016-10-19
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**: [#9143](https://github.com/nodejs/node/issues/9143)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/18rnF8IfO10aQ0gRRasH3zSuv397-lm_x1fX1FSGcV7E>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/16l9D_OvAkeG6JoM_HRomHcFl--FTB61quvIWo9QfsVw>_
-
-## Present
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* James M Snell @jasnell (CTC)
-* Josh Gavant @joshgav (observer/Microsoft)
-* Michael Dawson @mhdawson (CTC)
-* Julien Gilli @misterdjules (CTC)
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-* Steven R. Loomis @srl295 (observer)
-* Sakthipriyan Vairamani @thefourtheye (observer)
-* Trevor Norris @trevnorris (CTC)
-* Rich Trott @Trott (CTC)
-
-## Standup
-
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Vacation, work on import changes for ES spec
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewed issues and PRs. Revisited an old PR.
-* Evan Lucas @evanlucas (CTC)
-  * cut v6.8.1 release
-  * opened small doc PR
-  * issue/pr review
-* James M Snell @jasnell (CTC)
-  * Preparing v7.0.0 release
-  * HTTP/2 implementation
-  * PRs
-* Josh Gavant @joshgav (observer/Microsoft)
-  * PR’s to improve user experience with new debugger
-  * investigating how to integrate guides with API docs
-  * off this week
-* Michael Dawson @mhdawson (CTC)
-  * couple days vacation
-  * Added code coverage nightly job and PR for doc
-  * misc issue review/comment/lands
-  * Some Abi stable node discussion/work
-  * A number of benchmarking issues to look at
-* Julien Gilli @misterdjules (CTC)
-  * nothing too significant
-* Mikeal Rogers @mikeal (observer/Node.js Foundation)
-  * Putting together bugeting stuff
-* Brian White @mscdex (CTC)
-  * Continued work on improving string encoding/decoding
-  performance.
-  * Commented on issues, reviewed PRs.
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Some V8 backport triage. Not much else notable.
-* Jenn Turner @renrutnnej (observer/Node.js Foundation)
-  * Just observing, no update
-* Steven R. Loomis @srl295 (observer)
-  * ICU 58 going GA  end of week so will submit PR to update - [#7844](https://github.com/nodejs/node/issues/7844)
-  * Backported break iterator fix to v4.x [#9008](https://github.com/nodejs/node/pull/9008)
-* Sakthipriyan Vairamani @thefourtheye (observer)
-  * mostly PR reviews
-* Trevor Norris @trevnorris (CTC)
-  * Worked with Matt Loring, proposed promise hooks api is
-  sufficient combined with debugger API.
-* Rich Trott @Trott (CTC)
-  * Outreachy
-  * flaky tests
-  * linting tools and rules
-
----
-
-## Agenda
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-### nodejs/node
-
-* doc: add ctc-review label information [#9072](https://github.com/nodejs/node/pull/9072) @Trott
-* http: improve invalid character in header error message [#9010](https://github.com/nodejs/node/pull/9010) @evanlucas
-* net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419) @jasnell
-
-### nodejs/TSC
-
-* Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146) @rvagg
-
-
----
-
-## Previous Meeting Review
-
-### nodejs/node
-
-* governance: expand use of CTC issue tracker [#8945](https://github.com/nodejs/node/pull/8945)
-
-    * Finalize through GitHub discussions.
-    * Consider `ctc-review` label (#9072).
-
-* doc: add supported platforms list [#8922](https://github.com/nodejs/node/pull/8922)
-
-    * Complete, remove from agenda.
-
-* net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419)
-
-    * Back to GitHub for further discussion.
-
-### nodejs/TSC
-
-* Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146)
-
----
-
-## Minutes
-
-### doc: add ctc-review label information [#9072](https://github.com/nodejs/node/pull/9072) @Trott
-
-@trott: Has landed. If any objections speak now. Goal is more resolutions within tracker, less in meetings.
-
----
-
-### http: improve invalid character in header error message [#9010](https://github.com/nodejs/node/pull/9010) @evanlucas
-
-@evanlucas: Concerns about this leading to an information leak, because header name is displayed.
-
-Would like to land this for v7. Would have to be merged today.
-
-@trott: Question is if people are uncomfortable moving forward now before information from @Chalker is available.
-
-@mhdawson: Seems there are already some hits (problems).
-
-@evanlucas: Package `http-node` had problems, seems they copied `_http_outgoing.js`.
-
-@evanlucas: Perhaps we can just add a debug message, that would not be semver-major.
-
-@mhdawson: Seems better to do that than introduce a semver-major change this late.
-
-@evanlucas: That seems fine, as long as we can get the needed info.
-
-@trott: So land the debug message now, perhaps land standard output in v8.x.
-
-**Next steps**:
-
-* Create new PR with debug-based message, defer including in stderr/stdout till v8.x.
-
----
-
-### net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419) @jasnell
-
-@jasnell: Question is whether to land in v7.x. If so please take it up today!
-
----
-
-### Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146) @rvagg
-
-@trott: Mainly to bring this to people’s attention, continue conversation in tracker.
-
----
-
-### Info text in `--inspect` output [#8978](https://github.com/nodejs/node/pull/8978)
-
-@joshgav: Should we land this for v7.x?
-
-@trott: Is this a semver-major change?
-
-@jasnell: No, especially cause this is an experimental feature.
-
-@evanlucas: I’d prefer to wait till Chrome automatically lists Node.js targets via chrome://inspect, which is 55.
-
-@ofrobots: No urgency to land this change now and it will make it harder to get started.
-
-@mhdawson: Agreed, no urgency to land this before v7.x.
-
-@joshgav: So I’ll update PR to include generic URL but not remove the chrome-devtools URL for now.
-
-**Next steps**:
-
-* Josh to update PR to still include chrome-devtools URL.
-* Consider removing chrome-devtools URL when 55 is released (early December).
-
----
-
-## Q/A on public channels
-
-
----
-
-## Upcoming Meetings
-
-* CTC: 2016-10-26, 9am Pacific
-* TSC: 2016-10-20, 1pm Pacific
-* Build: 2016-10-24 (?)
-* Diagnostics: first week of November
-* Benchmarking:
-* LTS:
-* Post-Mortem:
-* API:
diff --git a/doc/ctc-meetings/2016-10-26.md b/doc/ctc-meetings/2016-10-26.md
deleted file mode 100644
index ed8f8fee78a1bf..00000000000000
--- a/doc/ctc-meetings/2016-10-26.md
+++ /dev/null
@@ -1,151 +0,0 @@
-# Node Foundation CTC Meeting 2016-10-26
-
-## Links
-
-* **Audio Recording**: TBP
-* **GitHub Issue**:
-[#9261](https://github.com/nodejs/node/issues/9261)
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1dUPFNyK8Yn1yWRAcXPY-mWM2KMWvOOB8Z5BH2s7RpJs>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/18rnF8IfO10aQ0gRRasH3zSuv397-lm_x1fX1FSGcV7E>_
-
-
-## Present
-
-* Anna Henningsen @addaleax (CTC)
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-* Ben Noordhuis @bnoordhuis (CTC)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-* Colin Ihrig @cjihrig (CTC)
-* Evan Lucas @evanlucas (CTC)
-* James M Snell @jasnell (CTC)
-* Brian White @mscdex (CTC)
-* Ali Ijaz Sheikh @ofrobots (CTC)
-* Seth Thompson @s3ththompson (observer/Google)
-* Shigeki Ohtsu @shigeki (CTC)
-* Sakthipriyan Vairamani @thefourtheye (observer)
-* Rich Trott @Trott (CTC)
-
-
-## Standup
-
-* Anna Henningsen @addaleax (CTC)
-  * Not much
-* Bradley Meck @bmeck (observer/GoDaddy/TC39)
-  * Work on making inspector work w/ vm
-  * Minor talks w/ modules spec authors
-* Ben Noordhuis @bnoordhuis (CTC)
-  * (Nothing reported.)
-* Сковорода Никита Андреевич @ChALkeR (CTC)
-  * Rebuilt a new dataset from npm packages, some further work on the tooling
-  * Some issue/pr comments as usual
-  * Some ecosystem security stuff
-* Colin Ihrig @cjihrig (CTC)
-  * Reviewing issues and PRs, opened a few PRs, libuv 1.10.0 update
-* Evan Lucas @evanlucas (CTC)
-  * Working on getting libuv to use fsevents for file watching on OS X
-  * Opened small PR to fix a test that kept failing on freebsd
-* James M Snell @jasnell (CTC)
-  * Getting v7.0.0 out the door
-  * PRs
-  * More work on HTTP/2
-* Brian White @mscdex (CTC)
-  * Continued working on string encoding/decoding performance. Starting to see even more promising results.
-  * Reviewed PRs, commented on issues
-* Ali Ijaz Sheikh @ofrobots (CTC)
-  * Not much
-* Seth Thompson @s3ththompson (observer/Google)
-  * V8 5.5 beta shipped with async/await
-* Shigeki Ohtsu @shigeki (CTC)
-  * Reviewed a few PR and made a security assessments of CVE-2016-8610 for Node-v0.10 and 0.12.
-* Sakthipriyan Vairamani @thefourtheye (observer)
-  * Held an event to help people to get their first contribution into Node.js
-  * Looking at V8 code base
-* Rich Trott @Trott (CTC)
-  * Outreachy, Node Todo, Node Interactive prep
-  * test and tools PRs
-  * usual PR review/commenting
-
-
----
-
-
-## Agenda
-
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-
-### nodejs/TSC
-
-
-* Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146)
-
-
-### nodejs/node
-
-
-* Debugging: name every function
-[#8913]https://github.com/nodejs/node/issues/8913
-
-
----
-
-
-## Previous Meeting Review
-
-
-Extracted from **ctc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
-
-
-### nodejs/node
-
-
-* doc: add ctc-review label information [#9072](https://github.com/nodejs/node/pull/9072) @Trott
-* http: improve invalid character in header error message [#9010](https://github.com/nodejs/node/pull/9010) @evanlucas
-* net: multiple listen() events fail silently [#8419](https://github.com/nodejs/node/pull/8419) @jasnell
-
-
-### nodejs/TSC
-
-
-* Consider folding TSC into CTC [#146](https://github.com/nodejs/TSC/issues/146) @rvagg
-
-
----
-
-
-## Minutes
-
-
-### Consider folding TSC into CTC
-
-
-Rich: Defer until Rod is here and have the conversation in the issue tracker until then?
-
-
-James: Makes sense. Also, TSC call is tomorrow so it can be discussed then.
-
-
-### Debugging: name every function
-
-
-Rich: It seemed like a good idea initially, but it is not clear if it is a good thing in all cases (some +, some -). Issue is marked as good first contribution which means lots of new contributors are coming in.
-Myles wanted a quick resolution, but it is not clear there is a quick resolution. Someone needs to sit down and come up with a list of cases where it would be beneficial
-
-
-Brian: Prototype functions?
-
-
-Rich: That is a case where it doesn't add value but doesn't hurt either. There are other cases where it does remove information.
-
-
-Sakthipriyan: One example was fs.readFileSync..
-
-
-Brian: V8 may also be inferring names from a variable in cases when you do `let a = () => {...}`. Another case to take into consideration.
-
-
-Rich: Move back to the issue tracker; remove 'good-first-contribution' label until we have documented what should/shouldn't be done. I can work with someone, or come up with documentation.
-
-
-Floor: General agreement? Yes, general agreement.
diff --git a/doc/guides/maintaining-V8.md b/doc/guides/maintaining-V8.md
new file mode 100644
index 00000000000000..82312cf6bcf4d1
--- /dev/null
+++ b/doc/guides/maintaining-V8.md
@@ -0,0 +1,279 @@
+# Maintaining V8 in Node
+
+# Background
+
+V8 follows the Chromium release schedule. The support horizon for Chromium is very different from the support horizon that Node.js needs to provide to its users. As a result Node.js needs to support a version of V8 for quite a bit longer than what upstream needs to support. Since V8 doesn't have an LTS supported branch, there is no official process around how the V8 branches in Node are maintained.
+
+This document attempts to document the current processes and proposes a workflow for maintaining the V8 branches in Node.js LTS and Current releases and how the Node and V8 teams at Google can help.
+
+# V8 Release Schedule
+
+V8 and Chromium follow a [roughly 6-week release cadence](https://www.chromium.org/developers/calendar). At any given time there are three V8 branches that are **active**.
+
+For example, at the time of this writing:
+
+* **Stable**: V8 5.4 is currently shipping as part of Chromium stable. This branch was created approx. 6 weeks before from when V8 5.3 shipped as stable.
+* **Beta**: V8 5.5 is currently in beta. It will be promoted to stable next; approximately 6 weeks after V8 5.4 shipped as stable.
+* **Master**: V8 tip-of-tree corresponds to V8 5.6. This branch gets regularly released as part of the Chromium **canary** builds. This branch will be promoted to beta next when V8 5.5 ships as stable.
+
+All older branches are considered **abandoned**, and are not maintained by the V8 team.
+
+## V8 merge process overview
+
+The process for backporting bug fixes to active branches is officially documented [on the V8 wiki](https://github.com/v8/v8/wiki/Merging%20&%20Patching). The summary of the process is:
+
+*   V8 only supports active branches. There is no testing done on any branches older than the current stable/beta/master.
+*   A fix needing backport is tagged w/ *merge-request-x.x* tag. This can be done by anyone interested in getting the fix backported. Issues with this tag are reviewed by the V8 team regularly as candidates for backporting.
+*   Fixes need some 'baking time' before they can be approved for backporting. This means waiting a few days to ensure that no issues are detected on the canary/beta builds.
+*   Once ready, the issue is tagged w/ *merge-approved-x.x* and one can do the actual merge by using the scripts on the [wiki page](https://github.com/v8/v8/wiki/Merging%20&%20Patching).
+*   Merge requests to an abandoned branch will be rejected.
+*   Only bug fixes are accepted for backporting.
+
+# Node Support Requirements
+
+At any given time Node needs to be maintaining a few different V8 branches for the various Current, LTS, and nightly releases. At present this list includes the following branches<sup>1</sup>:
+
+<table>
+  <tr>
+   <td><strong>Release</strong>
+   </td>
+   <td><strong>Support Start</strong>
+   </td>
+   <td><strong>Support End</strong>
+   </td>
+   <td><strong>V8 version</strong>
+   </td>
+   <td><strong>V8 branch released</strong>
+   </td>
+   <td><strong>V8 branch abandoned</strong>
+   </td>
+  </tr>
+  <tr>
+   <td>Node v4.x
+   </td>
+   <td>2015-10-01
+   </td>
+   <td>2018-04-01
+   </td>
+   <td>4.5
+   </td>
+   <td>2015-09-01
+   </td>
+   <td>2015-10-13
+   </td>
+  </tr>
+  <tr>
+   <td>Node v6.x
+   </td>
+   <td>2016-04-01
+   </td>
+   <td>2019-04-01
+   </td>
+   <td>5.1
+   </td>
+   <td>2016-05-31
+   </td>
+   <td>2016-06-26
+   </td>
+  </tr>
+  <tr>
+   <td>Node v7.x
+   </td>
+   <td>2016-10-01
+   </td>
+   <td>2017-04-01
+   </td>
+   <td>5.4
+   </td>
+   <td>2016-10-18
+   </td>
+   <td>~2016-12-01
+   </td>
+  </tr>
+  <tr>
+   <td>master
+   </td>
+   <td>N/A
+   </td>
+   <td>N/A
+   </td>
+   <td>5.4
+   </td>
+   <td>2016-10-18
+   </td>
+   <td>~2016-12-01
+   </td>
+  </tr>
+</table>
+
+
+The versions of V8 used in Node v4.x and v6.x have already been abandoned by upstream V8. However, Node.js needs to continue supporting these branches for many months (Current branches) or several years (LTS branches).
+
+# Maintenance Process
+
+Once a bug in Node.js has been identified to be caused by V8, the first step is to identify the versions of Node and V8 affected. The bug may be present in multiple different locations, each of which follows a slightly different process.
+
+* Unfixed bugs. The bug exists in the V8 master branch.
+* Fixed, but needs backport. The bug may need porting to one or more branches.
+    * Backporting to active branches.
+    * Backporting to abandoned branches.
+* Backports identified by the V8 team. Bugs identified by upstream V8 that we haven't encountered in Node yet.
+
+## Unfixed Upstream Bugs
+
+If the bug can be reproduced on the [`vee-eight-lkgr` branch](https://github.com/v8/node/tree/vee-eight-lkgr), Chromium canary, or V8 tip-of-tree, and the test case is valid, then the bug needs to be fixed upstream first.
+
+* Start by opening a bug upstream [using this template](https://bugs.chromium.org/p/v8/issues/entry?template=Node.js%20upstream%20bug).
+* Make sure to include a link to the corresponding Node.js issue (if one exists).
+* If the fix is simple enough, you may fix it yourself; [contributions](https://github.com/v8/v8/wiki/Contributing) are welcome.
+* V8's build waterfall tests your change.
+* Once the bug is fixed it may still need backporting, if it exists in other V8 branches that are still active or are branches that Node cares about. Follow the process for backporting below.
+
+## Backporting to Active Branches
+
+If the bug exists in any of the active V8 branches, we may need to get the fix backported. At any given time there are [two active branches](https://build.chromium.org/p/client.v8.branches/console) (beta and stable) in addition to master. The following steps are needed to backport the fix:
+
+* Identify which version of V8 the bug was fixed in.
+* Identify if any active V8 branches still contain the bug:
+* A tracking bug is needed to request a backport.
+    * If there isn't already a V8 bug tracking the fix, open a new merge request bug using this [Node.js specific template](https://bugs.chromium.org/p/v8/issues/entry?template=Node.js%20merge%20request).
+    * If a bug already exists
+        * Add a reference to the GitHub issue.
+        * Attach *merge-request-x.x* labels to the bug for any active branches that still contain the bug. (e.g. merge-request-5.3, merge-request-5.4)
+        * Add ofrobots-at-google.com to the cc list.
+* Once the merge has been approved, it should be merged using the [merge script documented in the V8 wiki](https://github.com/v8/v8/wiki/Merging%20&%20Patching). Merging requires commit access to the V8 repository. If you don't have commit access you can indicate someone on the V8 team can do the merge for you.
+* It is possible that the merge request may not get approved, for example if it is considered to be a feature or otherwise too risky for V8 stable. In such cases we float the patch on the Node side. See the process on 'Backporting to Abandoned branches'.
+* Once the fix has been merged upstream, it can be picked up during an update of the V8 branch, (see below).
+
+## Backporting to Abandoned Branches
+
+Abandoned V8 branches are supported in the Node.js V8 repository. The fix needs to be cherry-picked in the Node.js repository and V8-CI must test the change.
+
+* For each abandoned V8 branch corresponding to an LTS branch that is affected by the bug:
+    * Open a cherry-pick PR on nodejs/node targeting the appropriate *vY.x-staging* branch (e.g. *v6.x-staging* to fix an issue in V8-5.1).
+    * Increase the patch level version in v8-version.h. This will not cause any problems with versioning because V8 will not publish other patches for this branch, so Node.js can effectively bump the patch version.
+    * In some cases the patch may require extra effort to merge in case V8 has changed substantially. For important issues we may be able to lean on the V8 team to get help with reimplementing the patch.
+    * Run Node's [V8-CI](https://ci.nodejs.org/job/node-test-commit-v8-linux/) in addition to the [Node CI](https://ci.nodejs.org/job/node-test-pull-request/).
+
+An example for workflow how to cherry-pick consider the following bug: https://crbug.com/v8/5199. From the bug we can see that it was merged by V8 into 5.2 and 5.3, and not into V8 5.1 (since it was already abandoned). Since Node.js `v6.x` uses V8 5.1, the fix needed to cherry-picked. To cherry-pick, here's an example workflow:
+
+* Download and apply the commit linked-to in the issue (in this case a51f429). `curl -L https://github.com/v8/v8/commit/a51f429.patch | git apply --directory=deps/v8`. If the branches have diverged significantly, this may not apply cleanly. It may help to try to cherry-pick the merge to the oldest branch that was done upstream in V8. In this example, this would be the patch from the merge to 5.2. The hope is that this would be closer to the V8 5.1, and has a better chance of applying cleanly. If you're stuck, feel free to ping @ofrobots for help.
+* Modify the commit message to match the format we use for V8 backports. You may want to add extra description if necessary to indicate the impact of the fix on Node. In this case the original issue was descriptive enough. Example:
+```
+deps: cherry-pick a51f429 from V8 upstream
+
+Original commit message:
+  [regexp] Fix case-insensitive matching for one-byte subjects.
+
+  The bug occurs because we do not canonicalize character class ranges
+  before adding case equivalents. While adding case equivalents, we abort
+  early for one-byte subject strings, assuming that the ranges are sorted.
+  Which they are not.
+
+  R=marja@chromium.org
+  BUG=v8:5199
+
+  Review-Url: https://codereview.chromium.org/2159683002
+  Cr-Commit-Position: refs/heads/master@{#37833}
+
+PR-URL: <pr link>
+```
+* Open a PR against the `v6.x-staging` branch in the Node.js repo. Launch the normal and [V8-CI](https://ci.nodejs.org/job/node-test-commit-v8-linux/) using the Node.js CI system. We only needed to backport to `v6.x` as the other LTS branches weren't affected by this bug.
+
+## Backports Identified by the V8 team
+
+For bugs found through the browser or other channels, the V8 team marks bugs that might be applicable to the abandoned branches in use by Node.js. This is done through manual tagging by the V8 team and through an automated process that tags any fix that gets backported to the stable branch (as it is likely candidate for backporting further).
+
+Such fixes are tagged with the following labels in the V8 issue tracker:
+
+*   `NodeJS-Backport-Review` ([V8](https://bugs.chromium.org/p/v8/issues/list?can=1&q=label%3ANodeJS-Backport-Review), [Chromium](https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3ANodeJS-Backport-Review)): to be reviewed if this is applicable to abandoned branches in use by Node.js. This list if regularly reviewed by the node team at Google to determine applicability to Node.js.
+*   `NodeJS-Backport-Approved` ([V8](https://bugs.chromium.org/p/v8/issues/list?can=1&q=label%3ANodeJS-Backport-Approved), [Chromium](https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3ANodeJS-Backport-Approved)): marks bugs that are deemed relevant to Node.js and should be backported.
+*   `NodeJS-Backport-Done` ([V8](https://bugs.chromium.org/p/v8/issues/list?can=1&q=label%3ANodeJS-Backport-Done), [Chromium](https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3ANodeJS-Backport-Done)): Backport for Node.js has been performed already.
+*   `NodeJS-Backport-Rejected` ([V8](https://bugs.chromium.org/p/v8/issues/list?can=1&q=label%3ANodeJS-Backport-Rejected), [Chromium](https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3ANodeJS-Backport-Rejected)): Backport for Node.js is not desired.
+
+The backlog of issues with such is regularly reviewed by the node-team at Google to shepherd through the backport process. External contributors are welcome to collaborate on the backport process as well. Note that some of the bugs may be security issues and will not be visible to external collaborators.
+
+# Updating V8
+
+Node keeps a vendored copy of V8 inside of deps/ directory. In addition Node may need to float patches that do not exist upstream. This means that some care may need to be taken to update the vendored copy of V8.
+
+## Minor updates (patch level)
+
+Because there may be floating patches on the version of V8 in Node.js, it is safest to apply the patch level updates as a patch. For example, imagine that upstream V8 is at 5.0.71.47 and Node.js is at 5.0.71.32. It would be best to compute the diff between these tags on the V8 repository, and then apply that patch on the copy of V8 in Node.js. This should preserve the patches/backports that Node.js may be floating (or else cause a merge conflict).
+
+The rough outline of the process is:
+
+```shell
+# Assuming your fork of Node.js is checked out in $NODE_DIR
+# and you want to update the Node.js master branch.
+# Find the current (OLD) version in
+# $NODE_DIR/deps/v8/include/v8-version.h
+cd $NODE_DIR
+git checkout master
+git merge --ff-only origin/master
+git checkout -b V8_NEW_VERSION
+curl -L https://github.com/v8/v8/compare/${V8_OLD_VERSION}...${V8_NEW_VERSION}.patch | git apply --directory=deps/v8
+# You may want to amend the commit message to describe the nature of the update
+```
+
+V8 also keeps tags of the form *5.4-lkgr* which point to the *Last Known Good Revision* from the 5.4 branch that can be useful in the update process above.
+
+
+## Major Updates
+
+We upgrade the version of V8 in Node.js master whenever a V8 release goes stable upstream, that is, whenever a new release of Chrome comes out.
+
+Upgrading major versions would be much harder to do with the patch mechanism above. A better strategy is to
+
+1. Audit the current master branch and look at the patches that have been floated since the last major V8 update.
+1. Replace the copy of V8 in Node.js with a fresh checkout of the latest stable V8 branch. Special care must be taken to recursively update the DEPS that V8 has a compile time dependency on (at the moment of this writing, these are only trace_event and gtest_prod.h)
+1. Refloat (cherry-pick) all the patches from list computed in 1) as necessary. Some of the patches may no longer be necessary.
+
+To audit for floating patches:
+
+```shell
+git log --oneline deps/v8
+```
+
+To replace the copy of V8 in Node, use the '[update-v8](https://gist.github.com/targos/8da405e96e98fdff01a395bed365b816)' script<sup>2</sup>. For example, if you want to replace the copy of V8 in Node.js with the branch-head for V8 5.1 branch:
+
+```shell
+cd $NODE_DIR
+rm -rf deps/v8
+path/to/update-v8 branch-heads/5.1
+```
+
+You may want to look at the commits created by the above scripts, and squash them once you have reviewed them.
+
+This should be followed up with manual refloating of all relevant patches.
+
+# Proposal: Using a fork repo to track upstream V8
+
+The fact that Node.js keeps a vendored, potentially edited copy of V8 in deps/ makes the above processes a bit complicated. An alternative proposal would be to create a fork of V8 at nodejs/v8 that would be used to maintain the V8 branches. This has several benefits:
+
+* The process to update the version of V8 in Node.js could be automated to track the tips of various V8 branches in nodejs/v8.
+* It would simplify cherry-picking and porting of fixes between branches as the version bumps in v8-version.h would happen as part of this update instead of on every change.
+* It would simplify the V8-CI and make it more automatable.
+* The history of the V8 branch in nodejs/v8 becomes purer and it would make it easier to pull in the V8 team for help with reviewing.
+* It would make it simpler to setup an automated build that tracks Node.js master + V8 lkgr integration build.
+
+This would require some tooling to:
+
+* A script that would update the V8 in a specific Node branch with V8 from upstream (dependent on branch abandoned vs. active).
+* We need a script to bump V8 version numbers when a new version of V8 is promoted from nodejs/v8 to nodejs/node.
+* Enabled the V8-CI build in Jenkins to build from the nodejs/v8 fork.
+
+# Proposal: Dealing with the need to float patches to a stable/beta
+
+Sometimes upstream V8 may not want to merge a fix to their stable branches, but we might. An example of this would be a fix for a performance regression that only affects Node.js and not the browser. At the moment we don't have a mechanism to deal with this situation. If we float a patch and bump the V8 version, we might run into a problem if upstream releases a fix with the same version number.
+
+One idea we have been kicking around is that we could move to a 5-place version number in V8, e.g.: 5.4.500.30.${embedder}. The ${embedder} represents the number of patches an embedder is floating on top of an official V8 version. This would also help with auditing the floating patches in the Node commit history.
+
+We are trying this out in https://github.com/nodejs/node/pull/9754. If this ends up working, we will investigate making this change upstream.
+
+<!-- Footnotes themselves at the bottom. -->
+## Notes
+
+<sup>1</sup>Node.js 0.12 and older are intentionally omitted from this document as their support is ending soon.
+
+<sup>2</sup>It seems that @targos is working on port of this script here https://github.com/targos/update-v8.
diff --git a/doc/guides/writing_tests.md b/doc/guides/writing-tests.md
similarity index 94%
rename from doc/guides/writing_tests.md
rename to doc/guides/writing-tests.md
index 95a09540b47ee4..107e9cde7a42b3 100644
--- a/doc/guides/writing_tests.md
+++ b/doc/guides/writing-tests.md
@@ -3,11 +3,13 @@
 ## What is a test?
 
 A test must be a node script that exercises a specific functionality provided
-by node and checks that it behaves as expected. It should return 0 on success,
+by node and checks that it behaves as expected. It should exit with code `0` on success,
 otherwise it will fail. A test will fail if:
 
-- It exits by calling `process.exit(code)` where `code != 0`
-- It exits due to an uncaught exception.
+- It exits by setting `process.exitCode` to a non-zero number.
+  - This is most often done by having an assertion throw an uncaught
+    Error.
+  - Occasionally, using `process.exit(code)` may be appropriate.
 - It never exits. In this case, the test runner will terminate the test because
   it sets a maximum time limit.
 
diff --git a/doc/onboarding-extras.md b/doc/onboarding-extras.md
index 5fc5424224ca38..e19e1ef5795525 100644
--- a/doc/onboarding-extras.md
+++ b/doc/onboarding-extras.md
@@ -22,6 +22,7 @@
 | `src/node_crypto.*` | @nodejs/crypto |
 | `test/*` | @nodejs/testing |
 | `tools/eslint`, `.eslintrc` | @silverwind, @trott |
+| async_hooks | @nodejs/diagnostics |
 | upgrading V8 | @nodejs/v8, @nodejs/post-mortem |
 | upgrading npm | @fishrock123, @thealphanerd |
 | upgrading c-ares | @jbergstroem |
diff --git a/doc/topics/the-event-loop-timers-and-nexttick.md b/doc/topics/the-event-loop-timers-and-nexttick.md
index 1f2456a17c0e2f..03a886af019606 100644
--- a/doc/topics/the-event-loop-timers-and-nexttick.md
+++ b/doc/topics/the-event-loop-timers-and-nexttick.md
@@ -9,13 +9,13 @@ offloading operations to the system kernel whenever possible.
 Since most modern kernels are multi-threaded, they can handle multiple
 operations executing in the background. When one of these operations
 completes, the kernel tells Node.js so that the appropriate callback
-may added to the **poll** queue to eventually be executed. We'll explain
+may be added to the **poll** queue to eventually be executed. We'll explain
 this in further detail later in this topic.
 
 ## Event Loop Explained
 
 When Node.js starts, it initializes the event loop, processes the
-provided input script (or drops into the REPL, which is not covered in
+provided input script (or drops into the [REPL][], which is not covered in
 this document) which may make async API calls, schedule timers, or call
 `process.nextTick()`, then begins processing the event loop.
 
@@ -141,7 +141,9 @@ the timer's callback. In this example, you will see that the total delay
 between the timer being scheduled and its callback being executed will
 be 105ms.
 
-Note: To prevent the **poll** phase from starving the event loop, libuv
+Note: To prevent the **poll** phase from starving the event loop, [libuv]
+(http://libuv.org/) (the C library that implements the Node.js
+event loop and all of the asynchronous behaviors of the platform)
 also has a hard maximum (system dependent) before it stops polling for
 more events.
 
@@ -473,3 +475,5 @@ myEmitter.on('event', function() {
   console.log('an event occurred!');
 });
 ```
+
+[REPL]: https://nodejs.org/api/repl.html#repl_repl
diff --git a/doc/tsc-meetings/2015-05-27.md b/doc/tsc-meetings/2015-05-27.md
deleted file mode 100644
index 7c0bce36d5dd4f..00000000000000
--- a/doc/tsc-meetings/2015-05-27.md
+++ /dev/null
@@ -1,143 +0,0 @@
-# Node Foundation TSC Meeting 2015-05-27
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-05-27
-* **Public YouTube feed**: http://www.youtube.com/watch?v=0DPfLxulsbQ
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/41
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1-KlxiQGMsJFNJu3meok9e9XFsM39k_PMnQmY_9d_cy0
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/node-convergence-archive
-
-* \[Converge\] timers: Avoid linear scan in `_unrefActive`. [#23](https://github.com/nodejs/node-convergence-archive/issues/23)
-* \[Converge\] child_process argument type checking [#22](https://github.com/nodejs/node-convergence-archive/issues/22)
-* \[Converge\] SSLv2/3 disable/enable related commits [#20](https://github.com/nodejs/node-convergence-archive/issues/20)
-* doc: Add new working groups [#15](https://github.com/nodejs/node-convergence-archive/pull/15)
-
-### nodejs/io.js
-
-* Buffer implemented using Uint8Array [#1810](https://github.com/nodejs/io.js/issues/1810)
-* \[Discussion\] FFI - Giving Buffer more low-level C functionality [#1750](https://github.com/nodejs/io.js/pull/1750)
-* Chrome 43 released; time for V8 4.3! [#1735](https://github.com/nodejs/io.js/issues/1735)
-* Deprecation Policy [#1704](https://github.com/nodejs/io.js/issues/1704)
-* TSC needs to elect a board representative. [#1697](https://github.com/nodejs/io.js/issues/1697)
-* V8 4.4 to remove indexed properties via external data [#1451](https://github.com/nodejs/io.js/issues/1451)
-
-### joyent/node
-
-## Present
-
-* Alexis Campailla (TSC)
-* Ben Noordhuis (TSC)
-* Bert Belder (TSC)
-* Brian White
-* Chris Dickinson (TSC)
-* Colin Ihrig (TSC)
-* James M Snell (TSC)
-* Jeremiah Senkpiel (TSC)
-* Mikeal Rogers
-* Michael Dawson (TSC)
-* Mike Dolan (TSC)
-* Rod Vagg (TSC)
-* Shigeki Ohtsu
-* Trevor Norris (TSC)
-
-## Quick stand-up
-
-* Rod: Working on combining the build, 3.0
-* James: Working on repo convergence, triaging joyent/node issues, LTS policy drafting
-* Shigeki: Investigating a slow tls test and SSL mitigations for a log jam attack. 
-* Jeremiah: Lots of little things
-* Colin: Libuv work for os.homedir()
-* Chris: Removing sys, checking breakage; fixing bug I introduced in persistent history
-* Bert: Looking at issues
-* Alexis: Working on combining the build, fixing windows issues
-* Trevor: Working on the new Buffer impl using Uint8Array
-* Michael: Traging joyent/node, spun up the benchmarking WG, looking into adding powerpc build machines
-* Brian: Almost done the pure JS dns resolver, all tests are passing
-* Ben: 
- - Make require faster
- - Date.now() perf improvements
-
-## Review of last meeting
-
-* _Skipping_
-
-## Minutes
-
-### \[Converge\] timers: Avoid linear scan in `_unrefActive`. [#23](https://github.com/nodejs/node-convergence-archive/issues/23)
-
-* James: conflicting approaches in both repos
-* Ben: both are terrible under different workloads - do away with the code and start again
-* Jeremiah: might have a go at it, working off an existing heap impl by Ben (ACTION)
-* Bert: some problems with http - discussion happened about the implementation
-* Chris: would be good to have Julien’s input since he was active on the joyent/node impl
-
-### \[Converge\] child_process argument type checking [#22](https://github.com/nodejs/node-convergence-archive/issues/22)
-
-* James: arg checking merged in 0.10 after the fork
-* Discussion about why this wasn’t merged to io.js
-* Defer back to GitHub discussion after no reason for not merging could be found on the call
-
-### \[Converge\] SSLv2/3 disable/enable related commits [#20](https://github.com/nodejs/node-convergence-archive/issues/20)
-
-* James: SSLv2/3 removed in io.js, merging these commits would involve reverting
-* Jeremiah proposed 0.12 being the LTS for SSLv2/3 support
-* Rod: are we happy killing this off?
-* Michael: we don’t know how extensively it’s being used?
-* James: pending research into that question we’ll leave this alone, come back if there’s a compelling reason to revert
-
-### doc: Add new working groups [#15](https://github.com/nodejs/node-convergence-archive/pull/15)
-
-* Michael: Benchmarking and Post Mortem Debugging working groups are ready and have started, i18n group needs a bit more work to get off the ground
-* Group didn’t see any reason not to go forward with these groups, they have repos and can be in an “incubating” state for now
-
-
-### Buffer implemented using Uint8Array [#1810](https://github.com/nodejs/io.js/issues/1810)
-
-* Trevor: Buffer using Uint8Array is now working, all applicable tests pass, currently behind a flag:
-* Trevor Questions:
-  - Are we going with v8 4.3 or 4.4?
-  - If we go v8 4.3, do we want to release behind a flag?
-  - we still want an upper kMaxlength Buffer size limit?
-* Ben: Buffer size limit should be safe to remove
-* Rod: 4.3 and 4.4 both contain major breakage for native addons
-* Discussed if we would like to delay 3.0 until v8 4.4
-* Rod: no appetite here for delaying a 3.0 with 4.3, take discussion on that back to GitHub
-* Ben: suggested we release new Buffer impl with a flag to revert to old impl, Jeremiah seconded
-* Discussed how hard it would be to land and review
-* Fedor: how does it work with 32bit numbers?
-* Trevor: It acts the same as before
-
-### \[Discussion\] FFI - Giving Buffer more low-level C functionality [#1750](https://github.com/nodejs/io.js/pull/1750)
-
-* Trevor: concerns about being able to write to buffers and execute arbitrary code
-* Rod: concerned about changing the nature of what Node _is_ and the safety it exposes
-* Ben suggested that we move this new work to an ffi module rather than hanging it off Buffer
- - Group agreed to take this suggestion back to the issue for discussion
-
-### Chrome 43 released; time for V8 4.3! [#1735](https://github.com/nodejs/io.js/issues/1735)
-
-* Concerns about deps forcing semver-major, the C++ API changes are big enough to warrant this though
-
-### Deprecation Policy [#1704](https://github.com/nodejs/io.js/issues/1704)
-
-* Discussion dividing into two camps - conservative camp and those who want to test the size of the impact on the ecosystem
-* Suggestion (Michael?) that we use LTS releases to determine when things get properly removed
-* Discussed why we want a deprecation policy
-
-### TSC needs to elect a board representative. [#1697](https://github.com/nodejs/io.js/issues/1697)
-
-* Deferred till next meeting - need to nominate and vote someone in to this role and should discuss how we want to structure the role in terms of rotation
-
-### V8 4.4 to remove indexed properties via external data [#1451](https://github.com/nodejs/io.js/issues/1451)
-
-* Nothing to discuss, rolled up in to Buffer discussion earlier
-
-## Next meeting
-
-* June 3rd, 8PM UTC
diff --git a/doc/tsc-meetings/2015-06-03.md b/doc/tsc-meetings/2015-06-03.md
deleted file mode 100644
index e9b75db5d3aaf6..00000000000000
--- a/doc/tsc-meetings/2015-06-03.md
+++ /dev/null
@@ -1,166 +0,0 @@
-# Node.js Foundation TSC Meeting 2015-06-03
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-06-03
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/47
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1sTD0uryasBR15UBzEbJj3oHYtnuN9ZIqVxA2A_-N56E
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* Add working group state per Project Lifecycle. [#1880](https://github.com/nodejs/io.js/pull/1880)
-* Proposal: Split TSC agenda in to two meetings [#1879](https://github.com/nodejs/io.js/issues/1879)
-* Chrome 43 released; time for V8 4.3! [#1735](https://github.com/nodejs/io.js/issues/1735)
-* TSC needs to elect a board representative. [#1697](https://github.com/nodejs/io.js/issues/1697)
-* Expose `deepEqual` and `deepStrictEqual` in `util`. #1172 [#1177](https://github.com/nodejs/io.js/pull/1177)
-
-## Present
-
-* Rod Vagg (TSC)
-* Mikeal Rogers
-* Shigeki Ohtsu (TSC)
-* Chris Dickinson (TSC)
-* Colin Ihrig (TSC)
-* Julien Gilli (TSC)
-* James Snell (TSC)
-* Michael Dawson (TSC)
-* Bert Belder (TSC)
-* Fedor Indutny (TSC)
-* Jeremiah Senkpiel (TSC)
-* Domenic Denicola
-* Alexis Campailla (TSC)
-* Ben Noordhuis (TSC)
-
-## Quick stand-up
-
-* Rod: working on the build, looking into npm smoke-testing
-* Mikeal: getting foundation legalities and officialities in order
-* Shigeki: working on security issues, reviewing root cert update
-* Chris: working on getting npm static analysis working [estoc](https://github.com/chrisdickinson/estoc)
-* Colin: reviewing prs and issues, doing some libuv work (uv_os_homedir, which landed in libuv 1.6.0)
-* Julien: vacation, nodejs.org downtime postmortem
-* James: working on convergence, triaging joyent/node issues
-* Michael: triaging some joyent/node issues, working on powerpc build and npm testing
-* Bert: not much, looked at some issues, discussing with Saul if libuv should move into the Node Foundation
-* Fedor: reviewed some pull requests and issues, working on some openssl mode
-* Jeremiah: issues, convergence, `_unrefActive` timers work, looking at improving Ben’s binary heap implementation
-* Domenic: vm fixes in v8 integrating patches
-* Alexis: patch for timers firing early, CI convergence work - jenkins hackery
-* Ben: reviewing pull requests, making libuv threadpool more scalable
-* Brian: JS dns resolver
-* Trevor: merged UInt8Array Buffer changes into the next branch, additional ArrayBuffer-related changes and fiddling
-
-## Review of last meeting
-
-### nodejs/node
-
-* \[Converge\] timers: Avoid linear scan in `_unrefActive`. [#23](https://github.com/nodejs/node/issues/23)
-* \[Converge\] child_process argument type checking [#22](https://github.com/nodejs/node/issues/22)
-* \[Converge\] SSLv2/3 disable/enable related commits [#20](https://github.com/nodejs/node/issues/20)
-* doc: Add new working groups [#15](https://github.com/nodejs/node/pull/15)
-
-### nodejs/io.js
-
-* Buffer implemented using Uint8Array [#1810](https://github.com/nodejs/io.js/issues/1810)
-* \[Discussion\] FFI - Giving Buffer more low-level C functionality [#1750](https://github.com/nodejs/io.js/pull/1750)
-* Chrome 43 released; time for V8 4.3! [#1735](https://github.com/nodejs/io.js/issues/1735)
-* Deprecation Policy [#1704](https://github.com/nodejs/io.js/issues/1704)
-* TSC needs to elect a board representative. [#1697](https://github.com/nodejs/io.js/issues/1697)
-* V8 4.4 to remove indexed properties via external data [#1451](https://github.com/nodejs/io.js/issues/1451)
-
-## Minutes
-
-### Add working group state per Project Lifecycle. [#1880](https://github.com/nodejs/io.js/pull/1880)
-
-* Mikeal: making working groups as “core” means they get to elect a TSC seat.
-* Brief discussion about what WG’s should be considered “core” and get a TSC seat.
-* Deferred to GitHub.
-
-### Chrome 43 released; time for V8 4.3! [#1735](https://github.com/nodejs/io.js/issues/1735)
-
-Domenic: things are ready to go. There’s some concern about double-breakage in 4.3 and 4.4.
-
-Jeremiah: what about the maybe changes?
-
-Domenic: the non-Maybe versions are still there, and haven’t been removed yet, either in 4.3 or 4.4 or even 4.5 (which isn’t finalized yet though).
-
-Rod: blocker is whether the double-breakage is real, if not then we should move forward.
-
-Domenic: there’s also the issue of some people in the thread advocating blocking a release on readying the ecosystem.
-
-Rod: we shouldn’t be following the ecosystem and waiting for them to catch up before we release.
-
-Mikeal: it’s more a matter of how we approach these things.
-
-Michael: LTS should help this?
-
-Mikeal: the problem is about major releases and the messaging - currently when people download them lots of stuff is broken.
-
-Domenic called for a vote on a 3.0 release _assuming there is no double-breakage_.
-
-Rod: I need to get the fix for node-gyp in place. Also we should see if we can get nvm to allow testing nightlies so that people can test them more easily (including on Travis).
-
-Jeremiah: when I last talked to Jordan (@ljharb) he wanted to make sure that the mechanism we used for nightlies would also be the mechanism used in the converged project.
-
-Mikeal: well that’s definitely true. So we should be good.
-
-Trevor: do we have a way of measuring uptake?
-
-Domenic/Rod: npm traffic is probably the best metric.
-
-Rod calls for a vote.
-
-Domenic: can we clarify whether we allow minor, covered-by-nan breakages between 4.3/3.0.0 and 4.4/4.0.0, or do we require no breakages at all?
-
-Mikeal: is nan released?
-
-Jeremiah: not yet; it is experimental and they don’t release until we merge next into master
-
-Mikeal: that seems bad
-
-(General agreement that we want nan to release first.)
-
-Trevor: looking at nan they seem to be working to encapsulate changes all the way out to V8 4.6.
-
-Bert: what was the problem with putting nan into core?
-
-Rod/Ben: sometimes V8 makes big changes that cause breaking changes in nan. E.g. isolates, buffer changes, maybes. Until now it’s been just individual APIs, but the 4.3 and 4.4 change has been very big. nan’s promise is just that you can write against a single, possibly-changing API that will support multiple node versions.
-
-### Expose `deepEqual` and `deepStrictEqual` in `util`. #1172 [#1177](https://github.com/nodejs/io.js/pull/1177)
-
-Jeremiah: what do we want to expose from core, there’s pressure from some parts of the community for core to be more isomorphic and support a lot of browser stuff. This issue is specifically about exposing what’s already implemented.
-
-Ben: why not pull it out of core and put it in npm? util has always been about utilities that core uses.
-
-Rod: when you expose something you’re stuck with it forever, minimising surface area should be our goal because the more we have to officially support the slower our release cycle will be.
-
-### Proposal: Split TSC agenda in to two meetings [#1879](https://github.com/nodejs/io.js/issues/1879)
-
-Mikeal: the scope of the TSC responsibilities are too wide, making meeting times go to long. The suggestion is to split up in to “project” related issues and “core” related issues.
-
-Rod: can there be a clear distinction between the issues?
-
-Domenic: assuming nobody wanted to attend two meetings, would there be enough?
-
-Mikeal: yes because there are lots of people that aren’t here who would be in the other group
-
-Rod: I wonder about the timing, e.g. letting the foundation kickoff happen first; it feels a bit premature to split now.
-
-Mikeal: it’s a little premature but that’s because we haven’t onboarded the core working groups to this meeting.
-
-Bert: in favour of the proposal.
-
-_Discussed the pros and cons and agreed to tentatively move forward with experimentation, time slot for the new “project” meeting would either be after the current meeting or the day after that meeting._
-
-### TSC needs to elect a board representative. [#1697](https://github.com/nodejs/io.js/issues/1697)
-
-***Call ended prematurely due to Uberconference difficulties***
-
-## Next meeting
-
-* 
-
diff --git a/doc/tsc-meetings/2015-06-10.md b/doc/tsc-meetings/2015-06-10.md
deleted file mode 100644
index a554b582649568..00000000000000
--- a/doc/tsc-meetings/2015-06-10.md
+++ /dev/null
@@ -1,184 +0,0 @@
-# Node Foundation TSC Meeting 2015-06-10
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-06-10
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/53
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1cn7SKaKYUMYLBiQhE6HAAknnwPabKsYjpOuyQkVikW8
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* Add working group state per Project Lifecycle. #1880
-* Chrome 43 released; time for V8 4.3! #1735
-* TSC needs to elect a board representative. #1697
-
-### joyent/node
-* Nominating new collaborators to this repository #25481
-* Node should not automatically change rlimits #8704
-* Re-purpose previous joyent/node TSC meeting as LTS working group
-* Releases for logjam - expect new openssl version soon (possibly should be discussed in LTS working group instead)
-
-## Minutes
-
-### Present
-
-* Shigeki Ohtsu (TSC)
-* Colin Ihrig (TSC)
-* Alexis Campailla (TSC)
-* Bert Belder (TSC)
-* Ben Noordhuis (TSC)
-* Julien Gilli (TSC)
-* Mikeal Rogers
-* Michael Dawson (TSC)
-* Domenic Denicola
-* Brian White (TSC)
-* Bradley Meck
-* Trevor Norris (TSC)
-
-### Quick review of the previous meeting
-
-* **Bert**: Discussed adding WG for project life cycle. Don’t remember what the idea was.
-* **Mikeal**: Need to merge the associated PR.
-* **Bert**: Discussed upgrading V8 to 4.3. Some contention, much in favor of doing it. Issue is V8 is changing API in 4.3 and 4.4 again.
-* **Trevor**: Biggest issue is nan 2.0 hadn’t come out yet. There would be a gap in time when no native module would work.
-* **Bert**: Resolution was that we would try to get nan to update asap. If 4.4 wasn’t done yet we would not upgrade to 4.3 yet.
-* **Bert**: Mikeal had proposed to split meeting in two different meetings: one technical, one non technical.
-
-### Standup
-
-* **Shigeki**: preparing for the next OpenSSL update.
-* **Michael**: working on triaging issues, made sure V8 beta/stable build properly on PPC. Internally setup some build to build io.js next on PPC, so that we can hook up build machines asap.
-* **Colin**: mostly just reviewed PRs and triaged issues.
-* **Brian**: mostly triaging issues, looked at some PRs.
-* **Julien**: triaged issues, reviewed PRs. Started documenting Node.js’ release process and CI platform. Also started to document breaking changes between v0.12 and the converged repo between io.js and Node.js.
-* **Alexis**: investigations on native addon WG.
-* **Bert**: not a lot of technical work. Working on libuv changes to make the multi isolate/workers stuff work. PR #396 in libuv.
-* **Ben**: reviewed PRs.
-* **Domenic**: some reviews and tried to gear up for 3.0.
-* **Trevor**: Lot of reviewing and landing of PRs, prototype for lower-level JS API. Worked on async listeners API.
-* **Bradley**: here for rlimits discussion on the agenda.
-* **Mikeal**: launch of the foundation, getting the PR ready and working on nodeconf that starts tomorrow.
-
-### Today’s agenda
-
-#### Add working group state per Project Lifecycle
-
-* **Mikeal**: pretty much resolved, we just need to close the PR.
-
-#### Chrome 43 released; time for V8 4.3
-
-* **Domenic**: not sure if there’s much progress on that. Haven’t seen news from nan.
-* **Bert**: remove tsc-agenda, someone should put back the tag when there’s news.
-
-#### TSC needs to elect a board representative.
-
-* **Mikeal**: thought that we had a resolution, and Bert and Rod would both be on the board for a short time.
-* **Bert**: see if that can stay that way in the long term. Any objection?
-* **Michael**: have we approached other people from the foundation to see if that’s possible?
-* **Bert**: haven’t reached out yet. Who is organizing these meetings?
-* **Mikeal**: Mike Dolan.
-* **Bert**: Will send an email to see if that’s feasible.
-* **Michael**: what about voting?
-* **Mikeal**: we would need to put down just one person who has voting rights.
-* **Michael**: having two present in meetings, only one who has the vote is fine by me.
-* **Bert**: I don’t expect to be any kind of contention, trademark is probably the only one I can think of now.
-* **Mikeal**: It seems that people don’t have a good idea of what will be decided during these meetings, so maybe we can just flip a coin for this short period of time, and then when we know more of what’s discussed in these meetings we can have a vote.
-* **Michael**: maybe have some sort of alternance between two people in the beginning?
-* **Bert**: I think it would still be good to have one person who will always be there.
-* **Bert**: proposed resolution: let’s both (Rod and I) be there and then we’ll reevaluate later.
-
-#### Nominating new collaborators to this repository
-
-See https://github.com/joyent/node/issues/25481.
-
-Main question was: should we add nominated collaborators who are not io.js collaborators too the “collaborators” team in the nodejs organization too?
-
-Decision was that it might be confusing at first, so onboarding of these collaborators will be done first in joyent/node only, but they will conceptually be Node.js collaborators (as in collaborators in the nodejs GitHub organization). Shortly after they will be added as io.js collaborators by people familiar with the onboarding process at io.js.
-
-#### Node should not automatically change rlimits
-
-* **Bradley**: summary is in node v0.10. Node respected soft ulimit for fds. Soft limit is recommended limit, second one called hard limit which is an enforced limit. By default, OSX has a very low soft limit, and that’s the reason why this patch landed. However when running programs, they usually don’t change rlimits, and we started seeing failures after the patch landed. Argument for the side for keeping the patch, you don’t hear people complaining about being out of file descriptors.
-* **Michael**: did patch change only for OSX?
-* **Bradley**: did for all platforms. Hard limit becomes soft, soft limit are erased.
-* **Michael**: fix means you don’t see errors?
-* **Bradley**: yes, but it has undesirable side effects. Traditionally when you limit resources, you set soft limits to what you want your process to be able to get. Node started to ignore those, so we started seeing things like fds leaks not being caught, etc.
-* **Ben**: why wouldn’t you set the hard limit to the soft limit?
-* **Bradley**: This patch completely erases your soft limit, can’t recover it. No option to use soft limits at this point. Cluster would want very high limit, workers would want lower limit. Using soft limit is usually how people do that. You can use hard limits, but once you do that you’re talking about absolute enforcement.
-* **Bert**: proposal is to revert the patch?
-* **Bradley**: couple options. Ideal option to me is to revert the patch. I would expect UNIX programs to leave my settings alone. I would at least expect an option to recover the soft limits. Having some way to pass settings via command line maybe?
-* **Bradley**: either command line flag or environment variable. Problem with command line anything that spawns with something like fork would ignore it.
-* **Bert**: actually happy that the patch landed. Just works solution seems better, I’ve seen so many problems in production. Two concerns: agree this is a bit weird that node changes limits of child processes. Would not be opposed to use an environment variable.
-* **Bradley**: argument will come from sysadmins, not people not familiar with EMFILE and rlimits. Usually you see the EMFILE error, you request to someone to bump this limit and the problem is solved.
-* **Trevor**: what if we added process.resetRlimits and when that process spawns it resets rlimits.
-* **Bradley**: need to pass that to child processes still.
-* **Trevor**: if using cluster, then that seems easy.
-* **Bert**: Don’t like having globals for that kind of stuff, related to multi isolates. Maybe add as an option to child_process.spawn?
-* **Trevor**: how would that help regarding multi isolates environments?
-* **Bert**: Yeah, not suggesting to be able to set different limits per isolate. Ben any opinion?
-* **Ben**: Resetting rlimits when we spawn new process would be fine. Don’t care about environment variable that would make node not touch rlimits.
-* **Domenic**: Does node change system wide rlimits?
-* **Bradley**: that depends on how the node process lifecycle.
-* **Domenic**: Is there any way to ignore rlimits while not changing system wide rlimits?
-* **Bradley**: it’s a per process setting. Want a way to keep limits to get warnings about file descriptors, and a way to recover limits in child processes. I can write a patch for that.
-* **Ben**: Keep in mind you’ll probably need to update libuv in some way. Forking takes places in libuv.
-* **Bert**: summary: node will restore rlimits on spawn.Other thing would be command line switch or environment variable.
-* **Ben**: How are you going to use that?  Are you using sandbox?
-* **Bradley**: Not using sandbox. When I see EMFILE, I can set a warning that notifies me when things go crazy.
-
-##### Resolution
-
-* The current (rlimit-changing) behavior will be maintained.
-* Node/libuv should restore the ulimit for the child processes it spawns.
-* Support for leaving the ulimit untouched by setting an an environment variable will be added.
-* Bradley Meck is going to create patches to node and libuv for this.
-
-#### New OpenSSL version about to be released, with fixed for logjam
-
-* **Michael**: will need a v0.10 and v0.12 release when OpenSSL release comes out.
-
-#### Repurpose previous node.js TSC meeting as LTS WG meeting
-
-* **Julien**: timing might not work for anyone.
-* **Bert**: Rod pinged a bunch of people, haven’t seen a lot of response. Wyatt Preul is involved, you will probably want to reach out to him, Same for ofrobots.
-* **Michael**: want to make sure that everyone is ok with merging LTS meeting with joyent/node TSC meeting.
-* **Julien**: discussion ongoing here: https://github.com/nodejs/LTS/issues/6#issuecomment-109352447.
-
-### Discussion items not on the agenda
-
-#### 3.0 upgrade documentation
-
-* **Trevor**: haven’t seen any doc on how to upgrade to 3.0. Should be put notes about breaking changes there, or somewhere else?
-* **Domenic**: hard part is C++ side changes. Everything else should be handled by semver-major/minor labels.
-
-### Rebasing on top of the 'next' branch (not on the agenda)
-
-* **Trevor**: rebase of next on master is going to be fairly broken. Is there somebody who usually takes those merges?
-* **Ben**: Not sure I understood.
-* **Trevor**: Lots of fixes that went into 2.x will not merge cleanly in next. Some of the fixes are minor. Fix in zlib that uses kMaxLength.
-* **Ben**: what’s the question?
-* **Trevor**: wondering who’s responsible for the merge? Maybe I can help with that?
-* **Ben**: most of the time I do that. I usually create a PR and ask people to give a quick sign off on it.
-
-##### Action items 
-
-* Trevor will document C++ side changes.
-
-#### Workers (multi-isolate) PR
-
-* **Bert**: decided to take a look at the multi isolates patch. I know that Ben tried to review it and went half-way through.
-* **Trevor**: tried twice now and haven’t managed to go all the way through.
-* **Bert**: proposed solution is to just make sure it doesn’t break anything major, put it behind a flag and review it in more details later.
-* **Trevor**: a lot of stylistic issues, and haven’t got any response.
-* **Ben**: petka mentioned he’s quite busy at the moment. Maybe someone could address these comments?
-* **Bert**: ping petka, maybe we can land it in small increments. Do we want it to be perfect before it lands?
-* **Ben**: not comfortable landing code that hasn’t been reviewed.
-* **Trevor**: nice thing is that there’s a lot of tests. Didn’t see anything invasive that would make things difficult later. One change that I don’t understand 100%. I would depend on someone else to give the OK.
-* **Bert**: interesting and valuable change, it needs work to get landed.
-
-## Next meeting
-
-Will be held on June 17th, 1pm PST.
diff --git a/doc/tsc-meetings/2015-06-17.md b/doc/tsc-meetings/2015-06-17.md
deleted file mode 100644
index c07fe82b7050e2..00000000000000
--- a/doc/tsc-meetings/2015-06-17.md
+++ /dev/null
@@ -1,134 +0,0 @@
-# Node Foundation TSC Meeting 2015-06-17
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-06-17
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/56
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1d4mAJgm06rpPWLDqhZcxsRnKMrS92Ip4CW2akOyeIL4
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/node
-
-* Create a security team [#48](https://github.com/nodejs/node-convergence-archive/issues/48)
-
-### nodejs/io.js
-
-* Nominating Shigeki Ohtsu @shigeki to the TC [#1501](https://github.com/nodejs/io.js/issues/1501)
-* Nominating Brian White @mscdex to the TC [#1500](https://github.com/nodejs/io.js/issues/1500)
-* on working with proposals from the API WG [#1993](https://github.com/nodejs/io.js/issues/1993)
-* zlib: prevent uncaught exception in zlibBuffer [#1993](https://github.com/nodejs/io.js/issues/1811)
-* Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-### joyent/node
-
-* Nominating new collaborators to this repository [#25481](https://github.com/joyent/node/issues/25481)
-
-## Minutes
-
-
-### Present
-
-* Rod Vagg (TSC)
-* Colin Ihrig (TSC)
-* Chris Dickinson (TSC)
-* Michael Dawson (TSC)
-* Mikeal Rogers
-* Steven R. Loomis (TSC)
-* Bert Belder (TSC)
-* Alexis Campailla (TSC)
-* Julien Gilli (TSC)
-* Shigeki Ohtsu
-* Jeremiah Senkpiel (TSC)
-* Brian White
-* Trevor Norris (TSC)
-* Domenic Denicola
-* Fedor Indutny (TSC)
-
-### Review of the previous meeting
-
-* Add working group state per Project Lifecycle
-* Chrome 43 released; time for V8 4.3
-* TSC needs to elect a board representative.
-* Nominating new collaborators to this repository
-* Node should not automatically change rlimits
-* New OpenSSL version about to be released, with fixed for logjam
-* Repurpose previous node.js TSC meeting as LTS WG meeting
-* 3.0 upgrade documentation 
-* Rebasing on top of the 'next' branch (not on the agenda)
-* Workers PR from Petka
-
-### Standup:
-
-* Rod: build, productive work on improving the ci and build convergence, ci now does linting before running the tests, also improving the io.js make file so that less logic for releases is contained in jenkins
-* Colin: reviewing issues and pr’s, landed a cluster patch to not use --debug_port on cluster workers by default
-* Chris: NodeConf, got great feedback there. PR for code coverage incoming soon, spun up the docs WG.
-  * http://neversaw.us/scratch/node-coverage/ – code coverage
-  * https://github.com/nodejs/docs 
-* Michael: Reviewing OpenSSL changes for LogJam; PPC LE & BE work nearly complete, some OpenSSL blockers (EC related)--working towards including PPC in CI
-* Mikeal: running NodeConf and writing up feedback & foundation work
-* Steven: getting back on board
-* Bert: libuv work for multi-worker on Windows (https://github.com/libuv/libuv/pull/396), found a potential libuv/Windows contributor at NodeConf, NF board meeting
-* Alexis: Working on build & CI convergence with Rod, CI can now automatically decide what options to use for different node versions, and porting node-accept-pull-request CI job.
-* Julien: time off, launching nodejs.org updates for NF launch, working on changes for 0.10/0.12 releases, onboarded two new collaborators for joyent/node - https://github.com/nodejs/LTS/wiki/Breaking-changes-between-v0.12-and-next-LTS-release
-* Shigeki: Working on upgrading OpenSSL, the upgrade process is becoming much simpler, landed the CINNIC whitelist
-* Jeremiah: NodeConf - brought back good feedback, helping spin up the Diversity WG, integrating timers heap impl, struggling with bugs
-* Brian: not much, triage & PR review
-* Trevor: reviewing, commenting, merging, PR to next branch allowing passing ArrayBuffers to Buffers constructor
-* Domenic: reviewing, some work with Trevor, discussing release procedure
-* Fedor: Reviewing issues(?), working on http/2 in node-spdy
-
-### Nominating Shigeki Ohtsu @shigeki to the TC [#1501](https://github.com/nodejs/io.js/issues/1501)
-### Nominating Brian White @mscdex to the TC [#1500](https://github.com/nodejs/io.js/issues/1500)
-
-Called for a vote, got +1's for both candidates from each of: Chris, Rod, Bert, Colin, Trevor, Jeremiah, Julien, Michael, Alexis
-
-### on working with proposals from the API WG [#1993](https://github.com/nodejs/io.js/issues/1993)
-
-* Trevor: started discussions back in advisory board before io.js existed, large companies wanted “official Node.js compatibility” at both module and JS layer. Some dissenting voices in Joyent that prevented things proceeding. After io.js happened the formal discussion ended but informal discussion continued, e.g. in https://github.com/nodejs/nan/issues/349, aim at the C++ level is to reduce API turn-over. Companies involved have their own VMs and want to maintain them for their own purposes (e.g. Chakra, JVM).
-* Trevor: interested in starting a WG or piggy-backing Addon API WG.
-* Domenic: would like more clarity on what this thing could be, is it libuv.js? is it a VM abstraction layer?
-* Bert: would be good to scope this work
-* Trevor: there’s one interest group--concerned with binary addons and not having to ship new versions with each new Node release. Another interest group is concerned with something akin to a process.bindings abstraction layer so you could put the Node JS layer on top of whatever runtime chosen.
-* Bert: standardising the process.bindings API might be easiest but standardising the C++ API has more beneifits because it solves the v8-upgrade-breaks-addons problem.
-* Rod: https://github.com/nodejs/nan/issues/373 is an issue in NAN for organising a meeting for the various groups interested in exploring C++ API compatibility, specifically for addons.
-
-### zlib: prevent uncaught exception in zlibBuffer [#1811](https://github.com/nodejs/io.js/issues/1811)
-
-* Trevor: Issue #1811 is potentially CVE-worthy, it’s been fixed but what is the process for going forward with a CVE if necessary?
-* Rod: security@nodejs.org has an expanded team and security@iojs.org redirects there as well. That team should be delegated to for discussion--if you have concerns then email them and let them be responsible for deciding how to proceed.
-* ACTION: Trevor to email summary of potential security concern to security@nodejs.org for further discussion amongst that group. Potentially also backporting to 0.10 and 0.12.
-
-### Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-* Mikeal:
-  - next branch to be released on a more regular timeline
-need to message to users that are on the “next” branch that there is a tradeoff between new V8 (features + perf) and being able to use native modules
-  - bring next to current, current to LTS
-* Domenic:
-  - core of the proposal:
-    - pseudo-LTS
-    - maintain V8 version for ourselves
-    - don’t backport any breaking changes from master, only features and patches
-    - release this with name that implies “use this to work with native modules and features” ???? (CD - lost track here)
-    - active dev happens here
-* Trevor: Naming is confusing; why isn’t it sufficient to say “this release is LTS”?
-* Mikeal: We don’t want LTS to mean “this is stable”, we want it to mean “I can use this for five years”
-* Trevor: But that’s the same thing, isn’t it?
-* Rod: Using the term LTS is counterproductive (leave it to the LTS working group) – it distracts
-* Trevor: one year span before [V8] is merged – that sounds like LTS
-* Domenic: This is a new release channel/train
-* Mikeal: We need “stable for a year” / “new features in V8, no native modules” / “stable for five years”
-  we stick with semver
-  (CD: Mikeal could you fill this out further?)
-* Domenic: We don’t need to move away from semver for the next branch
-Yearly releases pick a version that aligns
-* Mikeal: don’t call it canary, get a codename – increment one, two, three or five over a year – when we merge into master we choose a new name
-* CD: Could not capture entirety of discussion – moved a bit fast for me.
-* Bert: there is no ideal answer here. Would like mikeal and domenic to continue discussion and come back with something to vote on.
-
-## Next meeting
-
-Next week, 2015-06-24
diff --git a/doc/tsc-meetings/2015-07-01.md b/doc/tsc-meetings/2015-07-01.md
deleted file mode 100644
index 9fcbd9e2a36884..00000000000000
--- a/doc/tsc-meetings/2015-07-01.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Node Foundation TSC Meeting 2015-07-01
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-07-01
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/60
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1TN3Ks0fC4ciY3jeS0VxXxXRkT_dq8-tfs-bWQqZGRoE
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* Policy for PR blocking? [#2078](https://github.com/nodejs/io.js/issues/2078)
-* International WG
-* lts: strawman LTS cycle [lts#13](https://github.com/nodejs/LTS/pull/13) / Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-## Minutes
-
-### Present
-
-* James Snell (TSC)
-* Bert Belder (TSC)
-* Steven Loomis (TSC)
-* Chris Dickinson (TSC)
-* Mikeal Rogers
-* Trevor Norris (TSC)
-* Brian White (TSC)
-* Jeremiah Senkpiel (TSC)
-
-### Review of the previous meeting
-
-* discussion of stability for internal APIs [#2030](https://github.com/nodejs/io.js/issues/2030)
-* Nominating new collaborators to this repository [#25481](https://github.com/joyent/node/issues/25481)
-* Use something that’s not uberconference ?
-
-### Standup:
-
-* James: continued triaging of joyent/node issues, working on the LTS strawman proposal
-* Bert: not much on node, some minor libuv and installer stuff
-* Steven: Intl WG work
-* Chris: Not too much on node, working on docs tooling
-* Mikeal: working on a conferencing solution / replacement
-* Trevor: webassembly discussion, api wg
-* Brian: not much, triaging io.js issues and PRs
-* Jeremiah: reviewing PRs and issues, more work on `_unrefActive()`
-* Rod: busy week, worked on the build & release procedures. New jenkins job for all the types of release builds. v3.0.0 is now blocked on NAN. It’s a very big job. Node-gyp in `next` now works for rc’s and nightlies, and downloads a tarball of just the headers. First LTS WG meeting was also productive.
-
-
-### Policy for PR blocking? [#2078](https://github.com/nodejs/io.js/issues/2078)
-
-* Steven Belanger tagged this issue: can we come up with a policy for dealing with PRs that block each other?
-* James clarified that this specific issue was about the url parsing changes, there were a couple of PRs that blocked each other
-* Chris: the PRs here are a “hot stove” situation where they all break url functionality so they are not trivial
-* Chris listed some of the blocking issues that are mainly held up because people are too busy so we probably need a way to communicate status to the community
-* James: would like to table this issue until it really becomes a problem
-* Bert: we could introduce some workflows - e.g. if you introduce an issue that is blocked on something else then you could mention that it’s blocked
-* Jeremiah: more relevant to communicate when things are in the pipeline and provide feedback for timelines so people are reasonably blocked but can be unblocked if there is no activity
-* Rod: doesn’t feel like something that needs a policy, perhaps it’s an open source 101 skill
-* Mikeal: the problem is that often people who are blocking each other don’t have context so need shepherding by someone with context.
-* Rod: doesn’t seem like there’s actionable items here, come back when there’s something more concrete to discuss
-* Bert: the workers PR has stalled because of Petka’s lack of time, anything that it’s blocking should just move forward, url changes are unlikely to get in as they are now because they are so _breaking_
-
-### Internationalization WG (Steven)
-
-* https://github.com/nodejs/internationalization (repo)
-* https://github.com/nodejs/internationalization/issues/4 (README)
-* https://github.com/nodejs/internationalization/issues/5 (CFP)
-
-* Steven introduced the work towards getting this set up
-* Steven clarified the scope of the work (this is done in the README), it’s different to outreach and user assistance (i.e. the i18n translation stuff that io.js already has).
-* Jeremiah suggested we name the group after `Intl` so it’s clearer what it’s about.
-* James: It’s about Intl stuff in the code, unicode, REPL dying because of bad unicode
-* Mikeal: We’ve talked about starting a formal translation/language group that unifies all of the independent translation efforts. That’s probably why people are showing up for this group thinking it’s the translation group that we’ve talked about setting up. We should set up that separate group and maybe use `Intl` as the name for this separate group.
-* Bikeshedded naming for a little while.
-* Conclusion: rename as the Intl WG or similar for clarity. (renamed to Intl)
-
-
-### lts: strawman LTS cycle [lts#13](https://github.com/nodejs/LTS/pull/13) / Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-* James walked through the LTS strawman proposal as formulated by the LTS WG
-* Lots of bikeshedding about releases and LTS trivia
-* Mikeal: we can probably move the release discussion to a formal proposal
-
-### Next Meeting
-
-July 8th 2015
diff --git a/doc/tsc-meetings/2015-07-08.md b/doc/tsc-meetings/2015-07-08.md
deleted file mode 100644
index 0b4b60be8c73f7..00000000000000
--- a/doc/tsc-meetings/2015-07-08.md
+++ /dev/null
@@ -1,131 +0,0 @@
-# Node Foundation TSC Meeting 2015-07-08
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-07-08
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/64
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1HuRtu5ZP7ZlrIp756EbZYo4I26v2RY-7CY1pr_3y1nY
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* Default Unhandled Rejection Detection Behavior [#830](https://github.com/nodejs/io.js/issues/830)
-
-### joyent/node
-
-* Adding a "mentor-available" label [#25618](https://github.com/joyent/node/issues/25618)
-
-## Minutes
-
-
-### Present
-
-* Mikeal Rogers
-* Colin Ihrig (TSC)
-* Ben Noordhuis (TSC)
-* James Snell (TSC)
-* Fedor Indutny (TSC)
-* Bert Belder (TSC)
-* Michael Dawson (TSC)
-* Steven R Loomis (TSC)
-* Alexis Campailla (TSC)
-* Jeremiah Senkpiel (TSC)
-* Julien Gilli (TSC)
-* Chris Dickinson (TSC)
-* Shigeki Ohtsu (TSC)
-* Trevor Norris (TSC)
-* Domenic Denicola
-* Brian White (TSC)
-* Rod Vagg (TSC)
-
-### Review of the previous meeting
-
-* Policy for PR blocking? [#2078](https://github.com/nodejs/io.js/issues/2078)
- - Resolution was to deal with it on a case-by-case basis for now.
-
-* Internationalization WG (Steven)
- - Steven Loomis is going to kick off the working group.
- - Steven: no further responses on the github issue.
- - James: just need to get started
-
-* lts: strawman LTS cycle [lts#13](https://github.com/nodejs/LTS/pull/13) / Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-
-### Standup:
-
-* Mikeal Rogers: wrote a new confrence call tool for us that uses Twillio
-* Colin Ihrig: Not much, reviewing PRs, triaging issues.
-* Ben Noordhuis: reviewed a lot of PRs, upgraded v8 in `next` and `next+1`.
-* James Snell: Working on the LTS Proposal, triaging issues in joyent/node, investigating stuff for the upcoming openssl fix.
-* Fedor Indutny: fixed node after v8 upgrade. Exposed critical issues.
-* Bert Belder: Not much code, had conversations with Mike Dolan and James Snell about the foundation and organizational issues. Working through a laundry list of libuv PRs blocking the next release.
-* Michael Dawson: Working on getting PowerPC to build on io.js, tested the security fix from last week, joyent/node triage.
-* Steven R Loomis: Worked a bit on the Intl WG, not much else.
-* Alexis Campailla: converged CI, almost done. Dealing with windows installer issues. Expect converged CI to work in a week.
-* Jeremiah Senkpiel: General triaging and reviewing, helped do the release last friday. `_unrefActive` with optimizations with heap timers. At CascadiaJS the next of the week to get people’s feedback.
-* Julien Gilli: Released 0.12.6 last week, working on setting up other people to do joyent/node releases, joyent/node issue triage
-* Chris Dickinson: Working on docs more, have a new tool for docs to make sure the links are correct in a tree of docs, started a collaborator check-in on the io.js issue tracker, hopefully will be weekly.
-Jeremiah: what is that doctool? 
-Chris: “count-docula”, a MDAST-based tool to verify correctness of the docs.
-* Shigeki Ohtsu: Not much on io.js, preparing to update OpenSSL tonight to get the OpenSSL security fix out.
-* Trevor Norris: Investigating the UTF8 decoder security issue and working on the fix. Reviewing PRs and being involved in the W3C Web Assembly working group.
-* Domenic Denicola: Not much on io.js, travelling, stress testing the vm module.
-* Brian White: Triaging issues, working on the javascript http parser more & benchmarking it.
-* Rod Vagg: We should discuss the LTS proposal again since there was lots of work done on that. Working on lots, including the security fix from last friday (writing up a post-mortem for it), getting external people involved to review our security processes.
-
-### Default Unhandled Rejection Detection Behavior [#830](https://github.com/nodejs/io.js/issues/830)
-
-* Domenic: let’s say there was a magic way to detect when an error in an err-back style callback was not handled, what would we do? Print to stderr?
-* Bert: We do have a history of printing things to stderr. We should follow browser semantics if we can, in favor of primnting a warning but nothing else.
-* Discussion about the technicalities of handling unhandledRejections
-* Rod: not sure we should do anything since detecting this is somewhat arbitrary.
-* Domenic: there is a proposal for this that chrome implements behind a flag that comes close to how the unhandledRejection hook in node works
-* Discussion about the technicalities of having a better hook for printing a warning after garbage collection of an unhandled rejection.
-* See this thread for background detail of options in v8: https://code.google.com/p/v8/issues/detail?id=3093#c1
-* Action: nothing now, maybe if v8 adds a hook for when rejections get garbage collected.
-* Domenic: looking at v8, it seems to have most of the hooks, so this may be possible soon.
-
-### Adding a "mentor-available" label [#25618](https://github.com/joyent/node/issues/25618)
-
-* Folks are interested in contributing to larger tasks, need mentors to help them understand the process. Should we add a label?
-* Julien: Many people are interested in making “deeper” contributions, but they need a mentor. Let people add a mentor-available tag so they can locate these.
-* … part of the discussion missing here ...
-* Resolution: let’s try it, one such label has already been added.
-
-### Having more people managing releases for Node.js v0.10.x and v0.12.x
-
-* Julien: I will have less time to do releases; it needs to become more of a team effort.
-* Alexis: in the long term this will be a responsibility of the build team.
-* Julien: unsure how responsibilities will be decided. LTS will need to sign off and build will need to produce the release.
-* Jeremiah: the iojs/current releases are already a group effort. It’s just that the “long-term” v0.10/v0.12 releases fall on few individuals now.
-* Julien: it’s a bit too much to handle for one person. Also people are sometimes unavailable or on vacation. Would like to have a group of about four people.
-* Ben: more contributors recently signed up. I think Sam Roberts might be interested.
-* Julien: would like to have a release management team.
-* Chris: iojs has had the release manager propose other release managers. Open an issue for this.
-* Resolved as such.
-
-### lts: LTS Proposal https://github.com/nodejs/LTS#proposed-lts)/ Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-* James: when are we cutting over to the converged stream? Thinking of late august, first LTS release in October. Is this a good time? Most users won’t start migrating until next year because of the holidays.
-* Julien: what are other projects doing, when do they release?
-* James: looking it into it, some do it in fall. No clear pattern.
-* Alexis: what is the benefit of being on a fixed release schedule?
-* James: benefit is it makes planning easier.
-* Trevor: coming from the enterprise side, not having a predictable release schedule isn’t useful.
-* Steven: ICU and Unicode has announced that there will be a yearly release. It’s been helpful for planning.
-* James: It also ties into our regular release schedule and merging next into master etc. The next-to-master merge defines when we can do an LTS release. This should happen at least twice a year. The LTS is cut just before a merge (major bump), so by the time a LTS is cut it should have been stable for half a year.
-* James: please kick tires on this proposal, get feedback from the user communities you’re connected to wrt the frequency and release date.
-* Rod: the TSC should consider the timeframe, and the requirement that there should be two next-to-master merge yearly.
-* Trevor: how does this fit with a 6-week release schedule on master?
-* James: depends on the schedule.
-* Domenic: I don’t see the problem. Just take a 6 months old release and turn it into an LTS.
-* Rod/James/Trevor: because version numbers. The LTS version number needs to be a continuation of a release version.
-* Rod: fixed date, or part of the month.
-* Chris, Rod: get feedback, comment on the issue 
-
-### Next Meeting
-
-July 15th 2015
diff --git a/doc/tsc-meetings/2015-07-15.md b/doc/tsc-meetings/2015-07-15.md
deleted file mode 100644
index c78be93bc6d2cb..00000000000000
--- a/doc/tsc-meetings/2015-07-15.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# Node Foundation TSC Meeting 2015-07-15
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-07-15
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/67
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1r8boI4E67Cq7PEsYeIpXkFZM0be4Ww5UDlNr_uXOop0
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* Intl [#238](https://github.com/nodejs/io.js/issues/238)
-* TC39 representation [#2153](https://github.com/nodejs/io.js/issues/2153)
-
-### Other
-
-* Foundation Discussion
-* lts: [LTS Proposal](https://github.com/nodejs/LTS#proposed-lts) / Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-## Minutes
-
-### Present
-
-* Mikeal Rogers
-* Colin Ihrig (TSC)
-* James Snell (TSC)
-* Fedor Indutny (TSC)
-* Michael Dawson (TSC)
-* Steven R Loomis (TSC)
-* Alexis Campailla (TSC)
-* Jeremiah Senkpiel (TSC)
-* Shigeki Ohtsu (TSC)
-* Trevor Norris (TSC)
-* Domenic Denicola
-* Brian White (TSC)
-* Angela Brown (Linux F)
-* Mike Dolan (Linux F)
-* Laura Kempke (Linux F)
-* Bert Belder (TSC)
-
-### Review of the previous meeting
-
-* Default Unhandled Rejection Detection Behavior [#830](https://github.com/nodejs/io.js/issues/830)
-* Adding a "mentor-available" label [#25618](https://github.com/joyent/node/issues/25618)
-* Having more people managing releases for Node.js v0.10.x and v0.12.x
-* lts: [LTS Proposal](https://github.com/nodejs/LTS#proposed-lts) / Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-### Standup:
-
-* Steven Loomis: Intl WG - https://github.com/nodejs/io.js/issues/2165
-* Mikeal Rogers: Meeting with the Linux Foundation
-* Colin Ihrig: Issues & PRs, met with Julien & Sam for joyent/node release onboarding
-* James Snell: Deep diving on a couple issues, looking into TC39 involvement, LTS feedback
-* Fedor Indutny: some bugs and node-spdy, not too much
-* Alexis Campailla: build-related things to converge the CI, most of the work is done, trying to get the CI working for 0.10. Also speeding up arm builds. +Windows issues.
-* Jeremiah Senkpiel: CascadiaJS Feedback was positive for the project convergence, sick from the cascadiajs cold, not much else.
-* Shigeki Ohtsu: Did the security update for OpenSSL on thursday
-* Domenic Denicola: Not much, working on the unhandled rejection spec.
-* Brian White: Mostly working on the JS Http parser, also working on a JSPerf.com-like tool for testing different node versions from the browser.
-
-### Foundation Discussion (@mikeal leading)
-
-Security policy best-practices
-
-### Intl [#238](https://github.com/nodejs/io.js/issues/238)
-
-Discussion if we can land this into `master` rather than `next`.
-
-Action: Check that there is no objection to landing in `master`.
-
-Steven, Domenic, James: Should be a direct port from 0.12, we can work on making a PR.
-
-### TC39 representation [#2153](https://github.com/nodejs/io.js/issues/2153)
-
-Discussion about the legalities of joining officially and if unofficial representation would be workable.
-
-Action: Domenic will invite Mikeal to check out one of the TC39 meetings.
-
-### lts: [LTS Proposal](https://github.com/nodejs/LTS#proposed-lts) / Proposal: Release Process [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-Mikeal: We are effectively working under the new release proposal ([#1997](https://github.com/nodejs/io.js/issues/1997)) now with how `next` / 3.0.0 is going.
-
-Jeremiah: Only real contested point is how we might version the `next` branch releases.
-
-Domenic: Having multiple release train versionings in confusing.
-
-Action: Mikeal will update the current PR and separate any contention points into new PRs for discussion.
-
-### Next Meeting
-
-July 22nd 2015
diff --git a/doc/tsc-meetings/2015-07-22.md b/doc/tsc-meetings/2015-07-22.md
deleted file mode 100644
index bca7d7991fec5a..00000000000000
--- a/doc/tsc-meetings/2015-07-22.md
+++ /dev/null
@@ -1,168 +0,0 @@
-# Node.js Foundation TSC Meeting 2015-07-22
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-07-22
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/69
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1r8boI4E67Cq7PEsYeIpXkFZM0be4Ww5UDlNr_uXOop0
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* doc: add GPG fingerprint for cjihrig [#2217](https://github.com/nodejs/io.js/pull/2217)
-* Process & Approval for Collab Summit Travel Fund [#2213](https://github.com/nodejs/io.js/issues/2213)
-* TC39 representation for the Node.js Foundation [#2153](https://github.com/nodejs/io.js/issues/2153)
-* Next branch release versioning [#2215](https://github.com/nodejs/io.js/issues/2215)
-
-## Minutes
-
-
-### Present
-
-* Mikeal Rogers
-* Rod Vagg (TSC)
-* Colin Ihrig (TSC)
-* James Snell (TSC)
-* Fedor Indutny (TSC)
-* Michael Dawson (TSC)
-* Steven R Loomis (TSC)
-* Jeremiah Senkpiel (TSC)
-* Brian White (TSC)
-* Ben Noordhuis (TSC)
-* Trevor Norris (TSC)
-* Chris Dickinson (TSC)
-* Mike Dolan (Linux F)
-* Emily Ratliff (Linux F)
-
-### Security Policy Discussion
-
-Emily Ratliff from the LF has joined us to help with our security and disclosure policy. TSC members were sent a briefing prior to the meeting.
-
-Discussed ISO 29147 “Vulnerability Disclosure Overview” and ISO 30111 “Vulnerability Handling Processes Overview”.
-
-
-### Review of the previous meeting
-
-* Foundation Discussion (@mikeal leading)
-* Intl [#238](https://github.com/nodejs/io.js/issues/238)
-* TC39 representation [#2153](https://github.com/nodejs/io.js/issues/2153)
-* lts: LTS Proposal (https://github.com/nodejs/LTS#proposed-lts)[ Proposal: Release Process] [#1997](https://github.com/nodejs/io.js/issues/1997)
-
-### Standup:
-
-* Mikeal Rogers: preparing for the foundation board meeting
-* Rod Vagg: working on 3.0 and release candidates / NAN
-* Colin Ihrig: reviewing issues  & PRs, worked with julien to do releases from joyent/node 0.x branches
-* James Snell: working on smoke-testing npm modules
-* Fedor Indutny: doing so bug fixes, and reviewing PRs
-* Michael Dawson: some joyent/node issue triage, PPC build work
-* Steven R Loomis: some Intl WG work, working on getting the Intl commits from joyent/node into io.js
-* Jeremiah Senkpiel: reviewing issues + prs, doing work on REPL in light of 3.0; fixing bugs in REPL
-* Brian White: working more on the in-browser node.js/io.js benchmarking tool, which is now in a usable state. using it now to test current and future performance improvement techniques for the the js http parser
-* Ben Noordhuis: (no mic)
-* Trevor Norris: did a fix for the buffer implementation for the 3.0 release
-* Chris Dickinson: npm work.
-
-### doc: add GPG fingerprint for cjihrig [#2217](https://github.com/nodejs/io.js/pull/2217)
-
-* Rod +1
-* James +1
-* Fedor +1
-* Michael +1
-* Steven +1
-* Jeremiah +1
-* Brian +1
-* Ben +1
-* Trevor +1
-* Chris +1
-
-Action: make sure Colin’s GPG key setup is correct on the PR, after we can merge and Rod can add Colin’s credentials to the build server.
-
-### Process & Approval for Collab Summit Travel Fund [#2213](https://github.com/nodejs/io.js/issues/2213)
-
-* Mikeal: budget auditing requires that spending be approved by the board - need to approve the budget and the process for expenditure of those funds. Mikeal has a proposal for the process with basic limits and a process for having the TSC approve expenditure beyond that.
-
-
-**Process as outlined**
-
-* TSC approves target budget (max amount to spend on travel) and caps on each type of spend (with the possibility that the TSC can approve a specific spend over if need be).
-* Contributors in need of the fund apply (this will happen in the GitHub thread) but should explicitly state if they need flight, accommodation or both.
-* If the number of contributors in need of the fund exceeds the target budget the TSC will prioritize the list of contributors applying for the fund.
-
-
-Voting on approving the process stated above:
-
-* Rod: +1
-* James: +1
-* Fedor: +1
-* Michael: +1
-* Steven: +1
-* Jeremiah: +1 
-* Brian: +1
-* Ben: +1
-* Trevor: +1
-* Chris: +1
-
-
-Specific proposal for August
-
-* 15K max budget (we had previously talked about 10K but I don't think that is enough)
-* Approve a $900 max spend per person on accommodations.
-* Approve a $500 max spend on domestic travel
-* Approve a $1500 max spend on international travel (if someone has to go over it just requires additional TSC approval)
-
-* Rod: +1
-* James: +1
-* Fedor: +1
-* Michael: +1
-* Steven: +1
-* Jeremiah: +1 
-* Brian: +1
-* Ben: +1
-* Trevor: +1
-* Chris: +1
-
-
-Approval for extra expenditure for @joaocgreis (from Portugal): $1,742.66
-
-* Rod: +1
-* James: +1
-* Fedor: +1
-* Michael: +1
-* Steven: +1
-* Jeremiah: +1 
-* Brian: +1
-* Ben: +1
-* Trevor: +1
-* Chris: +1
-
-Approval for expenditure on @yosuke-furukawa (from Japan) max spend of $2400
-
-* Rod: +1
-* James: +1
-* Fedor: +1
-* Michael: +1
-* Steven: +1
-* Jeremiah: +1 
-* Brian: +1
-* Ben: +1
-* Trevor: +1
-* Chris: +1
-
-### Next branch release versioning [#2215](https://github.com/nodejs/io.js/issues/2215)
-
-* Rod outlined the state of play:
-  - LTS WG moved from “proposal” to “plan” but are still depending on the stable release branch having a clear process
-  - LTS WG discussed a proposal by Trevor for how to handle next/canary/alpha & master & release branches & LTS branches: https://gist.github.com/trevnorris/7620a64b086e95271197
-* Mikeal: it’s more helpful if we think about V8 upgrades as a pull-request to master rather than a separate “next” that has to be separately managed.
-
-Much bikeshedding was had in an attempt to move forward.
-
-Group agreed in general with Trevor’s proposal, will organise further discussions amongst the group of interested parties at another time.
-
-### Next Meeting
-
-July 29th 2015
diff --git a/doc/tsc-meetings/2015-07-29.md b/doc/tsc-meetings/2015-07-29.md
deleted file mode 100644
index e3b27a30dd1bda..00000000000000
--- a/doc/tsc-meetings/2015-07-29.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# Node.js Foundation TSC Meeting 2015-07-29
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-07-29
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/71
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1FBmDczHD4D8jfffc6A8CW-K9mmT0KI8shG6dm_d3jXI
-* Previous minutes: https://docs.google.com/document/d/1eCETYn44gAOUp0udl22QxqyxrJ0oEeAFRdWHDCIq9V4
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-### nodejs/io.js
-
-* Next branch release versioning [#2215](https://github.com/nodejs/io.js/issues/2215)
-* TSC Chair - Election? [#2136](https://github.com/nodejs/io.js/issues/2136)
-
-## Minutes
-
-
-### Present
-
-* Mikeal Rogers
-* Rod Vagg (TSC)
-* Colin Ihrig (TSC)
-* James Snell (TSC)
-* Fedor Indutny (TSC)
-* Michael Dawson (TSC)
-* Steven R Loomis (TSC)
-* Jeremiah Senkpiel (TSC)
-* Shigeki Ohtsu(TSC)
-* Ben Noordhuis (TSC)
-* Trevor Norris (TSC)
-* Chris Dickinson (TSC)
-* Alexis Campailla (TSC)
-* Bert Belder (TSC)
-
-### Review of the previous meeting
-
-* Security Policy Discussion
-* doc: add GPG fingerprint for cjihrig [#2217](https://github.com/nodejs/io.js/pull/2217)
-* Process & Approval for Collab Summit Travel Fund [#2213](https://github.com/nodejs/io.js/issues/2213)
-* Next branch release versioning [#2215](https://github.com/nodejs/io.js/issues/2215)
-
-
-### Standup:
-
-* Mikeal Rogers: Got ready for the board meeting, working to get the new website spun up based on the iojs.org build system
-* Rod Vagg: Finished writing NAN 2.0 documentation
-* Colin Ihrig: Issues & PRs, did the 2.5.0 release (armv6 build had an issue), playing around with the citgm package smoke-testing tool
-* James Snell: Working on citgm (npm package smoke-testing), halfway done writing up the release plan
-* Fedor Indutny: ?
-* Michael Dawson: Triaging joyent/node issues / PRs, looking at AIX build support on the `next` branch, looking at updating some docs
-* Steven R Loomis: Worked on the Intl converge PR [#2264](https://github.com/nodejs/io.js/pull/2264)
-* Jeremiah Senkpiel: Issue and PR review, helping to get someone to start contributing to core
-* Ben Noordhuis: not much, reviewed some PRs this week and did some minor patches
-* Trevor Norris: Just had time to review some issues and respond to PRs
-* Chris Dickinson: Not much, did docs work, trying to document streams (again), and the REPL history-paintext change PR [#2224](https://github.com/nodejs/io.js/pull/2224)
-* Alexis Campailla: Working on CI/Jenkins convergence, and some windows issue triage
-* Shigeki Ohtsu: Working on the updated crypto module for weak ciphers
-* Bert Belder: Not much except started reviewing a VS2015 support PR
-
-#### Next branch release versioning [#2215](https://github.com/nodejs/io.js/issues/2215)
-
-Discussion about the release plan (not yet written up, James Snell is working on that.)
-
-#### TSC Chair - Election? [#2136](https://github.com/nodejs/io.js/issues/2136)
-
-Vote?
-
-* Colin: +1
-* Chris: +1
-* James: +1
-* Fedor: +1
-* Michael: +1
-* Steven: +1
-* Jeremiah: +1
-* Shigeki: +1
-* Ben: +1
-* Trevor: +1
-* Chris: +1
-* Alexis: +1
-* Bert: +1
-
-### Next Meeting
-
-Not happening on August 5th (as it usually would).
-Possibly a (short) TSC meeting will be held during the summit.
diff --git a/doc/tsc-meetings/2015-08-12.md b/doc/tsc-meetings/2015-08-12.md
deleted file mode 100644
index 88b08b91cf4e51..00000000000000
--- a/doc/tsc-meetings/2015-08-12.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Node.js Foundation TSC Meeting 2015-08-12
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-08-12
-* **GitHub Issue**: https://github.com/nodejs/node-convergence-archive/issues/71
-* **Minutes Google Doc**: https://docs.google.com/document/d/1q2bFjnf0Y23Ljxoze56Pmrbailaj5-UAqIUqIYVhiIk
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1FBmDczHD4D8jfffc6A8CW-K9mmT0KI8shG6dm_d3jXI>_
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-* Travel assistance amendment (no issue for this)
-* FYI: Collaboration WG: https://github.com/nodejs/collaboration  
-* Summit recap
-* level-set on repo rename
-* Future: “project lifecycle” (Mikeal) - process by which top level projects are added (libuv, node-gyp, etc), (conferences…)
-
-
-## Minutes
-
-
-### Present
-
-* Mikeal Rogers
-* Rod Vagg (TSC)
-* James Snell (TSC)
-* Michael Dawson (TSC)
-* Steven R Loomis (TSC) 
-* Chris Dickinson (TSC)
-* Alexis Campailla (TSC)
-* Brian White (TSC)
-
-### Review of the previous meeting
-
-* Next branch release versioning [#2215](https://github.com/nodejs/io.js/issues/2215)
-* TSC Chair - Election? 
-
-### Standup:
-
-* Mikeal: summit, code & learn project for new collab
-* Rod: Summit, migrating nodejs/io.js to nodejs/node
-* James: convergence, joyent/node PRs
-* Michael: patch for AIX, 0.12 work, Benchmarking meeting
-* Steven: Summit, 1st Intl meeting, Intl convergence work, VS2015 fixes
-* Chris: Summit, Docs repo has taken off, [HTTP lifecycle doc by Bryan English](https://github.com/nodejs/docs/blob/master/src/guides/anatomy-of-an-http-transaction.md)
-* Alexis: Summit, progress on CI convergence, reviewed some PRs.
-* Brian: Triaging and reviewing PRs and Issues.
-
-### Travel assistance amendment (no issue for this)
-
-* Chris Dickinson adding $500 to the travel expenditure 
-* Passed unanimously.
-
-### FYI: Collaboration WG: https://github.com/nodejs/collaboration  
-
-* Steven: new WG coming out of the Summit, Sean (@snostorm) is taking lead on this. One idea under discussion now is to have a multi-timezone meetings for the language working groups.
-* Mikeal: is this going to serve as a collaboration point for the language groups?
-* Steven: https://github.com/nodejs/Intl/issues/9
-* Rod: beyond the language groups, what are the aims of this new group?
-* Steven: trying to address, or having a place to discuss, common items across working groups.
-* James: filling a need to liaise with the other working groups, acting as an intermediary
-
-### Summit recap
-
-* Mikeal: 6 sessions in 2 days, not solid answers to problems but a shared understanding of the common problems, feels like we are on the same page from that
-* Mikeal: bigger sessions: what is the Node API and what is the Node platform? V8 release cycle. Errors and the inconsistencies. Kept coming back to the collaboration WG, which is why it exists. Talked about expanding the collaborator base, idea was to do some collaboration sprints to bring new folks up to speed, https://github.com/nodejs/code-and-learn comes from that idea (there is foundation budget for that).
-* Mikeal: there were extensive notes taken, those are being edited now and will be published into the repo(s) and turned into blog posts.
-
-### level-set on repo rename
-
-* James: what are the remaining things to do - there’s confusion around the naming
-  - Renaming everything in the documentation (README, docs & other misc docs)
-  - Renaming binary
-  - Alexis: finishing convergence work
-* Mikeal: preparing a blog post about what’s happening, will be reviewed and posted soon
-
-### Future: “project lifecycle” (Mikeal) - process by which top level projects are added (libuv, node-gyp, etc), (conferences…)
-
-* Mikeal: the TSC charter states that we will adopt a project lifecycle that will allow us to bring in other _top level projects_. Additionally, the TSC has had to take on board some non-technical work because of its position in the Foundation (voting on expenditure, etc.), a number of TSC members don’t want to be involved in that kind of activity. Have started drafting a new project lifecycle plan which splits off a “Core TSC” that contains the existing TSC members but with a focus on Node.js Core work while the existing TSC will take on board the higher-level foundation work and members can optionally resign if they aren’t interested in that work and we can expand it to non-Core collaborators. https://github.com/nodejs/TSC/tree/lifecycle 
-
-
-### Next Meeting
-
-August 19th
-
diff --git a/doc/tsc-meetings/2015-08-19.md b/doc/tsc-meetings/2015-08-19.md
deleted file mode 100644
index 55b862aa88bbfa..00000000000000
--- a/doc/tsc-meetings/2015-08-19.md
+++ /dev/null
@@ -1,120 +0,0 @@
-# Node.js Foundation TSC Meeting 2015-08-19
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-08-19
-* **GitHub Issue**: https://github.com/nodejs/node/issues/2435
-* **Minutes Google Doc**: https://docs.google.com/document/d/1xsj_4UlrLNxahRvC7SpLtFM3D-Ks6CZEqEM5nyj6bjk
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1q2bFjnf0Y23Ljxoze56Pmrbailaj5-UAqIUqIYVhiIk>_
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests prior to meeting.
-
-* Procedure for rolling out node-accept-pull-request [#2434](https://github.com/nodejs/node/issues/2434)
-* Release procedure changes & nominating @sam-github and @jasnell as releasers [#2416](https://github.com/nodejs/node/issues/2416)
-
-## Minutes
-
-
-### Present
-
-* Mikeal Rogers
-* Rod Vagg (TSC)
-* James Snell (TSC)
-* Michael Dawson (TSC)
-* Steven R Loomis (TSC) 
-* Chris Dickinson (TSC)
-* Alexis Campailla (TSC)
-* Brian White (TSC)
-* Jeremiah Senkpiel (TSC)
-* Shigeki Ohtsu (TSC)
-* Trevor Norris (TSC)
-* Domenic Denicola
-* Ben Noordhuis (TSC)
-* Colin Ihrig (TSC)
-* Bert Belder (TSC)
-
-
-### Standup
-
-* Mikeal Rogers: Linuxconf, preparing next board meeting agenda, nailing down the foundation conf
-* Rod Vagg: build work, memory leak testing, progress towards v4 (mainly infra)
-* James Snell: some joyent/node PR triaging, preparing for nodeconf.eu
-* Michael Dawson: nodeconf.eu, some AIX build work, talking to the v8 team about security notifications
-* Steven R Loomis: Intl WG, landed Intl with small-icu by default in nodejs/node
-* Chris Dickinson: first docs WG meeting, working on streams docs (again), working on docs tooling
-* Alexis Campailla: working on ci convergence and jenkins jobs
-* Brian White: not much, looking over issues and PRs, submitted a couple PRs
-* Jeremiah Senkpiel: not so much, working on 0.10, 0.12 -> v4 upgrade docs, 3.1.0 release which should be ready straight after this meeting.
-* Shigeki Ohtsu: little time to work on node right now, joined the LTS meeting to discuss OpenSSL LTS
-* Trevor Norris: reviewing issues and PRs, noticed a bug in asyncwrap
-* Domenic Denicola: issues and PRs, v8 team has a new Project Manager who is more interested in node; communicated our API stability concerns to him
-* Ben Noordhuis: fixed a big memory leak, fixed a regression in windows module loading, reviewing PRs, responding to bug reports
-
-### Review of the previous meeting
-
-* Travel assistance amendment (no issue for this)
-* FYI: Collaboration WG: https://github.com/nodejs/collaboration  
-* Summit recap
-* level-set on repo rename
-* Future: “project lifecycle” (Mikeal) - process by which top level projects are added (libuv, node-gyp, etc), (conferences…)
-
-### Procedure for rolling out node-accept-pull-request [#2434](https://github.com/nodejs/node/issues/2434)
-
-* Discussed some potential concerns, which were alleviated:
-* Jeremiah: Wondered how to land PRs where nits needed to be fixed.
-* Bert: Concerns about Jenkins costantly building the wrong PR in the io.js CI infrastructure.
-* Trevor: asked for a dropdown to pick the reviewers.
-* Bert: asked whether the job would support landing multiple commits. Alexis confirmed this.
-* Alexis: mentioned that there is also an node-accept-commit job that is more low-level and advanced.
-
-### Release procedure changes & nominating @sam-github and @jasnell as releasers [#2416](https://github.com/nodejs/node/issues/2416)
-
-Votes for @jasnell:
-
-* Rod Vagg: +1
-* Michael Dawson: +1 
-* Steven R Loomis: +1
-* Chris Dickinson: +1
-* Alexis Campailla: +1
-* Brian White: +1
-* Jeremiah Senkpiel: +1
-* Shigeki Ohtsu: +1
-* Trevor Norris: +1
-* Ben Noordhuis: +1
-* Colin Ihrig: +1
-* Bert Belder: +1
-
-Votes for @sam-github:
-
-* Rod Vagg: +1
-* Michael Dawson: +1 
-* Steven R Loomis: +1
-* Chris Dickinson: +1
-* Alexis Campailla: +1
-* Brian White: +1
-* Jeremiah Senkpiel: +1
-* Shigeki Ohtsu: +1
-* Trevor Norris: +1
-* Ben Noordhuis: +1
-* Colin Ihrig: +1
-* Bert Belder: +1
-
-No objections to combining the a whole "release team" to handle all release branches including 0.10, 0.12, stable and LTS.
-
-### node-gyp is now in our org [#2379](https://github.com/nodejs/node/issues/2379)
-
-* Rod: node-gyp has a busy issue tracker and has no tests, needs more eyes
-* Ben: Zero tests?
-* Rod: Correct.
-* Domenic: on Windows Chromium’s depot_tools will automatically download VS community edition and put it in the right place. Someone with copious free time could have node-gyp do similar things.
-
-* Discussed maybe looking at `gn` (the eventual replacement for `gyp`)
-
-* Domenic: even v8 still uses gyp, don’t worry about it for a good while until noise about it being deprecated gets louder
-* Rod: issue [#151](https://github.com/nodejs/build/issues/151) in build has a discussion about precompiled native addons. Chime in!
-
-## Next Meeting
-
-August 26th
diff --git a/doc/tsc-meetings/2015-08-26.md b/doc/tsc-meetings/2015-08-26.md
deleted file mode 100644
index 54cf3377865e08..00000000000000
--- a/doc/tsc-meetings/2015-08-26.md
+++ /dev/null
@@ -1,112 +0,0 @@
-# Node Foundation TSC Meeting 2015-08-26
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-08-26
-* **GitHub Issue**: https://github.com/nodejs/node/issues/2560
-* **Minutes Google Doc**: https://docs.google.com/document/d/1aB76ClCgdjZUw3p-gHq9j6YwU11zWgJ4pmYPEWk6gjE
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1q2bFjnf0Y23Ljxoze56Pmrbailaj5-UAqIUqIYVhiIk>_
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### joyent/node
-
-* Update README to reflect move to nodejs/node [#25897](https://github.com/joyent/node/pull/25897)
-
-### nodejs/node
-
-* doc: merge CHANGELOG.md with joyent/node ChangeLog [#2536](https://github.com/nodejs/node/pull/2536)
-* (guidance on) rename of "language groups" from iojs-* to nodejs-*? [#2525](https://github.com/nodejs/node/issues/2525)
-* Node.js v4 Release Timeline [#2522](https://github.com/nodejs/node/issues/2522)
-
-### nodejs/collaboration
-
-* How to onboard into WG? [#4](https://github.com/nodejs/collaboration/issues/4)
-
-## Minutes
-
-
-### Present
-
-* Rod Vagg (TSC)
-* Brian White (TSC)
-* Steven R Loomis (TSC) 
-* Fedor Indutny (TSC)
-* Bert Belder (TSC)
-* Colin Ihrig (TSC)
-* Ben Noordhuis (TSC)
-* Mikeal Rogers
-* Alexis Campailla (TSC)
-* Trevor Norris (TSC)
-* Shigeki Ohtsu (TSC)
-
-
-### Review of the previous meeting
-
-* Travel assistance amendment (no issue for this)
-* FYI: Collaboration WG: https://github.com/nodejs/collaboration  
-* Summit recap
-* level-set on repo rename
-* Future: “project lifecycle” (Mikeal) - process by which top level projects are added (libuv, node-gyp, etc), (conferences…)
-
-### Standup:
-
-* Rod Vagg: v4 release stuff, got certificates from/for the foundation, new website including CDN offering from CloudFlare
-* Brian White: continuing work on benchmark app for node.js/io.js, triaging, reviewing/answering issues and pull requests.
-* Steven R Loomis: Intl for convergence VS2015
-* Fedor Indutny: http perf improvement PR, reviewing PRS, looking at issue for shared ports for http cluster
-* Bert Belder: busy with work, reviewing libuv PRs and responding to issues
-* Colin Ihrig: Rename from io.js to Node.js, reviewing issues and PRs
-* Ben Noordhuis: Running native addons as part of CI, libuv bugs, reviewing PRs
-* Mikeal Rogers: Website ready for release, working on CloudFlare CDN stuff
-* Alexis Campailla: CI for release, parallelising test runs for ARM, looking at managing dependencies with git
-* Trevor Norris: reviewing PRs and issues
-* Shigeki Ohtsu: reviewing convergence tests for SSLv2/3, working on TLS ALPN features before freeze
-
-### Update README to reflect move to nodejs/node [#25897](https://github.com/joyent/node/pull/25897)
-
-* Alexis: made changes in CI to prepare for this, we’ll keep PRs in original repo, node-accept-pull-request will land changes in new repo as well, mirroring changes in 0.10 and 0.12 across both old and new repos. Still using the old Jenkins for releases for 0.10 and 0.12 right now and that doesn’t depend on repo name & location.
-Target ETA for transition: Monday.
-
-
-### doc: merge CHANGELOG.md with joyent/node ChangeLog [#2536](https://github.com/nodejs/node/pull/2536)
-
-* Rod seeking confirmation from this group that this was _not a bad idea_.
-* Discussion about documentation for people upgrading from older versions of Node and having a linear history. Jeremiah has been working on 0.10 -> v4 documentation.
-
-### (guidance on) rename of "language groups" from iojs-* to nodejs-*? [#2525](https://github.com/nodejs/node/issues/2525)
-
-* Steven discussed renaming the language groups
-* Mikeal: some groups are not in a position to make decisions because they are not active but the ones that are should be given the opportunity to agree or disagree to the move rather than us imposing a move on them. We should post an issue in their repos.
-* Steven: we should give them a timeline in issues in their repos
-* Discussed naming, could be “lang” or “community” to make it more clear what they are about.
-* ACTION: Steven to add a proposal to #2525, let TSC/collaborators add comments, later in the week will reach out to each of the groups.
-
-### Node.js v4 Release Timeline [#2522](https://github.com/nodejs/node/issues/2522)
-
-* Rod gave a summary of the proposed release timeline https://github.com/nodejs/node/issues/2522 (and appologised for documenting it as “the” release proposal just for the sake of getting it done). 
-  - “feature freeze” Friday, 28th of August, cut v4.x branch
-  - nodejs.org DNS changeover to new website Monday, 31st of August
-  - release Thursday, 3rd of September
-  - RC builds between website and release
-  - backup release date of Monday, 7th of September if absolutely necessary to punt
-* Discussed the outstanding items in the 4.0.0 milestone: https://github.com/nodejs/node/milestones/4.0.0, some concerning items:
-  - mdb support is late and may not get done, might have to be a semver-minor prior to LTS
-  - vcbuilt.bat needs to use the new build_release target and we have to verify that all builds have Intl enabled - Steven to work with Rod on this
-  - `process.send()` async/sync, Ben said that this is async on all platforms now (was just Windows previously but now it’s cross-platform) but it’s missing a callback so there’s no way of doing back-pressure. No time to add this prior to v4 but could be done as semiver-minor later. Ben agreed to document current behaviour properly in the docs.
-  - `_unrefActive` is in Jeremiah’s hands, he will land the 0.12 changes as the io.js version is terrible. Discussed further perf improvements but agreed to leave those changes till later, ideally till v5 because of the potential for subtle edge-case bugs being introduced.
-
-### How to onboard into WG? [nodejs/collaboration#4](https://github.com/nodejs/collaboration/issues/4)
-
-* Discussed GitHub onboarding mechanics
-
-### V8 embedders unified debugger proposal
-
-* Trevor raised https://github.com/nodejs/node/issues/2546 which is a proposal for a unified debugger for V8 embedders using Chromium DevTools.
-* Discussion ensued, agreed to leave it for GitHub discussion unless/until there is something the TSC actually needs to make a decision about.
-
-### Next Meeting
-
-September 2nd
diff --git a/doc/tsc-meetings/2015-09-02.md b/doc/tsc-meetings/2015-09-02.md
deleted file mode 100644
index 36f3a9efb7ae9e..00000000000000
--- a/doc/tsc-meetings/2015-09-02.md
+++ /dev/null
@@ -1,418 +0,0 @@
-# Node Foundation TSC Meeting 2015-09-02
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-09-02
-* **GitHub Issue**: https://github.com/nodejs/node/issues/2654
-* **Minutes Google Doc**: https://docs.google.com/document/d/1rXBdtsD9PJTExNXgzNZ9bez9oOjW45kLPjun4zdt0dY
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1aB76ClCgdjZUw3p-gHq9j6YwU11zWgJ4pmYPEWk6gjE>_
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node
-
-* deps: update v8 to 4.5.103.30 [#2632](https://github.com/nodejs/node/pull/2632)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-* Node.js v4 Release Timeline [#2522](https://github.com/nodejs/node/issues/2522)
-* doc: update COLLABORATOR_GUIDE.md [#2638](https://github.com/nodejs/node/pull/2638)
-
-### nodejs/build
-
-* Merge job overwrites metadata [#179](https://github.com/nodejs/build/issues/179)
-
-## Minutes
-
-
-### Present
-
-* Rod Vagg (TSC)
-* Brian White (TSC)
-* Steven R Loomis (TSC) 
-* Fedor Indutny (TSC)
-* Bert Belder (TSC)
-* Colin Ihrig (TSC)
-* Trevor Norris (TSC)
-* James M Snell (TSC)
-* Chris Dickinson (TSC)
-* Jeremiah Senkpiel (TSC)
-
-### Standup
-
-* Rod Vagg (TSC): node v4 prep, new website
-* Brian White (TSC): issue/PR reviewing, working on JS DNS implementation some more
-* Steven R Loomis (TSC): syncing with james, creating text for renaming of language groups (#2525), intl triaging, commenting on joyent/node issues
-* Bert Belder (TSC): indisposed until end of october
-* Colin Ihrig (TSC): reviewing issues/prs
-* Trevor Norris (TSC): prs/issues, finagling the new build pr landing tool
-* James M Snell (TSC): old prs in joyent/node cleaned up (64 remaining, wow), citgm tool updates, child process arguments pr, nodeconf.eu 
-* Michael Dawson (TSC): AIX support PR, some triage with Devin, preparing for NodeConfEU
-* Chris Dickinson (TSC): Static analysis work (ongoing), docs (slowly), npm
-* Jeremiah Senkpiel (TSC): v4 release prep
-* Fedor Indutny (TSC): v8 arraybuffer perf, patch landed on v8; reviewing PRs
-
-
-### Jenkins merge jobs always overwrites PR-URL and Reviewed-By [#179](https://github.com/nodejs/build/issues/179)
-
-Trevor: currently if you submit a job to land a pr, it will always remove all existing metadata and re-apply it based on the info passed to the jenkins build. from convo, good fix is to let old metadata persist & only append new metadata if it’s entered, if no metadata entered, nothing appended
-Issue with current state: current system does not work for cherry-picks onto release branch — will wipe metadata and replace it 
-Goal: solidify with TSC that this is a good path forward
-
-James: absolutely, +1
-
-Jeremiah: clarification on which branches this applies to
-
-Rod: cherry-picks are becoming increasingly difficult on iojs anyway, so the pr landing job may be master-specific
-
-James: no mixing of “with pr tool” and “manually”, things go bad quickly that way
-
-Trevor: cherry-pick PRs are accumulating too many cherry-picks; runnin it through the system manually doesn’t add useful info
-
-Domenic: description of chromium
- - tests are run after landing
- - no one is allowed to land commits if the build is broken on a branch
- - sheriff of the day is responsible for fixing the issue
- - in practice it’s painful, but it’s important for keeping things sane
-
-Trevor: this would make us better about flaky tests, also, admiration for how sporadically our flaky tests break
-
-Jeremiah: trying to do this now before v4 seems like a bad idea
-
-Rod: we’re smoothing out a little bit; circle back to original topic, we’re kind of talking about the larger issue, let the trial of the tool continue and come back to the discussion later. specifically: ask that metadata not be overridden in a github issue
-
-Domenic: addressing jeremiah’s concern: should we not run the trial while releasing v4?
-
-Trevor: agreement — have felt pain from this as we march to v4
-
-Jeremiah: stuff that gets released to people is in the release branches, if we’re not using the pr tool on that branch, what is the point of using this tool?
-
-Rod: this will become more of a problem as we have more extended and LTS
-
-Domenic: clarification: intent of ci is to make sure tests pass everywhere
-
-Trevor: this tool only runs a subset
-
-Rod: since we branched 3.x there’s 4 commits in the tree that have faulty/missing metadata — like that the pr tool is enforcing this metadata, maybe move to using github status api for telling us whether the metadata is OK
-
-Trevor: clarify: contributors have landed commits that lack metadata?
-
-Rod: yep
-
-Trevor: argh
-
-Jeremiah: github suggested we use the status api
-
-Trevor: status api autoruns?
-
-Rod: you hook it up to webhooks, has in-progress and pass/fail
-
-Trevor: TJ can verify that devs destroy jenkins (multiple force pushes explode the jenkins box with so many jobs)
-
-Rod: we can cancel on force push (or add a “trevor is pushing, wait half an hour to run the tests” exception, har har)
-
-Jeremiah: you can tell if it’s been run on the last commits
-
-Rod: multiple statuses — up to 100? — “this pr is passing on these platforms! this pr has the right metadata. this pr lints well.”
-
-Rod: let’s move on!
-
-James: what’s the action item?
-
-Rod: don’t feel that we should cancel the trial
-
-Trevor: two prs that prevent segfaults because of other flaky tests that have to be reapplied
-
-James: in the 4.x branch do we need to use test-pr job to land commits?
-
-Rod: nope, cherry-pick onto those branches, only use the tool on master
-
-Jeremiah: it’s weird to use it on the unstable branch. I guess we could make it better for release branches in the meantime
-* ci-run middle of hte night us time this has a
-
-Rod: vote for who whether we’d like to put this on hold
-
-Jeremiah: +0 put on hold
-
-Rod: who would like to continue it?
-
-...crickets...
-
-Trevor: give me another day
-
-James: one PR took 8 hours to land last friday
-
-Jeremiah: they take about an hour to land right now
-
-Rod: they are getting quicker, adding raspberrypis to the cluster. good incentive to make node startup time quicker! arm startup times have gone down over the last month or so
-
-Rod: let’s move on
-
-### doc: update COLLABORATOR_GUIDE [#2638](https://github.com/nodejs/node/pull/2638)
-
-Jeremiah: Alexis wanted to put the pr tool into the collaborator guide should punt on this right now notifying collaborators on issues is more effective messaging than the docs
-
-Rod: let’s hold off
-
-### deps: update v8 to 4.5.103.30 [#2632](https://github.com/nodejs/node/pull/2632)
-
-Rod: looking at the possibility of jumping to 4.5 for the v4 release it’s ready to merge. ofrobots has been doing the work, it’s good to go, there are pros and cons whether we stick with 4.4 or 4.5 for this release & associated LTS has anyone done any work on testing NAN?
-
-Bert: what breaks? what are the cons?
-
-Domenic: looking at v8 by code inspection, there are no breakages, just new deprecations — should *in theory* work — I don’t think anyone’s been testing it though
-
-Bert: can this v8 release be supported for LTS? we don’t know if this is better or worse than 4.4? maybe ask goog eng
-
-Trevor: they will say “Stay current”
-
-Bert: I think I agree with them — with no other info, picking the latest version seems best
-
-Michael: Z targets 4.4 — just recently got it fully clean — a move to 4.5 would cause a delay on getting release to community
-
-James: that’s just Z, not PPC, yes?
-
-Rod: how much work?
-
-Michael: going 4.3->4.4 took about a month
-
-Jeremiah: 4.3->4.4 breakage delta was much bigger
-
-Rod: that’s the external API though
-
-Michael: 7-8 patches/week? if we have to upgrade it will be extra work + delay for us
-
-James: if we’re sitll looking at LTS in early-mid oct, it’s going to give us a month to prove out v8 4.5
-
-Domenic: we’ve been proving out 4.5 for 12 weeks
-
-Rod: we’re talking node here, though we’d have google support for an extra month. my concern is: we need v4 out now, latest by monday, this is a quick change and there’s potential for breakage
-
-James: we decided before that we weren’t going to make such a big change so quickly before a release. i agree with rod, but such a big change makes me nervous — making sure that nan et al works with 4.5 is a concern
-
-Jeremiah: we’re not going to be the ones to find the flaws in 4.5; want clarification on nan major/minor/patch?
-
-Rod: minor
-
-Domenic: should require no changes
-
-Rod: benjamin (kkoopa) is on the positive side of this, he wants to see us move to 4.5, and is willing to put in the work to do this
-
-Trevor: not that it matters much, but node has taken a hit from v8 in terms of perf recently, 4.5 has some improvements, fedor wrote an easily backportable patch as well, there are perf advantages
-
-James: it makes me nervous that we’ll have enough time to test things on the node side before LTS — if we’re comfortable saying we have a plan that we think exercises this before going LTS, I’m more ok
-
-Jeremiah: technically we have over a month
-
-Rod: vote
-
-who is leaning sticking to 4.4 
-
-James + michael + steven
-
-4.5:
-
-fedor, colin, jeremiah, brian, chris
-
-Rod: clarifying concerns
-
-Michael: share concerns with james, but also Z
-
-Rod: longer we have to support our own V8, the harder it is, and another 6 weeks of support would be great great
-
-James: I’m -0
-
-Rod: spending some time today testing some existing addons taht have upgraded to nan@2. if there’s breakage, that tells me nan’s not ready, and that should be taken into account
-
-Domenic: if nan’s not ready, we don’t upgrade
-
-Rod: heading for 4.5, but with final go/no-go coming from nan testing; where are you at on this bert?
-
-Bert: I am happy to upgrade if you land it and nothing changes — which sounds like it might be the case (sans deprecation warnings)
-
-Rod: want ben’s opinion, but there may be no chance of that?
-
-Bert: it seems silly to go with a version that is almost already out of support, but OTOH, on the scale of LTS lifetime, 6 weeks is not really significant
-
-I wouldn’t worry too much about actual bugs in v8, about as likely in 4.5 as in 4.4; LTS is not about “no bugs”, it’s about “We support it”
-
-Rod: we want a **solid** release, though
-
-Bert: the LTS will also have a beta for a while, yes?
-
-Rod: the beta period for LTS is the stable line
-
-James: first LTS will have a beta of a little over a month, in the future 6 months
-
-Bert: realistically a month is a longer beta than we’ve ever had before
-
-Rod: 0.12 had a beta of 2 years
-
-{zing} :trollface:
-
-Bert: a beta with a lot of api changes, which is explicitly what we’re not going to do
-
-Bert: we need to move on
-
-Jeremiah: 4.5 brings arrow functions and that will make many people very happy
-
-Rod: it’s a good sales pitch!
-
-Rod: I’ll make the call.
-
-### Node.js v4 Release Timeline [#2522](https://github.com/nodejs/node/issues/2522)
-
-Rod: status update: v4 was to get out by Thurs, slipping on that, monday is the release date, cannot afford to slip any further
-
-Jeremiah: what’s actually slipping other than mdb?
-
-Rod: we’re not going to get mdb into v4, encourage before LTS, but that’s the best we can do, child process argument type checking where are we at on that?
-
-Trevor: it’s not ready
-
-James: working on that PR right now
-
-Rod: great, that feels like a fairly light one, process.send is the other one; ben’s on holiday, where are we at with that pr of his
-
-Jeremiah: multiple people have soft signed off on it
-
-Colin: weren’t there some strange ci failures with it?
-
-Rod: do not know, does someone want to put their hand up for that?
-
-Trevor: what’s the PR number?
-
-Jeremiah: #2620
-
-Jeremiah: Trevor +1’d it
-
-Jeremiah: OH! that’s the one with the weird test failures we could not reproduce the breakage
-
-Rod: this seems like it can be run again and it won’t show flaky tests: maybe we should just re-run it
-
-Trevor: that really sucks when you’re trying to land 3 tests
-
-Rod: test runner should auto-rerun to make sure
-
-Trevor: oh, gotcha
-
-Rod: that’d be really quick for flaky tests
-
-Trevor: I’ve already reviewed and LGTM’d it, I’ll look at running it through the land-ci job
-
-James: looked at it earlier today, nothing concerning stood out 
-
-Rod: no RC’s are out! that’s a problem! we’ve renamed the executable. I wanted to have a period of time where folks could download (with a working node-gyp) — we need this period of time. I’ve been working on that, some bits and pieces to get things to the right place on the server. first build had a broken OS X installer. there are a few yaks yet to shave, so that’s why we can’t get this out by thursday
-
-Rod: steven: could you confirm that 3.x has INTL enabled?
-
-Steven: will look into, take as action item (confirmed!)
-
-Rod: not going to tick that off till we confirm, but I _think_ that one’s done
-
-Rod: how’s everyone with the timeline? rcs ASAP + release on monday
-
-James: sounds reasonable, yes. will take as much time as possible on monday. several of us will be at nodeconf, so that complicates
-
-Rod: I’m using monday in airquotes, it’ll be tuesday for me. other thing: smoke testing, citgm, I’ve been using it, and there are a lot of weird failures, after v4 we’re going to have to switch modes to make the ecosystem happy with it
-
-Rod: let’s move ahead with that plan; nodeconf.eu is going to take up a lot of time for a lot of folk. congrats to everyone that contributed to new website, it seems really smooth
-
-### Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-Rod: opened by member of v8 team, extracting debugger code from blink and making it so all embedded v8 projects can use it
-
-Trevor: gist is: devtools team is considering pulling inspector out of blink into its own project so we could consume it; domenic can correct me wherever I’m wrong here,
-
-Domenic: “making node work the same as android” able to point chrome dev tools at node processes to debug ‘em
-
-???: only works with chrome
-
-Trevor: OTW API we consume have remained fairly stable, even if the API does change, chrome dev tools is capable of pulling in a previous version, making sure it’s possible to use with LTS releases
-
-OTW wire is generic, consumable by anyone, chrome dev tools is a key consumer, but anyone can consume (new consoles can compete!)
-
-cons:
-
-APIs going to need to be tightly integrated — needs to know about all async events
-  add conditionals to e.g. nextTick + timers
-
-Domenic: add something to MakeCallback?
-
-Trevor: we have to add it to that + on the way back in
-
-Domenic: this is for async stack traces
-
-Trevor: we don’t have to have it
-
-Bert: that’s awesome, because we have to grow a single entry point (opposite MakeCallback)
-
-Trevor: not going touch nextTick/timers, though — need to wrap each (because those APIs don’t roundtrip to C++ for each callback)
-
-Bert: we don’t have to do that immediately though, but eventually it’d be a good idea
-
-Domenic: could also move to microtask for nexttick — integrating with domains sounds hard, then we get those events for us
-
-Trevor: would you be able to do unhandledRejections?
-
-Domenic: we already have this for promises
-
-Rod: if we could use this as a good justification for removing domains, that’d be awesome
-
-Trevor: next point is pro and con: importantly, we’d have to support websockets natively in node
-
-Jeremiah: we could just keep ‘em private
-
-Trevor: that would just anger people
-
-Domenic: you could bundle them and hide them while you’re not clear on the api, iterate and expose later
-
-Rod: that’s a good point
-
-Trevor: the interesting flip to this: they need to be running off the main thread, in a debugger thread — it can all be written in C++
-
-mscdex: any way to avoid websockets?
-
-Trevor: no
-
-Bert: is the protocol really that complicated? I don’t think so — especially sans full HTTP and WSS — just websockets though is probably not difficult
-
-Trevor: necessary because it’s the protocol that chrome dev tools uses
-
-Rod: decision points: are we being asked to get on board?
-
-Trevor: them removing the inspector from blink depends on whether we’ll use it if they do it.
-
-Rod: debugging in node sucks, we are shipping with substandard debugging in v4, we don’t have the contributors + collaborators to make this better, so if we can lean on v8 to do this, I’m +1
-
-debugging is important enough to override “small core”
-
-Bert: we’re not adding the full inspector, _just_ the protocol
-
-Trevor: wasn’t completely clear on how much API we’d need to implement
-
-Domenic: we should get clarification on this
-
-Trevor: if we can implement this in segments — if we’re all +1 on this, we need to create a new isolate, but …
-
-Domenic: would the workers pr solve this?
-
-Trevor: probably overkill. I’m +1 on the debugger
-
-Bert: I propose we don’t vote
-
-{broad assent}
-
-Rod: trevor + domenic: you’ve got enough input
-
-Domenic: only worry is finding someone to devote some of their daytime hours to implement websockets
-
-Rod: nodesource could contribute, related to our interests
-
-Trevor: even if we don’t say yes today, taking inspector out of blink is a complicated process and will take time
-
-Rod: anything else?
-
-### Next Meeting
-
-September 9th
diff --git a/doc/tsc-meetings/2015-09-16.md b/doc/tsc-meetings/2015-09-16.md
deleted file mode 100644
index 2f3d6af395a331..00000000000000
--- a/doc/tsc-meetings/2015-09-16.md
+++ /dev/null
@@ -1,116 +0,0 @@
-# Node Foundation TSC Meeting 2015-09-16
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-09-16
-* **GitHub Issue**: https://github.com/nodejs/node/issues/2898
-* **Minutes Google Doc**: https://docs.google.com/document/d/1RCR2pGOc2d80NNusaX5DZaktWvHEsDUqfEZP-tvexBk
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1rXBdtsD9PJTExNXgzNZ9bez9oOjW45kLPjun4zdt0dY>_
-
-## Present
-
-* Rod Vagg (TSC)
-* Brian White (TSC)
-* Steven R Loomis
-* Fedor Indutny (TSC)
-* Bert Belder (TSC)
-* Colin Ihrig (TSC)
-* Trevor Norris (TSC)
-* Shigeki Ohtsu (TSC)
-* Chris Dickinson (TSC)
-* Jeremiah Senkpiel (TSC)
-* Ben Noordhuis (TSC)
-* Alexis Campailla (TSC)
-* Domenic Denicola
-* Michael Dawson
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node-v0.x-archive
-
-* Deprecate Array#values() in 0.12.x [#25877](https://github.com/nodejs/node-v0.x-archive/issues/25877)
-* Deprecate smalloc in v0.12 [#25784](https://github.com/nodejs/node-v0.x-archive/issues/25784)
-
-### nodejs/node
-
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-* util: Remove p, has been deprecated for years [#2529](https://github.com/nodejs/node/pull/2529)
-
-## Minutes
-
-Due to IBM’s acquisition of StrongLoop, IBM is over the TSC 25% company limit rule. Michael Dawson and Steven Loomis have stepped down from TSC, but they are here as observers.
-
-### Standup
-
-* Rod Vagg: Released 4.0.0, also 3.3.1 maintenance release. Getting the build system ready for building/publishing 0.10 and 0.12 binaries.
-* Brian White: not much, triaging issues and PRs, some work on dns parser
-* Steven R Loomis: tsc resignation for IBM/SL merge, some issue triage, working on a more robust download for ICU (ICU server was overloaded, fixed to ICU again redirects to sourceforge, discussed longer term discussions) 
-* Fedor Indutny: v8’s ArrayBuffer fixes, reviewing PRs, fixing issues
-* Bert Belder: very few reviews/issue comments. Some libuv work on rwlocks.
-* Colin Ihrig: not much, some issue tracker work
-* Trevor Norris: Trying to make things (including Buffers) faster, some issue/PR review
-* Shigeki Ohtsu: Just a few reviews of issues.
-* Chris Dickinson: Working on shoving static npm analysis data into a database, slowly    
-* Jeremiah Senkpiel: NodeConf.eu, issues and PRs, 4.1.0 release
-* Ben Noordhuis: only PR review and responding to bug reports, a patch or two upstreamed to v8
-* Alexis Campailla: ARM cross-compile for CI. Misc fixes for VS 2015 / Win10
-* Domenic Denicola: some issue and PR review, talking with v8 team
-* Michael Dawson: landed the build updated for AIX, also updating the tests for AIX where necessary. Looking into PPC failures. Working on getting us hooked into v8 security notifications.
-
-### Previous meeting’s agenda
-
-* Jenkins merge jobs always overwrites PR-URL and Reviewed-By [#179](https://github.com/nodejs/build/issues/179)
-* doc: update COLLABORATOR_GUIDE [#2638](https://github.com/nodejs/node/pull/2638)
-* deps: update v8 to 4.5.103.30 [#2632](https://github.com/nodejs/node/pull/2632)
-* Node.js v4 Release Timeline [#2522](https://github.com/nodejs/node/issues/2522)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-### Deprecate Array#values() in 0.12.x [#25877](https://github.com/nodejs/node-v0.x-archive/issues/25877)
-
-### Deprecate smalloc in v0.12 [#25784](https://github.com/nodejs/node-v0.x-archive/issues/25784)
-
-Jeremiah: Are these things that we think we can do? Should we go ahead with that? Is it a good idea to deprecate these things?
-
-Ben: How are we going to deprecate? Literal `util.deprecate`?
-
-Jeremiah: Probably?
-
-Trevor: They’re already floating a patch
-
-Rod: I’m fine with deprecating smalloc
-
-Trevor: Is there a deprecation cycle between LTS? I’m not sure how this would work? (i.e., if we deprecate now, LTS -> LTS upgraders will not see a deprecation warning.)
-
-Rod: Maybe punt to LTS WG? It could be quite a lot — it could be that we decide between stable versions to remove things (or we’re forced to), do we backport the deprecation to LTS?
-
-Jeremiah: I think it should be only for things we’re _forced_ to remove 
-
-Action: Punt to LTS WG
-
-### Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-Trevor: Have an 80% understanding of the work needed: WebSocket support in core (though not necessarily exposed publicly), API injection points. Are we ok with including web sockets support one way or another?
-
-Rod, Domenic, others: +1
-
-### util: Remove p, has been deprecated for years [#2529](https://github.com/nodejs/node/pull/2529)
-
-Discussion of Buffer “raw{s,}” encoding as well — undocumented, deprecated, inconsistently implemented in core.
-
-Action: Remove util.p (Jeremiah to respond.)
-
-Bert: Perhaps we should bulk remove?
-
-Rod: util.p is relatively trivial, has a deprecation warning, etc.
-
-Jeremiah: Brought this up because these things have been deprecated forever. util.exec has been deprecated for a while, as well.
-
-Trevor: raw/raws are deprecated in name only, no warnings, but C++ layer does not know about them (falls back to utf8) — maybe should be removed as a bugfix, because it does not work consistently.
-
-Action: Chris to list “least used stuff” (with apologies for how longs its taken!)
-
-### Next Meeting
-
-September 23
diff --git a/doc/tsc-meetings/2015-09-30.md b/doc/tsc-meetings/2015-09-30.md
deleted file mode 100644
index c10b9e75bc2ad9..00000000000000
--- a/doc/tsc-meetings/2015-09-30.md
+++ /dev/null
@@ -1,161 +0,0 @@
-# Node Foundation TSC Meeting 2015-09-30
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-09-30
-* **GitHub Issue**: https://github.com/nodejs/node/issues/3126
-* **Minutes Google Doc**: https://docs.google.com/document/d/1RkLAWTIrhD3BTB2rs9_FahWI0C7lt9F8xnQXaueJPIE
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1RCR2pGOc2d80NNusaX5DZaktWvHEsDUqfEZP-tvexBk>_
-
-## Present
-
-* Rod Vagg (TSC)
-* Brian White (TSC)
-* Chris Dickinson (TSC)
-* James Snell (TSC)
-* Michael Dawson
-* Ben Noordhuis (TSC)
-* Steven R Loomis
-* Bert Belder (TSC)
-* Alexis Campailla (TSC)
-* Domenic Denicola
-* Seth Thompson
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node
-
-* Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-### nodejs/TSC
-
-* Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-## Minutes
-
-### Standup
-
-* Rod Vagg (TSC) - Lots! Pass.
-* Brian White (TSC) - DNS PR (querying NSS modules like mDNS works now, continuing work on other getnameinfo/getaddrinfo compat issues)
-* Chris Dickinson (TSC) - Static Analysis
-* James Snell (TSC) - Review of the HTTP module, going in depth with spec compliance
-* Michael Dawson - AIX, contributing changes from IBM repos, node-gyp, all related to getting native modules working on AIX, submitted PR to core, benchmarking — bare metal machine for benchmarking group, backporting test fix to 0.12, FIPS-compat work on the test suite, getting hooked into v8 security reporting
-* Ben Noordhuis (TSC) - Review PRs, bug reports, fixed 1-2 bugs, sent a few patches upstream to V8 and gyp, fixed a few bugs in node-gyp.
-* Steven R Loomis - Review PRs, bug reports. Looking into alternatives to packaging full ICU data. Might be able to `npm install` ICU data.
-* Bert Belder (TSC) -
-* Alexis Campailla (TSC) - working on Node-serialport on Windows in Jenkins, looking into native module build service
-* Domenic Denicola - v8-extras are starting to appear in Chrome, maybe use them in Node for startup performance.
-
-### Review of previous meeting
-
-* Deprecate Array#values() in 0.12.x [#25877](https://github.com/nodejs/node-v0.x-archive/issues/25877)
-* Deprecate smalloc in v0.12 [#25784](https://github.com/nodejs/node-v0.x-archive/issues/25784)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-* util: Remove p, has been deprecated for years [#2529](https://github.com/nodejs/node/pull/2529)
-
-### Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-
-(Chris: apologies, I did a bad job here.)
-
-Ben: Plan is to ship the first LTS release with v8 4.5, not 4.6
-
-Rod: Yes.
-
-Ben: Is there a pressing reason to do so?
-
-Rod: LTS comes off the v4.x branch, we committed to not bump V8 in stable releases.
-
-Ben: It basically means that the first LTS release is going to ship with an outdated release.
-
-James: Yes, we knew this was a strong possibility.
-
-Michael: The model is that we give the community time to catch up. In the future that’s 6 months, so we’re never going to be on a supported version.
-
-Ben: V8 moves quickly. If we stick with 4.5, we’re going to have to manage a bigger delta between our copy and upstream.
-
-James: Yes, this was always going to be the case. We’re committed to supporting the V8 for 36 months.
-
-Ben: Yes, my point is that we could be starting with a smaller delta.
-
-Rod: One of the reasons we had this LTS delay on 4 is to shake out some of these concerns, like the buffer changes. Normally this shakeout will be 6 months, but this time it’s only been a month.
-
-Alexis: Is v5 going to be LTS also?
-
-Rod: We are having discussions about the overlap between v5 and v6, whether there’ll be a strict cutoff or some overlap. No decision yet. That’ll happen in April. It sounds like most folks are leaning towards
-making the two releases (v4 LTS + v5) independent — option 1 [here](https://github.com/nodejs/node/issues/3000#issuecomment-144026295).
-
-Ben: We still haven’t come up with a way to maintain V8 going forward.
-
-James: We do need a good process there, you are absolutely right about that.
-
-Rod: I vote for IBM to hire someone dedicated to this. (Laughter)
-
-Michael: I can’t promise that at this point.
-
-Rod: As the delta increases between versions this becomes more concerning.
-
-James: make sure this is on the LTS WG agenda for next week.
-
-Rod: We tried to tackle this once before, came up with job description but nothing concrete.
-
-Michael: We stopped short of telling the foundation that this is a position that we need to staff.
-
-James: I would agree. We’re at the point where bringing someone in at the foundation level is probably a good idea.
-
-Rod: Noted. OK. We’ve got resolution there.
-
-Michael: James: Make sure it’s on the LTS agenda for going back to the foundation for resources.
-
-Rod: LTS is meeting this Monday (issue 43 on the repo). There’s some discussion around codenames and how to expose LTS info. We’ve committed to first week of October for LTS releases, so timing is going to be a little awkward with 4.1.2 coming out monday. Version 5 will be shipping when we have a stable V8, presumably mid-to-late october (1-3 weeks with no stable release line.)
-
-Rod: We’ll be pulling in semver minor and patch changes, we’ll continue to have bugfix releases for version 4,
-
-### Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-Rod: Trevor is lead on this, but isn’t present. Does anyone else have any updates?
-
-Ben: Wasn’t the last contentious issue putting WS in core? I think we agreed that if it’s not exposed to user-land, it's fine.
-
-Alexis: (discussion of another WS issue)
-
-Bert: we decided on this
-
-Ben: We agreed that if it was internal, non-exposed to core,
-
-(Talk about native deps for WS, buffer-util can be )
-
-Ben: if this is a private dependency, we don’t need it to be fast, so we don’t necessarily need the native deps.
-
-Chris: (Hopped into discussion from minute-taking, hence the bad minutes)
-https://github.com/nodejs/node/pull/1202 - add mask/unmask
-https://github.com/nodejs/node/pull/1319 - add utf8 validator
-
-### Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-Ben: it’s basically a template for describing projects that are under the umbrella of the node foundation. It doesn’t look that controversial to me.
-
-Rod: it also doesn’t look that complete.
-
-Ben: Indeed. I suggest we discuss next week when mikeal is on the call. Seems like a rubber-stamp LGTM to me.
-
-Rod: We should think about what projects we want to introduce to the organization, including what happens to competition in the ecosystem when we pull in things (like build tools)
-Domenic: This is for things like libuv, yes?
-
-Rod: There are already npm projects knocking on the door. One such project is request. It has its own org right now, but could work under the auspices of the node foundation. However it exists in an ecosystem where there is competition — is it okay for us to bless one project over others? NAN is sort of in the same position, it _could_ have competition. Another example is the npm client possibly. If the foundation were in a position to take npm would we even want it?
-
-### renaming of “language groups” from iojs-\* to nodejs-\* [#2525](https://github.com/nodejs/node/issues/2525)
-
-Steven: Looking for buyoff on this.
-
-Ben: Seen the approach and it looks good.
-
-Rod: You should take this as “you have authority to move ahead”.
-
-Steven: Will do.
-
-### Next Meeting
-
-October 7th
diff --git a/doc/tsc-meetings/2015-10-07.md b/doc/tsc-meetings/2015-10-07.md
deleted file mode 100644
index 6cb8813a5cac02..00000000000000
--- a/doc/tsc-meetings/2015-10-07.md
+++ /dev/null
@@ -1,102 +0,0 @@
-# Node Foundation TSC Meeting 2015-10-07
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-10-07
-* **GitHub Issue**: https://github.com/nodejs/node/issues/3126
-* **Minutes Google Doc**: https://docs.google.com/document/d/1LIrTCdTUjKtb_GGecrJ3Es0rPOpVdpkV5kefJ_p5FGU
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1RkLAWTIrhD3BTB2rs9_FahWI0C7lt9F8xnQXaueJPIE>_
-
-## Present
-
-* Rod Vagg (TSC)
-* Brian White (TSC)
-* Steven Loomis (observer)
-* Trevor Norris (TSC)
-* Shigeki Ohtsu (TSC)
-* Ben Noordhuis (TSC)
-* Mikeal Rogers (observer)
-* Michael Dawson (observer)
-* Seth Thompson (observer)
-* Jeremiah Senkpiel (TSC)
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node
-
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-* lib,test: deprecate _linklist [#3078](https://github.com/nodejs/node/pull/3078)
-* Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-* Compiling node v4.0.0 with OpenSSL 1.0.1 fails [#2783](https://github.com/nodejs/node/issues/2783)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-### nodejs/TSC
-
-* Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-## Minutes
-
-### Standup
-
-* Rod Vagg: 4.1.2 release, security procedures surrounding that
-* Brian White: Working on javascript dns resolver, regular PR + Issue work.
-* Steven Loomis: Working on ICU 56 Release. TC 39 & emca spec work for Intl WG. Working on Intl build issues.
-* Trevor Norris: Focused on fixing async_wrap, writing tests and preparing for it to become more official
-* Shigeki Ohtsu: No works for node project, I spent all time to my internal works.
-* Ben Noordhuis: Nothing to report—the usual
-* Mikeal Rogers: Looking into stalled Wgs and seeing how to help out. Working on the umbrella program. Lots of conference things.
-* Michael Dawson: Added a benchmarking machine to the CI, working on some tests issues. Working on PPC for the CI.
-* Seth Thompson: Working on v8 4.7, scheduled soon
-* Jeremiah Senkpiel: vacation, some issue catch-up
-
-### Review of previous meeting
-
-* Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-* Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-* renaming of “language groups” from iojs-\* to nodejs-\* [#2525](https://github.com/nodejs/node/issues/2525)
-
-
-### WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-
-* Discussed the HTTP WG based on James’ comments @ https://github.com/nodejs/node/issues/3234#issuecomment-146293038
-* Generally positive, only concerns are regarding decision making power—TSC may not want to hand that off as this is not quite like Streams (in that few people grok the code!) and there are philosophical questions to be resolved about HTTP that the TSC should be involved in.
-
-### lib,test: deprecate _linklist [#3078](https://github.com/nodejs/node/pull/3078)
-
-* Userland modules exist that could be used instead
-* Ben suggested straight removal, Jeramiah raised the matter of process that we have committed to adding a warning before removal, so we could remove in v6 but probably shouldn’t in v5
-* No disagreement with moving forward for deprecation
-
-### Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-
-* Recap of the latest LTS meeting [LTS#43](https://github.com/nodejs/LTS/issues/43)
-* Aim to have LTS / v4.2.0 out tomorrow, backup date of Monday if we miss that. LTS starts then for v4.x, v5.x has to wait until V8 4.6 to be stable mid to late October.
-
-### Compiling node v4.0.0 with OpenSSL 1.0.1 fails [#2783](https://github.com/nodejs/node/issues/2783)
-
-* Shigeki, Ben: It would be quite hard to support 1.0.1 since we are using 1.0.2 APIs.
-
-* Discussion on the possible difficulty of using 1.0.2 on varied Linux distros
-
-* ubuntu wily (not released) seems to use 1.0.2 - work has been done to package.  1.0.2 is only in Wily - https://launchpad.net/ubuntu/+source/openssl/1.0.2d-0ubuntu1 - https://answers.launchpad.net/ubuntu/+source/openssl/+question/263725 - “My guess is that we will see openssl 1.0.2 from Ubuntu 15.10 onwards (or eventually only starting with 16.04)”
-
-* Concern that allowing 1.0.1 would result in a substandard (insecure?) & untested binary.
-
-* Some discussion about the fact that we don’t test building with shared / static dependencies
-
-* feedback to issue: No appetite to do the work from the TSC, maybe someone could do it but we wouldn’t support.
-
-### Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-
-_skipped discussion_
-
-### Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-_skipped discussion_
-
-## Next Meeting
-
-October 14th, 2015
diff --git a/doc/tsc-meetings/2015-10-14.md b/doc/tsc-meetings/2015-10-14.md
deleted file mode 100644
index 65a0f467cdffb3..00000000000000
--- a/doc/tsc-meetings/2015-10-14.md
+++ /dev/null
@@ -1,121 +0,0 @@
-# Node Foundation TSC Meeting 2015-10-14
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-10-14
-* **GitHub Issue**: https://github.com/nodejs/node/issues/3363
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1tVPxA4Y3n3dmICJFZN2vK93PXjCaUQ-eiN2mvt7zqbE>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1LIrTCdTUjKtb_GGecrJ3Es0rPOpVdpkV5kefJ_p5FGU>_
-
-## Present
-
-* Rod Vagg (TSC)
-* Domenic Denicola (observer)
-* Brian White (TSC)
-* Steven Loomis (observer)
-* James Snell (TSC)
-* Michael Dawson (observer)
-* Ben Noordhuis (TSC)
-* Jeremiah Senkpiel (TSC)
-* Trevor Norris (TSC)
-* Alexis Campailla (TSC)
-* Mikeal Rogers (observer)
-
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node
-
-* V8 security reporting [#3348](https://github.com/nodejs/node/issues/3348)
-* doc: add information about Assert behavior and maintenance [#3330](https://github.com/nodejs/node/pull/3330)
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-* Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-* Compiling node v4.0.0 with OpenSSL 1.0.1 fails [#2783](https://github.com/nodejs/node/issues/2783)
-
-### nodejs/TSC
-
-* Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-
-## Minutes
-
-### Standup
-
-* Rod Vagg: Not quite as involved, took a bit of time off. Getting back up to speed on build
-* Domenic: Nothing this week
-* Brian: PRs & Issues
-* Steven: Worked on getting ICU 56.1 out and into v4.2.0 LTS, working on making the ICU [install better](https://github.com/nodejs/node-v0.x-archive/issues/8996#issuecomment-89411193). Also shepherding iojs-* rename to nodejs-* [#2525](https://github.com/nodejs/node/issues/2525)
-* James: Worked on the 4.2.0 and 4.2.1 releases. Working on the cgitm smoke-testing tool and http WG.
-* Michael: Worked on adding pLinux to the CI. Looking into running the tests on fips-compliant mode. Investigated some AIX issues.
-* Ben: PRs & Issues, doing some work on the debugger and memory bugs in libuv
-* Jeremiah: PRs & Issues, working on resolving the timers in beforeExit bug: https://github.com/nodejs/node/pull/2795
-* Trevor: Helped Jeremiah with the beforeExit thing, worked on PRs and Issues. Looking into AsyncWrap improvements.
-* Alexis: Looking into a native module build service. Worked on the Ci a bit.
-* Mikeal: Worked on the Umbrella Program proposal. Helping set up the Node.js Interactive conference.
-
-
-### Review of previous meeting
-
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-* lib,test: deprecate _linklist [#3078](https://github.com/nodejs/node/pull/3078)
-* Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-* Compiling node v4.0.0 with OpenSSL 1.0.1 fails [#2783](https://github.com/nodejs/node/issues/2783)
-* Inspecting Node.js with Chrome DevTools [#2546](https://github.com/nodejs/node/issues/2546)
-* Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-
-### V8 security reporting [#3348](https://github.com/nodejs/node/issues/3348)
-
-Michael: Proposal is to add one or more TSC members to the V8 security list. Not all issues will actually be V8 issues, but there shouldn’t be too many.
-
-* Concerns about too many issues
-
-Michael: Let’s go back and ask if a handfull means only 4-5 a week.
-
-Mikeal: Part of the Umbrella Program is to make a top-level security group that all security issues are funneled through. This group may not need to be TSC members.
-
-Ben: How would this group know an issue is relevant to us?
-
-Rod: We are talking about a Chromium security list, so we would probably need someone with enough knowledge to filter out which issues affect us.
-
-Mikeal: They would only be an initial filter.
-
-Rod: Some chromium issues will not be recognizable as V8 issues without prior understanding.
-
-Rod & others: Suggest to add Ben and Fedor to add to the Chromium/V8 security list.
-
-Discussion about the current Security repo / group, and current mailing lists
-
-### doc: add information about Assert behavior and maintenance [#3330](https://github.com/nodejs/node/pull/3330)
-
-Discussion about what assert is intended to do, and how we want to deal with additions and breaking changes in the future.
-
-Discussion about the stability index in the docs.
-
-Resolution: Lock the assert module. Possibly re-evaluate in the future. Close existing open PRs/issues against it after landing doc change.
-
-
-### WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-
-James: having scheduling problems for an initial hangout but are getting a lot of interest from outside of core, including Doug Wilson and Eran Hammer.
-
-Discussion about the WG’s goals and how we should possibly think about handing over authority of the http module to this WG in the future. (At charter time or later on)
-
-### Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-
-James: recommended that we adopt a general rule that commits must go through at least one stable release before going into an LTS. Exceptions to this are security problems and changes that can’t go on to stable.
-
-### Compiling node v4.0.0 with OpenSSL 1.0.1 fails [#2783](https://github.com/nodejs/node/issues/2783)
-
-Conclusion was that this would be difficult and would result in a build that had some features disabled. The TSC is not going to undertake this work and would have reservations officially supporting a build that cripples some crypto features. However, pull requests for this work are welcome and would be considered.
-
-### Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-Mikeal sought a vote from the TSC to adopt the Project Lifecycle document and the Core TLP document.
-
-Resolution: there were no abstentions from voting and no disagreement amongst TSC members present, additional TSC members have registered their +1 on the PR so the motion is passed.
-
-## Next Meeting
-
-October 21st, 2015
diff --git a/doc/tsc-meetings/2015-10-21.md b/doc/tsc-meetings/2015-10-21.md
deleted file mode 100644
index 5aad511600bb88..00000000000000
--- a/doc/tsc-meetings/2015-10-21.md
+++ /dev/null
@@ -1,214 +0,0 @@
-# Node Foundation Core Technical Committee (CTC) Meeting 2015-10-21
-
-## Links
-
-* **Audio Recording**: https://soundcloud.com/node-foundation/tsc-meeting-2015-10-21
-* **GitHub Issue**: https://github.com/nodejs/node/issues/3464
-* **Minutes Google Doc**: <https://docs.google.com/document/d/1ad8Xlza_B-iWexdlAd1Z5muzBy_HH88t_iSD31OUepA>
-* _Previous Minutes Google Doc: <https://docs.google.com/document/d/1tVPxA4Y3n3dmICJFZN2vK93PXjCaUQ-eiN2mvt7zqbE>_
-
-## Present
-
-* Rod Vagg (CTC)
-* Brian White (CTC)
-* Steven R. Loomis (observer)
-* James Snell (CTC)
-* Michael Dawson (observer)
-* Chris Dickinson (CTC)
-* Ben Noordhuis (CTC)
-* Jeremiah Senkpiel (CTC)
-* Trevor Norris (CTC)
-* Alexis Campailla (CTC)
-* Mikeal Rogers (observer)
-* Shigeki Ohtsu (CTC)
-* Seth Thompson (observer)
-* Bert Belder (CTC)
-* Fedor Indutny (CTC)
-## Agenda
-
-Extracted from **tsc-agenda** labelled issues and pull requests in the nodejs org prior to meeting.
-
-### nodejs/node
-
-* governance: add new collaborators #VIII [#3472](https://github.com/nodejs/node/issues/3472)
-* detect "full-icu" module [#3460](https://github.com/nodejs/node/issues/3460)
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-* node: deprecate public access to `process.binding` [#2768](https://github.com/nodejs/node/pull/2768)
-
-## Minutes
-
-### Review of previous meeting
-
-* V8 security reporting [#3348](https://github.com/nodejs/node/issues/3348)
-* doc: add information about Assert behavior and maintenance [#3330](https://github.com/nodejs/node/pull/3330)
-* WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-* Discussion: LTS & v5 release planning [#3000](https://github.com/nodejs/node/issues/3000)
-* Compiling node v4.0.0 with OpenSSL 1.0.1 fails [#2783](https://github.com/nodejs/node/issues/2783)
-* Umbrella Program [#2](https://github.com/nodejs/TSC/pull/2)
-
-### Standup
-
-* Rod Vagg: index.tab and index.json updates (nodejs.org/dist/index.*) including an “lts” field, also made consistent directories for ancient Node tarballs with shasums files so nvm and other tools can simplify their access. v5 and other build yak shaving.
-* Brian White: usual triaging and PR and Issues commenting, not much else
-* Steven R. Loomis: Intl meeting, "full-icu" npm module [will be away until Nov 11 meeting, Unicode conf/Unicode-TC]
-* James Snell: Working on localization for the node runtime [#3413](https://github.com/nodejs/node/pull/3413)
-* Michael Dawson: Working through PPC and AIX PRs and issues, LTS WG discussions, Benchmarking WG, working with Stefan on agenda items for API WG meeting.
-* Chris Dickinson: was busy with vacation and conferences, but looking into the WhatWG Streams spec, next up is static analysis server
-* Ben Noordhuis: The usual. Looking into make the debugger better. The test suite is in bad shape
-* Jeremiah Senkpiel: issue and PR work — going back through the backlog now, helping with v5 release + npm@3
-* Trevor Norris: flurry of AsyncWrap PRs, trying to get it to a point where people could more reliably use it, it can’t be hidden forever.
-* Alexis Campailla: Sick, traveling; CI progress on flakiness, some progress on native module build service
-* Mikeal Rogers: Foundation resources for v5 release: PR folks wrote a blog post, expectation setting, make sure enterprises are still using LTS, if you’re a dev here’s what to be excited about, etc.
-* Shigeki Ohtsu: Worked semver-major fix to limit DH key size [#1831] (https://github.com/nodejs/node/pull/1831) and some works for root certs.
-* Seth Thompson: Security mailing list stuff went through this week, working on v8 side of things to create a new version of the octane benchmark, excited about the benchmarking WG
-* Bert Belder: nothing
-* Fedor Indutny: reviewing PRs, helped fix a beforeExit bug, fixing yet another V8’s ArrayBuffer issue
-  - Discussed the ArrayBuffer issue in detail
-
-* (Aside: Shigeki and Fedor were asked to look at [#3406](https://github.com/nodejs/node/issues/3406) - “p1/p2” issue )
-
-### governance: add new collaborators #VIII [#3472](https://github.com/nodejs/node/issues/3472)
-
-- Discussed onboarding.
-
-- Action: Jeremiah to schedule and run another onaboarding, Chris to tune in.
-
-### detect "full-icu" module [#3460](https://github.com/nodejs/node/issues/3460)
-
-Stems from conversation from the 0.X days about whether Node should ship other languages separately.
-
-This is a module published on npm as an alternative to shipping with Node proper.
-
-Whether node can detect a full-icu install in a special place (node_modules/full-icu, global/node_modules/full-icu)
-
-Nathan7 commented with a concern about coupling npm to node
-
-Currently have to start node with ICU_DATA_PATH=some/path/to/file
-
-Rod: Couple it to `execPath`
-
-James: globally installed could install into a well known global location
-
-Rod: Does this have to be done at startup?
-
-Stephen: Yes. V8 has to have the data available before starting.
-
-James: Happens right after parsing args
-
-Rod: Could use HOME?
-
-Stephen: Could use NODE_PATH?
-
-Rod: Trying to move away from NODE_PATH
-
-Ben: Might just bite the bullet and include ICU?
-
-Stephen: I would like that, but I am sympathetic to folks running on OpenWRT
-
-Ben: I can see that, but all this installing in special paths leaves a lot of margin for error.
-
-James: Full ICU will double the size of the Node binary. Hard pill to swallow.
-
-Rod: We could offer alternative downloads?
-
-Stephen: Two downloads would work as well. We could do this all from build infra.
-
-Bert: I would not be in favor of that. We end up with “oh my module doesn’t work” “oh you didn’t download the right flavor of Node”
-
-Jeremiah: It’s going to make it confusing no matter what
-
-... [I missed this]
-
-Chris: could we offer better error messages?
-
-Rod: it peeks through in a lot of places — the ICU object, strings, etc. Maybe best to leave to module authors? Include a process.versions.icu object?
-
-James: small-icu is the default build running locally — CI doesn’t run with ICU enabled?
-
-Trevor: even if small-icu is there, it means less data, but not less build time. I would like to see how that affects the raspberry pi’s build time.
-
-Ben: we could avoid rebuilding ICU on rasppis
-
-Stephen: or use a precompiled ICU
-
-Jeremiah: Assumes an internet connected machine
-
-Rod: If we go with small-icu we should make it available
-
-Ben: should we add it to the repo?
-
-Alexis: I think so, it’s causing problems
-
-[???]: It’s about 80mb
-
-Rod: How big is it?
-
-Stephen: The source size & binary size was comparable to Node.
-We could have a non-standard source checked in.
-
-Mikeal: we could use the large file storage stuff GH just added.
-Stephen: 25mb uncompressed, 130mb for source tree
-
-Mikeal: if we say “you need ICU to build”  we need to make it available
-
-Trevor: How’s this going to work with bouncing between branches?
-
-Alexis: What about keeping it as text?
-
-Ben:
-
-Steven: We have a 25mb compressed zip of source, that itself contains a 25mb compressed zip. We could strip that down — what would it take to delete the tests, etc — a subset
-
-Mikeal: so could we just install this 25mb file?
-
-Rod: This adds a dep on Git LFS
-
-Mikeal: Let’s try to solve one problem at a time — fix downloading, not making the default
-
-Rod: I’m happy with how the CI does it
-
-…
-
-Stephen: The first time you hit something ICU-based it loads it.
-
-Rod: I’m just wondering if this could be turned into a proper npm module.
-
-Stephen: I’m not sure — it looks pretty deeply enmeshed into V8
-
-Seth: I don’t have answers off the top of my head on that one, I responded on the thread; we don’t currently have a priority to mess
-around with localization. If there’s a design doc that proposes cleaning things up we’d be interested
-
-James: Resource bundle mechanism — [Note: didn’t get all of this] “using the same startup sequence as Intl.. so needs to be configured at start time” (https://github.com/nodejs/node/pull/3413 uses ICU’s resource bundle mechanism, which uses the same init path as the core data. ICU does not allow multiple initializations.
-
-Alexis: If the only reason we’re trying to package it is to use npm to install it, maybe we’re complicating this unnecessarily
-
-Rod: On the iojs side we decided not to go with ICU. It’s in core because it has to be initialized before v8 is started, my question is this something that could be changed upstream in v8? Ideally this should not be in core.
-
-Steven: It didn’t look like it could be split off easily.
-
-Chris: JS proxies
-
-Steven: Possible, but _very_ tricky
-
-[Moving conversation to GH]
-
-
-### WG: Considering a new HTTP WG [#3214](https://github.com/nodejs/node/issues/3214)
-
-HTTP WG first meeting is tomorrow at 1pm Pacific, nothing to discuss yet
-
-### node: deprecate public access to `process.binding` [#2768](https://github.com/nodejs/node/pull/2768)
-
-Lots of discussion, focused on `process.binding('natives')`. Summary: We should at least try to make it read-only first. Ben said he would follow up with a PR.
-
-### node: make listen address configurable [#3316](https://github.com/nodejs/node/pull/3316)
-
-Fedor: Ben suggested commandline argument to submit hostname and port. Fedor concerned about the amout of code required to parse and separate the two parts of the option. Would be better to have a separate argument for hostname.
-
-Discussion about usability vs simplicity of code.
-
-Quick vote on whether to move forward with the PR in its current form, no objections.
-
-## Next Meeting
-
-October 28th, 2015
diff --git a/doc/tsc-meetings/io.js/2014-10-09.md b/doc/tsc-meetings/io.js/2014-10-09.md
deleted file mode 100644
index 57c4e34c769eec..00000000000000
--- a/doc/tsc-meetings/io.js/2014-10-09.md
+++ /dev/null
@@ -1,61 +0,0 @@
-- Contribution Policy was merged last week.
-
-- Concerns about https://github.com/node-forward/node/issues/2 have been brought
-  up, it effects almost every line and will make merges with Joyent
-  unnecessarily painful in the short term. The consensus was to put it on the
-  back burner.
-
-- It's a little difficult to work in the fork at the moment:
-  - It's hard to contextualize what to fix without having a release in mind
-  - We'll start doing source-only releases ASAP so that we can create a work
-    scope.
-  - Someone will be in charge of keeping their head around and driving each
-    release. This should probably rotate, Bert will take on the first one with
-    the goal of releasing before the end of the month.
-  - For now tagging will create a GitHub "release." Eventually the build infra
-    can attach binary installers to that GitHub release.
-  - It's hard to keep a list of issues that are being tackled from the backlog
-    in joyent's repo
-  - Bert will maintain a list of TODO checkbox items in a GitHub Issue for a
-    release the references the PRs and Issues in Joyent's repo. We'll also be on
-    the lookout for other tools that might make this easier.
-
-- The build stuff is coming up a lot and the discussion about how releases work
-  should include someone from the build project.
-
-- Invite whoever is leading the build effort (current @rvagg) to the TC meeting
-  to participate (non-voting).
-
-- Eventually we'll need a better support structure where community members can
-  triage issues and respond to all the incoming requests.
-  - @mikeal created a "community" group and a repo for larger community issues.
-    Once there is some momentum there we can bring problems like this to the
-    community but the repo we currently control write access to doesn't have all
-    of the issues in it so this can wait.
-  - @indutny suggested a bot that auto-responds. @isaacs thought an
-    autoresponder was a little inhuman. It was agreed that the best thing to do
-    is have a bot that comments on the issue *once a tag is added* that is
-    specific to that tag and run in concert with humans tagging issues.
-  - @piscisaureus really wants to find a way for him to tell if someone already
-    looked at an issue so that him, trevor, ben, and fedor don't independently
-    look at every issue.
-
-- @indutny wants to get a newer v8 in. this work is slated to be finished for
-  the first release.
-  - @trevnorris mentioned that there are some new features in v8 that we may
-    want to use to replace certain parts of node down the road.
-
-- @trevnorris and @isaacs want a "commit script" that people can run which
-  automates a lot of the manual cleanliness we currently require for all commits.
-  v8 has as simliar one. this will be written in javascript by @isaacs and
-  @trevnorris .
-
-- When pulling in joyent/node commits we should use no-fast-forward commits.
-
-- If people want to talk to the TC in a more "chatty" way we should use the
-  `#node-forward` IRC channel on freenode. We need to add logging.
-
-- The video of TC meetings doesn't include the chat so we need to be aware of
-  that when using it during the calls.
-
-Video of the call is https://www.youtube.com/watch?v=fNW_tu2QnpA
diff --git a/doc/tsc-meetings/io.js/2014-10-15.md b/doc/tsc-meetings/io.js/2014-10-15.md
deleted file mode 100644
index 0499cddefb4f8a..00000000000000
--- a/doc/tsc-meetings/io.js/2014-10-15.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# node-forward TC Meeting 2014-10-15
-
-## Agenda
-
-* Openssl upgrade / openssl 1.0.1j, disabling SSL3 support
-* Status of the build system & release automation
-* https://github.com/node-forward/node/pull/14 - refine TC percentage rules - CONTRIBUTING.md
-* Items preventing node-forward from releasing v0.12.
-* Node Forward release cycle/schedule.
-* (Maybe discuss v8 3.29 in node-forward vs 3.28 in joyent/node, and merging them? ...just a suggestion) 
-* Performance situation
-* Node Forward website, non-core stuff, help repo.
-
-## Links
-
-* **Google Hangouts Video**: https://www.youtube.com/watch?v=aRBuu2m5xbI
-* **Original Minutes Google Doc**: https://docs.google.com/a/vagg.org/document/d/18l01PO2Rb3OZXWMcIkZ_sU4f1JKP2LKOwjuiENkg37M
-
-## Minutes
-
-### Present
-
-* Rod Vagg (facilitator, build representative)
-* Mikeal Rogers (facilitator)
-* Ben Noordhuis (TC)
-* Bert Belder (TC)
-* Fedor Indutny (TC)
-* Trevor Norris (TC)
-
-### Discussion
-
-* Fedor: **OpenSSL upgrade to 1.0.1j done in a branch**, build bots reporting OK, ready to merge. SSLv3 disabled completely in joyent/node 0.12 because the protocol is broken--attack comes from downgrade request from TLS to SSLv3. 0.10 has a runtime flag to enable it via process arguments (`--enable-ssl3`).
-* Rod (representing the build group): tried Jenkins and BuildBot. Neither are great, but right now they’re working on getting something to work now, although eventually they’d like a great build system. There are build bots running for most platforms right now, except OS X (but there’s commitment from voxer to sponsor machines). Building branches works, but PRs doesn’t. This week some basic useful stuff should be available.
-  - https://github.com/graydon/bors - rust
-  - Benchmarks? Make a CI target just for benchmarks so we can track it over time. Not run on every PR, perhaps manually triggered, perhaps time triggered. http-simple? Fedor: large nightly benchmarks would be nice. Start with Linux, a single consistent box running the suite (doing a release too).
-* **Refine TC percentage**: pull node-forward/node#14. TC is short two people without Joyent & is small. 2 of 6 people are from Strongloop. #14 allows changing to 33% to allow the current TC to not be in violation for the time being and then change it back to 20% when we can. Consensus has been relatively easy, no votes have been needed thus far so there isn’t much concern.
-* **Release cycle**: time based releases? node-forward discussion have strong consensus for a desire to move to semver and also a quicker release cycle.
- - **General agreement on semver**, minor releases backward-compatible, major releases can break.
-  - Discussion on **native API compatibility**, NAN or NAN-like or something more brave like having ABI compatibility. Ben: “You can’t forecast the future, the abstraction will break”.
-  - **Supporting old versions**: deal with it when the project has “prior releases”. Defer discussion on exactly the model until the project is ready to make proper releases. Move discussion to GitHub.
-* **V8 3.29**, Fedor: joyent/node has 3.28, node-forward/node has 3.29. Trevor & Fedor agreed to put 3.29 in joyent/node pending agreement with TJ.
-* **node-forward website**, Mikeal: there is a website, http://nodeforward.org/ 
-  - Forrest suggests a help repo to replace what the mailing list works, he has offered to help support that.
-
diff --git a/doc/tsc-meetings/io.js/2014-10-29.md b/doc/tsc-meetings/io.js/2014-10-29.md
deleted file mode 100644
index ce64c62ddb0586..00000000000000
--- a/doc/tsc-meetings/io.js/2014-10-29.md
+++ /dev/null
@@ -1,33 +0,0 @@
-* Update on Build
- * @rvagg is working on getting the builds consistently green
-   before moving on to more complicated things.
-* @issacs brought up the Joyent Advisory board
- * Some confusion out there about Node Forward vs. Advisory Board
- * @mikeal updated the messaging on the website to be clearer
- * The website has clearer calls to action for the community
-* Libuv move
- * The libuv contributors want to move to the libuv org.
- * @mikeal will email @indutny and other libuv contributors to ask them
-   to log an issue about this on their repo for transparency and so that
-   this is not a surprise to Joyent
-* Update on "release buckets"
- * doesn't make sense while we're private, we'll wait until it is public again
-* `node-forward/node` going public
- * when we made the repo private it was messaged as only being for "four weeks"
- * "four weeks" is up on November 8th
- * someone on the Advisory Board needs to remind Joyent of this in the
-   next advisory board meeting so they aren't suprised by it even though
-   it was communicated to them when it was first made public.
- * @mikeal will work on the messaging in the README to make it clear this is
-   a "soft" fork and not a "hard" fork.
- * ramifications of going public will be discussed in next week's TC meeting as
-   well
-* @mikeal proposed a change in TC meeting process
- * it's impossible to schedule all the timezones involved in every meeting
- * every Monday create a "Weekly TC Agenda" Issue people can contribute to
- * the TC members who care about that Agenda will state they want to be in the
-   meeting
- * @mikeal will work to schedule the TC members who care for a hangout
-* people are using and liking gitter
- * we'll consider moving from IRC to gitter once the repo is public again
- * yes, gitter has IRC integration (you can login to gitter from an IRC client)
diff --git a/doc/tsc-meetings/io.js/2014-12-10.md b/doc/tsc-meetings/io.js/2014-12-10.md
deleted file mode 100644
index 8bbfdfed10df78..00000000000000
--- a/doc/tsc-meetings/io.js/2014-12-10.md
+++ /dev/null
@@ -1,139 +0,0 @@
-# io.js TC Meeting 2014-12-10
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* @chrisdickinson nomination to TC https://github.com/nodejs/io.js/issues/51
-* Move readable-stream to iojs org and make authoritative source for io.js to pull _from_ https://github.com/nodejs/io.js/issues/55
-* Deprecate domains https://github.com/nodejs/io.js/issues/66
-* Decide how to go forward with caine https://github.com/nodejs/io.js/issues/117
-*  Is it io.js, IO.js, or something else? https://github.com/nodejs/io.js/issues/118
-* Build automation update
-* extending options from a prototype
-https://github.com/nodejs/io.js/issues/62
-* Separate I/O tests from simple, so simple tests can be run in parallel
-* Statement / stance from TC on exposing a Promises API https://github.com/nodejs/io.js/issues/11
-
-## Links
-
-* **Google Hangouts Video**: https://www.youtube.com/watch?v=otE4IRMVUMo
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/112
-* **Original Minutes Google Doc**: https://www.youtube.com/watch?v=otE4IRMVUMo
-
-## Minutes
-
-### Present
-
-* Rod Vagg (facilitator, build representative)
-* Ben Noordhuis (TC)
-* Bert Belder (TC)
-* Chris Dickinson (nominee to TC)
-* Fedor Indutny (TC)
-* Trevor Norris (TC)
-
-
-### @chrisdickinson nomination to TC
-
-https://github.com/nodejs/io.js/issues/51 
-
-**Unanimous decision to add Chris to TC**
-
-### Move readable-stream to iojs org and make authoritative source for io.js to pull _from_
-
-https://github.com/nodejs/io.js/issues/55 
-
-* Chris expressed concerns on doing this, but a -0 for now, give it a go and see how it works
-* Discussed the potential difference with joyent/node
-* Trevor discussed concerns about the tight coupling of streams to core
-* Rod talked about organisational and community concerns
-* No -1’s on moving the source of authoritative code and moving readable-stream into iojs
-* Need to experiment with the flow: code, issues, docs, etc.
-* **Consensus reached on moving readable-stream to iojs and flipping the authoritative code and doc flow**
-* Chris and Rod to work on the process in GitHub
-
-### Deprecate domains
-
-https://github.com/nodejs/io.js/issues/66 
-
-* Trevor: domains are horrible but we don’t have a good alternative yet
-* Ben: +1 on removal but don’t have a good story on what to tell people to use
-* Bert: -1, would rather clean up docs to be honest about how it doesn’t do what it was hoped to
-* Trevor: domains inhibit progress because of their invasiveness
-* Discussed how to document concerns etc.
-* Discussed https://github.com/nodejs/io.js/pull/15 which adjusts the domain.run() API
-* Agreed:
-  - Accept PR #15
-  - **Document that domains are on the way out: soft deprecation** (no util.deprecate())
-
-### Decide how to go forward with Caine (bot)
-
-https://github.com/nodejs/io.js/issues/117 
-
-* Fedor talked about _what_ caine is and _why_ it exists: too many emails from the repo, want to set up a system where relevant people are pulled into particular issues rather than having to subscribe to the repo for all notifications
-* Chris: primary concern with having an automated bot is the incoming experience for users (like having a join bot on IRC)
-* Discussed notifications / labels / etc.
-* Bert discussed using a “new” label for triage--automatically add to incoming issues and remove when the issues have been looked at / dealt with by a contributor.
-* Trevor voted to **move the discussion to GitHub**
-
-
-### Is it io.js, IO.js, or something else?
-
-https://github.com/nodejs/io.js/issues/118 
-
-* Ben: lowercase is “objectively superior” (j/k)
-* No disagreements, the name is “io.js”
-* Ben: binary name suggestion “iojs” with symlink to “node”, lots of discussion in https://github.com/nodejs/io.js/issues/43
-* **No disagreements, binary name will be “iojs”**
-* Ben: how do we handle it on Windows? .bat file (problems with arg forwarding), small .exe
-* Agreed to open a new issue to discuss Windows compat (Ben)
-
-### Build automation update
-
-Rod gave a summary of build project status:
- - Containerized build system is being improved by an active team in the https://github.com/nodejs/build-containers repo, on target to enable automatic PR tests and status reports back to GitHub (will likely just be Linux distros for the forseeable future)
- - Next step is to enable committers to be able to trigger full builds across the build cluster
- - Aiming for more automation for a mid-January release, have concerns about Windows and OSX signing and the need for signing keys and how complex they are.
- - Chris Lea is working towards nightly builds for .deb-based systems (RHEL / Fedora based systems could come later but the assumption is that people running those systems are _less_ likely to want nightlies)
- - https://github.com/nodejs/io.js/issues/13 is an ARM build failure that still needs attention to have ARM part of the build mix and not constantly fail (see https://jenkins-node-forward.nodesource.com for some ARM failures)
-
-
-### Extending options from a prototype
-
-https://github.com/nodejs/io.js/issues/62 
-
-* Chris is asking for input
-* Ben: we’re currently only looking at the object’s own properties, and ignoring properties on the prototype.
-* Fedor: in general there’s no reason to explicitly check whether properties are on the object or on the prototype chain.
-* Ben: **continue in the issue tracker**
-* Bert: be consistent. Slightly agree with fedor.
-
-### Separate I/O tests from simple, so simple tests can be run in parallel
-
-* Fedor: discussed the possibility of moving out net and possibly fs tests so the rest can be parallelized. There may be problems with many of the fs tests because they use fixtures.
-* Fedor: **agreed to try it out**
-* Bert: preference for the “tests” target to run the current test target
-
-### Statement / stance from TC on exposing a Promises API
-
-https://github.com/nodejs/io.js/issues/11 
-
-* Rod: can we come up with some kind of statement from the TC regarding the possibility of adding a Promises API to core, even if it’s vague
-* Bert: there’s a convergence of functionality around Promises that are making them more useful in conjunction with other ES6/ES7 features, TC should be _open_ to adding a Promises API in the future
-* Trevor: would like to simplify the current API so that it’s easier to extend and add abstractions on the top
-* Ben: when simplifying, it would be good to have a target for how the simplification can be used, Promises could be one of those
-* Bert: It would be weird for Node to go its own path if the rest of the JS ecosystem were to go that way
-* Rod & Bert: suggested a statement along the lines of: **Promises doesn’t make sense right now, so it’s not going to happen in the short-term, but the TC is open to change as things evolve in ES6 and ES7 and practical issues are worked out, TC is open to  experimentation, a _callback API is unlikely to ever go away_**
-* Ben: a +0
-* Trevor: pending practical concerns
-* Fedor: a -0
-* Chris: +0
-
-
-###  Working with nvm, nvmw and similar installation managers
-
-https://github.com/nodejs/io.js/issues/40 
-
-* Ben: suggested a dist.iojs.org for hosting binaries
-* Ben: suggested a release.txt
-* Rod: **leave it up to the build team to work out the mechanics of releases and release.txt and/or release.json and come back to TC for approval or adjustments prior to formal release** (i.e. no need to bikeshed on this here right now)
diff --git a/doc/tsc-meetings/io.js/2014-12-17.md b/doc/tsc-meetings/io.js/2014-12-17.md
deleted file mode 100644
index 6d302ab88fcad8..00000000000000
--- a/doc/tsc-meetings/io.js/2014-12-17.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# io.js TC Meeting 2014-12-17
-
-## Links
-
-* **Google Hangouts Video**: https://www.youtube.com/watch?v=7s-VJLQEWXg
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/163
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1PoqGfxpfTFKv5GcKmhMM2siZpPjT9Ba-ooBi-ZbYNi0
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* Bundle tick processor with iojs #158 https://github.com/nodejs/io.js/issues/158
-* Release Cycle Proposal #168 https://github.com/nodejs/io.js/issues/168
-* Module search security #176 https://github.com/nodejs/io.js/pull/176 
-* Dealing with feature requests 
-
-## Review of last meeting
-
-* Move readable-stream to io.js and flip authoritative flow of code, docs and issues
-* Soft deprecation of domains, accept PR #15 as last feature addition
-* Caine, discussion continued on GitHub
-* Project name is “io.js”, binary name is “iojs”
-* Extending options from prototype, discussion continued on GitHub
-* Promises statement for issue #11
-* Working with nvm, etc.
-
-## Minutes
-
-### Present
-
-* Bert (TC)
-* Chris (TC)
-* Trevor (TC)
-* Isaac (TC)
-* Rod (build, facilitator)
-
-### Bundle tick processor with iojs #158 
-
-https://github.com/nodejs/io.js/issues/158
-
-* Bert: important because it’s tied to the version of V8, not practical to put it in npm because one is needed for each version
-* Isaac: this is minimal and shouldn’t set a standard for just adding more stuff to core (i.e. keep core minimal), so +1
-
-+1 from Isaac, +1 from Bert, **no disagreement amongst group, consensus has been reached on bundling a tick processor with releases.**
-
-### Release Cycle Proposal #168 
-
-https://github.com/nodejs/io.js/issues/168
-
-* Bert & Isaac discussed how this feeds into the ability to have frequent releases. Discussed semver plays into this.
-* Rod: consensus seems to be around having stability, predictability, lead-time but more frequent releases.
-* **Bert: Move discussion to #168. Still premature to discuss here.**
-
-### Module search security #176
-
-https://github.com/nodejs/io.js/pull/176 
-
-* Limiting node_modules search path to $HOME as a top-level
-* Isaac ~ -1 on this because EACCES already happens when you don’t have permission
-* Isaac and Bert bikeshedded Windows C:\ writability and security on Windows. i.e. if someone can install code on a shared system above where a node application is running (e.g. C:\) then you could have untrusted code run by your application.
-* Isaac: this PR is only addressing projects running in the home directory.
-* Rod: module system is locked-down, TC needs to come to consensus that this is a _security_ issue and therefore warrants breaking it.
-* Chris: `useradd node_modules` is a situation this could be a problem
-* Isaac: not convinced this is a security problem, even the `useradd` situation requires root access on a system.
-* Bert: this is an academic issue, it may _feel_ wrong but that doesn’t mean it’s strictly a security issue.
-* Isaac: proposed the issue be closed as not a security issue.
-* **No consensus that this is a security issue. Move discussion back to GitHub, potentially close issue, potentially bringing discussion back here. Encourage users to bring examples of real problems.**
-
-
-### Dealing with feature requests
-
-* Bert: asking for discussion about what to do with feature requests that come up but aren’t clearly something that are wanted.
-* Bert: should we put a time limit on feature requests? Would like some guidelines for how to deal with these.
-* Chris: have already been putting a 4-6 day window before closing them. If there is no code then it’s easier to close. If there is code then there could be more discussion.
-* Isaac: this is a broader problem about the roadmap-setting process.
-* Rod & Isaac: It’s up to someone on TC (or elsewhere) to start coming up with a roadmap, or at least start the discussion.
-* **Agreed to start a GitHub discussion on roadmap and soliciting feedback from the community.**
-* Rod: in an open model, it’s up to TC and those with commit access to take the initiative to just close things, given enough warning and chance for discussion and better arguments.
-* Isaac: builtins (like Blog of FileReader) are TC39 / WhatWG groups out there that are doing this at the language & V8 level and we pull from there. It should be straightforward to close those issues.
-* Bert: the roadmap shouldn’t be about locking down the dev process and tightly limiting scope of what’s added.
-* **Agreed that feedback to all contributors (including TC), regarding closing issues: close issues that are instinctively bad and worth closing (close can be undone), anything potentially controversial can be flagged with a “will close” but give ~ 1 week for discussion, disagreement, lobbying etc.**
-
-
-### Logos
-
-* **Agreed that the release is the only _technical_ blocker from the TC’s perspective to a logo, so deferring discussion till then. Encourage interested parties from discussing this further on GitHub issue #37.**
-
-### Next meeting
-
-* Bert proposed 2014-12-30 as next meeting time
diff --git a/doc/tsc-meetings/io.js/2014-12-30.md b/doc/tsc-meetings/io.js/2014-12-30.md
deleted file mode 100644
index 5956e3a6f316ae..00000000000000
--- a/doc/tsc-meetings/io.js/2014-12-30.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# io.js TC Meeting 2014-12-30
-
-## Links
-
-* **Google Hangouts Video**: http://www.youtube.com/watch?v=O60sOsesjOo
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/211
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1KLfX2MZQbVSIaD2lBVqOFK0Kap4uFz9cTGihnpTuvPE
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* sys: Remove after 3 years of deprecation #182 https://github.com/nodejs/io.js/pull/182
-* module: force require('process') to return a reference to process #206 https://github.com/nodejs/io.js/pull/206
-* File copyright policy #216 https://github.com/nodejs/io.js/pull/216
-* Rename v0.12 to v1.0.0 https://github.com/nodejs/io.js/issues/218
-* Merge strategy (v0.10 and joyent/node)
-
-## Minutes
-
-### Present
-
-* Rod (build, facilitator)
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Fedor (TC)
-* Trevor (TC)
-
-### sys: Remove after 3 years of deprecation #182 
-
-https://github.com/nodejs/io.js/pull/182
-
-* Ben: what sort of strategy to take? Deprecated only in the docs but no warning. Looking for an official deprecation policy.
-* Bert: suggest we could properly deprecate but not a good case for removing it completely, Chris agreed
-* Fedor: suggested a policy that removal of deprecated features should be done where there is a maintenance overhead, but otherwise if there is little/no cost then "who cares"
-* Discussed a deprecation message on `require(‘sys’)`
-  * Ben: -0
-  * Fedor: +1
-  * Chris: +1
-  * Trevor: -0
-  * Bert: +1
-* No disagreement to adding a deprecation message, **ask initial PR submitter to change to just adding a message**
-
-### module: force require('process') to return a reference to process #206
-
-https://github.com/nodejs/io.js/pull/206
-
-* #157 has a long discussion on this: https://github.com/nodejs/io.js/issues/157
-* Chris: +1 on a PR adding this
-* Trevor: it just returns a global, no point
-* Bert: not the way that JS adds new features; discussed the new Intl addition to joyent/node, in favor of making more things requirable rather than adding new globals all the time
-* Tangential discussion on the Intl object being added in joyent/node
-* Collected votes:
-  * Bert: +0
-  * Ben: +0.5
-  * Trevor: -0
-  * Fedor: +1
-  * Chris: +1
-* **Ben to handle the merge / resolution**
-
-
-### File copyright policy #216
-
-https://github.com/nodejs/io.js/pull/216
-
-* Rod asked if there are any strong opinions about how to handle this
-* **Group agreed that Rod will take this issue and seek legal advice to find a way forward**
-
-### Rename v0.12 to v1.0.0
-
-https://github.com/nodejs/io.js/issues/218
-
-* Trevor: concerns about 1.0 vs 1.x branch naming with maintaining semver releases while also doing LTS, 1.x effectively becomes master until a 2.0 comes along.
-* Bert: -1
-* Ben: +1
-* Chris: +1
-* Fedor: +1
-* Trevor: 0
-
-Action: **Rename to "v1.x", Ben agreed to make the change**
-
-
-### Merge strategy (v0.10 and joyent/node)
-
-* _Much_ discussion about merge strategies, patches, branches, etc.
-* Agreed to merge regularly
-* **Bert agreed to monitor the situation and propose a merge strategy when the time is right**
-
-### Next meeting
-
-* Agreed to meet again on the 7th of January UTC
-* Agreed to have mini-stand-up at the beginning of each meeting
-
-
diff --git a/doc/tsc-meetings/io.js/2015-01-07.md b/doc/tsc-meetings/io.js/2015-01-07.md
deleted file mode 100644
index 5ba0f86d7f4770..00000000000000
--- a/doc/tsc-meetings/io.js/2015-01-07.md
+++ /dev/null
@@ -1,154 +0,0 @@
-# io.js TC Meeting 2015-01-07
-
-## Links
-
-* **Google Hangouts Video**: http://www.youtube.com/watch?v=hWDSToC9EV8
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/230
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1j7Sdui5DqHE8GZHxuoAaoIQ4jlntacZI285OCfVa-Eo
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* Invite Colin Ihrig to the TC #223 https://github.com/nodejs/io.js/issues/223
-* File copyright policy #216 https://github.com/nodejs/io.js/issues/216
-* Doc: clarified & split up contribution docs #233 https://github.com/nodejs/io.js/pull/233
-* Governance: Add new Collaborators #234 https://github.com/nodejs/io.js/issues/234
-* deps: upgrade v8 to 3.31.74.1 #243 https://github.com/nodejs/io.js/pull/243
-* Build
-* Intl - defaults
-* Merge v0.10
-* npm upgrade _(did not get to this)_
-
-## Minutes
-
-### Present
-
-* Bert (TC)
-* Ben (TC)
-* Chris (TC)
-* Fedor (TC)
-* Isaac (TC)
-* Colin (for voting as addition to TC)
-* Mikeal
-* Rod (facilitator)
-
-### Mini stand-up
-
-* ben: integrating tick processor, rename binary to “iojs”, upgrade v8, and plenty of libuv features/bug fixes.
-* bert: libuv: readdir on windows, build with clang, plan for next unstable libuv, use similar ev loop impl on windows as unix first tentative patches available for review.
-* chris: streams - solving failure on v1.x branch for npm, zlib patch breaks stuff, streams visualization stuff doc/writeup of node streams and whatWG streams
-* fedor /few-dir/: no updates, working on non-iojs stuff and holidays
-* colin: triaging issues in io.js and joyent/node.  helping with merge of 0.12 to 0.10
-* isaac: no io.js, vacation
-* mikeal: nada
-* rod: build build build ci ci ci.  re-did all the build slaves on Jenkins, introduced a bunch more.  Ansible scripts for linux machines (CentOS 5,6,7, Ubuntu all LTS + Current 14.10 +32bit versions, 2 ARM v7s one virtual one physical, 2 of each Windows 2012,2008, a couple interim OS X machines more permanent ones coming from Voxer soon).  https://github.com/nodejs/build Still lacking specific Jenkins setup and secrets.  Working on release process.
-    mikeal: issue re release?
-    rod: not yet, a lot of little bugs to get CI working consistently.  No grand plan for what’s in release yet.
-
-
-### Review of last meeting
-
-* sys: Remove after 3 years of deprecation #182 
-* module: force require('process') to return a reference to process #206
-* File copyright policy #216
-* Rename v0.12 to v1.0.0
-* Merge strategy (v0.10 and joyent/node)
-
-### Invite Colin Ihrig to the TC #223 
-
-https://github.com/nodejs/io.js/issues/223
-
-Asked for vote
-
-Passed unanimously
-
-Some discussion about TC member addition process
-
-### File copyright policy #216
-
-https://github.com/nodejs/io.js/issues/216
-
-* Rod: got feedback from NodeSource GC on this, recommendation is to keep the copyright but removal of the license notice is acceptable
-* Mikeal & Isaac: removing the copyright should be OK because we have full git record of who made & edited the file, it’s a PITA
-* Asked for vote on removing copyright and license from the top of each source file, moving it a single top level file. **Nobody objected**.
-* Agreed to table further discussion on modifying the license and copyright.
-* isaacs will submit PR to remove license blocks from files.
-
-### Doc: clarified & split up contribution docs #233 
-
-https://github.com/nodejs/io.js/pull/233
-
-* Rod: discussed changes introduced in #233, this is in TC because there are some minor modifications to the governance structure. Recommended that we deal with further changes to governance as a separate discussion.
-* Fedor: remove caine block from CONTRIBUTING.md
-* Mikeal: take PR as is, move the rest to further discussion & PR
-* No objections, agreed to move changes to governance and other adjustments such as moving docs into the docs dir to separate pull requests.
-* Isaacs and Chris will review and +1 the PR.
-
-### Governance: Add new Collaborators #234 
-
-https://github.com/nodejs/io.js/issues/234
-
-Rod discussed the generation of the list of proposed collaborators. 
-
-Long discussion:
-
-* Isaacs, Chris, Bert suggest throttling new contrib additions to 5/week, bump up to 10/week if it goes well, etc.
-* Ben 50/50 on “add everyone now” or “throttle new additions”
-* Bert to review list and see if there’s any contributors that seem we should not add.
-* Other TC members can review list this week.
-* Two issues to vote on at next TC meeting
-  - Issue 1:
-    a. Add everyone
-    b. Add everyone except some that are not added
-  - Issue 2:
-    a. Create a queue of people to add, throttle per week
-    b. Add immediately
-
-### deps: upgrade v8 to 3.31.74.1 #243 
-
-https://github.com/nodejs/io.js/pull/243
-
-* Ben: clean compile, apparently a clean upgrade. It does break postmortem support so Ben removed it completely. Asked who was using it.
-* Ben: adds new features:
- - numeric literals
- - string methods
- - block scoping
- - classes (strict mode)
- - object literal extensions
- - template literals.
-* Fedor: Voxer using postmortem support, so it’s not just Joyent. Would prefer to fix it.
-* No disagreement about merging this.
-* Ben and Fedor to take discussion about details to GitHub.
-
-### Build & release
-
-Rod rambled on about build & release:
-
-* Lots of minor test failures to take care of and make sure there are no serious blockers: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/
-* is osx 32-bit necessary? group agreed to leave it out.
-* binary naming: Ben currently taking care of renaming, Bert will help out with a solution for windows
-* release blobs:
-  - source
-  - windows 32, 64
-  - osx 64-bit, built on 10.10 - specify minimum requirement in XCode (apparently)
-  - linux, centos 5, libstdc++ static - Ben says we shouldn't have to, although Rod found it necessary when built with Debian Weezy, give Ben access to CentOS box to try it out
-  - linux armv7 (built on Ubuntu 14.04) (perhaps armv6 for rpi, but compile should not hold up a release--drop in later?)
-  - Windows bare files, Bert explained the files currently released in nodejs.org/dist/*/
-    - node.lib downloaded by node-gyp for compile
-    - node.pdb contains debug information (may not be needed, not used by the group, perhaps someone asked for it?), leave it out
-    - node.exe is useful where an .msi is a problem to run (no admin access)
-    - Rod proposed to move to a .zip for these for 32 and 64, but this may be a problem to get ready for release, discuss further with Bert
-* Version number - all agreed to go with 1.0.0, but it should be clearly labeled as an initial “beta”-type release for the project.
-* Website for blog/announce/news, Rod proposed Mikeal take responsibility for now until we find a better owner / team, Mikeal agreed.
-* Dist folder structure
- - Agreed to keep iojs.org/dist/ to mirror nodejs.org/dist, other things via symlinks and html hyperlinks.
- - Maybe have a iojs.org/downloads/v1/1.0.0/… and perhaps a text/html thing with links to each relevant release
-
-* Bert: Node still merging in 0.10 to 0.12, is there anything that should be merged in 0.10 that we really need?
-* intl: Bert kind of hates this patch.  joyent/node is moving towards building with small icu, you get intl object, but only supports english.  CAN build with another icu to add other intls. Bert to open an issue to discuss further. May leave out ICU completely from 1.0.0.
-
-
-### Next meeting
-
-* Bring a day forward to bless a release, i.e. 2015-01-13
diff --git a/doc/tsc-meetings/io.js/2015-01-13.md b/doc/tsc-meetings/io.js/2015-01-13.md
deleted file mode 100644
index 76e529bf8b9e24..00000000000000
--- a/doc/tsc-meetings/io.js/2015-01-13.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# io.js TC Meeting 2015-01-13
-
-## Links
-
-* **Google Hangouts Video**: http://www.youtube.com/watch?v=Z0KHYPlFI3E
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/300
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1HDUayYxTjolYZhu_hGm9hc-6MGAwWrHlNGT2Zo708ck
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* File copyright policy #216 https://github.com/nodejs/io.js/issues/216
-* governance: Add new Collaborators #234 https://github.com/nodejs/io.js/issues/234
-* The state of ES6 on io.js _(re V8 upgrade policy)_ #251 https://github.com/nodejs/io.js/issues/251
-  Quick recap:
-  - Whether if it is ok to release 1.0.0 with V8 3.31.74 minus ES6 Classes and Object Literals Extensions, considering that the initial version of io.js will be "beta" quality and probably the stable version will coincide with the stable release of V8 3.31 (~6 weeks), which will have these features reinstated.
-  - How to handle V8 updates with semver so that if the same issue arised with a different timing it could mean a bump to 2.0.0.
-  - Community suggestions:
-    * Different version naming (e.g. 1.x+v8beta, 1.x+v8dev, 1.x+v8canary)
-    * Avoid BC by moving from tip-of-stable-Chrome-branch to the next tip-of-stable-Chrome-branch (~6 weeks release cycle)
-  - How do nightly builds fit into the process.
-* 1.0.0 release checklist https://github.com/nodejs/io.js/issues/302
-
-## Minutes
-
-### Present
-
-* Trevor (TC)
-* Chris (TC)
-* Ben (TC)
-* Bert (TC)
-* Rod (facilitator)
-
-### Mini stand-up
-
-* Ben: 1.0.0 work
-* Bert: 1.0.0 work (and other things)
-* Chris: Docs mainly, made a new repo for it
-* Trevor: Stuff
-* Rod: tons of 1.0.0 release prep work, tidying up test slaves, preparing fresh release slaves and configuring release builds & installers
-
-### Review of last meeting
-
-* Invite Colin Ihrig to the TC #223 https://github.com/nodejs/io.js/issues/223
-* File copyright policy #216 https://github.com/nodejs/io.js/issues/216
-* Doc: clarified & split up contribution docs #233 https://github.com/nodejs/io.js/pull/233
-* Governance: Add new Collaborators #234 https://github.com/nodejs/io.js/issues/234
-* deps: upgrade v8 to 3.31.74.1 #243 https://github.com/nodejs/io.js/pull/243
-* Build & release (& Intl)
-
-
-### File copyright policy #216 
-
-https://github.com/nodejs/io.js/issues/216
-
-Rod: prepared a proposed new LICENSE file, needed for release, adds a new license block for io.js at the top, shifts the Joyent copyright block down but still acknowledges their claim on inherited work. https://github.com/nodejs/io.js/pull/294
-
-Group agreed to merge for now until a better (or more legally appropriate) solution is proposed.
-
-### governance: Add new Collaborators #234 
-
-https://github.com/nodejs/io.js/issues/234
-
-Rod asked if we should punt to next meeting since the group was small and we’re 1.0.0 obsessed.
-
-Group agreed.
-
-### The state of ES6 on io.js _(re V8 upgrade policy)_ #251 
-
-https://github.com/nodejs/io.js/issues/251
-
-Rod: this is about V8 version matching and V8 version stability. We’re going live with 3.31.
-
-Discussion with the V8 team suggests that 3.31 is probably not appropriate because of stability concerns. We have already had to disable class support because the V8 team announced their intention to disable it in the next release anyway.
-
-Group agreed to stick with 3.31, too late to do otherwise. Come up with a more solid stability policy later.
-
-### v1.0.0 release checklist
-
-https://github.com/nodejs/io.js/issues/302
-
-* Rod will land LICENSE change after meeting
-* Bert spoke about the v0.10 and the things that remain unmerged
-  - abort on uncaughtException for domains not landed, so may be missed; feature used by Hapi / Walmart Labs for postmoretem debugging
-  - private buffer object patch not landed, repl will crash if you do this currently
-  - sslv2 & sslv3 fixes -- we have agreed to disable these completely
-  - re timers slowness - Bert and Ben don’t like the 0.10 fix, need to find our own - not landing in 1.0.0, probably our own fix in 1.0.1
-* Bert spoke about node.exe, has code for it but it’s crashy, could release with a symlink for 1.0.0. Asked for input on the approach.
-* Discussed node-gyp - Ben to PR node-gyp (and maybe land a modified version in io.js codebase) for iojs.org/dist/vx.y.z/... for source tarball.
-  - discussed process.versions.iojs property, https://github.com/nodejs/io.js/issues/269 - group agreed to do nothing on this. Rod to find discussion or create issue to have discussion on this.
-  - discussed visual assets not being in the repo, currently copied by CI manually into src, Rod to land a PR with them
-* Rod: Changelog, we don’t have one.
-  - https://github.com/joyent/node/wiki/API-changes-between-v0.10-and-v0.12
-  - Rod: is it a blocker? Ben: not per-se but very good to have.
-  - Rod: proposed to come up with something on GitHub and ask for people to take work. Trevor will do Buffer, Chris streams, Bert child processes.
-
-
-### Next meeting
-
-* Back to normal schedule next week
diff --git a/doc/tsc-meetings/io.js/2015-01-21.md b/doc/tsc-meetings/io.js/2015-01-21.md
deleted file mode 100644
index 87e9e6b1796a94..00000000000000
--- a/doc/tsc-meetings/io.js/2015-01-21.md
+++ /dev/null
@@ -1,166 +0,0 @@
-# io.js TC Meeting 2015-01-21
-
-## Links
-
-* **Google Hangouts Video**: http://www.youtube.com/watch?v=OUoWlIshY9s
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/509
-* **Original Minutes Google Doc**: https://docs.google.com//document/d/1yOS17cUt7QUHJXxdVmEpS1ZS_N32HMO9QTHb2qL-KHk
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* Invite Domenic Denicola to the TC Meetings (https://github.com/nodejs/io.js/issues/403)
-* Governance: Add new collaborators (https://github.com/nodejs/io.js/issues/234)
-* Stabilization and Release Cycles and Process (https://github.com/nodejs/io.js/issues/405)
-  * also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/nodejs/io.js/issues/251)
-* doc: bump punycode api stability to ‘stable’ (https://github.com/nodejs/io.js/issues/470)
-* Working group reports
- * Streams
- * Website
-* ICU
-
-## Minutes
-
-### Present
-
-* Bert (TC)
-* Ben (TC)
-* Chris (TC)
-* Colin (TC)
-* Fedor (TC)
-* Isaac (TC)
-* Mikeal
-* Rod
-* Domenic
-
-### Mini stand-up
-
-* Bert: Release, polish, Windows installer, Windows XP, ICU
-* Ben: Fixing bugs, reviewing PRs, maintenance
-* Chris: Cleaning up points where core reaches in to private state of streams, TLS bug with New Relic
-* Colin: Reviewing PRs, moving vars to ES6 consts
-* Fedor: Commenting, working on replacement for GYP, written in C: https://github.com/indutny/pyg
-* Isaac: npm stuff, some streams discussing
-* Mikeal: Website WG, social media accounts, facebook, G+, etc. 
-* Domenic: Changelog & Release, clarifying V8 stuff
-* Rod: Release, etc.
-
-### Review of last meeting
-
-* File copyright policy #216 
-  - LICENSE file
-* governance: Add new Collaborators #234 
-  - Deferred to this meeting
-* The state of ES6 on io.js _(re V8 upgrade policy)_ #251 
-  - Only discussed V8 upgrade policy, re 3.31 vs 3.30
-* 1.0.0 release checklist
-
-
-### Invite Domenic Denicola to the TC Meetings
-
-(https://github.com/nodejs/io.js/issues/403)
-
-Enough agreement on GitHub and in private communications amongst TC. **Done.**
-
-### Governance: Add new collaborators 
-
-(https://github.com/nodejs/io.js/issues/234)
-
-* Mikeal: Proposed Chris leads an onboarding process, do a Hangout with a group of people from the original list who are willing to go through the process and take them in the first week and iterate from there.
-* Bert: +1 for an onboarding process, more interested in handing out voting rights to a larger group.
-* Mikeal: Would rather separate the voting rights issue from adding contributors, make a separate issue for this with ideas and come back to it at next meeting.
-* Ben: is an onboarding process necessary? New contributor should pick it up fairly quickly.
-* Chris: How we review code and deal with issues (cultural things) is hard to get across with just a written process.
-* Isaac: Basically apprentice model for joyent/node but faster and more inclusive. Some brief instruction on how to do things.
-* Mikeal: adding collaborators gives us an informal voting process, +/-1s on issues with the “collaborator” badge
-* Bert: would like to widen and formalise the voting process
-* Mikeal: wants to tackle the issue by bringing org to the roadmap repo, will bring Bert in on the process
-
-Discussed whether onboarding should be mandatory.
-
-Proposal: **take anyone proposed that +1s in that thread, mandatory onboarding process by Chris, limited by how many he can take.**
-
-Passed
-
-
-### Stabilization and Release Cycles and Process 
-
-(https://github.com/nodejs/io.js/issues/405)
-
-#### V8
-
-* Mikeal:
-  - how to align with V8 process and increase collaboration
-  - semver + V8 introduces some challenges
-* Domenic: V8 is synced to Chrome releases, Beta should ship with the version that ships with release
-* Ben: is the proposal to stick with stable V8 release that’s in stable Chrome?
-* Domenic: ideally some “beta” version of io.js that uses a Beta V8
-* Mikeal: we need more releases to get experience with this, assumption is that at some point we say “this is stable” and have a stable and unstable branch.
-* Discussed current release patterns, how they map to minor/patch
-* Domenic: we are in a “danger zone”
-* Mikeal & Domenic discussed how you might achieve a “canary”
-* Bert: proposal:
-  - io.js track stable V8, bump minor and possibly major as required
-  - have a pre-release that tracks the Beta
-* Domenic: would like to keep V8 version upgrades as a separate concern to other experimental additions to io.js, decouple from io.js releases / semver?
-* Ben: happy with stable proposal, want to move discussion on unstable to an issue for further discussion.
-* Action: **Ben file an issue to discuss how unstable works**
-* **Agreement: V8 should track stable**
-
-#### Logo
-
-* Discussed logo-per-release
-* Mikeal: we need a versatile logo to use across all web / social presences. Having a logo to designate a release would be good.
-* Mikeal: ideally website team would like JSON file containing release info to be checked in to the website repo upon completion.
-
-#### Releases
-
-* Rod: patch releases should be frequent, there have been 4 so far, it seems to be working well but we should monitor
-* Domenic: frequent releases should be normal, patch & minor should just be part of the normal process
-* Bert: would be good to have API change notes into the git log
-* Discussed further about how to deal with API changes minor/major, unstable branches, etc.
-* **Agreement: patch and minor releases are merged as part of normal business, a release then is either a patch or minor bump depending on what was merged.**
-* Move discussion about tagging vs git log recording for patch/minor/major to GitHub.
-* **Punt on discussions about who can release and how that happens**
-* **Punt on discussions about synchronizing with important ecosystem projects (NAN, node-gyp, nvm, etc.)**
-
-
-
-### also: the state of ES6 on io.js (re: V8 upgrade policy) 
-
-(https://github.com/nodejs/io.js/issues/251)
-
-Part of previous discussion
-
-### doc: bump punycode api stability to ‘stable’ 
-
-(https://github.com/nodejs/io.js/issues/470)
-
-* **Agreement**
-
-### Working group reports
-
-* Mikeal and Chris to semi-formalise the model
-* Mikeal: 6 people actively engaged and growing, “could not be going better”
-* Chris: streams group has initial set of members, some discussions going on, first meeting pending
-  * initial set of members: https://github.com/nodejs/readable-stream/issues/97#issuecomment-70399923
-* Rod:
-  - The Docker sub-group is going great and has even got the docker-iojs images accepted as the official Docker "iojs" images.
-  - Other "build" efforts are all release-focused for now, trying to streamline the process to make it possible to have multiple people able to cut releases.
-
-
-### ICU
-
-* Bert:
-  - joyent/node has small-icu enabled by default making `Intl` work
-  - can get it working but it makes the binary twice as big (~8M more)
-* Domenic: ideally we would track browsers and just include it
-* Ben: V8 adds ICU by default but you need to opt-out, which we do
-* Action: **Invite Steven Loomis to the next TC meeting to discuss further**
-
-
-### Next meeting
-
-* 28th January 2015
-
diff --git a/doc/tsc-meetings/io.js/2015-01-28.md b/doc/tsc-meetings/io.js/2015-01-28.md
deleted file mode 100644
index c24a44dbe13b86..00000000000000
--- a/doc/tsc-meetings/io.js/2015-01-28.md
+++ /dev/null
@@ -1,179 +0,0 @@
-# io.js TC Meeting 2015-01-28
-
-## Links
-
-* **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/565
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-*  governance: Add new Collaborators [#234](https://github.com/nodejs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
-*  Stabilization and Release Cycles and Process [#405](https://github.com/nodejs/io.js/issues/405) / further discussion / @iojs/tc
-  -  doc: add releases document detail release cycle [#630](https://github.com/nodejs/io.js/issues/630) / proposal from @chrisdickinson
-*  dgram: implicit binds should be exclusive [#325](https://github.com/nodejs/io.js/issues/325) / minor version bump / @bnoordhuis
-*  buffer: implement `iterable` interface [#525](https://github.com/nodejs/io.js/issues/525)  / minor version bump / @bnoordhuis
-* replace util.isType() with typeof [#607](https://github.com/nodejs/io.js/issues/607) / general use of util.is*() in core re perf
-* docs: lower the maximum stability level to "stable" [#633](https://github.com/nodejs/io.js/pull/633)
-* maintain our own package registries for io.js related packages [#640](https://github.com/nodejs/io.js/issues/640#issuecomment-71882645)
-* Working Groups PR [#599](https://github.com/nodejs/io.js/pull/599)
-* Remove “unstable” from messaging [#108](https://github.com/nodejs/website/issues/108)
-
-## Minutes
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Colin (TC)
-* Fedor (TC)
-* Isaac (TC)
-* Mikeal
-* Rod
-
-Apologies from:
-
-* Trevor (TC)
-* Domenic
-
-### Mini stand-up
-
-* Ben: Reviewed/landed pull requests, fixed bugs, the usual
-* Bert: Same as Ben, but not as much
-* Chris: On-boarding stuff
-* Colin: 
-* Fedor: working on pyg (gyp alternative in C)
-* Rod: ARMv6 builds, fixing persistent bug on Ubuntu 10.04, yay!
-* Isaacs: Only doing npm CEO stuff
-* Mikeal: social media stuff for io.js, PR, roadmap, feedback from Big Cos.
-
-### Review of last meeting
-
-* Invite Domenic Denicola to the TC Meetings (https://github.com/nodejs/io.js/issues/403)
-* Governance: Add new collaborators (https://github.com/nodejs/io.js/issues/234)
-* Stabilization and Release Cycles and Process (https://github.com/nodejs/io.js/issues/405)
-  * also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/nodejs/io.js/issues/251)
-* doc: bump punycode api stability to ‘stable’ (https://github.com/nodejs/io.js/issues/470)
-* Working group reports
- * Streams
- * Website
-* ICU
-
-### governance: Add new Collaborators
-
-[#234](https://github.com/nodejs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
-
-* Chris: Onboarded 2 groups of 4 new collaborators last week. (first group: @vkurchatkin, @micnic, @seishun, @brendanashworth, second group: @evanlucas, @Fishrock123, @Qard, @thlorenz)
-  - 30 min summary of how everything works, gov, git, etc.
-  - took exit poll to get reactions
-  - notes here: https://gist.github.com/chrisdickinson/80df88b9089c19e0459e
-* Rod: how do we iterate?
-* Chris: Do it again next week with ~4 more
-* Discussed timezones and how that works
-
-### Stabilization and Release Cycles and Process
-
-[#405](https://github.com/nodejs/io.js/issues/405) / further discussion / @iojs/tc
-
-***Also:*** doc: add releases document detail release cycle [#630](https://github.com/nodejs/io.js/issues/630) / proposal from @chrisdickinson
-
-Moved straight to Chris’ proposal:
-
-* Chris discussed thoughts in his proposal @ https://github.com/nodejs/io.js/issues/630
-* Mikeal: would rather not have a static number/list of supported versions, let that be dynamic as people & companies step up to help support them
-* Ben: “stable” and “next” would be easiest to reason about
-* Chris: “dev” is for ad-hoc semver releases, replaces nightlies with a better train system.
-* Chris: branches will be “master” - development happens here, maintain “v1.x”, “v2.x” etc. for major releases. Ideally LTS would be from major versions.
-* Fedor asked about communication to users and how much fragmentation this would cause
-* Ben: how do you keep the delta between dev and stable from getting too big
-* Chris: at most there would be a 2-week lag between something hitting dev and something going out on stable
-* Bert: suggested that we need a better batching mechanism, particularly for breaking changes, so we’re not constantly bumping major.
-
-### dgram: implicit binds should be exclusive 
-
-[#325](https://github.com/nodejs/io.js/issues/325) / minor version bump / @bnoordhuis
-
-* Ben: this is about minor version bump, that’s been decided and we’re doing a 1.1.0 so this is being merged and released
-
-### buffer: implement `iterable` interface
-
-[#525](https://github.com/nodejs/io.js/issues/525)  / minor version bump / @bnoordhuis
-
-* Ben: same as previous issue, resolved
-
-### replace util.isType() with typeof 
-
-[#607](https://github.com/nodejs/io.js/issues/607) / general use of util.is*() in core re perf
-
-* Bert: find with direct comparisons and checks where it makes sense (undefined, simple stuff)
-* Isaac: hate it all, they are difficult to inline so manually inline--pick one and use it across all
-* Colin: working on a PR to do the replacement already
-* Chris volunteered to PR a style-guide into docs
-* Isaac: better linter would be great
-
-### Doc-tool - Should we merge with the joyent/node version?
-
-* Isaac: Robert Kowalski reached out to me to ask about this.
-  - Seems silly to have two nearly-identical tools for this.
-  - Delegate to doc working group?
-  - Suggested that he just pick one from io.js or joyent/node and send a PR for that
-* Mikeal: Website WG is meeting next week, will pull in Robert to that discussion
-
-### docs: lower the maximum stability level to "stable" 
-
-[#633](https://github.com/nodejs/io.js/issues/633)
-
-* General disagreement about this
-* Mikeal suggested moving things that are likely to change into vendored packages (like streams)
-* Motivation was to set some things (frozen/locked) as unchangable because they would break too much stuff
-* Bert: we effectively have 4 levels: strict-deprecation, soft-deprecation, moving, pretty-much-done
-* Mikeal: proposed punting this for a few weeks
-* Isaac: the labels are useful for guiding people on where best to contribute and where to not bother
-
-### maintain our own package registries for io.js related packages
-
-[#640](https://github.com/nodejs/io.js/issues/640)
-
-* Mikeal: each distro (Homebrew, Debian, etc.) has their own conception of “stable”, suggestion is to maintain them under io.js and instruct people how to do this. e.g. using our own custom Homebrew end-point and instruct people how to use it with `brew`. Also could bring in complicated packages from the community.
-* Mikeal: Should come under the Build WG for now, ideally a single repo where external projects can put in a single PR to update their stuff.
-
-### Working Groups PR 
-
-[#599](https://github.com/nodejs/io.js/issues/599)
-
-* Mikeal introduced his proposal: if you’re going to do the work in a WG then you can spin that up as a separate concern
-* Ben asked for clarification about whether WGs get a free-pass in core
-  - Mikeal: no, they are isolated from core
-* Rod: clarification about relationship to TC
-  - TC has charter-revocation powers, beyond that they don’t have control over the activities of a WG
-* Consensus reached, Mikeal will put in the suggested fixes (in the PR) into the docs and merge
-
-### Remove “unstable” from messaging
-
-[#108](https://github.com/nodejs/io.js/issues/108)
-
-* Remove “unstable” from the website but not say it’s “stable”
-* Bert: big +1, use semver, don’t try and message something else, only concern is the version of V8 we are using
-* Discussed V8 4.1 and how “stable” it is
-
-### Node.js and io.js should not break each other (no, they shouldn't)
-
-[#631](https://github.com/nodejs/io.js/issues/631)
-
-Rod brought this up for quick discussion and draw attention to TC members for possible input.
-* Mikeal suggested that this should be taken to the website WG for better documentation
-
-### Working group reports
-
-* Streams
- - first WG meeting this week
-* Website
- - meeting next week
-
-### Next meeting
-
-* 4th of February
-
diff --git a/doc/tsc-meetings/io.js/2015-02-04.md b/doc/tsc-meetings/io.js/2015-02-04.md
deleted file mode 100644
index 8a2a06352a2c5a..00000000000000
--- a/doc/tsc-meetings/io.js/2015-02-04.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# io.js TC Meeting 2015-02-04
-
-## Links
-
-* **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/509
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* assert: don't compare object `prototype` property [#636](https://github.com/nodejs/io.js/pull/636) _and_  assert: introduce `deepStrictEqual` [#639](https://github.com/nodejs/io.js/pull/639) / @vkurchatkin
-* Release PGP key strategy and policy [#709](https://github.com/nodejs/io.js/issues/709)
-* If time: vm bugs? [#548](https://github.com/nodejs/io.js/issues/548), [joyent/node#9084](https://github.com/joyent/node/issues/9084)
-## Minutes
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Colin (TC)
-* Fedor (TC)
-* Isaac (TC)
-* Trevor (TC)
-* Mikeal
-* Domenic
-* Rod
-
-### Mini stand-up
-
-* Bert: Lots of commenting, still working on ICU, investigating binary size and memory size minimisation, playing with transforming the data to C
-* Chris: Integrating ESLint, held first Streams WG meeting
-* Colin: Issues and codez, removed all util.is type functions
-* Isaac: “Real job” stuff
-* Domenic: Streams WG
-* Mikeal: Starting Tracing WG, lots of org stuff, roadmap work, early feedback from reaching out to companies is that there is concern about version number conflict between io.js and Node, and debugging/tracing.
-* Trevor: moving house, tracing
-* Rod: build collaboration stuff
-
-### Review of last meeting
-
-*  governance: Add new Collaborators [#234](https://github.com/nodejs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
-*  Stabilization and Release Cycles and Process [#405](https://github.com/nodejs/io.js/issues/405) / further discussion / @iojs/tc
-  -  doc: add releases document detail release cycle [#630](https://github.com/nodejs/io.js/issues/630) / proposal from @chrisdickinson
-*  dgram: implicit binds should be exclusive [#325](https://github.com/nodejs/io.js/issues/325) / minor version bump / @bnoordhuis
-*  buffer: implement `iterable` interface [#525](https://github.com/nodejs/io.js/issues/525)  / minor version bump / @bnoordhuis
-* replace util.isType() with typeof [#607](https://github.com/nodejs/io.js/issues/607) / general use of util.is*() in core re perf
-* docs: lower the maximum stability level to "stable" (https://github.com/nodejs/io.js/pull/633)
-* maintain our own package registries for io.js related packages (https://github.com/nodejs/io.js/issues/640#issuecomment-71882645)
-* Working Groups PR (https://github.com/nodejs/io.js/pull/599)
-* Remove “unstable” from messaging (https://github.com/nodejs/website/issues/108)
-* Node.js and io.js should not break each other (no, they shouldn't)
-* Working group reports
-
-
-### assert: don't compare object `prototype` property _and_  assert: introduce `deepStrictEqual` / @vkurchatkin 
-@vkurchatkin questions:
-
-* the future of assert module;
-* relationship between assert and CommonJS Unit Testing spec;
-* particular #636 bug;
-* what "deep equality" means and how it should deal with prototypes;
-* [#639](https://github.com/nodejs/io.js/pull/639) proposal
-
-* Isaac: CommonJS is gone & dead, good ideas have to stand on their own
-* Mikeal: assert probably shouldn’t be in core
-* Isaac: it’s useful for testing Node itself and useful for runtime asserts
-* Rod asked if anyone had any objections to the changes because perhaps Validmir should just be given a blessing to go ahead and improve it.
-* Domenic: medium risk, low reward, perhaps slate this for a 2.0 release.
-* Lots of discussion about the technical merits
-* Ben: the `a.prototype !== b.prototype` is clearly a bug in the initial implementation, it should have been checking `__proto__`
-* Rod: new deepStrictEqual() does that check properly
-
-
-Conclusion: accept both of
-
-- [#636](https://github.com/nodejs/io.js/pull/636)
-- [#639](https://github.com/nodejs/io.js/pull/639)
-
-(Contrast #636 with [#621](https://github.com/nodejs/io.js/pull/621), which is a more ambitious change and probably not a good idea.)
-
-1. deepEqual = No prototype checking
-2. deepStrictEqual = proper prototype checking
-Passed without objection
-
-### Release PGP key strategy and policy / @rvagg
-
-[#709](https://github.com/nodejs/io.js/issues/709)
-
-* Rod summarised how the current release key strategy works and is documented on the README. Asked for feedback on:
-  - Which keyserver(s) to use
-  - Whether to go with a master/sub key design for the project
-* No strong opinions, nothing actionable here
-
-### VM bugs? [#548](https://github.com/nodejs/io.js/issues/548) / @domenic
-
-[joyent/node#9084](https://github.com/joyent/node/issues/9084)
-
-* Domenic introduced #548, some odd VM bugs that seem to be V8 bugs, 
-* Isaac encouraged Domenic to follow this up with the V8 team to get feedback on how this works
-
-### Next meeting
-
-* Skipping a week due to Node Summit
-* Feb 18th 2015
diff --git a/doc/tsc-meetings/io.js/2015-02-18.md b/doc/tsc-meetings/io.js/2015-02-18.md
deleted file mode 100644
index 15ef54588282de..00000000000000
--- a/doc/tsc-meetings/io.js/2015-02-18.md
+++ /dev/null
@@ -1,129 +0,0 @@
-# io.js TC Meeting 2015-02-18
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=jeBPYLJ2_Yc
-* **Google Plus Event page**: https://plus.google.com/events/ccrkam8uup1k8qbo0fmcea0n2v4
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/509
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1JnujRu6Rfnp6wvbvwCfxXnsjLySunQ_yah91pkvSFdQ
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* util: fixed behavior of isObject() [#822](https://github.com/nodejs/io.js/issues/822) / @chrisdickinson / major version release
-* Translate installers for OS X and Windows [#819](https://github.com/nodejs/io.js/issues/819) / @rvagg / maintenance overhead
-* lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
-* Implement unhandled rejection tracking [#758](https://github.com/nodejs/io.js/issues/758) / @rvagg / how can we help this land
-* Logo / Brand Treatment
-[website/181](https://github.com/nodejs/website/issues/181) @ mikeal
-https://www.behance.net/gallery/23269525/IOJS-logo-concept
-* Stability Policy/Statement & Roadmap
-[#725](https://github.com/nodejs/io.js/issues/725) / @mikeal
-[roadmap/14](https://github.com/nodejs/roadmap/issues/14) / @mikeal
-
-## Minutes
-
-### Present
-
-* Bert (TC)
-* Chris (TC)
-* Colin (TC)
-* Isaac (TC)
-* Trevor (TC)
-* Mikeal
-* Domenic
-* Rod
-* Apologies for Ben and Fedor
-
-### Mini stand-up
-
-* Bert: NodeSummit and company stuff, Windows io.js stuff
-* Chris: styleguide work, wrangling ESLint, slow week
-* Colin: busy with work, porting joyent/node work to io.js
-* Domenic: having fun with VM stuff in jsdom, have a release coming soon
-* Rod: not as much as usual, preparing for 1.3.0
-* Isaac: Node Summit, npm stuff
-* Mikeal: i18 groups, >160 new people doing translations, press inquiries because of Node Foundation news, lots of website stuff (i18n & build), roadmap and stability
-* Trevor: Some critical stuff on joyent/node, work, moving house
-
-### Review of last meeting
-
-* assert: don't compare object `prototype` property _and_  assert: introduce `deepStrictEqual` / @vkurchatkin 
-* Release PGP key strategy and policy / @rvagg
-* VM bugs? [#548](https://github.com/nodejs/io.js/issues/548) / @domenic
-
-### util: fixed behavior of isObject() [#822](https://github.com/nodejs/io.js/issues/822) / @chrisdickinson / major version release
-
-* Chris: Requires semver-major, what’s the vibe on bumping major at this stage?
-* Chris: isObject() would now return true when checking for functions
-* Mikeal: interested in separating “things that break” and “API breakage”
-* Chris: consider this a “fix” but is also an API change that could break people’s downstream code
-* Isaac: probably want to put off a 2.x release until we have more substantial changes, not to wait for 2 years but have some time frame, like 6 months
-* Bert: messaging is off for a 2.0 bump just for this
-* Domenic: versions shouldn’t mean the same as they used to, major version bumps should be more casual
-* Rod: are we stopping saying that this is compatible with “Node”?
-* Mikeal: compatible with past-Node, not joyent/node 0.12+ because we have no control over that
-* Mikeal: release channels - standard semver & canary which is everything else
-* Chris: +1 for release channels, but not so much on substance of the proposal.
-* Rod: concerned about the emotional energy we’re still investing in version numbers when we should be just doing semver
-* Mikeal: ignore version numbers, have a “canary” type branch and start releasing on that until we’re confident to merge back in
-* Chris: difference between Mikeal’s proposal and the original proposal is having a “canary” branch that stuff gets merged in to and eventually is merged in to master, original proposal merged new stuff in to master and used the time delay as “canary” (like Chrome)
-* Rod: proposal is to tag this issue as a milestone for now and punt until we have more substantive changes - no disagreements, passed
-
-### Translate installers for OS X and Windows [#819](https://github.com/nodejs/io.js/issues/819) / @rvagg / maintenance overhead
-
-* Rod: concern here is the maintenance overhead in keeping all of the translations in sync, are we happy to have that headache in core?
-* Mikeal: let English be the default and let the translation teams be responsible for watching for changes and making updates as appropriate
-* Bert: installer framework is largely out of our control for how the mechanics of translations and fallbacks work, -1 on this because it’s just an installer and there are probably better targets for translation
-* Mikeal: the translation teams will prioritise for themselves what gets translated.
-* Domenic: enable the community as long as it doesn’t add friction
-* Bert: if there is no technical issue then OK with landing this, the responsibility for translation will have to be with that community
-* Resolution: allow this to land unless there are going to be technical blockers to future installer changes needing to wait for translations to be updated
-
-### lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
-
-* Ben’s issue, punt till next meeting, note in “known issues” for releases
-
-### Implement unhandled rejection tracking [#758](https://github.com/nodejs/io.js/issues/758) / @rvagg / how can we help this land
-
-* Rod: Brought to TC to get some more engagement and help get this landed unless there are any major objections
-* Domenic: PR looks good, it’s mainly a matter of code quality, doesn’t add any default handlers which is a good incremental way of adding this
-* Trevor discussed concerns about how V8 runs the events, synchronously vs on the micro-task queue
-* Trevor: OK with the change because there is almost no overhead if you’re not using Promises or this event, concerned about the disconnect between the V8 API vs what we expect it to be--the PR compensates for V8 behavior.
-* Domenic: user-exposed semantics of this PR are good
-* Mikeal: concerned about behavior change in the future leading to a 
-* Rod: proposed resolution is to give the TC’s blessing to that PR for it to land when everyone in there is happy with it
-  - No objections
-
-### Logo / Brand Treatment
-[website/181](https://github.com/nodejs/website/issues/181) @ mikeal
-https://www.behance.net/gallery/23269525/IOJS-logo-concept
-
-* Mikeal discussed the proposed website changes and logo choice @ https://www.behance.net/gallery/23269525/IOJS-logo-concept
-* Some discussion about choice of logo, no strong opinions on design
-* Rod: may be best to let the website group make this choice because they are more qualified from a design perspective
-* Chris: design group could be asked to come up with a few options and present them for selection
-* Mikeal: design by committee sucks, everyone knows this
-* Chris: can we come up with some standards and assert them ack to designers - such as number of colors, needs to look good at 16x16 all the way up
-* Rod: maybe this group isn’t qualified to even do that, perhaps push it on to the WG
-* Discussion on the process of selecting a logo and brand treatment
-* Agreed to delegate to the website WG to make this decision
-
-### Stability Policy/Statement & Roadmap
-[#725](https://github.com/nodejs/io.js/issues/725) / @mikeal
-[roadmap/14](https://github.com/nodejs/roadmap/issues/14) / @mikeal
-
-* Mikeal: none of this is fixed in stone, we can change it in the future if we decide it won’t work
- - one change still to go in is that the wording on stability should be that “we won’t remove an API”
- - people are terrified that we’re going to break compatibility and go off in new directions, this is a way of dealing with that
-* Bert: concerned about this being a reflection of the way we work rather than enforcing new behaviors
-* Discussion around breaking / removing APIs and how firm this policy is going forward
-* Rod asked for specific things that need to be resolved now vs punting to a later meeting
-* Mikeal: https://github.com/nodejs/roadmap/commit/190690a1b5f206c22f64adc3d29d10c4b08cb8cd
-* Group discussed presentations, no major objections so the blessing was given for Mikeal to move forward with ratifying that, expect further discussion on the broader topic next meeting.
-
-### Next meeting
-
-* Next week, 25th Feb 2015
-
diff --git a/doc/tsc-meetings/io.js/2015-03-04.md b/doc/tsc-meetings/io.js/2015-03-04.md
deleted file mode 100644
index 4b1751a5c705be..00000000000000
--- a/doc/tsc-meetings/io.js/2015-03-04.md
+++ /dev/null
@@ -1,164 +0,0 @@
-# io.js TC Meeting 2015-03-04
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=vxX2CkFPEtk
-* **Google Plus Event page**: https://plus.google.com/events/c9ijr7edl14im7dspk5njktmjq4
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1053
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1RoIE68l8B2iWLdEPM7ApSN2FxFDd3OY0wfTeqUh-K9w
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
-* iojs: introduce internal modules [#848](https://github.com/nodejs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin)
-* url: significantly improve the performance of the url module [#933](https://github.com/nodejs/io.js/issues/933) / @mikeal
-* Ship websockets in core [#1010](https://github.com/nodejs/io.js/issues/1010) / @piscisaureus
-* RFC: upgrade to V8 4.2? [#1026](https://github.com/nodejs/io.js/issues/1026) / @bnoordhuis
-* Colin resigning from TC [#1056](https://github.com/nodejs/io.js/pull/1056)
-
-## Minutes
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Domenic
-* Fedor (TC)
-* Mikeal (meeting lead)
-* Isaac (TC)
-* Trevor (TC)
-* Rod
-
-### Mini stand-up
-
-* Ben: PRs, bugs, perf improvements, same old awesome Ben
-* Bert: talking, child process bugs, looking further in to Windows bugs that are still outstanding, no coding
-* Chris: reviewing PRs, onboarding Julian, Christian, Brian, Robert, Ben. Code for core module discovery / use in packages in npm.
-* Domenic: Streams work WHATWG sync with io.js streams ideas.
-* Fedor: fixing bugs, PRs
-* Isaac: coding for fun, node-tap rewrite, global/window alias discussions, node_modules flattening, Windows stuff. Looking in to TLS issues for io.js and 0.12, TLS over Pound causes problems, possibly OpenSSL problem.
-* Mikeal: Website and Evangelism WG work, lots of new collabs and work, getting things in sync
-* Rod: Releases, Windows bug / Jenkins drama, ARMv8 support
-* Trevor: Buffer.indexOf(), nextTick perf improvement
-
-
-### Review of last meeting
-
-* util: fixed behavior of isObject() [#822](https://github.com/nodejs/io.js/issues/822) / @chrisdickinson / major version release
-* Translate installers for OS X and Windows [#819](https://github.com/nodejs/io.js/issues/819) / @rvagg / maintenance overhead
-* lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
-* Implement unhandled rejection tracking [#758](https://github.com/nodejs/io.js/issues/758) / @rvagg / how can we help this land
-* Logo / Brand Treatment
-[website/181] https://github.com/nodejs/website/issues/181 @ mikeal
-https://www.behance.net/gallery/23269525/IOJS-logo-concept
-* Stability Policy/Statement & Roadmap
-[#725](https://github.com/nodejs/io.js/issues/725) / @mikeal
-[roadmap/14](https://github.com/nodejs/roadmap/issues/14) / @mikeal
-
-
-### Colin resigning from TC [#1056](https://github.com/nodejs/io.js/pull/1056)
-
-
-### lib: fix process.send() sync i/o regression
-[#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
-
-* Ben: @orangemocha did some work on Windows for libuv, unsure if this helps.
-* Bert: process.send() has been made sync on *nix because otherwise it’s a breaking change, but on Windows it’s always been async so changing it to sync would also be a breaking change. So the situation is crazy.
-* Isaac: ideal is that they behave the same and behave well
-* Discussion about whether this would be a breaking change or a bugfix
-* Bikeshed, moving to GitHub
-* Bert: proposed that we revert Unix behaviour and leave Windows as it is
-* Ben: current fix adds blocking on Windows
-
-
-### iojs: introduce internal modules
-[#848](https://github.com/nodejs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin)
-
-Chris: lets us have modules that can’t be required from outside of core. I’m in favor; it’s a nice insurance policy, especially in light of the stability policy that we will try not to make any breaking changes to the JavaScript API.
-
-Mikeal: this doesn’t change the existing pseudo-internal modules to become truly internal, right?
-
-Chris: correct, that is separate.
-
-Domenic: but, doing that operation would be a good thing to do in a major version bump.
-
-Isaac/Mikeal: yes, but don’t do that for `util._extend`, too many people use it.
-
-Chris: *gives example of how this would have been helpful for a recent refactor*
-
-Ben: how will the test suite test internal functions from then on?
-
-Chris: there would be a flag, e.g. --allow_internal_modules.
-
-Mikeal: I like it.
-
-Bert: I like it too. However I am concerned about products that do monkeypatching; would that still be possible?
-
-Chris: I think so, as long as they monkeypatch the public APIs…
-
-Ben: not sure that’s quite sufficient…
-
-Domenic: seems like a pure win because it allows you not to have to put everything in one file to keep things private.
-
-### url: significantly improve the performance of the url module
-[#933](https://github.com/nodejs/io.js/issues/933) / @mikeal
-
-This will get rolled in to the major version issue Chris is putting together.
-
-### Ship websockets in core
-[#1010](https://github.com/nodejs/io.js/issues/1010) / @piscisaureus
-
-Bert: I’m not sure I believe in this any more; the major reason I wanted this was that building native addons is terrible, but people brought up that the native part of the web socket implementations only do some bitwise buffer stuff and so we could probably just add *those* to core.
-
-Discussion of how we should probably just add more Buffer methods to core.
-
-Bert: there’s another aspect of this. At some point Node was really modern, but we’ve fallen behind. We can’t even get HTTP/2 or web sockets, we’re in trouble.
-
-Domenic: we’ve learned a lot over the last few years that pushes us to userland code instead of in core. But we need to have some things be “official.”
-
-Trevor: I would like the infrastructure for HTTP/2 to be similar to HTTP/1, with http-parser etc.
-
-Ben: is there any reason HTTP/2 couldn’t be done in pure JS?
-
-Discussion of http-parser and current HTTP/1 implementation strategy and speed.
-
-Bert: I think as a TC what we should say is “we would like to support HTTP/2, but want to see some userland ideas first.” We don’t need to actually start implementation progress right now.
-
-Ben: does anyone on the TC want to write a userland HTTP/2 module?
-
-Discussion of how Fedor already has a SPDY implementation.
-
-Trevor: are we going to do TLS-only HTTP/2?
-
-Mikeal: we probably don't want to, because our HTTPS is not as fast as terminators.
-
-Conclusion:
-We should start an issue in NG about the core modules/modernity stuff.
-We should publicly state that we’re interested in supporting HTTP/2 in the related issue thread, although we’re not sure about implementation strategy and want to see experiments.
-
-### RFC: upgrade to V8 4.2?
-[#1026](https://github.com/nodejs/io.js/issues/1026) / @bnoordhuis
-
-* Ben: V8 4.1 has gone gold/stable so we should probably upgrade by un-floating a revert we placed on top of it. I propose we revert that revert, so that we get 4.1-as-shipped-in-Chrome. [#952](https://github.com/nodejs/io.js/pull/952) for details on the floating revert.
-* Domenic: do we have clarity about ABI vs. API implications for io.js major version?
-* Ben: ABI change means everyone has to recompile their add-ons so we should bump the minor.
-* Fedor: this feels more like a major version?
-* Domenic: do we consider forcing people to run “npm rebuild” a breaking change?
-* Chris: I think I agree that users should not expect to have to rebuild within the same major version.
-* Mikeal: how often does a V8 ABI change happen *after that V8 gets into stable Chrome*?
-* Domenic: not sure, but would suspect not often at all. Maybe we should check with V8.
-* Ben: yes, not often.
-* Fedor: having a call with V8 might be helpful.
-* Mikeal: if it doesn’t happen, then we won’t end up in this situation again.
-
-Conclusion:
-
-Work with V8 team to make sure this doesn’t happen again
-Add “un-revert” to the growing list of issues that would trigger a minor version bump.
-
-### Next meeting
-
-* 
diff --git a/doc/tsc-meetings/io.js/2015-03-18.md b/doc/tsc-meetings/io.js/2015-03-18.md
deleted file mode 100644
index 63b1bb758fc070..00000000000000
--- a/doc/tsc-meetings/io.js/2015-03-18.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# io.js TC Meeting 2015-03-18
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=tQwVcuYCiZ4
-* **Google Plus Event page**: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1187
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1It6PTEBQ7OjW8P88hCLoXvcWKA3Q8dY2eYEHIF6FvS4
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* [#1134](https://github.com/nodejs/io.js/pull/1134) Add Docker working group
-* [#1140](https://github.com/nodejs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions
-* [#1130](https://github.com/nodejs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
-* [#1077](https://github.com/nodejs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris
-
-## Minutes
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Fedor (TC)
-* Trevor (TC)
-* Rod
-
-### Mini stand-up
-
-* Ben: reviewing bugs, fixing pull requests
-* Bert: debugging Windows issues (related to #1005), working on a more helpful CI dashboard
-* Chris: working on tools to inspect amount of ecosystem breakage that changes cause
-* Fedor: working through PayPal leak issue, working on net.socket() changes
-* Rod: ..
-* Trevor: misc PRs, process.nextTick(), timer bug
-
-### Review of last meeting
-
-* lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
-* iojs: introduce internal modules [#848](https://github.com/nodejs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin)
-* url: significantly improve the performance of the url module [#933](https://github.com/nodejs/io.js/issues/933) / @mikeal
-* Ship websockets in core [#1010](https://github.com/nodejs/io.js/issues/1010) / @piscisaureus
-* RFC: upgrade to V8 4.2? [#1026](https://github.com/nodejs/io.js/issues/1026) / @bnoordhuis
-* Colin resigning from TC [#1056](https://github.com/nodejs/io.js/pull/1056)
-
-### [#1134](https://github.com/nodejs/io.js/pull/1134) Add Docker working group
-
-* Rod: originally conceived to be a “sub-WG” of Build WG but this makes sense because there is little overlap with the Build team or skills required for the Build team.
-* Rod: this group is already maintaining official Docker images or io.js located at https://github.com/nodejs/docker-iojs which are also the “official” Docker images for io.js.
-
-### [#1140](https://github.com/nodejs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions
-
-* Bert: in favour of stream_base now and don’t want it reverted given the fixes that have been made. The real problem was the introduction of a major change that lead to a lot of breakage and a lot of fix commits. Proposed that we have a “ng” (or similar) branch with releases for testing before merging.
-* Chris: agree that we need a canary policy of some kind to deal with this
-* Bert: feature flags are a good way of dealing with this and letting them test changes
-* Ben: time-based releases like Rust and Chrome
-* Fedor: main problem is that we didn’t have enough tests for this feature when it was merged.
-* Rod: there’s awkwardness around releasing given that we only have one tip and we can’t cut patch releases once we have semver-minor changes are merged.
-* Trevor: should have semver-minor branches where patch fixes go in and minor changes go in to master/whatever.
-* Discussion about git process
-* Discussion about semver
-* Discussion about minor/patch and what it communicates
-* Discussion about test coverage
-* Rod asked OpenSSL fix: agreed to punt on a release until OpenSSL fix has been released and go immediately after that.
-
-### [#1130](https://github.com/nodejs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
-
-* Rod: there was some off-record discussion about TC membership process related to #1130 and #1131.
-  - Neither individual was asked and it would be good to at least have it passed by them first
-  - Would be good to have a smooth on-boarding mechanism to bringing someone on to meetings before officially making them TC, agreed to invite Jeremiah to next TC _if_ he’s interested in being involved.
-  - Generally agreed that increasing the size of the TC is a good thing (minus the meeting-overhead added by more people)
-
-### [#1077](https://github.com/nodejs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris
-
-* Trevor: passing arguments / context through process.nextTick() in core is common and would be significantly faster if we use a setArgs() feature.
-* Chris: needed in readable-stream
-* Discussed API concerns and how underscored methods still become defacto in userland
-* Chris: could land the internal-module PR and use a Symbol for setArg
-* Trevor: major speed increase comes from flattening the call-structure, there’s no additional stack entries for passing arguments. Particularly in crypto, nextTick() is called a lot.
-* Rod: we need perf numbers from a user-experience perspective, perhaps that will make it more compelling to merge or perhaps it will make this look trivial that it’s not worth the cost of introducting ugly API
-* Trevor: will go off and come back with numbers
-
-### Major version bump
-
-* Ben: proposed making a new integration branch to merge all of the semver-minor features, plus a V8 upgrade, we can start pushing out nightly-style releases for playing around and punt the decision on _how_ to do a major release down the road a little.
-* Group agreed, Rod agreed to help come up with a release mechanism for nightlies to couple with this.
-
-### Next meeting
-
-* 25th March 2015
diff --git a/doc/tsc-meetings/io.js/2015-04-01.md b/doc/tsc-meetings/io.js/2015-04-01.md
deleted file mode 100644
index 43a756e75bf060..00000000000000
--- a/doc/tsc-meetings/io.js/2015-04-01.md
+++ /dev/null
@@ -1,107 +0,0 @@
-# io.js TC Meeting 2015-04-01
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=B1pTT60E73M
-* **Google Plus Event page**: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1311
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1iEzSiQpB3me-x1R0_FzlMtGuPmgxR2x7NMITp779690
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* reconciliation update (Mikeal and Bert)
-* doc: add NAN WG [#1226](https://github.com/nodejs/io.js/issues/1226)
-* Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/nodejs/io.js/issues/1225)
-* governance: Raise the bar for changes in membership and governance policy  [#1222](https://github.com/nodejs/io.js/issues/1222)
-* Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/nodejs/io.js/issues/1131)
-
-## Minutes
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Domenic
-* Fedor (TC)
-* Jeremiah
-* Mikeal
-* Trevor (TC)
-* Rod
-
-### Mini stand-up
-
-* Ben: rewriting the timers module
-* Bert: making it possible to rename node.exe/iojs.exe (made it into 1.6.3); governance documents for Node Foundation
-* Chris: building a UTF-8 consumer that can validate/skip invalid glyphs; working on a tool around control flow analysis
-* Domenic: not much io.js related
-* Fedor: rewrote io.js in Go, deciding whether it should be go.io or io.go
-* Jeremiah: managing issues, reviewing PRs, investigating timers bugs
-* Mikeal: io.js charter / Linux foundation work
-* Trevor: looking into beforeExit/timer unref/uv_loop_alive interactions; Node API compliance working group docs (not io.js ... might be fed into the Foundation)
-* Rod: released 1.6.3; GitHub DDOS and CI errors/timeouts are frustrating
-
-### Review of last meeting
-
-* [#1134](https://github.com/nodejs/io.js/pull/1134) Add Docker working group
-* [#1140](https://github.com/nodejs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions
-* [#1130](https://github.com/nodejs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
-* [#1077](https://github.com/nodejs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris
-* Major version bump
-
-
-### Reconciliation update (Mikeal and Bert)
-
-* Mikeal: getting close to a really good position where the governance structures can be merged between io.js and joyent/node. New working group structure and relationship with “TSC”. People can engage @ https://github.com/joyent/nodejs-advisory-board/ with active PRs @ https://github.com/joyent/nodejs-advisory-board/pull/30 & https://github.com/joyent/nodejs-advisory-board/pull/33
-* Bert: discussed why this is good for io.js:
-  - io.js still has a very low profile, merging would be good for everyone
-  - budget from corporate backers, including the ability to travel
-* Mikeal: added to those comments: institutional backing would be very helpful at this stage
-* Ben: current PR seems to give the board more influence than originally suggested
-* Mikeal: the intent is the board is not to make technical decisions, the TSC is
-* Trevor: counterpoint example is IBM maintaining their own fork of V8 so they may want influence on the release process
-* Mikeal: they will be taken care of by an LTS schedule
-* Bert: IBM agrees that there should be a fast-moving tip and they just use an LTS. Board could also assert influence by way of a corporation threatening to withdraw backing.
-
-### doc: add NAN WG [#1226](https://github.com/nodejs/io.js/issues/1226)
-
-* Rod: discussed proposed move of rvagg/nan and rvagg/node-addon-examples to iojs to be governed by an “Addons API Working Group”
-
-Bert: +1
-Chris: +1
-Fedor: +1
-Ben: +1
-Trevor: +1
-
-### Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/nodejs/io.js/issues/1225)
-
-* No disagreement, lots of +1s, good to go
-
-### governance: Raise the bar for changes in membership and governance policy [#1222](https://github.com/nodejs/io.js/issues/1222)
-
-* Mikeal: the PR is a bit stale because of a miscount, just want to make sure that there are no concerns with this even though it may not end up being required given the movements with the TC.
-* Rod: requested that we not hold up progress in io.js pending movement on the JNAB / Foundation process and we should treat that as a separate thing that may or may not happen.
-* Bert: happy with the changes but can’t +1 because of the TC company proportion counting
-* Mikeal: just a miscount, needs to be changed, wanted to test if people are OK with this once we have more people on the TC. Main point was to flush out any concerns about raising the bar.
-* Ben: suggested that it become 2 PRs, make the 2/3rds thing a separate issue.
-
-### Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/nodejs/io.js/issues/1131)
-
-* Rod: fine with this
-* Discussed meeting facilitation, agreed that it wasn’t a strictly defined role but it would be good to share it around a bit.
-
-Bert: +1
-Chris: +1
-Fedor: +1
-Trevor: +1
-Ben: +1
-
-### Open to QA from IRC
-
-_Nothing clear to discuss, but we’ll keep trying this_
-
-### Next meeting
-
-* 8th April 2015
diff --git a/doc/tsc-meetings/io.js/2015-04-08.md b/doc/tsc-meetings/io.js/2015-04-08.md
deleted file mode 100644
index 489df62ef9b5e3..00000000000000
--- a/doc/tsc-meetings/io.js/2015-04-08.md
+++ /dev/null
@@ -1,184 +0,0 @@
-# io.js TC Meeting 2015-04-08
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=OjlK8k10oyo
-* **Google Plus Event page**: https://plus.google.com/events/c1c3234uog6svplgrapqucb557k
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1369
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1EsDjfRGpVKFABH4LcNXNxsAsBTnHsU-i5cehmAcp1A8
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* [#1101](https://github.com/nodejs/io.js/pull/1101) http: allow HTTP to return an HTTPS server / @silverwind / the use of a `tls` option to trigger `https` module functionality
-* [#1301](https://github.com/nodejs/io.js/pull/1301) Util(.is*) Deprecations / @Fishrock123 & @brendanashworth / [this comment](https://github.com/nodejs/io.js/pull/1301#issuecomment-90829575) asking for an opinion from the TC on how to move forward
-* Discuss https://github.com/jasnell/dev-policy [[comment by @mikeal]](https://github.com/nodejs/io.js/issues/1369#issuecomment-90955688)
-* Discuss / Review the `require(‘.’)` situation [[comments by @silverwind and @Fishrock123]](https://github.com/nodejs/io.js/issues/1369#issuecomment-90933134)
-
-
-### Present
-
-* Bert (TC)
-* Domenic
-* Trevor (TC)
-* Ben (TC)
-* Fedor (TC)
-* Jeremiah
-* Mikeal
-* Chris (TC)
-
-### Review of last meeting
-
-* reconciliation update (Mikeal and Bert)
-* doc: add NAN WG [#1226](https://github.com/nodejs/io.js/issues/1226)
-* Proposal: Authorise @Fishrock123 to create releases  [#1225](https://github.com/nodejs/io.js/issues/1225)
-* governance: Raise the bar for changes in membership and governance policy.  [#1222](https://github.com/nodejs/io.js/issues/1222)
-* Nominating Rod Vagg @rvagg to the TC  [#1134](https://github.com/nodejs/io.js/issues/1131)
-
-### Quick stand-up
-
-* Ben: fixing bugs, reviewing PRs. Looked into adding `Generator.prototype.return()` in V8, but more complicated than expected (crashes and can’t figure out why). Fedor might help.
-* Bert: working on a CI status dashboard. Reviewing a patch that makes Node use Chakra instead of V8 (!)
-* Chris: worked on a patch to add a UTF8 consumer to utils, for the purposes of eventually adding UTF8 validation as well as being able to externalize buffer-strings. Talked about standardizing destroy() behavior on streams
-* Domenic: Not much on io.js, reviewed some dev policy stuff especially with regard to V8
-* Fedor: bugs and PRs
-* Jeremiah: bugs and PRs and 1.6.4 release
-* Mikeal: worked on dev policy for the foundation, continuing to iterate; distilling feedback from worried-about-reconciliation thread, but had to lock it in the end with links to other places to address such things.
-* Trevor: code reviews
-
-## Minutes
-
-### [#1101](https://github.com/nodejs/io.js/pull/1101) http: allow HTTP to return an HTTPS server
-
-***@silverwind / the use of a `tls` option to trigger `https` module functionality***
-
-Jeremiah: two options we have (that we’ve discussed) are a tls option, or just auto-detect if you provide appropriate options.
-
-Ben: why is this a TC issue?
-
-Jeremiah/Domenic: three or four weeks without consensus.
-
-Mikeal: related to issue in NG, where you could pass options to listen() instead of createServer().
-
-Chris/Jeremiah: there is a PR for it in joyent/node; not merged yet.
-
-Fedor: to me the problem is `http.request` vs. `https.request`.
-
-Mikeal: (advocates for .listen again)
-
-Trevor: -1 for doing it .listen; it’s too complicated internally; there is lots of weirdness going on here already.
-
-Fedor: would be harder to share a server among workers in a cluster.
-
-DD: but this particular PR is just a simple change to allow you to avoid having to decide between require('http') vs. require('https').
-
-Bert: I kind of like the version where you put the options in listen().
-
-Ben: what happens when iojs is compiled without TLS support?
-
-**Conclusion**: punt on this. Initial feedback is that if we were to go down this route, we would slightly prefer the explicit tls option; however, there needs to be a discussion about the listen() idea, and also about compilation without TLS.
-
-### [#1301](https://github.com/nodejs/io.js/pull/1301) Util(.is*) Deprecations
-
-***@Fishrock123 & @brendanashworth / [this comment](https://github.com/nodejs/io.js/pull/1301#issuecomment-90829575) asking for an opinion from the TC on how to move forward***
-
-Bert: what’s the point?
-
-Trevor: that we won’t really fix bugs in these.
-
-Mikeal: this is just in the docs?
-
-Ben: also util.deprecate to log a warning
-
-Mikeal: that just sounds annoying
-
-Trevor: it’s supposed to be; fix your code
-
-Mikeal: yeah but it’s not always your code…
-
-Bert: we already have two levels of deprecation, warning and not warning
-
-Domenic: however we only use the latter for domains, since we don’t have an alternative for them
-
-Mikeal: can we do staged deprecations, marking things in the docs for one major release cycle, then in the next major release cycle start warning
-
-Domenic: could we add an option to show the deprecation warnings for people who are contentious?
-
-Mikeal: I don’t think anyone would actually turn that on…
-
-Chris: I might be able to run my tooling over all of npm to detect uses
-
-Bert: we need a better strategy in general for moving things out of core. The reason we want to deprecate these is that we don’t really want to fix it because that would be backward incompatible, so this is really too big to be in core. Any ideas for making these better? Maybe if you install a module called util it can take precedence over the one in node? So then we can release the fixed one on npm?
-
-Mikeal: that does sound better than versioning core modules … we hit a flag that lets you replace the core one with a new one. Over time we’ll be able to get data.
-
-Bert: there were some talks about doing this in browsers?
-
-Domenic: not really, nobody wants to ship two versions.
-
-**Conclusions: mark util.isXYZ deprecated in the docs, but do not show a warning in the console this version**
-
-### [Dev Policy](https://github.com/jasnell/dev-policy)
-
-Chris: looking good to me, on the right path, some minor issues still being worked out. E.g. around using priority tags and ways to funnel work to smaller number of contributors in joyent/node vs. just adding more contributors as we do.
-
-Jeremiah: Node has a CI Jenkins PR integration thing that they are in favor of using
-
-Domenic: honestly anything that prevents people from committing things that turn the build red would be awesome…
-
-Bert: agree.
-
-Bert: there’s an issue about version numbers
-
-Mikeal: if we merge, it’ll be a 2.0.0, and we’ll bring in the backward incompatible changes we’ve been sitting on for a while
-
-Mikeal: more on this tomorrow, audio will be public after it happens (due to technology being used it won’t be live). Please review dev policy beforehand.
-
-### Isaac
-
-Ben: Isaac doesn’t seem to be involved anymore. What do we do when a TC member goes AWOL?
-
-Mikeal: well, we cancelled two meetings he was ready to attend, and then he went on vacation for two weeks, so AWOL isn’t quite the right characterization… But yeah, he’s not doing too much. We can just ask if he wants to be there, or we can vote it off.
-
-Bert: I asked him and didn’t get an extremely clear answer; we’ll probably get more clarity when he’s back from vacation. I would not suggest throwing him off right now.
-
-Ben: yeah, there’s no urgency, just…
-
-Bert: yes, but I agree that if you’re on the TC you should show up to meetings
-
-Fedor: what if we made votes exponentially decay in power based on attendance…
-
-### `require('.')`
-
-Mikeal: if we knew the impact of this change would we have done a major?
-
-Chris: if we would have done a major we wouldn’t have done it at all because the API is locked and only bugfixes are allowed.
-
-Jeremiah: that being said the only thing that breaks is a strange workflow from an undocumented feature.
-
-Ben: I am not very sympathetic to that argument; we broke someone’s workflow, and that’s bad.
-
-Domenic: I don’t think that’s fair. Every change is breaking to someone; even changing error messages will break people who parse error messages. The question is what side of the line this is on.
-
-Mikeal: it seemed weird…
-
-Domenic: I always thought NODE_PATH was deprecated. Should we warn about people using it?
-
-Ben: I understand that someone is already using the new require behavior, so reverting it would be backward-incompatible. So we have a few options: 1) add a hack that makes NODE_PATH interactions with require('.') work as they used to; 2) say “sorry” and keep as-is
-
-Bert: I’m sympathetic to adding the hack and a warning.
-
-Domenic: agree. And maybe try to kill NODE_PATH in 3.x.
-
-**Conclusion: hack plus a warning that shows up in this hacky case (“hey, you’re using the require-dot trick with NODE_PATH; we made it work because we’re nice people, but we want to take it away in 2.x, so gear up”). In 2.x, probably warn on any use of NODE_PATH at all.**
-
-### Bert shows off his CI prototype
-
-It’s pretty cool.
-
-It groups tests in interesting ways that are useful. (OS, flakiness, …)
-
-### Next meeting
-
-* 2015-04-15
diff --git a/doc/tsc-meetings/io.js/2015-04-15.md b/doc/tsc-meetings/io.js/2015-04-15.md
deleted file mode 100644
index 931c568cef2ade..00000000000000
--- a/doc/tsc-meetings/io.js/2015-04-15.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# io.js TC Meeting 2015-04-15
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=lsRu_of0Xp8
-* **Google Plus Event page**: https://plus.google.com/events/cdinisa9mlisv81um91h71g3css
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1431
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1zlYeYS0LCyIjN4KsjXh9d46hNjp302M6L1K_-_OckzQ
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
-* [#1413](https://github.com/nodejs/io.js/issues/1413) combining TC and Node core call
-* [#1416](https://github.com/nodejs/io.js/issues/1416) io.js diff node.js foundation
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Chris (TC)
-* Domenic
-* Isaac (TC)
-* Jeremiah
-* Mikeal
-* Rod (TC)
-
-### Review of last meeting
-
-* [#1101](https://github.com/nodejs/io.js/pull/1101) http: allow HTTP to return an HTTPS server
-* [#1301](https://github.com/nodejs/io.js/pull/1301) Util(.is*) Deprecations
-* [Dev Policy](https://github.com/jasnell/dev-policy)
-* Isaac
-* [#1365](https://github.com/nodejs/io.js/issues/1356) `require('.')`
-
-
-### Quick stand-up
-
-* Ben: will be working less on io.js in the coming weeks
-* Bert: come clang hacking but not much else
-* Chris: some review/work on dev-policy
-* Domenic: did some review of the URL work
-* Isaac: on vacation and busy re fundraising, probably have less time for io.js into the future, will likely be moved out of the role
-* Jeremiah: some issue management, working with dev-policy
-* Mikeal: dev-policy and readable summary of the foundation documents
-* Rod: lots of build WG work including auto Jenkins runs, write-up on “the state of the build”
-
-## Minutes
-
-### [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
-
-* Ben: `next` branch should be ready to go though needs to be upgraded to 4.2.77.14, C++ changes are fairly minimal.
-* Discussed potentially bumping major:
-  - Mikeal: there was a meeting where it was generally agreed that an ABI change would warrant a version bump
-  - Rod & Isaac suggested that ABI changes shouldn’t bump major
-  - Discussion came around to most members agreeing that ABI change _should_ bump major. Rod voted 0 on this, everyone else apparently +1.
-  - Discussed semver-major changes including process.send() sync regressions, agreed that https://github.com/nodejs/io.js/milestones/2.0.0 represents the best info on what’s mergable
-* Discussed git, agreed that we should move back to master, Chris to handle git changes
-* Discussed RC build, could use nightly or next-nightly but officially link it off the website and maybe label it differently. Rod to figure this out.
-
-Actions:
- - Isaac to further review url changes, aside from his review and Domenic’s feedback in there it should be ready to merge
- - Chris to handle git and a move back to master
- - Ben to PR next branch back into master
- - Rod to figure out how to do and publish an RC build that’s not just “nightly-xxxxxxxxxxxxxx”
- - Chris will test packages against URL PR and write up results
-
-### [#1413](https://github.com/nodejs/io.js/issues/1413) combining TC and Node core call
-
-* Mikeal: last dev-policy call brought up the suggestion of combining TC calls for both projects, with an eye on merging it would be good to understand what both groups do. Single meeting for both would be good.
-* Discussed timing - we span more timezones than they do so our slot of 1pm PST makes more sense to get Rod and Fedor in at the same time. Could either be Tue or Wed UTC, they have a meeting the day before us.
-* No strong disagreement
-
-### [#1416](https://github.com/nodejs/io.js/issues/1416) io.js diff node.js foundation
-
-* Mikeal: Foundation doc is huge compared to ours and also contains some formalisation of our process that we just haven’t formalised yet. The diff contains a lot of those and some _actual_ changes too. Open for discussion amongst the community.
-* Rod: LTS discussion starting next week.
-
-## QA on Freenode/#io.js
-
-* Paused for input, nothing this week, will continue to offer a time for this.
-
-## Next meeting
-
-* FluentConf is on next week, Bert, Mikeal and Isaac will be at that. Agreed to go ahead and schedule one anyway.
-* 2015-04-22
diff --git a/doc/tsc-meetings/io.js/2015-04-22.md b/doc/tsc-meetings/io.js/2015-04-22.md
deleted file mode 100644
index f6715c7ad8cb0d..00000000000000
--- a/doc/tsc-meetings/io.js/2015-04-22.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# io.js TC Meeting 2015-04-22
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=s7LIMsTFaps
-* **Google Plus Event page**: https://plus.google.com/events/co7i7pv2a51270jat7jvkfcue64
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1502
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1G4aJ2OwiW2WphW7Vz2OW56VRot8xRBFitluKsuYPxk0
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* [#1130](https://github.com/nodejs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
-* [#1481](https://github.com/nodejs/io.js/issues/1481) Nominating @mikeal to the TC
-* [#1500](https://github.com/nodejs/io.js/issues/1500) Nominating Brian White @mscdex to the TC
-* [#1501](https://github.com/nodejs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC
-* [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
-* [#1413](https://github.com/nodejs/io.js/issues/1413) Combined node.js/io.js TC/Core Call
-* [#1416](https://github.com/nodejs/io.js/issues/1416) Diffing io.js and the Node.js Foundation
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Brian
-* Chris (TC)
-* Domenic
-* Fedor (TC)
-* Jeremiah
-* Shigeki
-* Trevor (TC)
-* Rod (TC)
-
-### Review of last meeting
-
-* [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
-* [#1413](https://github.com/nodejs/io.js/issues/1413) combining TC and Node core call
-* [#1416](https://github.com/nodejs/io.js/issues/1416) io.js diff node.js foundation
-
-### Quick stand-up
-
-* Ben: Not much, company stuff
-* Bert: Playing with clang and FFI, FluentConf
-* Brian: JS HTTP parser, optimising and messing with regex
-* Chris: URL changes, looking for breakage, checked on newSession/resumeSession, 1.8.x release
-* Domenic: Not much, some work on V8 extensions with possible news next weeks
-* Fedor: Looking at the “debugger is slow” in WebStorm issue, possible fix to V8 soon, working on using the OpenSSL 1.0.2 hello parser, HTTP parser patch review
-* Jeremiah: Not so much work on io.js, helped get 1.8.1 out and looking into moving npm out of our git repo.
-* Rod: CI cluster dramas around 1.8.x release, new Raspberry Pis
-* Shigeki: OpenSSL upgrade, ALPM enabling PR coming this week
-* Trevor: Has been testing re-implementing Buffers using ES6 and TypedArrays. Some trickiness but seems doable and with patches that avoid zero-filling, performant.
-
-## Minutes
-
-### [#1130](https://github.com/nodejs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
-
-Voted:
-
-* Ben: +1
-* Bert: +1
-* Chris: +1
-* Fedor: +1
-* Rod: +1
-* Trevor: +1
-
-**Action: Jeremiah Senkpiel is now a member of the io.js Technical Committee!**
-
-### [#1481](https://github.com/nodejs/io.js/issues/1481) Nominating @mikeal to the TC
-
-* Bert, Rod: Discussion regarding the potential consequences of expanding the TC and how that might work if a merger with node happens.
-
-Discussed consequences of expansion for merger and for the practicalities of meeting.
-
-### [#1500](https://github.com/nodejs/io.js/issues/1500) Nominating Brian White @mscdex to the TC
-
-_See above_
-
-### [#1501](https://github.com/nodejs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC
-
-_See above_
-
-### [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
-
-Rod: no formal “RC” builds yet but master is now going out on nightlies, they have a 2.0.0-pre version string now. Discussed whether we want formal RC builds or not. No strong opinions.
-
-Chris: `master` should be active for dev now, `next` should be used for ongoing V8 upgrade builds. Asked if the V8 changes were ready in `next` to merge - Ben confirmed - Chris to merge.
-
-Trevor: would like to get started on the upcoming V8 Buffer-related breakage and whether we should go to a 2.x branch and work on `master`.
-
-Chris: we should work on new stuff on `next` instead and leave `master` intact for now.
-
-Rod: status of URL parser changes?
-
-Chris: would like to test against candidate modules in npm that may cause breakage but otherwise seems good to merge.
-
-Domenic: would like there to be getters and setters for all data properties for completeness and future-proofing - still to be done
-
-Rod: any other breaking changes worth discussing?
-
-Ben: process.send() ready but not merged, any objections? - no objections.
-
-Chris: https://github.com/nodejs/io.js/milestones/2.0.0 new label “land-on-master” to indicate PRs that are still targeting the v1.x branch.
-
-Ben & Bert discussed Ben’s possible timers rewrite - Ben implemented a heap and red-black tree in JS, turned out to be a bit faster but not complete yet and Ben has been distracted on other projects. **
-
-### [#1413](https://github.com/nodejs/io.js/issues/1413) Combined node.js/io.js TC/Core Call
-
-Bert: probably not this week, intent is for next week.
-
-Jeremiah: there had been discussion around forming a convergence WG to handle some of this so as to not require everyone’s time except when necessary.
-
-### [#1416](https://github.com/nodejs/io.js/issues/1416) Diffing io.js and the Node.js Foundation
-
-_Nothing new to discuss_
-
-## Open QA on Freenode/#io.js
-
-Discussion on merger and how the possibility of merging may hold up progress in io.js. Generally agreed that we shouldn’t stop doing what we are doing, nor slow down progress. Bert would like us to be conscious of activities in the Foundation and how they may impact on what we are doing.
-
-Discussion about “production ready” - recommendation is to use latest, we follow semver so that should be enough information. Rod suggested not jumping straight on to 2.0 when it lands, just because of potential edge-cases around internal changes like the url parser.
-
-Discussed module integration testing to test certain modules that we would test with each release - Chris working on some tooling around being able to inspect what modules are impacted by changes - no specific work on actually running tests on modules but this could be a TODO for Build WG (Rod to make an issue for this).
-
-## Next meeting
-
-* 2015-04-29, UTC 20:00
diff --git a/doc/tsc-meetings/io.js/2015-04-29.md b/doc/tsc-meetings/io.js/2015-04-29.md
deleted file mode 100644
index 84b76a4ef4da68..00000000000000
--- a/doc/tsc-meetings/io.js/2015-04-29.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# io.js TC Meeting 2015-04-29
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=-e675TT4WEA
-* **Google Plus Event page**: https://plus.google.com/events/cei87pqnichrtt4qggbbo656bpk
-* **GitHub Issue**: https://github.com/nodejs/io.js/issues/1557
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/1C9nfm_5EhNz1jifITbtQcnGBX4R9vktoZ9KsFiCU7sQ
-
-## Agenda
-
-Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
-
-* Release Proposal: v2.0.0 [#1532](https://github.com/nodejs/io.js/pull/1532)
-* Forward-port from v1.x [#1559](https://github.com/nodejs/io.js/pull/1559)
-* Convergence plan (https://github.com/jasnell/dev-policy/pull/66)
-* Combined node.js/io.js TC/core call about convergence doc [#1413](https://github.com/nodejs/io.js/issues/1413)
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Brian
-* Chris (TC)
-* Domenic
-* Fedor (TC)
-* Jeremiah
-* Shigeki
-* Trevor (TC)
-
-
-### Review of last meeting
-
-* [#1130](https://github.com/nodejs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
-* [#1481](https://github.com/nodejs/io.js/issues/1481) Nominating @mikeal to the TC
-* [#1500](https://github.com/nodejs/io.js/issues/1500) Nominating Brian White @mscdex to the TC
-* [#1501](https://github.com/nodejs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC
-* [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
-* [#1413](https://github.com/nodejs/io.js/issues/1413) Combined node.js/io.js TC/Core Call
-* [#1416](https://github.com/nodejs/io.js/issues/1416) Diffing io.js and the Node.js Foundation
-
-
-### Quick stand-up
-
-* Ben: nothing
-* Bert: nothing
-* Brian: finished optimizations for JS HTTP parser, posted a few questions; other miscellaneous improvements in core HTTP.
-* Chris: upgraded V8 and documented the process; also did some work on the REPL so that classes (and let/const) work
-* Domenic: PR reviews for v2.0.0, starting on V8 extension work to improve startup time
-* Fedor: worked on fixing some TLS memory issues, so far appears to be a large improvement in memory usage.
-* Jeremiah: issue management; discussions on moving npm out of the repo, which seems to have converged toward a helper tool instead of moving it out of the repo
-* Mikeal: connection too bad to stand up.
-* Shigeki: working on SSL issues; root cert updates. Chrome and Firefox do whitelist of CNNIC cert hashes.
-* Trevor: looking at bugs, streams compliance
-
-## Minutes
-
-### Release Proposal: v2.0.0 [#1532](https://github.com/nodejs/io.js/pull/1532)
-
-* Domenic:
-  - v8 changes merged
-  - worried that we’re getting into a bad cycle of “wait a few more days” for things to land
-  - process.send
-  - open an rc, add to website for a few days, ship by friday
-* Bert/Ben:
-  - talk of process.send
-    - Ben: should not hold up release, windows tests break right now
-    - less of a regression than a change
-* Domenic:
-  - these releases are a train
-  - don’t hold up the train for features
-    - make sure it’s ready for 3
-* url updates from petka: might be ready
-  - ci run passes on all platforms but arm7
-* Domenic recalls in the runup to 1.0 – “nobody tests rc's” was the consensus
-
-Chris, Trevor: discussion about how the `master` and `next` branches are used.
-
-* process.send changes will slip for v2.0
-* waiting for Petka’s comment and review on url changes (https://github.com/nodejs/io.js/pull/1561)
-* release 2.x asap (friday)
-
-After the release:
-
-* the master branch will contain version 2.x.
-* api-breaking changes will land on the ‘next’ branch alongside v8 upgrades. master will be merged into next regularly
-* fixes are backported to the maintenance (v1.x) branch
-
-### Forward-port from v1.x [#1559](https://github.com/nodejs/io.js/pull/1559)
-
-Discussed current plan for backporting patches to maintenance patches.
-
-* Consensus that we should give the “land in master and backport” plan a go and see how it works out.
-
-### Convergence plan (https://github.com/jasnell/dev-policy/pull/66)
-
-### Combined node.js/io.js TC/core call [#1413](https://github.com/nodejs/io.js/issues/1413)
-
-## Next meeting
-
-* April 6th
diff --git a/doc/tsc-meetings/io.js/2015-05-13.md b/doc/tsc-meetings/io.js/2015-05-13.md
deleted file mode 100644
index 3e18071ac7bbda..00000000000000
--- a/doc/tsc-meetings/io.js/2015-05-13.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# io.js TC Meeting 2015-05-13
-
-## Links
-
-* **Public YouTube feed**: http://www.youtube.com/watch?v=UbYiFLf7MpU
-* **Google Plus Event page**: https://plus.google.com/events/cu606mlllfehl11u8kcj7q2407k
-* **GitHub Issue**: https://github.com/iojs/io.js/issues/1689
-* **Original Minutes Google Doc**: https://docs.google.com/document/d/15Y_kJlYm-8cIf-alniaqUWMM-TjGISCqLf40G3pv4sM
-
-## Agenda
-
-Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
-
-* V8 4.4 to remove indexed properties via external data [#1451](https://github.com/iojs/io.js/issues/1451)
-* NODE_PATH deprecation [#1627](https://github.com/iojs/io.js/issues/1627)
-* Join the Node Foundation? [#1664](https://github.com/iojs/io.js/issues/1664)
-* Put `*Sync` methods behind a flag in some future major version [#1665](https://github.com/iojs/io.js/issues/1665)
-* TC Nominations
- - Shigeki Ohtsu @shigeki [#1501](https://github.com/iojs/io.js/issues/1501)
- - Brian White @mscdex [#1500](https://github.com/iojs/io.js/issues/1500)
- - @mikeal [#1481](https://github.com/iojs/io.js/issues/1481)
-* Public QA via #io.js channel on Freenode
-
-### Present
-
-* Ben (TC)
-* Bert (TC)
-* Brian
-* Chris (TC)
-* Domenic
-* Jeremiah (TC)
-* Mikeal
-* Rod (TC)
-* Shigeki
-* Trevor (TC)
-
-### Quick stand-up
-
-* Ben: Upgraded V8, upgraded cares for the first time in 2 years, reviewed pull requests
-* Bert: Played Keen, not much io.js stuff; last Monday met with James, Mikeal about convergence
-* Brian: looking over potential optimizations in the JS codebase, started working on a DNS resolver as a potential replacement for cares
-* Chris: fixing race conditions in the REPL, poking at adding Ctrl-R history searching to readline
-* Domenic: working with V8 team in Munich, working on v8-extras feature, putting large portions of things into snapshot to speed up startup and other things: https://groups.google.com/forum/#!topic/v8-users/D6FmTwlvCgk
-* Jeremiah: issue management, working on tooling for automatic dependency upgrades, see [#1688](https://github.com/iojs/io.js/pull/1688)
-* Mikeal: Foundation stuff, getting ducks in a row
-* Shigeki: holiday in JP, fix TLS bug involving edge-case, needs review
-* Trevor: Helped with re-enabling snapshots, looking at changing the Buffer APIs to use TypedArrays
-* Rod: Been doing lots of little things, working on the CI and build cluster
-
-### Review of last meeting
-
-* Release Proposal: v2.0.0 [#1532](https://github.com/iojs/io.js/pull/1532)
-* Forward-port from v1.x [#1559](https://github.com/iojs/io.js/pull/1559)
-* Convergence plan (https://github.com/jasnell/dev-policy/pull/66)
-* Combined node.js/io.js TC/core call [#1413](https://github.com/iojs/io.js/issues/1413)
-
-## Minutes
-
-* Discussed creating a more formal deprecation policy, chris to open an issue.
-
-### V8 4.4 to remove indexed properties via external data [#1451](https://github.com/iojs/io.js/issues/1451)
-
-* ‘smalloc’ has to go away when we land this V8, thankfully it’s not been around for long but this is a forced deprecation & removal.
-* currently usage of ‘smalloc’ gives a deprecation warning, as of v2.0.0
-* @jeisinger has been backporting some APIs needed for Buffer, NAN will have to catch up but @kkoopa is involved
-* Domenic: V8 4.3 will be next week, 7 weeks from now will be 4.4 (~1 week behind Chrome release)
-* Trevor: no major problems with JS API, most problems will be in the C++ API, should be able to shim to ease it
-
-### NODE_PATH deprecation [#1627](https://github.com/iojs/io.js/issues/1627)
-
-* Jeremiah: there was a suggestion to deprecate NODE_PATH entirely, debate is over deprecation or not, lots of people appear to be finding novel uses of it.
-* Domenic: maybe we should document it
-* Chris: it is documented, Googling shows that it’s been ingrained into the Node background, there’s lots of info out there about how it’s used
-* Domenic: https://iojs.org/api/modules.html#modules_loading_from_the_global_folders
-* Mikeal: maybe write docs about how it exists but you shouldn’t use it
-
-**Action: Mikeal to open an issue to change the docs to talk about how you probably shouldn’t use them** (note: it might be as simple as styling!)
-
-### Join the Node Foundation? [#1664](https://github.com/iojs/io.js/issues/1664)
-
-* Mikeal: Mostly a consensus in the issue about joining
-* Mikeal: Next step is to move the “iojs” org to “nodejs”, then move the convergence repo in to be “node” to be the new tip: https://github.com/jasnell/node.js-convergence
-
-Lots of discussions about process and what needs to happen & when, Mikeal pushing for a vote to get the org moved.
-
-**Voting Question**: The io.js TC agrees to:
- 1. have the io.js project join the Node Foundation
- 2. rename the entire “iojs” GitHub org to be “nodejs”
- 3. invite the the current Node.js TC on to our TC to form the basis of a Node Foundation TSC under the policies of the Node Foundation
- 4. moving the io.js Working Groups to be under the Node Foundation
-
-**Voting Results**:
-
-* Fedor: 0
-* Ben: +1
-* Bert: +1
-* Chris: +1
-* Jeremiah: +1
-* Trevor: +1
-* Rod: +1
-
-Action: Mikeal to make the move happen in a coordinated way so we get redirects and whatnot
-
-### Put `*Sync` methods behind a flag in some future major version [#1665](https://github.com/iojs/io.js/issues/1665)
-
-* Ben: some people feel that `fs.*Sync()` methods are harmful and would like to see them go away and be behind a flag
-* Bert: don’t agree with deprecating but agree with a flag
-* Rod: agree with Bert, but would like to see doc changes
-* Trevor: working on a flag to print a stack trace
-
-### TC Nominations
-
-* Shigeki Ohtsu @shigeki [#1501](https://github.com/iojs/io.js/issues/1501)
-* Brian White @mscdex [#1500](https://github.com/iojs/io.js/issues/1500)
-* @mikeal [#1481](https://github.com/iojs/io.js/issues/1481)
-
-* Mikeal: joining
-* Rod: timing is awkward with convergence but I’d like to make sure that Shigeki and Brian have a path to join the TC and not have that delayed too much
-
-### Public QA via #io.js channel on Freenode
-
-* `<therebelrobot> After the converged release, will io.js/node still be semver? for example, the history would be node 0.10, 0.12, iojs 1.x 2.x then the converged one would be node 3.x?`
- - Mikeal: the dev policy says so, there’s nobody advocating not to
-* `<evanlucas> Are there plans to symlink node to iojs in the installers after the first converged release?`
- - Bert: undecided. We should figure out a way to allow users to “node lts” and “node bleeding edge” side by side.
- - Mikeal: part of the above is covered by a thread in NG about localizing the node installation to global modules.
-* `<phpnode> will members of the core team be able to revive io.js if they disagree with the direction of the project in future`
- - (Group) Yes
-* `<skinan5> any plans for nan resolution?`
- - Rod: it’s just a header file and you need it for older versions of Node so it doesn’t make sense to _not_ use it from npm
- - Ben: current NAN isn’t suitable for bringing in
- - Trevor: would support bringing in something that would provide proper ABI support
- - Action: Trevor to open an issue on the NAN repo to talk about a stable C++ layer
-
-## Next meeting
-
-* May 20th, invite joyent/node TC members, figure out who that is and if this timeslot works for them when we have a combined call tomorrow (14th)
diff --git a/lib/_debugger.js b/lib/_debugger.js
index 6d1043dda9d9d3..2ccbc5e6607379 100644
--- a/lib/_debugger.js
+++ b/lib/_debugger.js
@@ -186,7 +186,7 @@ Client.prototype._addScript = function(desc) {
   this.scripts[desc.id] = desc;
   if (desc.name) {
     desc.isNative = (desc.name.replace('.js', '') in natives) ||
-                    desc.name == 'node.js';
+                    desc.name === 'node.js';
   }
 };
 
@@ -201,7 +201,7 @@ Client.prototype._onResponse = function(res) {
   var index = -1;
 
   this._reqCallbacks.some(function(fn, i) {
-    if (fn.request_seq == res.body.request_seq) {
+    if (fn.request_seq === res.body.request_seq) {
       cb = fn;
       index = i;
       return true;
@@ -211,25 +211,25 @@ Client.prototype._onResponse = function(res) {
   var self = this;
   var handled = false;
 
-  if (res.headers.Type == 'connect') {
+  if (res.headers.Type === 'connect') {
     // Request a list of scripts for our own storage.
     self.reqScripts();
     self.emit('ready');
     handled = true;
 
-  } else if (res.body && res.body.event == 'break') {
+  } else if (res.body && res.body.event === 'break') {
     this.emit('break', res.body);
     handled = true;
 
-  } else if (res.body && res.body.event == 'exception') {
+  } else if (res.body && res.body.event === 'exception') {
     this.emit('exception', res.body);
     handled = true;
 
-  } else if (res.body && res.body.event == 'afterCompile') {
+  } else if (res.body && res.body.event === 'afterCompile') {
     this._addHandle(res.body.body.script);
     handled = true;
 
-  } else if (res.body && res.body.event == 'scriptCollected') {
+  } else if (res.body && res.body.event === 'scriptCollected') {
     // ???
     this._removeScript(res.body.body.script);
     handled = true;
@@ -327,7 +327,7 @@ Client.prototype.reqScopes = function(cb) {
 Client.prototype.reqEval = function(expression, cb) {
   var self = this;
 
-  if (this.currentFrame == NO_FRAME) {
+  if (this.currentFrame === NO_FRAME) {
     // Only need to eval in global scope.
     this.reqFrameEval(expression, NO_FRAME, cb);
     return;
@@ -357,7 +357,7 @@ Client.prototype.reqEval = function(expression, cb) {
 
 // Finds the first scope in the array in which the expression evals.
 Client.prototype._reqFramesEval = function(expression, evalFrames, cb) {
-  if (evalFrames.length == 0) {
+  if (evalFrames.length === 0) {
     // Just eval in global scope.
     this.reqFrameEval(expression, NO_FRAME, cb);
     return;
@@ -381,7 +381,7 @@ Client.prototype.reqFrameEval = function(expression, frame, cb) {
     arguments: { expression: expression }
   };
 
-  if (frame == NO_FRAME) {
+  if (frame === NO_FRAME) {
     req.arguments.global = true;
   } else {
     req.arguments.frame = frame;
@@ -528,9 +528,9 @@ Client.prototype.mirrorObject = function(handle, depth, cb) {
       var mirror;
       var waiting = 1;
 
-      if (handle.className == 'Array') {
+      if (handle.className === 'Array') {
         mirror = [];
-      } else if (handle.className == 'Date') {
+      } else if (handle.className === 'Date') {
         mirror = new Date(handle.value);
       } else {
         mirror = {};
@@ -770,10 +770,20 @@ function Interface(stdin, stdout, args) {
   process.once('SIGHUP', process.exit.bind(process, 0));
 
   var proto = Interface.prototype;
-  const ignored = ['pause', 'resume', 'exitRepl', 'handleBreak',
-                   'requireConnection', 'killChild', 'trySpawn',
-                   'controlEval', 'debugEval', 'print', 'childPrint',
-                   'clearline'];
+  const ignored = [
+    'pause',
+    'resume',
+    'exitRepl',
+    'handleBreak',
+    'requireConnection',
+    'killChild',
+    'trySpawn',
+    'controlEval',
+    'debugEval',
+    'print',
+    'childPrint',
+    'clearline'
+  ];
   const shortcut = {
     'run': 'r',
     'cont': 'c',
@@ -1093,14 +1103,14 @@ Interface.prototype.list = function(delta) {
       var lineno = res.fromLine + i + 1;
       if (lineno < from || lineno > to) continue;
 
-      const current = lineno == 1 + client.currentSourceLine;
+      const current = lineno === 1 + client.currentSourceLine;
       const breakpoint = client.breakpoints.some(function(bp) {
         return (bp.scriptReq === client.currentScript ||
                 bp.script === client.currentScript) &&
-                bp.line == lineno;
+                bp.line === lineno;
       });
 
-      if (lineno == 1) {
+      if (lineno === 1) {
         // The first line needs to have the module wrapper filtered out of
         // it.
         var wrapper = Module.wrapper[0];
@@ -1147,7 +1157,7 @@ Interface.prototype.backtrace = function() {
       return;
     }
 
-    if (bt.totalFrames == 0) {
+    if (bt.totalFrames === 0) {
       self.print('(empty stack)');
     } else {
       const trace = [];
@@ -1189,10 +1199,10 @@ Interface.prototype.scripts = function() {
     var script = client.scripts[id];
     if (script !== null && typeof script === 'object' && script.name) {
       if (displayNatives ||
-          script.name == client.currentScript ||
+          script.name === client.currentScript ||
           !script.isNative) {
         scripts.push(
-            (script.name == client.currentScript ? '* ' : '  ') +
+            (script.name === client.currentScript ? '* ' : '  ') +
             id + ': ' +
             path.basename(script.name)
         );
diff --git a/lib/_tls_wrap.js b/lib/_tls_wrap.js
index 7efe42ab46ca22..056499b723f0d0 100644
--- a/lib/_tls_wrap.js
+++ b/lib/_tls_wrap.js
@@ -916,8 +916,8 @@ Server.prototype.addContext = function(servername, context) {
   }
 
   var re = new RegExp('^' +
-                      servername.replace(/([\.^$+?\-\\[\]{}])/g, '\\$1')
-                                .replace(/\*/g, '[^\.]*') +
+                      servername.replace(/([.^$+?\-\\[\]{}])/g, '\\$1')
+                                .replace(/\*/g, '[^.]*') +
                       '$');
   this._contexts.push([re, tls.createSecureContext(context).context]);
 };
diff --git a/lib/assert.js b/lib/assert.js
index 233ca4ddc86fcc..469128f39b4911 100644
--- a/lib/assert.js
+++ b/lib/assert.js
@@ -176,8 +176,13 @@ function _deepEqual(actual, expected, strict, memos) {
              pToString(actual) === pToString(expected) &&
              !(actual instanceof Float32Array ||
                actual instanceof Float64Array)) {
-    return compare(new Buffer(actual.buffer),
-                   new Buffer(expected.buffer)) === 0;
+    return compare(
+      new Buffer(actual.buffer).slice(actual.byteOffset,
+                                      actual.byteOffset +
+                                      actual.byteLength),
+      new Buffer(expected.buffer).slice(expected.byteOffset,
+                                        expected.byteOffset +
+                                        expected.byteLength)) === 0;
 
   // 7.5 For all other Object pairs, including Array objects, equivalence is
   // determined by having the same number of owned properties (as verified
diff --git a/lib/internal/repl.js b/lib/internal/repl.js
index cea681f5837494..6cb3fffd85f5e0 100644
--- a/lib/internal/repl.js
+++ b/lib/internal/repl.js
@@ -5,7 +5,8 @@ const REPL = require('repl');
 const path = require('path');
 const fs = require('fs');
 const os = require('os');
-const debug = require('util').debuglog('repl');
+const util = require('util');
+const debug = util.debuglog('repl');
 
 module.exports = Object.create(REPL);
 module.exports.createInternalRepl = createRepl;
@@ -19,11 +20,11 @@ function createRepl(env, opts, cb) {
     cb = opts;
     opts = null;
   }
-  opts = opts || {
+  opts = util._extend({
     ignoreUndefined: false,
     terminal: process.stdout.isTTY,
     useGlobal: true
-  };
+  }, opts);
 
   if (parseInt(env.NODE_NO_READLINE)) {
     opts.terminal = false;
diff --git a/lib/repl.js b/lib/repl.js
index 284c4a381d0a3b..512ac39cea31a6 100644
--- a/lib/repl.js
+++ b/lib/repl.js
@@ -39,12 +39,12 @@ const parentModule = module;
 const replMap = new WeakMap();
 
 const GLOBAL_OBJECT_PROPERTIES = ['NaN', 'Infinity', 'undefined',
-    'eval', 'parseInt', 'parseFloat', 'isNaN', 'isFinite', 'decodeURI',
-    'decodeURIComponent', 'encodeURI', 'encodeURIComponent',
-    'Object', 'Function', 'Array', 'String', 'Boolean', 'Number',
-    'Date', 'RegExp', 'Error', 'EvalError', 'RangeError',
-    'ReferenceError', 'SyntaxError', 'TypeError', 'URIError',
-    'Math', 'JSON'];
+  'eval', 'parseInt', 'parseFloat', 'isNaN', 'isFinite', 'decodeURI',
+  'decodeURIComponent', 'encodeURI', 'encodeURIComponent',
+  'Object', 'Function', 'Array', 'String', 'Boolean', 'Number',
+  'Date', 'RegExp', 'Error', 'EvalError', 'RangeError',
+  'ReferenceError', 'SyntaxError', 'TypeError', 'URIError',
+  'Math', 'JSON'];
 const GLOBAL_OBJECT_PROPERTY_MAP = {};
 GLOBAL_OBJECT_PROPERTIES.forEach((p) => GLOBAL_OBJECT_PROPERTY_MAP[p] = p);
 
@@ -622,7 +622,7 @@ ArrayStream.prototype.writable = true;
 ArrayStream.prototype.resume = function() {};
 ArrayStream.prototype.write = function() {};
 
-const requireRE = /\brequire\s*\(['"](([\w\.\/-]+\/)?([\w\.\/-]*))/;
+const requireRE = /\brequire\s*\(['"](([\w./-]+\/)?([\w./-]*))/;
 const simpleExpressionRE =
     /(([a-zA-Z_$](?:\w|\$)*)\.)*([a-zA-Z_$](?:\w|\$)*)\.?$/;
 
@@ -870,7 +870,7 @@ REPLServer.prototype.complete = function(line, callback) {
       var newCompletionGroups = [];
       for (i = 0; i < completionGroups.length; i++) {
         group = completionGroups[i].filter(function(elem) {
-          return elem.indexOf(filter) == 0;
+          return elem.indexOf(filter) === 0;
         });
         if (group.length) {
           newCompletionGroups.push(group);
@@ -1124,8 +1124,8 @@ function regexpEscape(s) {
  * @return {String} The converted command.
  */
 REPLServer.prototype.convertToContext = function(cmd) {
-  const scopeVar = /^\s*var\s*([_\w\$]+)(.*)$/m;
-  const scopeFunc = /^\s*function\s*([_\w\$]+)/;
+  const scopeVar = /^\s*var\s*([\w$]+)(.*)$/m;
+  const scopeFunc = /^\s*function\s*([\w$]+)/;
   var matches;
 
   // Replaces: var foo = "bar";  with: self.context.foo = bar;
diff --git a/lib/timers.js b/lib/timers.js
index 2ff3381c857bbb..696df5a7ebb3e7 100644
--- a/lib/timers.js
+++ b/lib/timers.js
@@ -272,14 +272,18 @@ exports.setInterval = function(callback, repeat) {
   return timer;
 
   function wrapper() {
+    // If _repeat was overriden we are effectively canceled. Bail.
+    if (typeof timer._repeat !== 'function')
+      return;
+
     timer._repeat();
 
-    // Timer might be closed - no point in restarting it
-    if (!timer._repeat)
+    // Do not re-arm unenroll'd or closed timers.
+    if (timer._idleTimeout === -1)
       return;
 
     // If timer is unref'd (or was - it's permanently removed from the list.)
-    if (this._handle) {
+    if (this._handle && timer instanceof Timeout) {
       this._handle.start(repeat, 0);
     } else {
       timer._idleTimeout = repeat;
@@ -309,9 +313,17 @@ const Timeout = function(after) {
 
 
 function unrefdHandle() {
-  this.owner._onTimeout();
-  if (!this.owner._repeat)
+  // Don't attempt to call the callback if it is not a function.
+  if (typeof this.owner._onTimeout === 'function') {
+    this.owner._onTimeout();
+  }
+
+  // Make sure we clean up if the callback is no longer a function
+  // even if the timer is an interval.
+  if (!this.owner._repeat
+      || typeof this.owner._onTimeout !== 'function') {
     this.owner.close();
+  }
 }
 
 
@@ -351,6 +363,7 @@ Timeout.prototype.ref = function() {
 Timeout.prototype.close = function() {
   this._onTimeout = null;
   if (this._handle) {
+    this._idleTimeout = -1;
     this._handle[kOnTimeout] = null;
     this._handle.close();
   } else {
diff --git a/node.gyp b/node.gyp
index 26a9f615d028aa..e6e170d1d74487 100644
--- a/node.gyp
+++ b/node.gyp
@@ -506,11 +506,22 @@
             'NODE_PLATFORM="sunos"',
           ],
         }],
-        [ '(OS=="freebsd" or OS=="linux") and node_shared=="false"', {
+        [ '(OS=="freebsd" or OS=="linux") and node_shared=="false" and coverage=="false"', {
           'ldflags': [ '-Wl,-z,noexecstack',
                        '-Wl,--whole-archive <(V8_BASE)',
                        '-Wl,--no-whole-archive' ]
         }],
+        [ '(OS=="freebsd" or OS=="linux") and node_shared=="false" and coverage=="true"', {
+          'ldflags': [ '-Wl,-z,noexecstack',
+                       '-Wl,--whole-archive <(V8_BASE)',
+                       '-Wl,--no-whole-archive',
+                       '--coverage',
+                       '-g',
+                       '-O0' ],
+           'cflags': [ '--coverage',
+                       '-g',
+                       '-O0' ]
+        }],
         [ 'OS=="sunos"', {
           'ldflags': [ '-Wl,-M,/usr/lib/ld/map.noexstk' ],
         }],
@@ -811,7 +822,15 @@
       'targets': [
         {
           'target_name': 'node',
-          'type': 'executable',
+          'conditions': [
+            ['node_shared=="true"', {
+              'type': 'shared_library',
+              'ldflags': ['--shared'],
+              'product_extension': '<(shlib_suffix)',
+            }, {
+              'type': 'executable',
+            }],
+          ],
           'dependencies': ['<(node_core_target_name)', 'node_exp'],
 
           'include_dirs': [
diff --git a/src/async-wrap-inl.h b/src/async-wrap-inl.h
index 9f520de4429622..f8bfc2362dbe21 100644
--- a/src/async-wrap-inl.h
+++ b/src/async-wrap-inl.h
@@ -13,77 +13,6 @@
 
 namespace node {
 
-inline AsyncWrap::AsyncWrap(Environment* env,
-                            v8::Local<v8::Object> object,
-                            ProviderType provider,
-                            AsyncWrap* parent)
-    : BaseObject(env, object), bits_(static_cast<uint32_t>(provider) << 1),
-      uid_(env->get_async_wrap_uid()) {
-  CHECK_NE(provider, PROVIDER_NONE);
-  CHECK_GE(object->InternalFieldCount(), 1);
-
-  // Shift provider value over to prevent id collision.
-  persistent().SetWrapperClassId(NODE_ASYNC_ID_OFFSET + provider);
-
-  v8::Local<v8::Function> init_fn = env->async_hooks_init_function();
-
-  // No init callback exists, no reason to go on.
-  if (init_fn.IsEmpty())
-    return;
-
-  // If async wrap callbacks are disabled and no parent was passed that has
-  // run the init callback then return.
-  if (!env->async_wrap_callbacks_enabled() &&
-      (parent == nullptr || !parent->ran_init_callback()))
-    return;
-
-  v8::HandleScope scope(env->isolate());
-
-  v8::Local<v8::Value> argv[] = {
-    v8::Number::New(env->isolate(), get_uid()),
-    v8::Int32::New(env->isolate(), provider),
-    Null(env->isolate()),
-    Null(env->isolate())
-  };
-
-  if (parent != nullptr) {
-    argv[2] = v8::Number::New(env->isolate(), parent->get_uid());
-    argv[3] = parent->object();
-  }
-
-  v8::TryCatch try_catch(env->isolate());
-
-  v8::MaybeLocal<v8::Value> ret =
-      init_fn->Call(env->context(), object, arraysize(argv), argv);
-
-  if (ret.IsEmpty()) {
-    ClearFatalExceptionHandlers(env);
-    FatalException(env->isolate(), try_catch);
-  }
-
-  bits_ |= 1;  // ran_init_callback() is true now.
-}
-
-
-inline AsyncWrap::~AsyncWrap() {
-  if (!ran_init_callback())
-    return;
-
-  v8::Local<v8::Function> fn = env()->async_hooks_destroy_function();
-  if (!fn.IsEmpty()) {
-    v8::HandleScope scope(env()->isolate());
-    v8::Local<v8::Value> uid = v8::Number::New(env()->isolate(), get_uid());
-    v8::TryCatch try_catch(env()->isolate());
-    v8::MaybeLocal<v8::Value> ret =
-        fn->Call(env()->context(), v8::Null(env()->isolate()), 1, &uid);
-    if (ret.IsEmpty()) {
-      ClearFatalExceptionHandlers(env());
-      FatalException(env()->isolate(), try_catch);
-    }
-  }
-}
-
-
 inline bool AsyncWrap::ran_init_callback() const {
   return static_cast<bool>(bits_ & 1);
 }
diff --git a/src/async-wrap.cc b/src/async-wrap.cc
index 1a4ef67b6896d6..1a0976b91b45c7 100644
--- a/src/async-wrap.cc
+++ b/src/async-wrap.cc
@@ -5,6 +5,7 @@
 #include "util.h"
 #include "util-inl.h"
 
+#include "uv.h"
 #include "v8.h"
 #include "v8-profiler.h"
 
@@ -15,6 +16,7 @@ using v8::Function;
 using v8::FunctionCallbackInfo;
 using v8::HandleScope;
 using v8::HeapProfiler;
+using v8::Int32;
 using v8::Integer;
 using v8::Isolate;
 using v8::Local;
@@ -156,9 +158,9 @@ static void SetupHooks(const FunctionCallbackInfo<Value>& args) {
 }
 
 
-static void Initialize(Local<Object> target,
-                Local<Value> unused,
-                Local<Context> context) {
+void AsyncWrap::Initialize(Local<Object> target,
+                           Local<Value> unused,
+                           Local<Context> context) {
   Environment* env = Environment::GetCurrent(context);
   Isolate* isolate = env->isolate();
   HandleScope scope(isolate);
@@ -182,6 +184,38 @@ static void Initialize(Local<Object> target,
 }
 
 
+void AsyncWrap::DestroyIdsCb(uv_idle_t* handle) {
+  uv_idle_stop(handle);
+
+  Environment* env = Environment::from_destroy_ids_idle_handle(handle);
+  // None of the V8 calls done outside the HandleScope leak a handle. If this
+  // changes in the future then the SealHandleScope wrapping the uv_run()
+  // will catch this can cause the process to abort.
+  HandleScope handle_scope(env->isolate());
+  Context::Scope context_scope(env->context());
+  Local<Function> fn = env->async_hooks_destroy_function();
+
+  if (fn.IsEmpty())
+    return env->destroy_ids_list()->clear();
+
+  TryCatch try_catch(env->isolate());
+
+  for (auto current_id : *env->destroy_ids_list()) {
+    // Want each callback to be cleaned up after itself, instead of cleaning
+    // them all up after the while() loop completes.
+    HandleScope scope(env->isolate());
+    Local<Value> argv = Number::New(env->isolate(), current_id);
+    MaybeLocal<Value> ret = fn->Call(
+        env->context(), Undefined(env->isolate()), 1, &argv);
+
+    if (ret.IsEmpty()) {
+      ClearFatalExceptionHandlers(env);
+      FatalException(env->isolate(), try_catch);
+    }
+  }
+}
+
+
 void LoadAsyncWrapperInfo(Environment* env) {
   HeapProfiler* heap_profiler = env->isolate()->GetHeapProfiler();
 #define V(PROVIDER)                                                           \
@@ -192,6 +226,69 @@ void LoadAsyncWrapperInfo(Environment* env) {
 }
 
 
+AsyncWrap::AsyncWrap(Environment* env,
+                     Local<Object> object,
+                     ProviderType provider,
+                     AsyncWrap* parent)
+    : BaseObject(env, object), bits_(static_cast<uint32_t>(provider) << 1),
+      uid_(env->get_async_wrap_uid()) {
+  CHECK_NE(provider, PROVIDER_NONE);
+  CHECK_GE(object->InternalFieldCount(), 1);
+
+  // Shift provider value over to prevent id collision.
+  persistent().SetWrapperClassId(NODE_ASYNC_ID_OFFSET + provider);
+
+  Local<Function> init_fn = env->async_hooks_init_function();
+
+  // No init callback exists, no reason to go on.
+  if (init_fn.IsEmpty())
+    return;
+
+  // If async wrap callbacks are disabled and no parent was passed that has
+  // run the init callback then return.
+  if (!env->async_wrap_callbacks_enabled() &&
+      (parent == nullptr || !parent->ran_init_callback()))
+    return;
+
+  HandleScope scope(env->isolate());
+
+  Local<Value> argv[] = {
+    Number::New(env->isolate(), get_uid()),
+    Int32::New(env->isolate(), provider),
+    Null(env->isolate()),
+    Null(env->isolate())
+  };
+
+  if (parent != nullptr) {
+    argv[2] = Number::New(env->isolate(), parent->get_uid());
+    argv[3] = parent->object();
+  }
+
+  TryCatch try_catch(env->isolate());
+
+  MaybeLocal<Value> ret =
+      init_fn->Call(env->context(), object, arraysize(argv), argv);
+
+  if (ret.IsEmpty()) {
+    ClearFatalExceptionHandlers(env);
+    FatalException(env->isolate(), try_catch);
+  }
+
+  bits_ |= 1;  // ran_init_callback() is true now.
+}
+
+
+AsyncWrap::~AsyncWrap() {
+  if (!ran_init_callback())
+    return;
+
+  if (env()->destroy_ids_list()->empty())
+    uv_idle_start(env()->destroy_ids_idle_handle(), DestroyIdsCb);
+
+  env()->destroy_ids_list()->push_back(get_uid());
+}
+
+
 Local<Value> AsyncWrap::MakeCallback(const Local<Function> cb,
                                      int argc,
                                      Local<Value>* argv) {
@@ -291,4 +388,4 @@ Local<Value> AsyncWrap::MakeCallback(const Local<Function> cb,
 
 }  // namespace node
 
-NODE_MODULE_CONTEXT_AWARE_BUILTIN(async_wrap, node::Initialize)
+NODE_MODULE_CONTEXT_AWARE_BUILTIN(async_wrap, node::AsyncWrap::Initialize)
diff --git a/src/async-wrap.h b/src/async-wrap.h
index cb0c9e211a8923..4e016335a086bf 100644
--- a/src/async-wrap.h
+++ b/src/async-wrap.h
@@ -2,6 +2,7 @@
 #define SRC_ASYNC_WRAP_H_
 
 #include "base-object.h"
+#include "uv.h"
 #include "v8.h"
 
 #include <stdint.h>
@@ -47,12 +48,18 @@ class AsyncWrap : public BaseObject {
 #undef V
   };
 
-  inline AsyncWrap(Environment* env,
-                   v8::Local<v8::Object> object,
-                   ProviderType provider,
-                   AsyncWrap* parent = nullptr);
+  AsyncWrap(Environment* env,
+            v8::Local<v8::Object> object,
+            ProviderType provider,
+            AsyncWrap* parent = nullptr);
 
-  inline virtual ~AsyncWrap();
+  virtual ~AsyncWrap();
+
+  static void Initialize(v8::Local<v8::Object> target,
+                         v8::Local<v8::Value> unused,
+                         v8::Local<v8::Context> context);
+
+  static void DestroyIdsCb(uv_idle_t* handle);
 
   inline ProviderType provider_type() const;
 
diff --git a/src/env-inl.h b/src/env-inl.h
index 0a4ce55b3bc4ae..44d289bee91418 100644
--- a/src/env-inl.h
+++ b/src/env-inl.h
@@ -227,6 +227,8 @@ inline Environment::Environment(v8::Local<v8::Context> context,
 
   RB_INIT(&cares_task_list_);
   handle_cleanup_waiting_ = 0;
+
+  destroy_ids_list_.reserve(512);
 }
 
 inline Environment::~Environment() {
@@ -286,6 +288,15 @@ inline uv_idle_t* Environment::immediate_idle_handle() {
   return &immediate_idle_handle_;
 }
 
+inline Environment* Environment::from_destroy_ids_idle_handle(
+    uv_idle_t* handle) {
+  return ContainerOf(&Environment::destroy_ids_idle_handle_, handle);
+}
+
+inline uv_idle_t* Environment::destroy_ids_idle_handle() {
+  return &destroy_ids_idle_handle_;
+}
+
 inline Environment* Environment::from_idle_prepare_handle(
     uv_prepare_t* handle) {
   return ContainerOf(&Environment::idle_prepare_handle_, handle);
@@ -362,6 +373,10 @@ inline int64_t Environment::get_async_wrap_uid() {
   return ++async_wrap_uid_;
 }
 
+inline std::vector<int64_t>* Environment::destroy_ids_list() {
+  return &destroy_ids_list_;
+}
+
 inline uint32_t* Environment::heap_statistics_buffer() const {
   CHECK_NE(heap_statistics_buffer_, nullptr);
   return heap_statistics_buffer_;
diff --git a/src/env.h b/src/env.h
index 67d10b20e41673..543bef6ed20e4d 100644
--- a/src/env.h
+++ b/src/env.h
@@ -11,6 +11,7 @@
 #include "v8.h"
 
 #include <stdint.h>
+#include <vector>
 
 // Caveat emptor: we're going slightly crazy with macros here but the end
 // hopefully justifies the means. We have a lot of per-context properties
@@ -413,8 +414,10 @@ class Environment {
   inline uint32_t watched_providers() const;
 
   static inline Environment* from_immediate_check_handle(uv_check_t* handle);
+  static inline Environment* from_destroy_ids_idle_handle(uv_idle_t* handle);
   inline uv_check_t* immediate_check_handle();
   inline uv_idle_t* immediate_idle_handle();
+  inline uv_idle_t* destroy_ids_idle_handle();
 
   static inline Environment* from_idle_prepare_handle(uv_prepare_t* handle);
   inline uv_prepare_t* idle_prepare_handle();
@@ -451,6 +454,9 @@ class Environment {
 
   inline int64_t get_async_wrap_uid();
 
+  // List of id's that have been destroyed and need the destroy() cb called.
+  inline std::vector<int64_t>* destroy_ids_list();
+
   inline uint32_t* heap_statistics_buffer() const;
   inline void set_heap_statistics_buffer(uint32_t* pointer);
 
@@ -531,6 +537,7 @@ class Environment {
   IsolateData* const isolate_data_;
   uv_check_t immediate_check_handle_;
   uv_idle_t immediate_idle_handle_;
+  uv_idle_t destroy_ids_idle_handle_;
   uv_prepare_t idle_prepare_handle_;
   uv_check_t idle_check_handle_;
   AsyncHooks async_hooks_;
@@ -546,6 +553,7 @@ class Environment {
   bool trace_sync_io_;
   size_t makecallback_cntr_;
   int64_t async_wrap_uid_;
+  std::vector<int64_t> destroy_ids_list_;
   debugger::Agent debugger_agent_;
 
   HandleWrapQueue handle_wrap_queue_;
diff --git a/src/node.cc b/src/node.cc
index d34225e2132dca..2935729bbb9f41 100644
--- a/src/node.cc
+++ b/src/node.cc
@@ -4202,6 +4202,9 @@ Environment* CreateEnvironment(Isolate* isolate,
   uv_unref(reinterpret_cast<uv_handle_t*>(env->idle_prepare_handle()));
   uv_unref(reinterpret_cast<uv_handle_t*>(env->idle_check_handle()));
 
+  uv_idle_init(env->event_loop(), env->destroy_ids_idle_handle());
+  uv_unref(reinterpret_cast<uv_handle_t*>(env->destroy_ids_idle_handle()));
+
   // Register handle cleanups
   env->RegisterHandleCleanup(
       reinterpret_cast<uv_handle_t*>(env->immediate_check_handle()),
diff --git a/src/node_crypto.cc b/src/node_crypto.cc
index c6414a4ba82f8d..04c79702a7aa31 100644
--- a/src/node_crypto.cc
+++ b/src/node_crypto.cc
@@ -2131,18 +2131,13 @@ int SSLWrap<Base>::SSLCertCallback(SSL* s, void* arg) {
 
   Local<Object> info = Object::New(env->isolate());
 
-  SSL_SESSION* sess = SSL_get_session(s);
-  if (sess != nullptr) {
-    if (sess->tlsext_hostname == nullptr) {
-      info->Set(env->servername_string(), String::Empty(env->isolate()));
-    } else {
-      Local<String> servername = OneByteString(env->isolate(),
-                                               sess->tlsext_hostname,
-                                               strlen(sess->tlsext_hostname));
-      info->Set(env->servername_string(), servername);
-    }
-    info->Set(env->tls_ticket_string(),
-              Boolean::New(env->isolate(), sess->tlsext_ticklen != 0));
+  const char* servername = SSL_get_servername(s, TLSEXT_NAMETYPE_host_name);
+  if (servername == nullptr) {
+    info->Set(env->servername_string(), String::Empty(env->isolate()));
+  } else {
+    Local<String> str = OneByteString(env->isolate(), servername,
+                                      strlen(servername));
+    info->Set(env->servername_string(), str);
   }
 
   bool ocsp = false;
diff --git a/src/node_version.h b/src/node_version.h
index 321256a9c74184..ce513849f8dfc9 100644
--- a/src/node_version.h
+++ b/src/node_version.h
@@ -8,7 +8,7 @@
 #define NODE_VERSION_IS_LTS 1
 #define NODE_VERSION_LTS_CODENAME "Argon"
 
-#define NODE_VERSION_IS_RELEASE 0
+#define NODE_VERSION_IS_RELEASE 1
 
 #ifndef NODE_STRINGIFY
 #define NODE_STRINGIFY(n) NODE_STRINGIFY_HELPER(n)
diff --git a/test/addons/async-hello-world/test.js b/test/addons/async-hello-world/test.js
index 14b80b711b9b35..4344605121f905 100644
--- a/test/addons/async-hello-world/test.js
+++ b/test/addons/async-hello-world/test.js
@@ -1,7 +1,7 @@
 'use strict';
-require('../../common');
+var common = require('../../common');
 var assert = require('assert');
-var binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 var called = false;
 
 process.on('exit', function() {
diff --git a/test/addons/at-exit/test.js b/test/addons/at-exit/test.js
index c94453cb3b05a4..4e2ca810f01c87 100644
--- a/test/addons/at-exit/test.js
+++ b/test/addons/at-exit/test.js
@@ -1,3 +1,3 @@
 'use strict';
-require('../../common');
-require('./build/Release/binding');
+const common = require('../../common');
+require(`./build/${common.buildType}/binding`);
diff --git a/test/addons/buffer-free-callback/test.js b/test/addons/buffer-free-callback/test.js
index a70931d81e8977..dc527af2f83fe4 100644
--- a/test/addons/buffer-free-callback/test.js
+++ b/test/addons/buffer-free-callback/test.js
@@ -1,8 +1,8 @@
 'use strict';
 // Flags: --expose-gc
 
-require('../../common');
-var binding = require('./build/Release/binding');
+const common = require('../../common');
+const binding = require(`./build/${common.buildType}/binding`);
 
 function check(size) {
   var buf = binding.alloc(size);
diff --git a/test/addons/heap-profiler/test.js b/test/addons/heap-profiler/test.js
index 3fa00e9b86afad..32b32ddb6e6581 100644
--- a/test/addons/heap-profiler/test.js
+++ b/test/addons/heap-profiler/test.js
@@ -1,8 +1,8 @@
 'use strict';
 
-require('../../common');
+const common = require('../../common');
 
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 
 // Create an AsyncWrap object.
 const timer = setTimeout(function() {}, 1);
diff --git a/test/addons/hello-world-function-export/test.js b/test/addons/hello-world-function-export/test.js
index 6dcdf39ce1c413..89127fc787c94e 100644
--- a/test/addons/hello-world-function-export/test.js
+++ b/test/addons/hello-world-function-export/test.js
@@ -1,6 +1,6 @@
 'use strict';
-require('../../common');
+const common = require('../../common');
 var assert = require('assert');
-var binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 assert.equal('world', binding());
 console.log('binding.hello() =', binding());
diff --git a/test/addons/hello-world/test.js b/test/addons/hello-world/test.js
index 5637e9e6e93a3e..8d5c1238770064 100644
--- a/test/addons/hello-world/test.js
+++ b/test/addons/hello-world/test.js
@@ -1,6 +1,6 @@
 'use strict';
-require('../../common');
+const common = require('../../common');
 var assert = require('assert');
-var binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 assert.equal('world', binding.hello());
 console.log('binding.hello() =', binding.hello());
diff --git a/test/addons/load-long-path/test.js b/test/addons/load-long-path/test.js
index a4f3cb12dc0480..ffe1c5cc6eaa2d 100644
--- a/test/addons/load-long-path/test.js
+++ b/test/addons/load-long-path/test.js
@@ -21,7 +21,10 @@ for (var i = 0; i < 10; i++) {
   fs.mkdirSync(addonDestinationDir);
 }
 
-const addonPath = path.join(__dirname, 'build', 'Release', 'binding.node');
+const addonPath = path.join(__dirname,
+                            'build',
+                            common.buildType,
+                            'binding.node');
 const addonDestinationPath = path.join(addonDestinationDir, 'binding.node');
 
 // Copy binary to long path destination
diff --git a/test/addons/make-callback-recurse/test.js b/test/addons/make-callback-recurse/test.js
index f924ac61916ba5..f1403341ce8099 100644
--- a/test/addons/make-callback-recurse/test.js
+++ b/test/addons/make-callback-recurse/test.js
@@ -3,7 +3,7 @@
 const common = require('../../common');
 const assert = require('assert');
 const domain = require('domain');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const makeCallback = binding.makeCallback;
 
 // Make sure this is run in the future.
diff --git a/test/addons/make-callback/test.js b/test/addons/make-callback/test.js
index f3c98770ef335a..43ad014c4af478 100644
--- a/test/addons/make-callback/test.js
+++ b/test/addons/make-callback/test.js
@@ -3,7 +3,7 @@
 const common = require('../../common');
 const assert = require('assert');
 const vm = require('vm');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const makeCallback = binding.makeCallback;
 
 assert.strictEqual(42, makeCallback(process, common.mustCall(function() {
diff --git a/test/addons/new-target/binding.cc b/test/addons/new-target/binding.cc
new file mode 100644
index 00000000000000..a7e18eff70ea0d
--- /dev/null
+++ b/test/addons/new-target/binding.cc
@@ -0,0 +1,16 @@
+#include <node.h>
+#include <v8.h>
+
+namespace {
+
+inline void NewClass(const v8::FunctionCallbackInfo<v8::Value>&) {}
+
+inline void Initialize(v8::Local<v8::Object> binding) {
+  auto isolate = binding->GetIsolate();
+  binding->Set(v8::String::NewFromUtf8(isolate, "Class"),
+               v8::FunctionTemplate::New(isolate, NewClass)->GetFunction());
+}
+
+NODE_MODULE(binding, Initialize)
+
+}  // anonymous namespace
diff --git a/test/addons/new-target/binding.gyp b/test/addons/new-target/binding.gyp
new file mode 100644
index 00000000000000..7ede63d94a0d77
--- /dev/null
+++ b/test/addons/new-target/binding.gyp
@@ -0,0 +1,9 @@
+{
+  'targets': [
+    {
+      'target_name': 'binding',
+      'defines': [ 'V8_DEPRECATION_WARNINGS=1' ],
+      'sources': [ 'binding.cc' ]
+    }
+  ]
+}
diff --git a/test/addons/new-target/test.js b/test/addons/new-target/test.js
new file mode 100644
index 00000000000000..e4864adb1c24f3
--- /dev/null
+++ b/test/addons/new-target/test.js
@@ -0,0 +1,18 @@
+'use strict';
+
+const common = require('../../common');
+const assert = require('assert');
+const binding = require(`./build/${common.buildType}/binding`);
+
+class Class extends binding.Class {
+  constructor() {
+    super();
+    this.method();
+  }
+  method() {
+    this.ok = true;
+  }
+}
+
+assert.ok(new Class() instanceof binding.Class);
+assert.ok(new Class().ok);
diff --git a/test/addons/openssl-binding/test.js b/test/addons/openssl-binding/test.js
index aa515bac9a5c45..a146ffe5c68f1b 100644
--- a/test/addons/openssl-binding/test.js
+++ b/test/addons/openssl-binding/test.js
@@ -1,8 +1,8 @@
 'use strict';
 
-require('../../common');
+const common = require('../../common');
 const assert = require('assert');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const bytes = new Uint8Array(1024);
 assert(binding.randomBytes(bytes));
 assert(bytes.reduce((v, a) => v + a) > 0);
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-at-max.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-at-max.js
index 3f548112278cd6..dcc483fe51c7dc 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-at-max.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-at-max.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 // v8 fails silently if string length > v8::String::kMaxLength
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii.js
index b106e3d25aa085..df96a98d3f4bd2 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64.js
index 1df9d228d961d9..5471cd1b7191a4 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary.js
index de27859a06e1bc..e7a067f310e7ab 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex.js
index 4dbcf0efd86e39..21780b026aa3c6 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8.js
index 0333bc850b5c42..dcf11390a1f718 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2.js
index 094dee899030cc..f09770bbcc21e2 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max.js b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max.js
index ce4a488cca1d95..118cee3b2c1358 100644
--- a/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max.js
+++ b/test/addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max.js
@@ -1,7 +1,7 @@
 'use strict';
 
 const common = require('../../common');
-const binding = require('./build/Release/binding');
+const binding = require(`./build/${common.buildType}/binding`);
 const assert = require('assert');
 
 const skipMessage = 'intensive toString tests due to memory confinements';
diff --git a/test/cctest/util.cc b/test/cctest/util.cc
index 1f1584fa72124a..7f967871975dd5 100644
--- a/test/cctest/util.cc
+++ b/test/cctest/util.cc
@@ -87,4 +87,4 @@ TEST(UtilTest, Calloc) {
   EXPECT_NE(nullptr, Calloc(1, 0));
   EXPECT_NE(nullptr, Calloc(0, 1));
   EXPECT_NE(nullptr, Calloc(1, 1));
-}
\ No newline at end of file
+}
diff --git a/test/common.js b/test/common.js
index 774a960ab6a7ef..a72560be77a3a9 100644
--- a/test/common.js
+++ b/test/common.js
@@ -28,6 +28,7 @@ exports.isFreeBSD = process.platform === 'freebsd';
 
 exports.enoughTestMem = os.totalmem() > 0x40000000; /* 1 Gb */
 exports.rootDir = exports.isWindows ? 'c:\\' : '/';
+exports.buildType = process.config.target_defaults.default_configuration;
 
 function rimrafSync(p) {
   try {
@@ -336,6 +337,11 @@ if (global.Symbol) {
   knownGlobals.push(Symbol);
 }
 
+function allowGlobals() {
+  knownGlobals = knownGlobals.concat(Array.from(arguments));
+}
+exports.allowGlobals = allowGlobals;
+
 function leakedGlobals() {
   var leaked = [];
 
@@ -527,3 +533,17 @@ ArrayStream.prototype.writable = true;
 ArrayStream.prototype.pause = function() {};
 ArrayStream.prototype.resume = function() {};
 ArrayStream.prototype.write = function() {};
+
+exports.expectWarning = function(name, expected) {
+  if (typeof expected === 'string')
+    expected = [expected];
+  process.on('warning', exports.mustCall((warning) => {
+    assert.strictEqual(warning.name, name);
+    assert.ok(expected.includes(warning.message),
+              `unexpected error message: "${warning.message}"`);
+    // Remove a warning message after it is seen so that we guarantee that we
+    // get each message only once.
+    expected.splice(expected.indexOf(warning.message), 1);
+  }, expected.length));
+};
+
diff --git a/test/debugger/helper-debugger-repl.js b/test/debugger/helper-debugger-repl.js
index 766c6566f7e4c0..31b010b4d8cc60 100644
--- a/test/debugger/helper-debugger-repl.js
+++ b/test/debugger/helper-debugger-repl.js
@@ -108,7 +108,7 @@ function addTest(input, output) {
 }
 
 var handshakeLines = [
-  /listening on port \d+/,
+  /listening on /,
   /connecting.* ok/
 ];
 
diff --git a/test/parallel/test-assert-typedarray-deepequal.js b/test/parallel/test-assert-typedarray-deepequal.js
index be4462de5dff77..83f8ddf94060ba 100644
--- a/test/parallel/test-assert-typedarray-deepequal.js
+++ b/test/parallel/test-assert-typedarray-deepequal.js
@@ -25,7 +25,10 @@ const equalArrayPairs = [
   [new Int16Array([256]), new Uint16Array([256])],
   [new Float32Array([+0.0]), new Float32Array([-0.0])],
   [new Float64Array([+0.0]), new Float32Array([-0.0])],
-  [new Float64Array([+0.0]), new Float64Array([-0.0])]
+  [new Float64Array([+0.0]), new Float64Array([-0.0])],
+  [new Uint8Array([1, 2, 3, 4]).subarray(1), new Uint8Array([2, 3, 4])],
+  [new Uint16Array([1, 2, 3, 4]).subarray(1), new Uint16Array([2, 3, 4])],
+  [new Uint32Array([1, 2, 3, 4]).subarray(1, 3), new Uint32Array([2, 3])]
 ];
 
 const notEqualArrayPairs = [
diff --git a/test/parallel/test-async-wrap-check-providers.js b/test/parallel/test-async-wrap-check-providers.js
index 71fd93b77195e0..1b69c6b6cd2f38 100644
--- a/test/parallel/test-async-wrap-check-providers.js
+++ b/test/parallel/test-async-wrap-check-providers.js
@@ -41,7 +41,7 @@ async_wrap.setupHooks({ init });
 async_wrap.enable();
 
 
-setTimeout(function() { });
+setTimeout(function() { }, 1);
 
 fs.stat(__filename, noop);
 
diff --git a/test/parallel/test-async-wrap-disabled-propagate-parent.js b/test/parallel/test-async-wrap-disabled-propagate-parent.js
index 5b6dd837de2774..4a6df7500956bf 100644
--- a/test/parallel/test-async-wrap-disabled-propagate-parent.js
+++ b/test/parallel/test-async-wrap-disabled-propagate-parent.js
@@ -18,12 +18,12 @@ function init(uid, type, parentUid, parentHandle) {
     cntr++;
     // Cannot assert in init callback or will abort.
     process.nextTick(() => {
-      assert.equal(providers[type], 'TCPWRAP');
-      assert.equal(parentUid, server._handle[uidSymbol],
-                   'server uid doesn\'t match parent uid');
-      assert.equal(parentHandle, server._handle,
-                   'server handle doesn\'t match parent handle');
-      assert.equal(this, client._handle, 'client doesn\'t match context');
+      assert.strictEqual(providers[type], 'TCPWRAP');
+      assert.strictEqual(parentUid, server._handle[uidSymbol],
+                         'server uid doesn\'t match parent uid');
+      assert.strictEqual(parentHandle, server._handle,
+                         'server handle doesn\'t match parent handle');
+      assert.strictEqual(this, client._handle, 'client doesn\'t match context');
     });
   }
 }
@@ -48,5 +48,5 @@ async_wrap.disable();
 
 process.on('exit', function() {
   // init should have only been called once with a parent.
-  assert.equal(cntr, 1);
+  assert.strictEqual(cntr, 1);
 });
diff --git a/test/parallel/test-async-wrap-propagate-parent.js b/test/parallel/test-async-wrap-propagate-parent.js
index a3902081ea7708..0968490f5975cc 100644
--- a/test/parallel/test-async-wrap-propagate-parent.js
+++ b/test/parallel/test-async-wrap-propagate-parent.js
@@ -18,12 +18,12 @@ function init(uid, type, parentUid, parentHandle) {
     cntr++;
     // Cannot assert in init callback or will abort.
     process.nextTick(() => {
-      assert.equal(providers[type], 'TCPWRAP');
-      assert.equal(parentUid, server._handle[uidSymbol],
-                   'server uid doesn\'t match parent uid');
-      assert.equal(parentHandle, server._handle,
-                   'server handle doesn\'t match parent handle');
-      assert.equal(this, client._handle, 'client doesn\'t match context');
+      assert.strictEqual(providers[type], 'TCPWRAP');
+      assert.strictEqual(parentUid, server._handle[uidSymbol],
+                         'server uid doesn\'t match parent uid');
+      assert.strictEqual(parentHandle, server._handle,
+                         'server handle doesn\'t match parent handle');
+      assert.strictEqual(this, client._handle, 'client doesn\'t match context');
     });
   }
 }
@@ -47,5 +47,5 @@ const server = net.createServer(function(c) {
 
 process.on('exit', function() {
   // init should have only been called once with a parent.
-  assert.equal(cntr, 1);
+  assert.strictEqual(cntr, 1);
 });
diff --git a/test/parallel/test-async-wrap-throw-from-callback.js b/test/parallel/test-async-wrap-throw-from-callback.js
index bfbe32c38b021a..93b5bee470ce3f 100644
--- a/test/parallel/test-async-wrap-throw-from-callback.js
+++ b/test/parallel/test-async-wrap-throw-from-callback.js
@@ -6,7 +6,7 @@ const assert = require('assert');
 const crypto = require('crypto');
 const domain = require('domain');
 const spawn = require('child_process').spawn;
-const callbacks = [ 'init', 'pre', 'post', 'destroy' ];
+const callbacks = [ 'init', 'pre', 'post' ];
 const toCall = process.argv[2];
 var msgCalled = 0;
 var msgReceived = 0;
@@ -23,13 +23,9 @@ function post() {
   if (toCall === 'post')
     throw new Error('post');
 }
-function destroy() {
-  if (toCall === 'destroy')
-    throw new Error('destroy');
-}
 
 if (typeof process.argv[2] === 'string') {
-  async_wrap.setupHooks({ init, pre, post, destroy });
+  async_wrap.setupHooks({ init, pre, post });
   async_wrap.enable();
 
   process.on('uncaughtException', () => assert.ok(0, 'UNREACHABLE'));
@@ -44,8 +40,8 @@ if (typeof process.argv[2] === 'string') {
 } else {
 
   process.on('exit', (code) => {
-    assert.equal(msgCalled, callbacks.length);
-    assert.equal(msgCalled, msgReceived);
+    assert.strictEqual(msgCalled, callbacks.length);
+    assert.strictEqual(msgCalled, msgReceived);
   });
 
   callbacks.forEach((item) => {
@@ -62,7 +58,7 @@ if (typeof process.argv[2] === 'string') {
       if (errstring.includes('Error: ' + item))
         msgReceived++;
 
-      assert.equal(code, 1, `${item} closed with code ${code}`);
+      assert.strictEqual(code, 1, `${item} closed with code ${code}`);
     });
   });
 }
diff --git a/test/parallel/test-async-wrap-uid.js b/test/parallel/test-async-wrap-uid.js
index 5bf3a8856e0e3f..3497c3b0768ddd 100644
--- a/test/parallel/test-async-wrap-uid.js
+++ b/test/parallel/test-async-wrap-uid.js
@@ -6,7 +6,7 @@ const assert = require('assert');
 const async_wrap = process.binding('async_wrap');
 
 const storage = new Map();
-async_wrap.setupHooks({ init, pre, post, destroy });
+async_wrap.setupHooks({ init, pre, post });
 async_wrap.enable();
 
 function init(uid) {
@@ -14,7 +14,6 @@ function init(uid) {
     init: true,
     pre: false,
     post: false,
-    destroy: false
   });
 }
 
@@ -26,10 +25,6 @@ function post(uid) {
   storage.get(uid).post = true;
 }
 
-function destroy(uid) {
-  storage.get(uid).destroy = true;
-}
-
 fs.access(__filename, function(err) {
   assert.ifError(err);
 });
@@ -51,7 +46,6 @@ process.once('exit', function() {
       init: true,
       pre: true,
       post: true,
-      destroy: true
     });
   }
 });
diff --git a/test/parallel/test-beforeexit-event.js b/test/parallel/test-beforeexit-event.js
index d50ef67190c4c7..ef94da76af3883 100644
--- a/test/parallel/test-beforeexit-event.js
+++ b/test/parallel/test-beforeexit-event.js
@@ -1,42 +1,26 @@
 'use strict';
-require('../common');
-var assert = require('assert');
-var net = require('net');
-var revivals = 0;
-var deaths = 0;
+const common = require('../common');
+const net = require('net');
 
-process.on('beforeExit', function() { deaths++; });
-
-process.once('beforeExit', tryImmediate);
+process.once('beforeExit', common.mustCall(tryImmediate));
 
 function tryImmediate() {
-  console.log('set immediate');
-  setImmediate(function() {
-    revivals++;
-    process.once('beforeExit', tryTimer);
-  });
+  setImmediate(common.mustCall(() => {
+    process.once('beforeExit', common.mustCall(tryTimer));
+  }));
 }
 
 function tryTimer() {
-  console.log('set a timeout');
-  setTimeout(function() {
-    console.log('timeout cb, do another once beforeExit');
-    revivals++;
-    process.once('beforeExit', tryListen);
-  }, 1);
+  setTimeout(common.mustCall(() => {
+    process.once('beforeExit', common.mustCall(tryListen));
+  }), 1);
 }
 
 function tryListen() {
-  console.log('create a server');
   net.createServer()
     .listen(0)
-    .on('listening', function() {
-      revivals++;
+    .on('listening', common.mustCall(function() {
       this.close();
-    });
+      process.on('beforeExit', common.mustCall(() => {}));
+    }));
 }
-
-process.on('exit', function() {
-  assert.equal(4, deaths);
-  assert.equal(3, revivals);
-});
diff --git a/test/parallel/test-buffer-indexof.js b/test/parallel/test-buffer-indexof.js
index 51be92f2881f74..3f95366ea1581b 100644
--- a/test/parallel/test-buffer-indexof.js
+++ b/test/parallel/test-buffer-indexof.js
@@ -11,65 +11,65 @@ var buf_f = new Buffer('f');
 var buf_z = new Buffer('z');
 var buf_empty = new Buffer('');
 
-assert.equal(b.indexOf('a'), 0);
-assert.equal(b.indexOf('a', 1), -1);
-assert.equal(b.indexOf('a', -1), -1);
-assert.equal(b.indexOf('a', -4), -1);
-assert.equal(b.indexOf('a', -b.length), 0);
-assert.equal(b.indexOf('a', NaN), 0);
-assert.equal(b.indexOf('a', -Infinity), 0);
-assert.equal(b.indexOf('a', Infinity), -1);
-assert.equal(b.indexOf('bc'), 1);
-assert.equal(b.indexOf('bc', 2), -1);
-assert.equal(b.indexOf('bc', -1), -1);
-assert.equal(b.indexOf('bc', -3), -1);
-assert.equal(b.indexOf('bc', -5), 1);
-assert.equal(b.indexOf('bc', NaN), 1);
-assert.equal(b.indexOf('bc', -Infinity), 1);
-assert.equal(b.indexOf('bc', Infinity), -1);
-assert.equal(b.indexOf('f'), b.length - 1);
-assert.equal(b.indexOf('z'), -1);
-assert.equal(b.indexOf(''), -1);
-assert.equal(b.indexOf('', 1), -1);
-assert.equal(b.indexOf('', b.length + 1), -1);
-assert.equal(b.indexOf('', Infinity), -1);
-assert.equal(b.indexOf(buf_a), 0);
-assert.equal(b.indexOf(buf_a, 1), -1);
-assert.equal(b.indexOf(buf_a, -1), -1);
-assert.equal(b.indexOf(buf_a, -4), -1);
-assert.equal(b.indexOf(buf_a, -b.length), 0);
-assert.equal(b.indexOf(buf_a, NaN), 0);
-assert.equal(b.indexOf(buf_a, -Infinity), 0);
-assert.equal(b.indexOf(buf_a, Infinity), -1);
-assert.equal(b.indexOf(buf_bc), 1);
-assert.equal(b.indexOf(buf_bc, 2), -1);
-assert.equal(b.indexOf(buf_bc, -1), -1);
-assert.equal(b.indexOf(buf_bc, -3), -1);
-assert.equal(b.indexOf(buf_bc, -5), 1);
-assert.equal(b.indexOf(buf_bc, NaN), 1);
-assert.equal(b.indexOf(buf_bc, -Infinity), 1);
-assert.equal(b.indexOf(buf_bc, Infinity), -1);
-assert.equal(b.indexOf(buf_f), b.length - 1);
-assert.equal(b.indexOf(buf_z), -1);
-assert.equal(b.indexOf(buf_empty), -1);
-assert.equal(b.indexOf(buf_empty, 1), -1);
-assert.equal(b.indexOf(buf_empty, b.length + 1), -1);
-assert.equal(b.indexOf(buf_empty, Infinity), -1);
-assert.equal(b.indexOf(0x61), 0);
-assert.equal(b.indexOf(0x61, 1), -1);
-assert.equal(b.indexOf(0x61, -1), -1);
-assert.equal(b.indexOf(0x61, -4), -1);
-assert.equal(b.indexOf(0x61, -b.length), 0);
-assert.equal(b.indexOf(0x61, NaN), 0);
-assert.equal(b.indexOf(0x61, -Infinity), 0);
-assert.equal(b.indexOf(0x61, Infinity), -1);
-assert.equal(b.indexOf(0x0), -1);
+assert.strictEqual(b.indexOf('a'), 0);
+assert.strictEqual(b.indexOf('a', 1), -1);
+assert.strictEqual(b.indexOf('a', -1), -1);
+assert.strictEqual(b.indexOf('a', -4), -1);
+assert.strictEqual(b.indexOf('a', -b.length), 0);
+assert.strictEqual(b.indexOf('a', NaN), 0);
+assert.strictEqual(b.indexOf('a', -Infinity), 0);
+assert.strictEqual(b.indexOf('a', Infinity), -1);
+assert.strictEqual(b.indexOf('bc'), 1);
+assert.strictEqual(b.indexOf('bc', 2), -1);
+assert.strictEqual(b.indexOf('bc', -1), -1);
+assert.strictEqual(b.indexOf('bc', -3), -1);
+assert.strictEqual(b.indexOf('bc', -5), 1);
+assert.strictEqual(b.indexOf('bc', NaN), 1);
+assert.strictEqual(b.indexOf('bc', -Infinity), 1);
+assert.strictEqual(b.indexOf('bc', Infinity), -1);
+assert.strictEqual(b.indexOf('f'), b.length - 1);
+assert.strictEqual(b.indexOf('z'), -1);
+assert.strictEqual(b.indexOf(''), -1);
+assert.strictEqual(b.indexOf('', 1), -1);
+assert.strictEqual(b.indexOf('', b.length + 1), -1);
+assert.strictEqual(b.indexOf('', Infinity), -1);
+assert.strictEqual(b.indexOf(buf_a), 0);
+assert.strictEqual(b.indexOf(buf_a, 1), -1);
+assert.strictEqual(b.indexOf(buf_a, -1), -1);
+assert.strictEqual(b.indexOf(buf_a, -4), -1);
+assert.strictEqual(b.indexOf(buf_a, -b.length), 0);
+assert.strictEqual(b.indexOf(buf_a, NaN), 0);
+assert.strictEqual(b.indexOf(buf_a, -Infinity), 0);
+assert.strictEqual(b.indexOf(buf_a, Infinity), -1);
+assert.strictEqual(b.indexOf(buf_bc), 1);
+assert.strictEqual(b.indexOf(buf_bc, 2), -1);
+assert.strictEqual(b.indexOf(buf_bc, -1), -1);
+assert.strictEqual(b.indexOf(buf_bc, -3), -1);
+assert.strictEqual(b.indexOf(buf_bc, -5), 1);
+assert.strictEqual(b.indexOf(buf_bc, NaN), 1);
+assert.strictEqual(b.indexOf(buf_bc, -Infinity), 1);
+assert.strictEqual(b.indexOf(buf_bc, Infinity), -1);
+assert.strictEqual(b.indexOf(buf_f), b.length - 1);
+assert.strictEqual(b.indexOf(buf_z), -1);
+assert.strictEqual(b.indexOf(buf_empty), -1);
+assert.strictEqual(b.indexOf(buf_empty, 1), -1);
+assert.strictEqual(b.indexOf(buf_empty, b.length + 1), -1);
+assert.strictEqual(b.indexOf(buf_empty, Infinity), -1);
+assert.strictEqual(b.indexOf(0x61), 0);
+assert.strictEqual(b.indexOf(0x61, 1), -1);
+assert.strictEqual(b.indexOf(0x61, -1), -1);
+assert.strictEqual(b.indexOf(0x61, -4), -1);
+assert.strictEqual(b.indexOf(0x61, -b.length), 0);
+assert.strictEqual(b.indexOf(0x61, NaN), 0);
+assert.strictEqual(b.indexOf(0x61, -Infinity), 0);
+assert.strictEqual(b.indexOf(0x61, Infinity), -1);
+assert.strictEqual(b.indexOf(0x0), -1);
 
 // test offsets
-assert.equal(b.indexOf('d', 2), 3);
-assert.equal(b.indexOf('f', 5), 5);
-assert.equal(b.indexOf('f', -1), 5);
-assert.equal(b.indexOf('f', 6), -1);
+assert.strictEqual(b.indexOf('d', 2), 3);
+assert.strictEqual(b.indexOf('f', 5), 5);
+assert.strictEqual(b.indexOf('f', -1), 5);
+assert.strictEqual(b.indexOf('f', 6), -1);
 
 assert.equal(b.indexOf(Buffer('d'), 2), 3);
 assert.equal(b.indexOf(Buffer('f'), 5), 5);
diff --git a/test/parallel/test-buffer-slow.js b/test/parallel/test-buffer-slow.js
index cf1a3fd8eb200d..9064e07f4910cc 100644
--- a/test/parallel/test-buffer-slow.js
+++ b/test/parallel/test-buffer-slow.js
@@ -30,7 +30,7 @@ assert.strictEqual(SlowBuffer(0).length, 0);
 try {
   assert.strictEqual(SlowBuffer(buffer.kMaxLength).length, buffer.kMaxLength);
 } catch (e) {
-  assert.equal(e.message, 'Invalid array buffer length');
+  assert.strictEqual(e.message, 'Invalid array buffer length');
 }
 
 // should work with number-coercible values
@@ -46,10 +46,10 @@ assert.strictEqual(SlowBuffer('string').length, 0);
 // should throw with invalid length
 assert.throws(function() {
   new SlowBuffer(Infinity);
-}, 'invalid Buffer length');
+}, /^RangeError: Invalid typed array length$/);
 assert.throws(function() {
   new SlowBuffer(-1);
-}, 'invalid Buffer length');
+}, /^RangeError: Invalid typed array length$/);
 assert.throws(function() {
   new SlowBuffer(buffer.kMaxLength + 1);
-}, 'invalid Buffer length');
+}, /^RangeError: (Invalid typed array length|Array buffer allocation failed)$/);
diff --git a/test/parallel/test-child-process-bad-stdio.js b/test/parallel/test-child-process-bad-stdio.js
new file mode 100644
index 00000000000000..e92bbcf11fbac8
--- /dev/null
+++ b/test/parallel/test-child-process-bad-stdio.js
@@ -0,0 +1,63 @@
+'use strict';
+// Flags: --expose_internals
+const common = require('../common');
+const assert = require('assert');
+const cp = require('child_process');
+
+if (process.argv[2] === 'child') {
+  setTimeout(() => {}, common.platformTimeout(100));
+  return;
+}
+
+// Monkey patch spawn() to create a child process normally, but destroy the
+// stdout and stderr streams. This replicates the conditions where the streams
+// cannot be properly created.
+const ChildProcess = require('internal/child_process').ChildProcess;
+const original = ChildProcess.prototype.spawn;
+
+ChildProcess.prototype.spawn = function() {
+  const err = original.apply(this, arguments);
+
+  this.stdout.destroy();
+  this.stderr.destroy();
+  this.stdout = null;
+  this.stderr = null;
+
+  return err;
+};
+
+function createChild(options, callback) {
+  const cmd = `${process.execPath} ${__filename} child`;
+
+  return cp.exec(cmd, options, common.mustCall(callback));
+}
+
+// Verify that normal execution of a child process is handled.
+{
+  createChild({}, (err, stdout, stderr) => {
+    assert.strictEqual(err, null);
+    assert.strictEqual(stdout, '');
+    assert.strictEqual(stderr, '');
+  });
+}
+
+// Verify that execution with an error event is handled.
+{
+  const error = new Error('foo');
+  const child = createChild({}, (err, stdout, stderr) => {
+    assert.strictEqual(err, error);
+    assert.strictEqual(stdout, '');
+    assert.strictEqual(stderr, '');
+  });
+
+  child.emit('error', error);
+}
+
+// Verify that execution with a killed process is handled.
+{
+  createChild({ timeout: 1 }, (err, stdout, stderr) => {
+    assert.strictEqual(err.killed, true);
+    assert.strictEqual(stdout, '');
+    assert.strictEqual(stderr, '');
+  });
+}
diff --git a/test/parallel/test-child-process-constructor.js b/test/parallel/test-child-process-constructor.js
index 6980810485c964..0abf1289f0737d 100644
--- a/test/parallel/test-child-process-constructor.js
+++ b/test/parallel/test-child-process-constructor.js
@@ -4,7 +4,7 @@ require('../common');
 var assert = require('assert');
 var child_process = require('child_process');
 var ChildProcess = child_process.ChildProcess;
-assert.equal(typeof ChildProcess, 'function');
+assert.strictEqual(typeof ChildProcess, 'function');
 
 // test that we can call spawn
 var child = new ChildProcess();
@@ -15,11 +15,11 @@ child.spawn({
   stdio: 'pipe'
 });
 
-assert.equal(child.hasOwnProperty('pid'), true);
+assert.strictEqual(child.hasOwnProperty('pid'), true);
 
 // try killing with invalid signal
 assert.throws(function() {
   child.kill('foo');
 }, /Unknown signal: foo/);
 
-assert.equal(child.kill(), true);
+assert.strictEqual(child.kill(), true);
diff --git a/test/parallel/test-child-process-detached.js b/test/parallel/test-child-process-detached.js
index 711c5d227d6b07..9ad86c3a4fb2e6 100644
--- a/test/parallel/test-child-process-detached.js
+++ b/test/parallel/test-child-process-detached.js
@@ -18,7 +18,7 @@ process.on('exit', function() {
   assert(persistentPid !== -1);
   assert.throws(function() {
     process.kill(child.pid);
-  });
+  }, /^Error: kill ESRCH$/);
   assert.doesNotThrow(function() {
     process.kill(persistentPid);
   });
diff --git a/test/parallel/test-child-process-double-pipe.js b/test/parallel/test-child-process-double-pipe.js
index 2d9805d687635c..c5b7c093af8a4a 100644
--- a/test/parallel/test-child-process-double-pipe.js
+++ b/test/parallel/test-child-process-double-pipe.js
@@ -91,5 +91,5 @@ sed.stdout.on('data', function(data) {
 });
 
 sed.stdout.on('end', function(code) {
-  assert.equal(result, 'hellO' + os.EOL + 'nOde' + os.EOL + 'wOrld' + os.EOL);
+  assert.strictEqual(result, `hellO${os.EOL}nOde${os.EOL}wOrld${os.EOL}`);
 });
diff --git a/test/parallel/test-child-process-stdio-big-write-end.js b/test/parallel/test-child-process-stdio-big-write-end.js
index 6a55c2b658e602..76427b69c29e42 100644
--- a/test/parallel/test-child-process-stdio-big-write-end.js
+++ b/test/parallel/test-child-process-stdio-big-write-end.js
@@ -23,7 +23,7 @@ function parent() {
     n += c;
   });
   child.stdout.on('end', function() {
-    assert.equal(+n, sent);
+    assert.strictEqual(+n, sent);
     console.log('ok');
   });
 
diff --git a/test/parallel/test-child-process-stdio-inherit.js b/test/parallel/test-child-process-stdio-inherit.js
index 409c0af7ca0d31..dc3bb3e9aa9391 100644
--- a/test/parallel/test-child-process-stdio-inherit.js
+++ b/test/parallel/test-child-process-stdio-inherit.js
@@ -22,10 +22,10 @@ function grandparent() {
   child.stdin.end(input);
 
   child.on('close', function(code, signal) {
-    assert.equal(code, 0);
-    assert.equal(signal, null);
+    assert.strictEqual(code, 0);
+    assert.strictEqual(signal, null);
     // cat on windows adds a \r\n at the end.
-    assert.equal(output.trim(), input.trim());
+    assert.strictEqual(output.trim(), input.trim());
   });
 }
 
diff --git a/test/parallel/test-child-process-validate-stdio.js b/test/parallel/test-child-process-validate-stdio.js
index 09d000467404b6..384efdf15a1425 100644
--- a/test/parallel/test-child-process-validate-stdio.js
+++ b/test/parallel/test-child-process-validate-stdio.js
@@ -19,10 +19,10 @@ assert.throws(function() {
 {
   const stdio1 = [];
   const result = _validateStdio(stdio1, false);
-  assert.equal(stdio1.length, 3);
-  assert.equal(result.hasOwnProperty('stdio'), true);
-  assert.equal(result.hasOwnProperty('ipc'), true);
-  assert.equal(result.hasOwnProperty('ipcFd'), true);
+  assert.strictEqual(stdio1.length, 3);
+  assert.strictEqual(result.hasOwnProperty('stdio'), true);
+  assert.strictEqual(result.hasOwnProperty('ipc'), true);
+  assert.strictEqual(result.hasOwnProperty('ipcFd'), true);
 }
 
 // should throw if stdio has ipc and sync is true
diff --git a/test/parallel/test-cli-eval-event.js b/test/parallel/test-cli-eval-event.js
index b19bdd38680f79..df356e50d37b66 100644
--- a/test/parallel/test-cli-eval-event.js
+++ b/test/parallel/test-cli-eval-event.js
@@ -10,6 +10,6 @@ const child = spawn(process.execPath, ['-e', `
 `]);
 
 child.once('exit', common.mustCall(function(exitCode, signalCode) {
-  assert.equal(exitCode, 0);
-  assert.equal(signalCode, null);
+  assert.strictEqual(exitCode, 0);
+  assert.strictEqual(signalCode, null);
 }));
diff --git a/test/parallel/test-cli-eval.js b/test/parallel/test-cli-eval.js
index e6a47a3175172e..0dc3cea6a243fd 100644
--- a/test/parallel/test-cli-eval.js
+++ b/test/parallel/test-cli-eval.js
@@ -19,15 +19,15 @@ var filename = __filename.replace(/\\/g, '/');
 // assert that nothing is written to stdout
 child.exec(nodejs + ' --eval 42',
     function(err, stdout, stderr) {
-      assert.equal(stdout, '');
-      assert.equal(stderr, '');
+      assert.strictEqual(stdout, '');
+      assert.strictEqual(stderr, '');
     });
 
 // assert that "42\n" is written to stderr
 child.exec(nodejs + ' --eval "console.error(42)"',
     function(err, stdout, stderr) {
-      assert.equal(stdout, '');
-      assert.equal(stderr, '42\n');
+      assert.strictEqual(stdout, '');
+      assert.strictEqual(stderr, '42\n');
     });
 
 // assert that the expected output is written to stdout
@@ -36,27 +36,27 @@ child.exec(nodejs + ' --eval "console.error(42)"',
 
   child.exec(cmd + '42',
       function(err, stdout, stderr) {
-        assert.equal(stdout, '42\n');
-        assert.equal(stderr, '');
+        assert.strictEqual(stdout, '42\n');
+        assert.strictEqual(stderr, '');
       });
 
   child.exec(cmd + "'[]'", common.mustCall(
       function(err, stdout, stderr) {
-        assert.equal(stdout, '[]\n');
-        assert.equal(stderr, '');
+        assert.strictEqual(stdout, '[]\n');
+        assert.strictEqual(stderr, '');
       }));
 });
 
 // assert that module loading works
 child.exec(nodejs + ' --eval "require(\'' + filename + '\')"',
     function(status, stdout, stderr) {
-      assert.equal(status.code, 42);
+      assert.strictEqual(status.code, 42);
     });
 
 // module path resolve bug, regression test
 child.exec(nodejs + ' --eval "require(\'./test/parallel/test-cli-eval.js\')"',
     function(status, stdout, stderr) {
-      assert.equal(status.code, 42);
+      assert.strictEqual(status.code, 42);
     });
 
 // Missing argument should not crash
@@ -67,26 +67,27 @@ child.exec(nodejs + ' -e', common.mustCall(function(status, stdout, stderr) {
 
 // empty program should do nothing
 child.exec(nodejs + ' -e ""', function(status, stdout, stderr) {
-  assert.equal(stdout, '');
-  assert.equal(stderr, '');
+  assert.strictEqual(stdout, '');
+  assert.strictEqual(stderr, '');
 });
 
 // "\\-42" should be interpreted as an escaped expression, not a switch
 child.exec(nodejs + ' -p "\\-42"',
     function(err, stdout, stderr) {
-      assert.equal(stdout, '-42\n');
-      assert.equal(stderr, '');
+      assert.strictEqual(stdout, '-42\n');
+      assert.strictEqual(stderr, '');
     });
 
 child.exec(nodejs + ' --use-strict -p process.execArgv',
     function(status, stdout, stderr) {
-      assert.equal(stdout, "[ '--use-strict', '-p', 'process.execArgv' ]\n");
+      assert.strictEqual(stdout,
+                         "[ '--use-strict', '-p', 'process.execArgv' ]\n");
     });
 
 // Regression test for https://github.com/nodejs/node/issues/3574
 const emptyFile = path.join(common.fixturesDir, 'empty.js');
 child.exec(nodejs + ` -e 'require("child_process").fork("${emptyFile}")'`,
     function(status, stdout, stderr) {
-      assert.equal(stdout, '');
-      assert.equal(stderr, '');
+      assert.strictEqual(stdout, '');
+      assert.strictEqual(stderr, '');
     });
diff --git a/test/parallel/test-cli-syntax.js b/test/parallel/test-cli-syntax.js
index 1118a63934d747..2f20ab0d11dcd9 100644
--- a/test/parallel/test-cli-syntax.js
+++ b/test/parallel/test-cli-syntax.js
@@ -30,9 +30,9 @@ var syntaxArgs = [
     var c = spawnSync(node, _args, {encoding: 'utf8'});
 
     // no output should be produced
-    assert.equal(c.stdout, '', 'stdout produced');
-    assert.equal(c.stderr, '', 'stderr produced');
-    assert.equal(c.status, 0, 'code == ' + c.status);
+    assert.strictEqual(c.stdout, '', 'stdout produced');
+    assert.strictEqual(c.stderr, '', 'stderr produced');
+    assert.strictEqual(c.status, 0, 'code == ' + c.status);
   });
 });
 
@@ -51,13 +51,13 @@ var syntaxArgs = [
     var c = spawnSync(node, _args, {encoding: 'utf8'});
 
     // no stdout should be produced
-    assert.equal(c.stdout, '', 'stdout produced');
+    assert.strictEqual(c.stdout, '', 'stdout produced');
 
     // stderr should have a syntax error message
     var match = c.stderr.match(/^SyntaxError: Unexpected identifier$/m);
     assert(match, 'stderr incorrect');
 
-    assert.equal(c.status, 1, 'code == ' + c.status);
+    assert.strictEqual(c.status, 1, 'code == ' + c.status);
   });
 });
 
@@ -74,12 +74,12 @@ var syntaxArgs = [
     var c = spawnSync(node, _args, {encoding: 'utf8'});
 
     // no stdout should be produced
-    assert.equal(c.stdout, '', 'stdout produced');
+    assert.strictEqual(c.stdout, '', 'stdout produced');
 
     // stderr should have a module not found error message
     var match = c.stderr.match(/^Error: Cannot find module/m);
     assert(match, 'stderr incorrect');
 
-    assert.equal(c.status, 1, 'code == ' + c.status);
+    assert.strictEqual(c.status, 1, 'code == ' + c.status);
   });
 });
diff --git a/test/parallel/test-cluster-send-deadlock.js b/test/parallel/test-cluster-send-deadlock.js
index 90b8c91695359b..fa3e1138248221 100644
--- a/test/parallel/test-cluster-send-deadlock.js
+++ b/test/parallel/test-cluster-send-deadlock.js
@@ -10,7 +10,7 @@ var net = require('net');
 if (cluster.isMaster) {
   var worker = cluster.fork();
   worker.on('exit', function(code, signal) {
-    assert.equal(code, 0, 'Worker exited with an error code');
+    assert.strictEqual(code, 0, 'Worker exited with an error code');
     assert(!signal, 'Worker exited by a signal');
     server.close();
   });
diff --git a/test/parallel/test-cluster-send-handle-twice.js b/test/parallel/test-cluster-send-handle-twice.js
index f1552d79265a0c..172a5563f306f5 100644
--- a/test/parallel/test-cluster-send-handle-twice.js
+++ b/test/parallel/test-cluster-send-handle-twice.js
@@ -14,7 +14,7 @@ if (cluster.isMaster) {
   for (var i = 0; i < workers.toStart; ++i) {
     var worker = cluster.fork();
     worker.on('exit', function(code, signal) {
-      assert.equal(code, 0, 'Worker exited with an error code');
+      assert.strictEqual(code, 0, 'Worker exited with an error code');
       assert(!signal, 'Worker exited by a signal');
     });
   }
diff --git a/test/parallel/test-cluster-setup-master-argv.js b/test/parallel/test-cluster-setup-master-argv.js
index e111ba9ffa1548..2df10ef79f0c69 100644
--- a/test/parallel/test-cluster-setup-master-argv.js
+++ b/test/parallel/test-cluster-setup-master-argv.js
@@ -1,16 +1,16 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var cluster = require('cluster');
+const common = require('../common');
+const assert = require('assert');
+const cluster = require('cluster');
 
 setTimeout(common.fail.bind(assert, 'setup not emitted'), 1000).unref();
 
-cluster.on('setup', function() {
+cluster.on('setup', common.mustCall(function() {
   var clusterArgs = cluster.settings.args;
   var realArgs = process.argv;
-  assert.equal(clusterArgs[clusterArgs.length - 1],
-               realArgs[realArgs.length - 1]);
-});
+  assert.strictEqual(clusterArgs[clusterArgs.length - 1],
+                     realArgs[realArgs.length - 1]);
+}));
 
 assert(process.argv[process.argv.length - 1] !== 'OMG,OMG');
 process.argv.push('OMG,OMG');
diff --git a/test/parallel/test-cluster-shared-handle-bind-error.js b/test/parallel/test-cluster-shared-handle-bind-error.js
index f5a08a1ed8481e..99573ef9539f56 100644
--- a/test/parallel/test-cluster-shared-handle-bind-error.js
+++ b/test/parallel/test-cluster-shared-handle-bind-error.js
@@ -12,7 +12,7 @@ if (cluster.isMaster) {
     var server = this;
     var worker = cluster.fork();
     worker.on('exit', common.mustCall(function(exitCode) {
-      assert.equal(exitCode, 0);
+      assert.strictEqual(exitCode, 0);
       server.close();
     }));
   });
@@ -20,7 +20,7 @@ if (cluster.isMaster) {
   var s = net.createServer(common.fail);
   s.listen(common.PORT, common.fail.bind(null, 'listen should have failed'));
   s.on('error', common.mustCall(function(err) {
-    assert.equal(err.code, 'EADDRINUSE');
+    assert.strictEqual(err.code, 'EADDRINUSE');
     process.disconnect();
   }));
 }
diff --git a/test/parallel/test-cluster-shared-handle-bind-privileged-port.js b/test/parallel/test-cluster-shared-handle-bind-privileged-port.js
index 9dc0e4ea773137..c58aa5393519ad 100644
--- a/test/parallel/test-cluster-shared-handle-bind-privileged-port.js
+++ b/test/parallel/test-cluster-shared-handle-bind-privileged-port.js
@@ -1,8 +1,8 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var cluster = require('cluster');
-var net = require('net');
+const common = require('../common');
+const assert = require('assert');
+const cluster = require('cluster');
+const net = require('net');
 
 if (common.isWindows) {
   common.skip('not reliable on Windows');
@@ -18,13 +18,13 @@ if (cluster.isMaster) {
   // Master opens and binds the socket and shares it with the worker.
   cluster.schedulingPolicy = cluster.SCHED_NONE;
   cluster.fork().on('exit', common.mustCall(function(exitCode) {
-    assert.equal(exitCode, 0);
+    assert.strictEqual(exitCode, 0);
   }));
 } else {
-  var s = net.createServer(common.fail);
+  const s = net.createServer(common.fail);
   s.listen(42, common.fail.bind(null, 'listen should have failed'));
   s.on('error', common.mustCall(function(err) {
-    assert.equal(err.code, 'EACCES');
+    assert.strictEqual(err.code, 'EACCES');
     process.disconnect();
   }));
 }
diff --git a/test/parallel/test-cluster-worker-events.js b/test/parallel/test-cluster-worker-events.js
index 0efad0e963e35c..561b969607f39a 100644
--- a/test/parallel/test-cluster-worker-events.js
+++ b/test/parallel/test-cluster-worker-events.js
@@ -10,7 +10,7 @@ if (cluster.isMaster) {
   var worker = cluster.fork();
 
   worker.on('exit', function(code) {
-    assert.equal(code, OK);
+    assert.strictEqual(code, OK);
     process.exit(0);
   });
 
@@ -49,7 +49,7 @@ function check(m) {
   assert.deepEqual(messages[0], messages[1]);
 
   cluster.worker.once('error', function(e) {
-    assert.equal(e, 'HI');
+    assert.strictEqual(e, 'HI');
     process.exit(OK);
   });
 
diff --git a/test/parallel/test-console-instance.js b/test/parallel/test-console-instance.js
index b8d9880865530b..4d2727d96b1a55 100644
--- a/test/parallel/test-console-instance.js
+++ b/test/parallel/test-console-instance.js
@@ -15,7 +15,7 @@ process.stdout.write = process.stderr.write = function() {
 };
 
 // make sure that the "Console" function exists
-assert.equal('function', typeof Console);
+assert.strictEqual('function', typeof Console);
 
 // make sure that the Console constructor throws
 // when not given a writable stream instance
@@ -35,7 +35,7 @@ out.write = err.write = function(d) {};
 var c = new Console(out, err);
 
 out.write = err.write = function(d) {
-  assert.equal(d, 'test\n');
+  assert.strictEqual(d, 'test\n');
   called = true;
 };
 
@@ -48,7 +48,7 @@ c.error('test');
 assert(called);
 
 out.write = function(d) {
-  assert.equal('{ foo: 1 }\n', d);
+  assert.strictEqual('{ foo: 1 }\n', d);
   called = true;
 };
 
@@ -60,10 +60,10 @@ assert(called);
 called = 0;
 out.write = function(d) {
   called++;
-  assert.equal(d, called + ' ' + (called - 1) + ' [ 1, 2, 3 ]\n');
+  assert.strictEqual(d, called + ' ' + (called - 1) + ' [ 1, 2, 3 ]\n');
 };
 [1, 2, 3].forEach(c.log);
-assert.equal(3, called);
+assert.strictEqual(3, called);
 
 // Console() detects if it is called without `new` keyword
 assert.doesNotThrow(function() {
diff --git a/test/parallel/test-crypto-authenticated.js b/test/parallel/test-crypto-authenticated.js
index 19643a9d80f2f3..191a5c58604c8c 100644
--- a/test/parallel/test-crypto-authenticated.js
+++ b/test/parallel/test-crypto-authenticated.js
@@ -352,7 +352,7 @@ for (const i in TEST_CASES) {
     var msg = decrypt.update(test.ct, 'hex', outputEncoding);
     if (!test.tampered) {
       msg += decrypt.final(outputEncoding);
-      assert.equal(msg, test.plain);
+      assert.strictEqual(msg, test.plain);
     } else {
       // assert that final throws if input data could not be verified!
       assert.throws(function() { decrypt.final('ascii'); }, / auth/);
diff --git a/test/parallel/test-crypto-binary-default.js b/test/parallel/test-crypto-binary-default.js
index da29d690645683..b489c0c8c23fed 100644
--- a/test/parallel/test-crypto-binary-default.js
+++ b/test/parallel/test-crypto-binary-default.js
@@ -3,30 +3,30 @@
 // to use buffers by default.
 
 
-var common = require('../common');
-var assert = require('assert');
-var constants = require('constants');
+const common = require('../common');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var crypto = require('crypto');
-var tls = require('tls');
 
-crypto.DEFAULT_ENCODING = 'binary';
+const assert = require('assert');
+const constants = require('constants');
+const crypto = require('crypto');
+const fs = require('fs');
+const path = require('path');
+const tls = require('tls');
 
-var fs = require('fs');
-var path = require('path');
+crypto.DEFAULT_ENCODING = 'binary';
 
 // Test Certificates
-var certPem = fs.readFileSync(common.fixturesDir + '/test_cert.pem', 'ascii');
-var certPfx = fs.readFileSync(common.fixturesDir + '/test_cert.pfx');
-var keyPem = fs.readFileSync(common.fixturesDir + '/test_key.pem', 'ascii');
-var rsaPubPem = fs.readFileSync(common.fixturesDir + '/test_rsa_pubkey.pem',
-    'ascii');
-var rsaKeyPem = fs.readFileSync(common.fixturesDir + '/test_rsa_privkey.pem',
-    'ascii');
+const certPem = fs.readFileSync(common.fixturesDir + '/test_cert.pem', 'ascii');
+const certPfx = fs.readFileSync(common.fixturesDir + '/test_cert.pfx');
+const keyPem = fs.readFileSync(common.fixturesDir + '/test_key.pem', 'ascii');
+const rsaPubPem = fs.readFileSync(common.fixturesDir + '/test_rsa_pubkey.pem',
+                                  'ascii');
+const rsaKeyPem = fs.readFileSync(common.fixturesDir + '/test_rsa_privkey.pem',
+                                  'ascii');
 
 // PFX tests
 assert.doesNotThrow(function() {
@@ -35,22 +35,22 @@ assert.doesNotThrow(function() {
 
 assert.throws(function() {
   tls.createSecureContext({pfx: certPfx});
-}, 'mac verify failure');
+}, /^Error: mac verify failure$/);
 
 assert.throws(function() {
   tls.createSecureContext({pfx: certPfx, passphrase: 'test'});
-}, 'mac verify failure');
+}, /^Error: mac verify failure$/);
 
 assert.throws(function() {
   tls.createSecureContext({pfx: 'sample', passphrase: 'test'});
-}, 'not enough data');
+}, /^Error: not enough data$/);
 
 // Test HMAC
 const hmacHash = crypto.createHmac('sha1', 'Node')
                        .update('some data')
                        .update('to hmac')
                        .digest('hex');
-assert.equal(hmacHash, '19fd6e1ba73d9ed2224dd5094a71babe85d9a892', 'test HMAC');
+assert.strictEqual(hmacHash, '19fd6e1ba73d9ed2224dd5094a71babe85d9a892');
 
 // Test HMAC-SHA-* (rfc 4231 Test Cases)
 var rfc4231 = [
@@ -207,9 +207,11 @@ for (let i = 0, l = rfc4231.length; i < l; i++) {
     if (rfc4231[i]['truncate']) {
       result = result.substr(0, 32); // first 128 bits == 32 hex chars
     }
-    assert.equal(rfc4231[i]['hmac'][hash],
-                 result,
-                 'Test HMAC-' + hash + ': Test case ' + (i + 1) + ' rfc 4231');
+    assert.strictEqual(
+      rfc4231[i]['hmac'][hash],
+      result,
+      `Test HMAC-${hash}: Test case ${i + 1} rfc 4231`
+    );
   }
 }
 
@@ -328,7 +330,7 @@ for (let i = 0, l = rfc2202_md5.length; i < l; i++) {
                  crypto.createHmac('md5', rfc2202_md5[i]['key'])
                      .update(rfc2202_md5[i]['data'])
                      .digest('hex'),
-                 'Test HMAC-MD5 : Test case ' + (i + 1) + ' rfc 2202');
+                 `Test HMAC-MD5 : Test case ${i + 1} rfc 2202`);
   }
 }
 for (let i = 0, l = rfc2202_sha1.length; i < l; i++) {
@@ -336,7 +338,7 @@ for (let i = 0, l = rfc2202_sha1.length; i < l; i++) {
                crypto.createHmac('sha1', rfc2202_sha1[i]['key'])
                    .update(rfc2202_sha1[i]['data'])
                    .digest('hex'),
-               'Test HMAC-SHA1 : Test case ' + (i + 1) + ' rfc 2202');
+               `Test HMAC-SHA1 : Test case ${i + 1} rfc 2202`);
 }
 
 // Test hashing
@@ -347,24 +349,27 @@ var a4 = crypto.createHash('sha1').update('Test123').digest('buffer');
 
 if (!common.hasFipsCrypto) {
   var a0 = crypto.createHash('md5').update('Test123').digest('binary');
-  assert.equal(
+  assert.strictEqual(
     a0,
     'h\u00ea\u00cb\u0097\u00d8o\fF!\u00fa+\u000e\u0017\u00ca\u00bd\u008c',
     'Test MD5 as binary'
   );
 }
 
-assert.equal(a1, '8308651804facb7b9af8ffc53a33a22d6a1c8ac2', 'Test SHA1');
+assert.strictEqual(a1, '8308651804facb7b9af8ffc53a33a22d6a1c8ac2', 'Test SHA1');
 
-assert.equal(a2, '2bX1jws4GYKTlxhloUB09Z66PoJZW+y+hq5R8dnx9l4=',
-             'Test SHA256 as base64');
+assert.strictEqual(a2, '2bX1jws4GYKTlxhloUB09Z66PoJZW+y+hq5R8dnx9l4=',
+                   'Test SHA256 as base64');
 
-assert.equal(a3, '\u00c1(4\u00f1\u0003\u001fd\u0097!O\'\u00d4C/&Qz\u00d4' +
-                 '\u0094\u0015l\u00b8\u008dQ+\u00db\u001d\u00c4\u00b5}\u00b2' +
-                 '\u00d6\u0092\u00a3\u00df\u00a2i\u00a1\u009b\n\n*\u000f' +
-                 '\u00d7\u00d6\u00a2\u00a8\u0085\u00e3<\u0083\u009c\u0093' +
-                 '\u00c2\u0006\u00da0\u00a1\u00879(G\u00ed\'',
-             'Test SHA512 as assumed binary');
+assert.strictEqual(
+  a3,
+  '\u00c1(4\u00f1\u0003\u001fd\u0097!O\'\u00d4C/&Qz\u00d4' +
+  '\u0094\u0015l\u00b8\u008dQ+\u00db\u001d\u00c4\u00b5}\u00b2' +
+  '\u00d6\u0092\u00a3\u00df\u00a2i\u00a1\u009b\n\n*\u000f' +
+  '\u00d7\u00d6\u00a2\u00a8\u0085\u00e3<\u0083\u009c\u0093' +
+  '\u00c2\u0006\u00da0\u00a1\u00879(G\u00ed\'',
+  'Test SHA512 as assumed binary'
+);
 
 assert.deepEqual(a4,
                  new Buffer('8308651804facb7b9af8ffc53a33a22d6a1c8ac2', 'hex'),
@@ -373,7 +378,7 @@ assert.deepEqual(a4,
 // Test multiple updates to same hash
 var h1 = crypto.createHash('sha1').update('Test123').digest('hex');
 var h2 = crypto.createHash('sha1').update('Test').update('123').digest('hex');
-assert.equal(h1, h2, 'multipled updates');
+assert.strictEqual(h1, h2, 'multipled updates');
 
 // Test hashing for binary files
 var fn = path.join(common.fixturesDir, 'sample.png');
@@ -382,16 +387,18 @@ var fileStream = fs.createReadStream(fn);
 fileStream.on('data', function(data) {
   sha1Hash.update(data);
 });
-fileStream.on('close', function() {
-  assert.equal(sha1Hash.digest('hex'),
-               '22723e553129a336ad96e10f6aecdf0f45e4149e',
-               'Test SHA1 of sample.png');
-});
+fileStream.on('close', common.mustCall(function() {
+  assert.strictEqual(
+    sha1Hash.digest('hex'),
+    '22723e553129a336ad96e10f6aecdf0f45e4149e',
+    'Test SHA1 of sample.png'
+  );
+}));
 
 // Issue #2227: unknown digest method should throw an error.
 assert.throws(function() {
   crypto.createHash('xyzzy');
-});
+}, /^Error: Digest method not supported$/);
 
 // Test signing and verifying
 var s1 = crypto.createSign('RSA-SHA1')
@@ -437,7 +444,7 @@ function testCipher1(key) {
   var txt = decipher.update(ciph, 'hex', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption');
+  assert.strictEqual(txt, plaintext, 'encryption and decryption');
 }
 
 
@@ -459,7 +466,7 @@ function testCipher2(key) {
   var txt = decipher.update(ciph, 'base64', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with Base64');
+  assert.strictEqual(txt, plaintext, 'encryption and decryption with Base64');
 }
 
 
@@ -477,7 +484,8 @@ function testCipher3(key, iv) {
   var txt = decipher.update(ciph, 'hex', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with key and iv');
+  assert.strictEqual(txt, plaintext,
+                     'encryption and decryption with key and iv');
 }
 
 
@@ -495,7 +503,8 @@ function testCipher4(key, iv) {
   var txt = decipher.update(ciph, 'buffer', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with key and iv');
+  assert.strictEqual(txt, plaintext,
+                     'encryption and decryption with key and iv');
 }
 
 if (!common.hasFipsCrypto) {
@@ -517,7 +526,7 @@ testCipher4(new Buffer('0123456789abcd0123456789'), new Buffer('12345678'));
 // update() should only take buffers / strings
 assert.throws(function() {
   crypto.createHash('sha1').update({foo: 'bar'});
-}, /buffer/);
+}, /^TypeError: Not a string or buffer$/);
 
 
 // Test Diffie-Hellman with two parties sharing a secret,
@@ -530,7 +539,7 @@ var key2 = dh2.generateKeys('hex');
 var secret1 = dh1.computeSecret(key2, 'hex', 'base64');
 var secret2 = dh2.computeSecret(key1, 'binary', 'buffer');
 
-assert.equal(secret1, secret2.toString('base64'));
+assert.strictEqual(secret1, secret2.toString('base64'));
 
 // Create "another dh1" using generated keys from dh1,
 // and compute secret again
@@ -539,14 +548,14 @@ var privkey1 = dh1.getPrivateKey();
 dh3.setPublicKey(key1);
 dh3.setPrivateKey(privkey1);
 
-assert.equal(dh1.getPrime(), dh3.getPrime());
-assert.equal(dh1.getGenerator(), dh3.getGenerator());
-assert.equal(dh1.getPublicKey(), dh3.getPublicKey());
-assert.equal(dh1.getPrivateKey(), dh3.getPrivateKey());
+assert.strictEqual(dh1.getPrime(), dh3.getPrime());
+assert.strictEqual(dh1.getGenerator(), dh3.getGenerator());
+assert.strictEqual(dh1.getPublicKey(), dh3.getPublicKey());
+assert.strictEqual(dh1.getPrivateKey(), dh3.getPrivateKey());
 
 var secret3 = dh3.computeSecret(key2, 'hex', 'base64');
 
-assert.equal(secret1, secret3);
+assert.strictEqual(secret1, secret3);
 
 // https://github.com/joyent/node/issues/2338
 var p = 'FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74' +
@@ -554,22 +563,24 @@ var p = 'FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74' +
         '4FE1356D6D51C245E485B576625E7EC6F44C42E9A637ED6B0BFF5CB6F406B7ED' +
         'EE386BFB5A899FA5AE9F24117C4B1FE649286651ECE65381FFFFFFFFFFFFFFFF';
 var d = crypto.createDiffieHellman(p, 'hex');
-assert.equal(d.verifyError, constants.DH_NOT_SUITABLE_GENERATOR);
+assert.strictEqual(d.verifyError, constants.DH_NOT_SUITABLE_GENERATOR);
 
 // Test RSA key signing/verification
 var rsaSign = crypto.createSign('RSA-SHA1');
 var rsaVerify = crypto.createVerify('RSA-SHA1');
-assert.ok(rsaSign);
-assert.ok(rsaVerify);
+assert.ok(rsaSign instanceof crypto.Sign);
+assert.ok(rsaVerify instanceof crypto.Verify);
 
 rsaSign.update(rsaPubPem);
 var rsaSignature = rsaSign.sign(rsaKeyPem, 'hex');
-assert.equal(rsaSignature,
-             '5c50e3145c4e2497aadb0eabc83b342d0b0021ece0d4c4a064b7c' +
-             '8f020d7e2688b122bfb54c724ac9ee169f83f66d2fe90abeb95e8' +
-             'e1290e7e177152a4de3d944cf7d4883114a20ed0f78e70e25ef0f' +
-             '60f06b858e6af42a2f276ede95bbc6bc9a9bbdda15bd663186a6f' +
-             '40819a7af19e577bb2efa5e579a1f5ce8a0d4ca8b8f6');
+assert.strictEqual(
+  rsaSignature,
+  '5c50e3145c4e2497aadb0eabc83b342d0b0021ece0d4c4a064b7c' +
+  '8f020d7e2688b122bfb54c724ac9ee169f83f66d2fe90abeb95e8' +
+  'e1290e7e177152a4de3d944cf7d4883114a20ed0f78e70e25ef0f' +
+  '60f06b858e6af42a2f276ede95bbc6bc9a9bbdda15bd663186a6f' +
+  '40819a7af19e577bb2efa5e579a1f5ce8a0d4ca8b8f6'
+);
 
 rsaVerify.update(rsaPubPem);
 assert.strictEqual(rsaVerify.verify(rsaPubPem, rsaSignature, 'hex'), true);
@@ -636,12 +647,13 @@ assert.strictEqual(rsaVerify.verify(rsaPubPem, rsaSignature, 'hex'), true);
 // Test PBKDF2 with RFC 6070 test vectors (except #4)
 //
 function testPBKDF2(password, salt, iterations, keylen, expected) {
-  var actual = crypto.pbkdf2Sync(password, salt, iterations, keylen);
-  assert.equal(actual, expected);
+  const actual = crypto.pbkdf2Sync(password, salt, iterations, keylen);
+  assert.strictEqual(actual, expected);
 
-  crypto.pbkdf2(password, salt, iterations, keylen, function(err, actual) {
-    assert.equal(actual, expected);
+  const cb = common.mustCall((err, actual) => {
+    assert.strictEqual(actual, expected);
   });
+  crypto.pbkdf2(password, salt, iterations, keylen, cb);
 }
 
 
diff --git a/test/parallel/test-crypto-certificate.js b/test/parallel/test-crypto-certificate.js
index 66a5da04073825..1dfb2c73b0eca5 100644
--- a/test/parallel/test-crypto-certificate.js
+++ b/test/parallel/test-crypto-certificate.js
@@ -19,20 +19,20 @@ var spkacPem = fs.readFileSync(common.fixturesDir + '/spkac.pem');
 
 var certificate = new crypto.Certificate();
 
-assert.equal(certificate.verifySpkac(spkacValid), true);
-assert.equal(certificate.verifySpkac(spkacFail), false);
+assert.strictEqual(certificate.verifySpkac(spkacValid), true);
+assert.strictEqual(certificate.verifySpkac(spkacFail), false);
 
-assert.equal(
+assert.strictEqual(
   stripLineEndings(certificate.exportPublicKey(spkacValid).toString('utf8')),
   stripLineEndings(spkacPem.toString('utf8'))
 );
-assert.equal(certificate.exportPublicKey(spkacFail), '');
+assert.strictEqual(certificate.exportPublicKey(spkacFail), '');
 
-assert.equal(
+assert.strictEqual(
   certificate.exportChallenge(spkacValid).toString('utf8'),
   'fb9ab814-6677-42a4-a60c-f905d1a6924d'
 );
-assert.equal(certificate.exportChallenge(spkacFail), '');
+assert.strictEqual(certificate.exportChallenge(spkacFail), '');
 
 function stripLineEndings(obj) {
   return obj.replace(/\n/g, '');
diff --git a/test/parallel/test-crypto-cipher-decipher.js b/test/parallel/test-crypto-cipher-decipher.js
index 2f03aa5db4db52..4ba5dab9b9354a 100644
--- a/test/parallel/test-crypto-cipher-decipher.js
+++ b/test/parallel/test-crypto-cipher-decipher.js
@@ -27,7 +27,7 @@ function testCipher1(key) {
   var txt = decipher.update(ciph, 'hex', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption');
+  assert.strictEqual(txt, plaintext, 'encryption and decryption');
 
   // streaming cipher interface
   // NB: In real life, it's not guaranteed that you can get all of it
@@ -41,7 +41,7 @@ function testCipher1(key) {
   dStream.end(ciph);
   txt = dStream.read().toString('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with streams');
+  assert.strictEqual(txt, plaintext, 'encryption and decryption with streams');
 }
 
 
@@ -63,7 +63,7 @@ function testCipher2(key) {
   var txt = decipher.update(ciph, 'base64', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with Base64');
+  assert.strictEqual(txt, plaintext, 'encryption and decryption with Base64');
 }
 
 testCipher1('MySecretKey123');
diff --git a/test/parallel/test-crypto-cipheriv-decipheriv.js b/test/parallel/test-crypto-cipheriv-decipheriv.js
index 4462ee0a5fc34a..3d437391cb6a39 100644
--- a/test/parallel/test-crypto-cipheriv-decipheriv.js
+++ b/test/parallel/test-crypto-cipheriv-decipheriv.js
@@ -1,60 +1,60 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var crypto = require('crypto');
+const crypto = require('crypto');
 
 function testCipher1(key, iv) {
   // Test encyrption and decryption with explicit key and iv
-  var plaintext =
-      '32|RmVZZkFUVmpRRkp0TmJaUm56ZU9qcnJkaXNNWVNpTTU*|iXmckfRWZBGWWELw' +
-      'eCBsThSsfUHLeRe0KCsK8ooHgxie0zOINpXxfZi/oNG7uq9JWFVCk70gfzQH8ZUJ' +
-      'jAfaFg**';
-  var cipher = crypto.createCipheriv('des-ede3-cbc', key, iv);
-  var ciph = cipher.update(plaintext, 'utf8', 'hex');
+  const plaintext =
+          '32|RmVZZkFUVmpRRkp0TmJaUm56ZU9qcnJkaXNNWVNpTTU*|iXmckfRWZBGWWELw' +
+          'eCBsThSsfUHLeRe0KCsK8ooHgxie0zOINpXxfZi/oNG7uq9JWFVCk70gfzQH8ZUJ' +
+          'jAfaFg**';
+  const cipher = crypto.createCipheriv('des-ede3-cbc', key, iv);
+  let ciph = cipher.update(plaintext, 'utf8', 'hex');
   ciph += cipher.final('hex');
 
-  var decipher = crypto.createDecipheriv('des-ede3-cbc', key, iv);
-  var txt = decipher.update(ciph, 'hex', 'utf8');
+  const decipher = crypto.createDecipheriv('des-ede3-cbc', key, iv);
+  let txt = decipher.update(ciph, 'hex', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with key and iv');
+  assert.strictEqual(txt, plaintext, 'encryption/decryption with key and iv');
 
   // streaming cipher interface
   // NB: In real life, it's not guaranteed that you can get all of it
   // in a single read() like this.  But in this case, we know it's
   // quite small, so there's no harm.
-  var cStream = crypto.createCipheriv('des-ede3-cbc', key, iv);
+  const cStream = crypto.createCipheriv('des-ede3-cbc', key, iv);
   cStream.end(plaintext);
   ciph = cStream.read();
 
-  var dStream = crypto.createDecipheriv('des-ede3-cbc', key, iv);
+  const dStream = crypto.createDecipheriv('des-ede3-cbc', key, iv);
   dStream.end(ciph);
   txt = dStream.read().toString('utf8');
 
-  assert.equal(txt, plaintext, 'streaming cipher iv');
+  assert.strictEqual(txt, plaintext, 'streaming cipher iv');
 }
 
 
 function testCipher2(key, iv) {
   // Test encyrption and decryption with explicit key and iv
-  var plaintext =
-      '32|RmVZZkFUVmpRRkp0TmJaUm56ZU9qcnJkaXNNWVNpTTU*|iXmckfRWZBGWWELw' +
-      'eCBsThSsfUHLeRe0KCsK8ooHgxie0zOINpXxfZi/oNG7uq9JWFVCk70gfzQH8ZUJ' +
-      'jAfaFg**';
-  var cipher = crypto.createCipheriv('des-ede3-cbc', key, iv);
-  var ciph = cipher.update(plaintext, 'utf8', 'buffer');
+  const plaintext =
+          '32|RmVZZkFUVmpRRkp0TmJaUm56ZU9qcnJkaXNNWVNpTTU*|iXmckfRWZBGWWELw' +
+          'eCBsThSsfUHLeRe0KCsK8ooHgxie0zOINpXxfZi/oNG7uq9JWFVCk70gfzQH8ZUJ' +
+          'jAfaFg**';
+  const cipher = crypto.createCipheriv('des-ede3-cbc', key, iv);
+  let ciph = cipher.update(plaintext, 'utf8', 'buffer');
   ciph = Buffer.concat([ciph, cipher.final('buffer')]);
 
-  var decipher = crypto.createDecipheriv('des-ede3-cbc', key, iv);
-  var txt = decipher.update(ciph, 'buffer', 'utf8');
+  const decipher = crypto.createDecipheriv('des-ede3-cbc', key, iv);
+  let txt = decipher.update(ciph, 'buffer', 'utf8');
   txt += decipher.final('utf8');
 
-  assert.equal(txt, plaintext, 'encryption and decryption with key and iv');
+  assert.strictEqual(txt, plaintext, 'encryption/decryption with key and iv');
 }
 
 testCipher1('0123456789abcd0123456789', '12345678');
diff --git a/test/parallel/test-crypto-domain.js b/test/parallel/test-crypto-domain.js
index 9bb6c0229648e7..ec9985719933d3 100644
--- a/test/parallel/test-crypto-domain.js
+++ b/test/parallel/test-crypto-domain.js
@@ -13,7 +13,7 @@ function test(fn) {
   var ex = new Error('BAM');
   var d = domain.create();
   d.on('error', common.mustCall(function(err) {
-    assert.equal(err, ex);
+    assert.strictEqual(err, ex);
   }));
   var cb = common.mustCall(function() {
     throw ex;
diff --git a/test/parallel/test-crypto-ecb.js b/test/parallel/test-crypto-ecb.js
index dbdb486e9bcf7f..655246d0586cbf 100644
--- a/test/parallel/test-crypto-ecb.js
+++ b/test/parallel/test-crypto-ecb.js
@@ -1,6 +1,6 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
@@ -10,24 +10,25 @@ if (common.hasFipsCrypto) {
   common.skip('BF-ECB is not FIPS 140-2 compatible');
   return;
 }
-var crypto = require('crypto');
+const crypto = require('crypto');
 
 crypto.DEFAULT_ENCODING = 'buffer';
 
 // Testing whether EVP_CipherInit_ex is functioning correctly.
 // Reference: bug#1997
 
-(function() {
-  var encrypt = crypto.createCipheriv('BF-ECB', 'SomeRandomBlahz0c5GZVnR', '');
-  var hex = encrypt.update('Hello World!', 'ascii', 'hex');
+{
+  const encrypt =
+    crypto.createCipheriv('BF-ECB', 'SomeRandomBlahz0c5GZVnR', '');
+  let hex = encrypt.update('Hello World!', 'ascii', 'hex');
   hex += encrypt.final('hex');
-  assert.equal(hex.toUpperCase(), '6D385F424AAB0CFBF0BB86E07FFB7D71');
-}());
+  assert.strictEqual(hex.toUpperCase(), '6D385F424AAB0CFBF0BB86E07FFB7D71');
+}
 
-(function() {
-  var decrypt = crypto.createDecipheriv('BF-ECB', 'SomeRandomBlahz0c5GZVnR',
-      '');
-  var msg = decrypt.update('6D385F424AAB0CFBF0BB86E07FFB7D71', 'hex', 'ascii');
+{
+  const decrypt =
+    crypto.createDecipheriv('BF-ECB', 'SomeRandomBlahz0c5GZVnR', '');
+  let msg = decrypt.update('6D385F424AAB0CFBF0BB86E07FFB7D71', 'hex', 'ascii');
   msg += decrypt.final('ascii');
-  assert.equal(msg, 'Hello World!');
-}());
+  assert.strictEqual(msg, 'Hello World!');
+}
diff --git a/test/parallel/test-crypto-padding.js b/test/parallel/test-crypto-padding.js
index a6174728735601..b0cbcf126c4723 100644
--- a/test/parallel/test-crypto-padding.js
+++ b/test/parallel/test-crypto-padding.js
@@ -74,16 +74,18 @@ function dec(encd, pad) {
  * Test encryption
  */
 
-assert.equal(enc(ODD_LENGTH_PLAIN, true), ODD_LENGTH_ENCRYPTED);
-assert.equal(enc(EVEN_LENGTH_PLAIN, true), EVEN_LENGTH_ENCRYPTED);
+assert.strictEqual(enc(ODD_LENGTH_PLAIN, true), ODD_LENGTH_ENCRYPTED);
+assert.strictEqual(enc(EVEN_LENGTH_PLAIN, true), EVEN_LENGTH_ENCRYPTED);
 
 assert.throws(function() {
   // input must have block length %
   enc(ODD_LENGTH_PLAIN, false);
-});
+}, /data not multiple of block length/);
 
 assert.doesNotThrow(function() {
-  assert.equal(enc(EVEN_LENGTH_PLAIN, false), EVEN_LENGTH_ENCRYPTED_NOPAD);
+  assert.strictEqual(
+    enc(EVEN_LENGTH_PLAIN, false), EVEN_LENGTH_ENCRYPTED_NOPAD
+  );
 });
 
 
@@ -91,21 +93,25 @@ assert.doesNotThrow(function() {
  * Test decryption
  */
 
-assert.equal(dec(ODD_LENGTH_ENCRYPTED, true), ODD_LENGTH_PLAIN);
-assert.equal(dec(EVEN_LENGTH_ENCRYPTED, true), EVEN_LENGTH_PLAIN);
+assert.strictEqual(dec(ODD_LENGTH_ENCRYPTED, true), ODD_LENGTH_PLAIN);
+assert.strictEqual(dec(EVEN_LENGTH_ENCRYPTED, true), EVEN_LENGTH_PLAIN);
 
 assert.doesNotThrow(function() {
   // returns including original padding
-  assert.equal(dec(ODD_LENGTH_ENCRYPTED, false).length, 32);
-  assert.equal(dec(EVEN_LENGTH_ENCRYPTED, false).length, 48);
+  assert.strictEqual(dec(ODD_LENGTH_ENCRYPTED, false).length, 32);
+  assert.strictEqual(dec(EVEN_LENGTH_ENCRYPTED, false).length, 48);
 });
 
 assert.throws(function() {
   // must have at least 1 byte of padding (PKCS):
-  assert.equal(dec(EVEN_LENGTH_ENCRYPTED_NOPAD, true), EVEN_LENGTH_PLAIN);
-});
+  assert.strictEqual(
+    dec(EVEN_LENGTH_ENCRYPTED_NOPAD, true), EVEN_LENGTH_PLAIN
+  );
+}, /bad decrypt/);
 
 assert.doesNotThrow(function() {
   // no-pad encrypted string should return the same:
-  assert.equal(dec(EVEN_LENGTH_ENCRYPTED_NOPAD, false), EVEN_LENGTH_PLAIN);
+  assert.strictEqual(
+    dec(EVEN_LENGTH_ENCRYPTED_NOPAD, false), EVEN_LENGTH_PLAIN
+  );
 });
diff --git a/test/parallel/test-crypto-sign-verify.js b/test/parallel/test-crypto-sign-verify.js
index e8d892a8d63f15..29f6683e2ee162 100644
--- a/test/parallel/test-crypto-sign-verify.js
+++ b/test/parallel/test-crypto-sign-verify.js
@@ -21,7 +21,7 @@ var keyPem = fs.readFileSync(common.fixturesDir + '/test_key.pem', 'ascii');
   let s1stream = crypto.createSign('RSA-SHA1');
   s1stream.end('Test123');
   s1stream = s1stream.sign(keyPem, 'base64');
-  assert.equal(s1, s1stream, 'Stream produces same output');
+  assert.strictEqual(s1, s1stream, 'Stream produces same output');
 
   const verified = crypto.createVerify('RSA-SHA1')
                          .update('Test')
@@ -37,7 +37,7 @@ var keyPem = fs.readFileSync(common.fixturesDir + '/test_key.pem', 'ascii');
   let s2stream = crypto.createSign('RSA-SHA256');
   s2stream.end('Test123');
   s2stream = s2stream.sign(keyPem, 'binary');
-  assert.equal(s2, s2stream, 'Stream produces same output');
+  assert.strictEqual(s2, s2stream, 'Stream produces same output');
 
   let verified = crypto.createVerify('RSA-SHA256')
                        .update('Test')
diff --git a/test/parallel/test-crypto-stream.js b/test/parallel/test-crypto-stream.js
index 652b81eab44878..6134c03b62443c 100644
--- a/test/parallel/test-crypto-stream.js
+++ b/test/parallel/test-crypto-stream.js
@@ -30,8 +30,10 @@ if (!common.hasFipsCrypto) {
   // Create an md5 hash of "Hallo world"
   var hasher1 = crypto.createHash('md5');
   hasher1.pipe(new Stream2buffer(common.mustCall(function end(err, hash) {
-    assert.equal(err, null);
-    assert.equal(hash.toString('hex'), '06460dadb35d3d503047ce750ceb2d07');
+    assert.strictEqual(err, null);
+    assert.strictEqual(
+      hash.toString('hex'), '06460dadb35d3d503047ce750ceb2d07'
+    );
   })));
   hasher1.end('Hallo world');
 
diff --git a/test/parallel/test-crypto.js b/test/parallel/test-crypto.js
index bf87900875b7c4..a325ee131cbb2e 100644
--- a/test/parallel/test-crypto.js
+++ b/test/parallel/test-crypto.js
@@ -1,34 +1,33 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var util = require('util');
+const common = require('../common');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var crypto = require('crypto');
 
-crypto.DEFAULT_ENCODING = 'buffer';
+const assert = require('assert');
+const crypto = require('crypto');
+const fs = require('fs');
+const tls = require('tls');
 
-var fs = require('fs');
+crypto.DEFAULT_ENCODING = 'buffer';
 
 // Test Certificates
-var caPem = fs.readFileSync(common.fixturesDir + '/test_ca.pem', 'ascii');
-var certPem = fs.readFileSync(common.fixturesDir + '/test_cert.pem', 'ascii');
-var certPfx = fs.readFileSync(common.fixturesDir + '/test_cert.pfx');
-var keyPem = fs.readFileSync(common.fixturesDir + '/test_key.pem', 'ascii');
-var tls = require('tls');
+const caPem = fs.readFileSync(common.fixturesDir + '/test_ca.pem', 'ascii');
+const certPem = fs.readFileSync(common.fixturesDir + '/test_cert.pem', 'ascii');
+const certPfx = fs.readFileSync(common.fixturesDir + '/test_cert.pfx');
+const keyPem = fs.readFileSync(common.fixturesDir + '/test_key.pem', 'ascii');
 
 // 'this' safety
 // https://github.com/joyent/node/issues/6690
 assert.throws(function() {
-  var options = {key: keyPem, cert: certPem, ca: caPem};
-  var credentials = crypto.createCredentials(options);
-  var context = credentials.context;
-  var notcontext = { setOptions: context.setOptions, setKey: context.setKey };
-  crypto.createCredentials({ secureOptions: 1 }, notcontext);
-}, TypeError);
+  const options = {key: keyPem, cert: certPem, ca: caPem};
+  const credentials = tls.createSecureContext(options);
+  const context = credentials.context;
+  const notcontext = { setOptions: context.setOptions, setKey: context.setKey };
+  tls.createSecureContext({ secureOptions: 1 }, notcontext);
+}, /^TypeError: Illegal invocation$/);
 
 // PFX tests
 assert.doesNotThrow(function() {
@@ -37,55 +36,55 @@ assert.doesNotThrow(function() {
 
 assert.throws(function() {
   tls.createSecureContext({pfx: certPfx});
-}, 'mac verify failure');
+}, /^Error: mac verify failure$/);
 
 assert.throws(function() {
   tls.createSecureContext({pfx: certPfx, passphrase: 'test'});
-}, 'mac verify failure');
+}, /^Error: mac verify failure$/);
 
 assert.throws(function() {
   tls.createSecureContext({pfx: 'sample', passphrase: 'test'});
-}, 'not enough data');
+}, /^Error: not enough data$/);
 
 
 // update() should only take buffers / strings
 assert.throws(function() {
   crypto.createHash('sha1').update({foo: 'bar'});
-}, /buffer/);
+}, /^TypeError: Not a string or buffer$/);
 
 
 function assertSorted(list) {
   // Array#sort() modifies the list in place so make a copy.
-  var sorted = util._extend([], list).sort();
+  const sorted = list.slice().sort();
   assert.deepEqual(list, sorted);
 }
 
 // Assume that we have at least AES-128-CBC.
-assert.notEqual(0, crypto.getCiphers().length);
-assert.notEqual(-1, crypto.getCiphers().indexOf('aes-128-cbc'));
-assert.equal(-1, crypto.getCiphers().indexOf('AES-128-CBC'));
+assert.notStrictEqual(0, crypto.getCiphers().length);
+assert.notStrictEqual(-1, crypto.getCiphers().indexOf('aes-128-cbc'));
+assert.strictEqual(-1, crypto.getCiphers().indexOf('AES-128-CBC'));
 assertSorted(crypto.getCiphers());
 
 // Assume that we have at least AES256-SHA.
-assert.notEqual(0, tls.getCiphers().length);
-assert.notEqual(-1, tls.getCiphers().indexOf('aes256-sha'));
-assert.equal(-1, tls.getCiphers().indexOf('AES256-SHA'));
+assert.notStrictEqual(0, tls.getCiphers().length);
+assert.notStrictEqual(-1, tls.getCiphers().indexOf('aes256-sha'));
+assert.strictEqual(-1, tls.getCiphers().indexOf('AES256-SHA'));
 assertSorted(tls.getCiphers());
 
 // Assert that we have sha and sha1 but not SHA and SHA1.
-assert.notEqual(0, crypto.getHashes().length);
-assert.notEqual(-1, crypto.getHashes().indexOf('sha1'));
-assert.notEqual(-1, crypto.getHashes().indexOf('sha'));
-assert.equal(-1, crypto.getHashes().indexOf('SHA1'));
-assert.equal(-1, crypto.getHashes().indexOf('SHA'));
-assert.notEqual(-1, crypto.getHashes().indexOf('RSA-SHA1'));
-assert.equal(-1, crypto.getHashes().indexOf('rsa-sha1'));
+assert.notStrictEqual(0, crypto.getHashes().length);
+assert.notStrictEqual(-1, crypto.getHashes().indexOf('sha1'));
+assert.notStrictEqual(-1, crypto.getHashes().indexOf('sha'));
+assert.strictEqual(-1, crypto.getHashes().indexOf('SHA1'));
+assert.strictEqual(-1, crypto.getHashes().indexOf('SHA'));
+assert.notStrictEqual(-1, crypto.getHashes().indexOf('RSA-SHA1'));
+assert.strictEqual(-1, crypto.getHashes().indexOf('rsa-sha1'));
 assertSorted(crypto.getHashes());
 
 // Assume that we have at least secp384r1.
-assert.notEqual(0, crypto.getCurves().length);
-assert.notEqual(-1, crypto.getCurves().indexOf('secp384r1'));
-assert.equal(-1, crypto.getCurves().indexOf('SECP384R1'));
+assert.notStrictEqual(0, crypto.getCurves().length);
+assert.notStrictEqual(-1, crypto.getCurves().indexOf('secp384r1'));
+assert.strictEqual(-1, crypto.getCurves().indexOf('SECP384R1'));
 assertSorted(crypto.getCurves());
 
 // Regression tests for #5725: hex input that's not a power of two should
@@ -100,18 +99,18 @@ assert.throws(function() {
 
 assert.throws(function() {
   crypto.createHash('sha1').update('0', 'hex');
-}, /Bad input string/);
+}, /^TypeError: Bad input string$/);
 
 assert.throws(function() {
   crypto.createSign('RSA-SHA1').update('0', 'hex');
-}, /Bad input string/);
+}, /^TypeError: Bad input string$/);
 
 assert.throws(function() {
   crypto.createVerify('RSA-SHA1').update('0', 'hex');
-}, /Bad input string/);
+}, /^TypeError: Bad input string$/);
 
 assert.throws(function() {
-  var priv = [
+  const priv = [
     '-----BEGIN RSA PRIVATE KEY-----',
     'MIGrAgEAAiEA+3z+1QNF2/unumadiwEr+C5vfhezsb3hp4jAnCNRpPcCAwEAAQIgQNriSQK4',
     'EFwczDhMZp2dvbcz7OUUyt36z3S4usFPHSECEQD/41K7SujrstBfoCPzwC1xAhEA+5kt4BJy',
@@ -121,7 +120,7 @@ assert.throws(function() {
     ''
   ].join('\n');
   crypto.createSign('RSA-SHA256').update('test').sign(priv);
-}, /digest too big for rsa key/);
+}, /digest too big for rsa key$/);
 
 assert.throws(function() {
   // The correct header inside `test_bad_rsa_privkey.pem` should have been
@@ -133,7 +132,7 @@ assert.throws(function() {
   //   $ openssl pkcs8 -topk8 -inform PEM -outform PEM -in mykey.pem \
   //     -out private_key.pem -nocrypt;
   //   Then open private_key.pem and change its header and footer.
-  var sha1_privateKey = fs.readFileSync(common.fixturesDir +
+  const sha1_privateKey = fs.readFileSync(common.fixturesDir +
                                         '/test_bad_rsa_privkey.pem', 'ascii');
   // this would inject errors onto OpenSSL's error stack
   crypto.createSign('sha1').sign(sha1_privateKey);
diff --git a/test/parallel/test-cwd-enoent.js b/test/parallel/test-cwd-enoent.js
index 9ff9f86405a333..dba2502922ccf0 100644
--- a/test/parallel/test-cwd-enoent.js
+++ b/test/parallel/test-cwd-enoent.js
@@ -21,6 +21,6 @@ proc.stdout.pipe(process.stdout);
 proc.stderr.pipe(process.stderr);
 
 proc.once('exit', common.mustCall(function(exitCode, signalCode) {
-  assert.equal(exitCode, 0);
-  assert.equal(signalCode, null);
+  assert.strictEqual(exitCode, 0);
+  assert.strictEqual(signalCode, null);
 }));
diff --git a/test/parallel/test-debug-port-from-cmdline.js b/test/parallel/test-debug-port-from-cmdline.js
index 527d72ee74a75f..cd92764df29c8e 100644
--- a/test/parallel/test-debug-port-from-cmdline.js
+++ b/test/parallel/test-debug-port-from-cmdline.js
@@ -42,7 +42,7 @@ function assertOutputLines() {
     'Debugger listening on (\\[::\\]|0\\.0\\.0\\.0):' + debugPort,
   ];
 
-  assert.equal(outputLines.length, expectedLines.length);
+  assert.strictEqual(outputLines.length, expectedLines.length);
   for (var i = 0; i < expectedLines.length; i++)
     assert(RegExp(expectedLines[i]).test(outputLines[i]));
 }
diff --git a/test/parallel/test-debugger-util-regression.js b/test/parallel/test-debugger-util-regression.js
index 4711d8e1509fd8..88c8f98b3b487e 100644
--- a/test/parallel/test-debugger-util-regression.js
+++ b/test/parallel/test-debugger-util-regression.js
@@ -46,8 +46,8 @@ proc.stdout.on('data', (data) => {
 proc.stderr.on('data', (data) => stderr += data);
 
 process.on('exit', (code) => {
-  assert.equal(code, 0, 'the program should exit cleanly');
-  assert.equal(stdout.includes('{ a: \'b\' }'), true,
-      'the debugger should print the result of util.inspect');
-  assert.equal(stderr, '', 'stderr should be empty');
+  assert.strictEqual(code, 0, 'the program should exit cleanly');
+  assert.strictEqual(stdout.includes('{ a: \'b\' }'), true,
+                     'the debugger should print the result of util.inspect');
+  assert.strictEqual(stderr, '', 'stderr should be empty');
 });
diff --git a/test/parallel/test-dgram-bind-default-address.js b/test/parallel/test-dgram-bind-default-address.js
old mode 100644
new mode 100755
index b2bd72f6db6a7c..142a5134c013c3
--- a/test/parallel/test-dgram-bind-default-address.js
+++ b/test/parallel/test-dgram-bind-default-address.js
@@ -1,7 +1,7 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var dgram = require('dgram');
+const common = require('../common');
+const assert = require('assert');
+const dgram = require('dgram');
 
 // skip test in FreeBSD jails since 0.0.0.0 will resolve to default interface
 if (common.inFreeBSDJail) {
@@ -13,7 +13,7 @@ dgram.createSocket('udp4').bind(0, common.mustCall(function() {
   assert.strictEqual(typeof this.address().port, 'number');
   assert.ok(isFinite(this.address().port));
   assert.ok(this.address().port > 0);
-  assert.equal(this.address().address, '0.0.0.0');
+  assert.strictEqual(this.address().address, '0.0.0.0');
   this.close();
 }));
 
@@ -26,9 +26,9 @@ dgram.createSocket('udp6').bind(0, common.mustCall(function() {
   assert.strictEqual(typeof this.address().port, 'number');
   assert.ok(isFinite(this.address().port));
   assert.ok(this.address().port > 0);
-  var address = this.address().address;
+  let address = this.address().address;
   if (address === '::ffff:0.0.0.0')
     address = '::';
-  assert.equal(address, '::');
+  assert.strictEqual(address, '::');
   this.close();
 }));
diff --git a/test/parallel/test-dgram-exclusive-implicit-bind.js b/test/parallel/test-dgram-exclusive-implicit-bind.js
index cebb16204200f4..b0aeb44c54fff6 100644
--- a/test/parallel/test-dgram-exclusive-implicit-bind.js
+++ b/test/parallel/test-dgram-exclusive-implicit-bind.js
@@ -45,7 +45,7 @@ if (cluster.isMaster) {
   var ports = {};
 
   process.on('exit', function() {
-    assert.equal(pass, true);
+    assert.strictEqual(pass, true);
   });
 
   var target = dgram.createSocket('udp4');
@@ -55,12 +55,12 @@ if (cluster.isMaster) {
     ports[rinfo.port] = true;
 
     if (common.isWindows && messages === 2) {
-      assert.equal(Object.keys(ports).length, 2);
+      assert.strictEqual(Object.keys(ports).length, 2);
       done();
     }
 
     if (!common.isWindows && messages === 4) {
-      assert.equal(Object.keys(ports).length, 3);
+      assert.strictEqual(Object.keys(ports).length, 3);
       done();
     }
 
diff --git a/test/parallel/test-dgram-msgsize.js b/test/parallel/test-dgram-msgsize.js
index 6330e2a82bdcc5..6cc415e83c00ca 100644
--- a/test/parallel/test-dgram-msgsize.js
+++ b/test/parallel/test-dgram-msgsize.js
@@ -1,18 +1,18 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var dgram = require('dgram');
+const common = require('../common');
+const assert = require('assert');
+const dgram = require('dgram');
 
 // Send a too big datagram. The destination doesn't matter because it's
 // not supposed to get sent out anyway.
-var buf = Buffer(256 * 1024);
-var sock = dgram.createSocket('udp4');
+const buf = Buffer.allocUnsafe(256 * 1024);
+const sock = dgram.createSocket('udp4');
 sock.send(buf, 0, buf.length, 12345, '127.0.0.1', common.mustCall(cb));
 function cb(err) {
   assert(err instanceof Error);
-  assert.equal(err.code, 'EMSGSIZE');
-  assert.equal(err.address, '127.0.0.1');
-  assert.equal(err.port, 12345);
-  assert.equal(err.message, 'send EMSGSIZE 127.0.0.1:12345');
+  assert.strictEqual(err.code, 'EMSGSIZE');
+  assert.strictEqual(err.address, '127.0.0.1');
+  assert.strictEqual(err.port, 12345);
+  assert.strictEqual(err.message, 'send EMSGSIZE 127.0.0.1:12345');
   sock.close();
 }
diff --git a/test/parallel/test-dgram-send-callback-recursive.js b/test/parallel/test-dgram-send-callback-recursive.js
index c54b05c3f86ba1..bca888a46785e9 100644
--- a/test/parallel/test-dgram-send-callback-recursive.js
+++ b/test/parallel/test-dgram-send-callback-recursive.js
@@ -37,7 +37,7 @@ client.on('message', function(buf, info) {
 });
 
 client.on('close', common.mustCall(function() {
-  assert.equal(received, limit);
+  assert.strictEqual(received, limit);
 }));
 
 client.bind(0);
diff --git a/test/parallel/test-dns.js b/test/parallel/test-dns.js
index 9a2577ec90de78..2d19da31f048c7 100644
--- a/test/parallel/test-dns.js
+++ b/test/parallel/test-dns.js
@@ -5,7 +5,7 @@ const assert = require('assert');
 const dns = require('dns');
 
 var existing = dns.getServers();
-assert(existing.length);
+assert(existing.length > 0);
 
 function noop() {}
 
@@ -15,7 +15,8 @@ var goog = [
 ];
 assert.doesNotThrow(function() { dns.setServers(goog); });
 assert.deepEqual(dns.getServers(), goog);
-assert.throws(function() { dns.setServers(['foobar']); });
+assert.throws(function() { dns.setServers(['foobar']); },
+              /^Error: IP address is not properly formatted: foobar$/);
 assert.deepEqual(dns.getServers(), goog);
 
 var goog6 = [
@@ -50,25 +51,28 @@ assert.throws(function() {
 }, 'Unexpected error');
 
 // dns.lookup should accept falsey and string values
+const errorReg =
+  /^TypeError: invalid arguments: hostname must be a string or falsey$/;
+
 assert.throws(function() {
   dns.lookup({}, noop);
-}, 'invalid arguments: hostname must be a string or falsey');
+}, errorReg);
 
 assert.throws(function() {
   dns.lookup([], noop);
-}, 'invalid arguments: hostname must be a string or falsey');
+}, errorReg);
 
 assert.throws(function() {
   dns.lookup(true, noop);
-}, 'invalid arguments: hostname must be a string or falsey');
+}, errorReg);
 
 assert.throws(function() {
   dns.lookup(1, noop);
-}, 'invalid arguments: hostname must be a string or falsey');
+}, errorReg);
 
 assert.throws(function() {
   dns.lookup(noop, noop);
-}, 'invalid arguments: hostname must be a string or falsey');
+}, errorReg);
 
 assert.doesNotThrow(function() {
   dns.lookup('', noop);
@@ -102,15 +106,15 @@ assert.doesNotThrow(function() {
 assert.throws(function() {
   dns.lookup('www.google.com', { hints: (dns.V4MAPPED | dns.ADDRCONFIG) + 1 },
     noop);
-});
+}, /^TypeError: invalid argument: hints must use valid flags$/);
 
 assert.throws(function() {
   dns.lookup('www.google.com');
-}, 'invalid arguments: callback must be passed');
+}, /^TypeError: invalid arguments: callback must be passed$/);
 
 assert.throws(function() {
   dns.lookup('www.google.com', 4);
-}, 'invalid arguments: callback must be passed');
+}, /^TypeError: invalid arguments: callback must be passed$/);
 
 assert.doesNotThrow(function() {
   dns.lookup('www.google.com', 6, noop);
@@ -148,15 +152,15 @@ assert.doesNotThrow(function() {
 
 assert.throws(function() {
   dns.lookupService('0.0.0.0');
-}, /invalid arguments/);
+}, /^Error: invalid arguments$/);
 
 assert.throws(function() {
   dns.lookupService('fasdfdsaf', 0, noop);
-}, /host needs to be a valid IP address/);
+}, /^TypeError: host needs to be a valid IP address$/);
 
 assert.throws(function() {
   dns.lookupService('0.0.0.0', '0', noop);
-}, /port argument must be a number, got "0"/);
+}, /^TypeError: port argument must be a number, got "0"$/);
 
 assert.doesNotThrow(function() {
   dns.lookupService('0.0.0.0', 0, noop);
diff --git a/test/parallel/test-domain-abort-on-uncaught.js b/test/parallel/test-domain-abort-on-uncaught.js
index 93d330e3d67370..493533e5750ec1 100644
--- a/test/parallel/test-domain-abort-on-uncaught.js
+++ b/test/parallel/test-domain-abort-on-uncaught.js
@@ -212,7 +212,7 @@ if (process.argv[2] === 'child') {
   tests[testIndex]();
 
   process.on('exit', function onExit() {
-    assert.equal(errorHandlerCalled, true);
+    assert.strictEqual(errorHandlerCalled, true);
   });
 } else {
 
@@ -233,7 +233,7 @@ if (process.argv[2] === 'child') {
     var child = child_process.exec(testCmd);
 
     child.on('exit', function onExit(code, signal) {
-      assert.equal(code, 0, 'Test at index ' + testIndex +
+      assert.strictEqual(code, 0, 'Test at index ' + testIndex +
         ' should have exited with exit code 0 but instead exited with code ' +
         code + ' and signal ' + signal);
     });
diff --git a/test/parallel/test-domain-exit-dispose-again.js b/test/parallel/test-domain-exit-dispose-again.js
index 0928addd9ace55..b1911bb40e0c93 100644
--- a/test/parallel/test-domain-exit-dispose-again.js
+++ b/test/parallel/test-domain-exit-dispose-again.js
@@ -51,7 +51,7 @@ setTimeout(function firstTimer() {
           'a domain that should be disposed.');
       disposalFailed = true;
       process.exit(1);
-    });
+    }, 1);
 
     // Make V8 throw an unreferenced error. As a result, the domain's error
     // handler is called, which disposes the domain "d" and should prevent the
@@ -69,8 +69,8 @@ setTimeout(function secondTimer() {
 }, TIMEOUT_DURATION);
 
 process.on('exit', function() {
-  assert.equal(a, 10);
-  assert.equal(disposalFailed, false);
+  assert.strictEqual(a, 10);
+  assert.strictEqual(disposalFailed, false);
   assert(secondTimerRan);
   console.log('ok');
 });
diff --git a/test/parallel/test-domain-exit-dispose.js b/test/parallel/test-domain-exit-dispose.js
index 94b3dbd4ca5a37..508cec18dccb7d 100644
--- a/test/parallel/test-domain-exit-dispose.js
+++ b/test/parallel/test-domain-exit-dispose.js
@@ -1,8 +1,8 @@
 'use strict';
 require('../common');
+var common = require('../common');
 var assert = require('assert');
 var domain = require('domain');
-var disposalFailed = false;
 
 // no matter what happens, we should increment a 10 times.
 var a = 0;
@@ -22,11 +22,7 @@ function err() {
   function err2() {
     // this timeout should never be called, since the domain gets
     // disposed when the error happens.
-    setTimeout(function() {
-      console.error('This should not happen.');
-      disposalFailed = true;
-      process.exit(1);
-    });
+    setTimeout(common.mustCall(() => {}, 0), 1);
 
     // this function doesn't exist, and throws an error as a result.
     err3(); // eslint-disable-line no-undef
@@ -41,7 +37,6 @@ function err() {
 }
 
 process.on('exit', function() {
-  assert.equal(a, 10);
-  assert.equal(disposalFailed, false);
+  assert.strictEqual(a, 10);
   console.log('ok');
 });
diff --git a/test/parallel/test-domain-from-timer.js b/test/parallel/test-domain-from-timer.js
index f0115018ec1879..2ffae758ef6490 100644
--- a/test/parallel/test-domain-from-timer.js
+++ b/test/parallel/test-domain-from-timer.js
@@ -2,17 +2,17 @@
 // Simple tests of most basic domain functionality.
 
 require('../common');
-var assert = require('assert');
+const assert = require('assert');
 
 // timeouts call the callback directly from cc, so need to make sure the
 // domain will be used regardless
 setTimeout(function() {
-  var domain = require('domain');
-  var d = domain.create();
+  const domain = require('domain');
+  const d = domain.create();
   d.run(function() {
     process.nextTick(function() {
       console.trace('in nexttick', process.domain === d);
-      assert.equal(process.domain, d);
+      assert.strictEqual(process.domain, d);
     });
   });
-});
+}, 1);
diff --git a/test/parallel/test-domain-http-server.js b/test/parallel/test-domain-http-server.js
index e131e02ea4d74b..9bb4e327435ac8 100644
--- a/test/parallel/test-domain-http-server.js
+++ b/test/parallel/test-domain-http-server.js
@@ -88,7 +88,7 @@ function next() {
 }
 
 process.on('exit', function() {
-  assert.equal(serverCaught, 2);
-  assert.equal(clientCaught, 2);
+  assert.strictEqual(serverCaught, 2);
+  assert.strictEqual(clientCaught, 2);
   console.log('ok');
 });
diff --git a/test/parallel/test-domain-multi.js b/test/parallel/test-domain-multi.js
index 1b0af1dd3f438f..cf85dbca460146 100644
--- a/test/parallel/test-domain-multi.js
+++ b/test/parallel/test-domain-multi.js
@@ -70,8 +70,8 @@ var server = http.createServer(function(req, res) {
 });
 
 process.on('exit', function() {
-  assert.equal(caughtA, false);
-  assert.equal(caughtB, true);
-  assert.equal(caughtC, true);
+  assert.strictEqual(caughtA, false);
+  assert.strictEqual(caughtB, true);
+  assert.strictEqual(caughtC, true);
   console.log('ok - Errors went where they were supposed to go');
 });
diff --git a/test/parallel/test-domain-top-level-error-handler-throw.js b/test/parallel/test-domain-top-level-error-handler-throw.js
index 7933c5d052fe11..a5576bdb5b5fda 100644
--- a/test/parallel/test-domain-top-level-error-handler-throw.js
+++ b/test/parallel/test-domain-top-level-error-handler-throw.js
@@ -45,8 +45,8 @@ if (process.argv[2] === 'child') {
       var expectedExitCode = 7;
       var expectedSignal = null;
 
-      assert.equal(exitCode, expectedExitCode);
-      assert.equal(signal, expectedSignal);
+      assert.strictEqual(exitCode, expectedExitCode);
+      assert.strictEqual(signal, expectedSignal);
     });
   }
 }
diff --git a/test/parallel/test-domain.js b/test/parallel/test-domain.js
index 19cd964a28923a..69521108f6e47b 100644
--- a/test/parallel/test-domain.js
+++ b/test/parallel/test-domain.js
@@ -31,67 +31,67 @@ d.on('error', function(er) {
 
   switch (er_message) {
     case 'emitted':
-      assert.equal(er.domain, d);
-      assert.equal(er.domainEmitter, e);
-      assert.equal(er.domainThrown, false);
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainEmitter, e);
+      assert.strictEqual(er.domainThrown, false);
       break;
 
     case 'bound':
       assert.ok(!er.domainEmitter);
-      assert.equal(er.domain, d);
-      assert.equal(er.domainBound, fn);
-      assert.equal(er.domainThrown, false);
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainBound, fn);
+      assert.strictEqual(er.domainThrown, false);
       break;
 
     case 'thrown':
       assert.ok(!er.domainEmitter);
-      assert.equal(er.domain, d);
-      assert.equal(er.domainThrown, true);
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainThrown, true);
       break;
 
     case "ENOENT: no such file or directory, open 'this file does not exist'":
-      assert.equal(er.domain, d);
-      assert.equal(er.domainThrown, false);
-      assert.equal(typeof er.domainBound, 'function');
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainThrown, false);
+      assert.strictEqual(typeof er.domainBound, 'function');
       assert.ok(!er.domainEmitter);
-      assert.equal(er.code, 'ENOENT');
-      assert.equal(er_path, 'this file does not exist');
-      assert.equal(typeof er.errno, 'number');
+      assert.strictEqual(er.code, 'ENOENT');
+      assert.strictEqual(er_path, 'this file does not exist');
+      assert.strictEqual(typeof er.errno, 'number');
       break;
 
     case
     "ENOENT: no such file or directory, open 'stream for nonexistent file'":
-      assert.equal(typeof er.errno, 'number');
-      assert.equal(er.code, 'ENOENT');
-      assert.equal(er_path, 'stream for nonexistent file');
-      assert.equal(er.domain, d);
-      assert.equal(er.domainEmitter, fst);
+      assert.strictEqual(typeof er.errno, 'number');
+      assert.strictEqual(er.code, 'ENOENT');
+      assert.strictEqual(er_path, 'stream for nonexistent file');
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainEmitter, fst);
       assert.ok(!er.domainBound);
-      assert.equal(er.domainThrown, false);
+      assert.strictEqual(er.domainThrown, false);
       break;
 
     case 'implicit':
-      assert.equal(er.domainEmitter, implicit);
-      assert.equal(er.domain, d);
-      assert.equal(er.domainThrown, false);
+      assert.strictEqual(er.domainEmitter, implicit);
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainThrown, false);
       assert.ok(!er.domainBound);
       break;
 
     case 'implicit timer':
-      assert.equal(er.domain, d);
-      assert.equal(er.domainThrown, true);
+      assert.strictEqual(er.domain, d);
+      assert.strictEqual(er.domainThrown, true);
       assert.ok(!er.domainEmitter);
       assert.ok(!er.domainBound);
       break;
 
     case 'Cannot read property \'isDirectory\' of undefined':
-      assert.equal(er.domain, d);
+      assert.strictEqual(er.domain, d);
       assert.ok(!er.domainEmitter);
       assert.ok(!er.domainBound);
       break;
 
     case 'nextTick execution loop':
-      assert.equal(er.domain, d);
+      assert.strictEqual(er.domain, d);
       assert.ok(!er.domainEmitter);
       assert.ok(!er.domainBound);
       break;
@@ -107,7 +107,8 @@ d.on('error', function(er) {
 
 process.on('exit', function() {
   console.error('exit', caught, expectCaught);
-  assert.equal(caught, expectCaught, 'caught the expected number of errors');
+  assert.strictEqual(caught, expectCaught,
+                     'caught the expected number of errors');
   console.log('ok');
 });
 
@@ -172,7 +173,7 @@ expectCaught++;
 
 // intercepted should never pass first argument to callback
 function fn2(data) {
-  assert.equal(data, 'data', 'should not be null err argument');
+  assert.strictEqual(data, 'data', 'should not be null err argument');
 }
 
 bound = d.intercept(fn2);
@@ -181,8 +182,8 @@ bound(null, 'data');
 // intercepted should never pass first argument to callback
 // even if arguments length is more than 2.
 function fn3(data, data2) {
-  assert.equal(data, 'data', 'should not be null err argument');
-  assert.equal(data2, 'data2', 'should not be data argument');
+  assert.strictEqual(data, 'data', 'should not be null err argument');
+  assert.strictEqual(data2, 'data2', 'should not be data argument');
 }
 
 bound = d.intercept(fn3);
@@ -225,14 +226,14 @@ expectCaught++;
 var result = d.run(function() {
   return 'return value';
 });
-assert.equal(result, 'return value');
+assert.strictEqual(result, 'return value');
 
 
 // check if the executed function take in count the applied parameters
 result = d.run(function(a, b) {
   return a + ' ' + b;
 }, 'return', 'value');
-assert.equal(result, 'return value');
+assert.strictEqual(result, 'return value');
 
 
 var fst = fs.createReadStream('stream for nonexistent file');
diff --git a/test/parallel/test-event-emitter-listeners.js b/test/parallel/test-event-emitter-listeners.js
index 77c44907b62d8c..dfd66287b194a7 100644
--- a/test/parallel/test-event-emitter-listeners.js
+++ b/test/parallel/test-event-emitter-listeners.js
@@ -1,32 +1,38 @@
 'use strict';
 
 require('../common');
-var assert = require('assert');
-var events = require('events');
+const assert = require('assert');
+const events = require('events');
 
 function listener() {}
 function listener2() {}
 
-var e1 = new events.EventEmitter();
-e1.on('foo', listener);
-var fooListeners = e1.listeners('foo');
-assert.deepEqual(e1.listeners('foo'), [listener]);
-e1.removeAllListeners('foo');
-assert.deepEqual(e1.listeners('foo'), []);
-assert.deepEqual(fooListeners, [listener]);
+{
+  const ee = new events.EventEmitter();
+  ee.on('foo', listener);
+  const fooListeners = ee.listeners('foo');
+  assert.deepStrictEqual(ee.listeners('foo'), [listener]);
+  ee.removeAllListeners('foo');
+  assert.deepStrictEqual(ee.listeners('foo'), []);
+  assert.deepStrictEqual(fooListeners, [listener]);
+}
 
-var e2 = new events.EventEmitter();
-e2.on('foo', listener);
-var e2ListenersCopy = e2.listeners('foo');
-assert.deepEqual(e2ListenersCopy, [listener]);
-assert.deepEqual(e2.listeners('foo'), [listener]);
-e2ListenersCopy.push(listener2);
-assert.deepEqual(e2.listeners('foo'), [listener]);
-assert.deepEqual(e2ListenersCopy, [listener, listener2]);
+{
+  const ee = new events.EventEmitter();
+  ee.on('foo', listener);
+  const eeListenersCopy = ee.listeners('foo');
+  assert.deepStrictEqual(eeListenersCopy, [listener]);
+  assert.deepStrictEqual(ee.listeners('foo'), [listener]);
+  eeListenersCopy.push(listener2);
+  assert.deepStrictEqual(ee.listeners('foo'), [listener]);
+  assert.deepStrictEqual(eeListenersCopy, [listener, listener2]);
+}
 
-var e3 = new events.EventEmitter();
-e3.on('foo', listener);
-var e3ListenersCopy = e3.listeners('foo');
-e3.on('foo', listener2);
-assert.deepEqual(e3.listeners('foo'), [listener, listener2]);
-assert.deepEqual(e3ListenersCopy, [listener]);
+{
+  const ee = new events.EventEmitter();
+  ee.on('foo', listener);
+  const eeListenersCopy = ee.listeners('foo');
+  ee.on('foo', listener2);
+  assert.deepStrictEqual(ee.listeners('foo'), [listener, listener2]);
+  assert.deepStrictEqual(eeListenersCopy, [listener]);
+}
diff --git a/test/parallel/test-event-emitter-method-names.js b/test/parallel/test-event-emitter-method-names.js
index c1e6540f0184af..e268e229b06b5b 100644
--- a/test/parallel/test-event-emitter-method-names.js
+++ b/test/parallel/test-event-emitter-method-names.js
@@ -4,10 +4,10 @@ var assert = require('assert');
 var events = require('events');
 
 var E = events.EventEmitter.prototype;
-assert.equal(E.constructor.name, 'EventEmitter');
-assert.equal(E.on, E.addListener);  // Same method.
+assert.strictEqual(E.constructor.name, 'EventEmitter');
+assert.strictEqual(E.on, E.addListener);  // Same method.
 Object.getOwnPropertyNames(E).forEach(function(name) {
   if (name === 'constructor' || name === 'on') return;
   if (typeof E[name] !== 'function') return;
-  assert.equal(E[name].name, name);
+  assert.strictEqual(E[name].name, name);
 });
diff --git a/test/parallel/test-event-emitter-remove-all-listeners.js b/test/parallel/test-event-emitter-remove-all-listeners.js
index 54dedfa1362d29..e32a0e3f94f5b4 100644
--- a/test/parallel/test-event-emitter-remove-all-listeners.js
+++ b/test/parallel/test-event-emitter-remove-all-listeners.js
@@ -1,13 +1,13 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var events = require('events');
+const common = require('../common');
+const assert = require('assert');
+const events = require('events');
 
 
 function expect(expected) {
-  var actual = [];
+  const actual = [];
   process.on('exit', function() {
-    assert.deepEqual(actual.sort(), expected.sort());
+    assert.deepStrictEqual(actual.sort(), expected.sort());
   });
   function listener(name) {
     actual.push(name);
@@ -17,56 +17,63 @@ function expect(expected) {
 
 function listener() {}
 
-var e1 = new events.EventEmitter();
-e1.on('foo', listener);
-e1.on('bar', listener);
-e1.on('baz', listener);
-e1.on('baz', listener);
-var fooListeners = e1.listeners('foo');
-var barListeners = e1.listeners('bar');
-var bazListeners = e1.listeners('baz');
-e1.on('removeListener', expect(['bar', 'baz', 'baz']));
-e1.removeAllListeners('bar');
-e1.removeAllListeners('baz');
-assert.deepEqual(e1.listeners('foo'), [listener]);
-assert.deepEqual(e1.listeners('bar'), []);
-assert.deepEqual(e1.listeners('baz'), []);
-// after calling removeAllListeners,
-// the old listeners array should stay unchanged
-assert.deepEqual(fooListeners, [listener]);
-assert.deepEqual(barListeners, [listener]);
-assert.deepEqual(bazListeners, [listener, listener]);
-// after calling removeAllListeners,
-// new listeners arrays are different from the old
-assert.notEqual(e1.listeners('bar'), barListeners);
-assert.notEqual(e1.listeners('baz'), bazListeners);
+{
+  const ee = new events.EventEmitter();
+  ee.on('foo', listener);
+  ee.on('bar', listener);
+  ee.on('baz', listener);
+  ee.on('baz', listener);
+  const fooListeners = ee.listeners('foo');
+  const barListeners = ee.listeners('bar');
+  const bazListeners = ee.listeners('baz');
+  ee.on('removeListener', expect(['bar', 'baz', 'baz']));
+  ee.removeAllListeners('bar');
+  ee.removeAllListeners('baz');
+  assert.deepStrictEqual(ee.listeners('foo'), [listener]);
+  assert.deepStrictEqual(ee.listeners('bar'), []);
+  assert.deepStrictEqual(ee.listeners('baz'), []);
+  // After calling removeAllListeners(),
+  // the old listeners array should stay unchanged.
+  assert.deepStrictEqual(fooListeners, [listener]);
+  assert.deepStrictEqual(barListeners, [listener]);
+  assert.deepStrictEqual(bazListeners, [listener, listener]);
+  // After calling removeAllListeners(),
+  // new listeners arrays is different from the old.
+  assert.notEqual(ee.listeners('bar'), barListeners);
+  assert.notEqual(ee.listeners('baz'), bazListeners);
+}
 
-var e2 = new events.EventEmitter();
-e2.on('foo', listener);
-e2.on('bar', listener);
-// expect LIFO order
-e2.on('removeListener', expect(['foo', 'bar', 'removeListener']));
-e2.on('removeListener', expect(['foo', 'bar']));
-e2.removeAllListeners();
-console.error(e2);
-assert.deepEqual([], e2.listeners('foo'));
-assert.deepEqual([], e2.listeners('bar'));
+{
+  const ee = new events.EventEmitter();
+  ee.on('foo', listener);
+  ee.on('bar', listener);
+  // Expect LIFO order
+  ee.on('removeListener', expect(['foo', 'bar', 'removeListener']));
+  ee.on('removeListener', expect(['foo', 'bar']));
+  ee.removeAllListeners();
+  assert.deepStrictEqual([], ee.listeners('foo'));
+  assert.deepStrictEqual([], ee.listeners('bar'));
+}
 
-var e3 = new events.EventEmitter();
-e3.on('removeListener', listener);
-// check for regression where removeAllListeners throws when
-// there exists a removeListener listener, but there exists
-// no listeners for the provided event type
-assert.doesNotThrow(e3.removeAllListeners.bind(e3, 'foo'));
+{
+  const ee = new events.EventEmitter();
+  ee.on('removeListener', listener);
+  // Check for regression where removeAllListeners() throws when
+  // there exists a 'removeListener' listener, but there exists
+  // no listeners for the provided event type.
+  assert.doesNotThrow(ee.removeAllListeners.bind(ee, 'foo'));
+}
 
-var e4 = new events.EventEmitter();
-var expectLength = 2;
-e4.on('removeListener', function(name, listener) {
-  assert.equal(expectLength--, this.listeners('baz').length);
-});
-e4.on('baz', function() {});
-e4.on('baz', function() {});
-e4.on('baz', function() {});
-assert.equal(e4.listeners('baz').length, expectLength + 1);
-e4.removeAllListeners('baz');
-assert.equal(e4.listeners('baz').length, 0);
+{
+  const ee = new events.EventEmitter();
+  var expectLength = 2;
+  ee.on('removeListener', function(name, listener) {
+    assert.strictEqual(expectLength--, this.listeners('baz').length);
+  });
+  ee.on('baz', function() {});
+  ee.on('baz', function() {});
+  ee.on('baz', function() {});
+  assert.strictEqual(ee.listeners('baz').length, expectLength + 1);
+  ee.removeAllListeners('baz');
+  assert.strictEqual(ee.listeners('baz').length, 0);
+}
diff --git a/test/parallel/test-event-emitter-remove-listeners.js b/test/parallel/test-event-emitter-remove-listeners.js
index 0d2ce551d3fcf9..912eefc9f4bf1e 100644
--- a/test/parallel/test-event-emitter-remove-listeners.js
+++ b/test/parallel/test-event-emitter-remove-listeners.js
@@ -1,111 +1,117 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var events = require('events');
-
-function listener1() {
-  console.log('listener1');
+const common = require('../common');
+const assert = require('assert');
+const events = require('events');
+
+function listener1() {}
+function listener2() {}
+
+{
+  const ee = new events.EventEmitter();
+  ee.on('hello', listener1);
+  ee.on('removeListener', common.mustCall((name, cb) => {
+    assert.strictEqual(name, 'hello');
+    assert.strictEqual(cb, listener1);
+  }));
+  ee.removeListener('hello', listener1);
+  assert.deepStrictEqual([], ee.listeners('hello'));
 }
 
-function listener2() {
-  console.log('listener2');
+{
+  const ee = new events.EventEmitter();
+  ee.on('hello', listener1);
+  ee.on('removeListener', common.fail);
+  ee.removeListener('hello', listener2);
+  assert.deepStrictEqual([listener1], ee.listeners('hello'));
 }
 
-function remove1() {
-  assert(0);
+{
+  const ee = new events.EventEmitter();
+  ee.on('hello', listener1);
+  ee.on('hello', listener2);
+  ee.once('removeListener', common.mustCall((name, cb) => {
+    assert.strictEqual(name, 'hello');
+    assert.strictEqual(cb, listener1);
+    assert.deepStrictEqual([listener2], ee.listeners('hello'));
+  }));
+  ee.removeListener('hello', listener1);
+  assert.deepStrictEqual([listener2], ee.listeners('hello'));
+  ee.once('removeListener', common.mustCall((name, cb) => {
+    assert.strictEqual(name, 'hello');
+    assert.strictEqual(cb, listener2);
+    assert.deepStrictEqual([], ee.listeners('hello'));
+  }));
+  ee.removeListener('hello', listener2);
+  assert.deepStrictEqual([], ee.listeners('hello'));
 }
 
-function remove2() {
-  assert(0);
+{
+  const ee = new events.EventEmitter();
+
+  function remove1() {
+    common.fail('remove1 should not have been called');
+  }
+
+  function remove2() {
+    common.fail('remove2 should not have been called');
+  }
+
+  ee.on('removeListener', common.mustCall(function(name, cb) {
+    if (cb !== remove1) return;
+    this.removeListener('quux', remove2);
+    this.emit('quux');
+  }, 2));
+  ee.on('quux', remove1);
+  ee.on('quux', remove2);
+  ee.removeListener('quux', remove1);
 }
 
-var e1 = new events.EventEmitter();
-e1.on('hello', listener1);
-e1.on('removeListener', common.mustCall(function(name, cb) {
-  assert.equal(name, 'hello');
-  assert.equal(cb, listener1);
-}));
-e1.removeListener('hello', listener1);
-assert.deepEqual([], e1.listeners('hello'));
-
-var e2 = new events.EventEmitter();
-e2.on('hello', listener1);
-e2.on('removeListener', common.fail);
-e2.removeListener('hello', listener2);
-assert.deepEqual([listener1], e2.listeners('hello'));
-
-var e3 = new events.EventEmitter();
-e3.on('hello', listener1);
-e3.on('hello', listener2);
-e3.once('removeListener', common.mustCall(function(name, cb) {
-  assert.equal(name, 'hello');
-  assert.equal(cb, listener1);
-  assert.deepEqual([listener2], e3.listeners('hello'));
-}));
-e3.removeListener('hello', listener1);
-assert.deepEqual([listener2], e3.listeners('hello'));
-e3.once('removeListener', common.mustCall(function(name, cb) {
-  assert.equal(name, 'hello');
-  assert.equal(cb, listener2);
-  assert.deepEqual([], e3.listeners('hello'));
-}));
-e3.removeListener('hello', listener2);
-assert.deepEqual([], e3.listeners('hello'));
-
-var e4 = new events.EventEmitter();
-e4.on('removeListener', common.mustCall(function(name, cb) {
-  if (cb !== remove1) return;
-  this.removeListener('quux', remove2);
-  this.emit('quux');
-}, 2));
-e4.on('quux', remove1);
-e4.on('quux', remove2);
-e4.removeListener('quux', remove1);
-
-var e5 = new events.EventEmitter();
-e5.on('hello', listener1);
-e5.on('hello', listener2);
-e5.once('removeListener', common.mustCall(function(name, cb) {
-  assert.equal(name, 'hello');
-  assert.equal(cb, listener1);
-  assert.deepEqual([listener2], e5.listeners('hello'));
-  e5.once('removeListener', common.mustCall(function(name, cb) {
-    assert.equal(name, 'hello');
-    assert.equal(cb, listener2);
-    assert.deepEqual([], e5.listeners('hello'));
+{
+  const ee = new events.EventEmitter();
+  ee.on('hello', listener1);
+  ee.on('hello', listener2);
+  ee.once('removeListener', common.mustCall((name, cb) => {
+    assert.strictEqual(name, 'hello');
+    assert.strictEqual(cb, listener1);
+    assert.deepStrictEqual([listener2], ee.listeners('hello'));
+    ee.once('removeListener', common.mustCall((name, cb) => {
+      assert.strictEqual(name, 'hello');
+      assert.strictEqual(cb, listener2);
+      assert.deepStrictEqual([], ee.listeners('hello'));
+    }));
+    ee.removeListener('hello', listener2);
+    assert.deepStrictEqual([], ee.listeners('hello'));
   }));
-  e5.removeListener('hello', listener2);
-  assert.deepEqual([], e5.listeners('hello'));
-}));
-e5.removeListener('hello', listener1);
-assert.deepEqual([], e5.listeners('hello'));
-
-const e6 = new events.EventEmitter();
-
-const listener3 = common.mustCall(() => {
-  e6.removeListener('hello', listener4);
-}, 2);
-
-const listener4 = common.mustCall(() => {}, 1);
+  ee.removeListener('hello', listener1);
+  assert.deepStrictEqual([], ee.listeners('hello'));
+}
 
-e6.on('hello', listener3);
-e6.on('hello', listener4);
+{
+  const ee = new events.EventEmitter();
+  const listener3 = common.mustCall(() => {
+    ee.removeListener('hello', listener4);
+  }, 2);
+  const listener4 = common.mustCall(() => {});
 
-// listener4 will still be called although it is removed by listener 3.
-e6.emit('hello');
-// This is so because the interal listener array at time of emit
-// was [listener3,listener4]
+  ee.on('hello', listener3);
+  ee.on('hello', listener4);
 
-// Interal listener array [listener3]
-e6.emit('hello');
+  // listener4 will still be called although it is removed by listener 3.
+  ee.emit('hello');
+  // This is so because the interal listener array at time of emit
+  // was [listener3,listener4]
 
-const e7 = new events.EventEmitter();
+  // Interal listener array [listener3]
+  ee.emit('hello');
+}
 
-const listener5 = () => {};
+{
+  const ee = new events.EventEmitter();
 
-e7.once('hello', listener5);
-e7.on('removeListener', common.mustCall((eventName, listener) => {
-  assert.strictEqual(eventName, 'hello');
-  assert.strictEqual(listener, listener5);
-}));
-e7.emit('hello');
+  ee.once('hello', listener1);
+  ee.on('removeListener', common.mustCall((eventName, listener) => {
+    assert.strictEqual(eventName, 'hello');
+    assert.strictEqual(listener, listener1);
+  }));
+  ee.emit('hello');
+}
diff --git a/test/parallel/test-file-write-stream.js b/test/parallel/test-file-write-stream.js
index b9d9fd76b88df2..d4b9a26c0fc5c8 100644
--- a/test/parallel/test-file-write-stream.js
+++ b/test/parallel/test-file-write-stream.js
@@ -46,7 +46,7 @@ file
     assert.throws(function() {
       console.error('write after end should not be allowed');
       file.write('should not work anymore');
-    });
+    }, /^Error: write after end$/);
 
     fs.unlinkSync(fn);
   });
diff --git a/test/parallel/test-file-write-stream3.js b/test/parallel/test-file-write-stream3.js
index 55806e8d22774c..cdb95dfd074c4c 100644
--- a/test/parallel/test-file-write-stream3.js
+++ b/test/parallel/test-file-write-stream3.js
@@ -9,7 +9,7 @@ const filepath = path.join(common.tmpDir, 'write_pos.txt');
 
 
 const cb_expected = 'write open close write open close write open close ';
-var cb_occurred = '';
+let cb_occurred = '';
 
 const fileDataInitial = 'abcdefghijklmnopqrstuvwxyz';
 
@@ -34,10 +34,8 @@ common.refreshTmpDir();
 
 
 function run_test_1() {
-  var file, buffer, options;
-
-  options = {};
-  file = fs.createWriteStream(filepath, options);
+  const options = {};
+  const file = fs.createWriteStream(filepath, options);
   console.log('    (debug: start         ', file.start);
   console.log('    (debug: pos           ', file.pos);
 
@@ -51,10 +49,10 @@ function run_test_1() {
     console.log('    (debug: start         ', file.start);
     console.log('    (debug: pos           ', file.pos);
     assert.strictEqual(file.bytesWritten, buffer.length);
-    var fileData = fs.readFileSync(filepath, 'utf8');
+    const fileData = fs.readFileSync(filepath, 'utf8');
     console.log('    (debug: file data   ', fileData);
     console.log('    (debug: expected    ', fileDataExpected_1);
-    assert.equal(fileData, fileDataExpected_1);
+    assert.strictEqual(fileData, fileDataExpected_1);
 
     run_test_2();
   });
@@ -65,7 +63,7 @@ function run_test_1() {
     throw err;
   });
 
-  buffer = new Buffer(fileDataInitial);
+  const buffer = Buffer.from(fileDataInitial);
   file.write(buffer);
   cb_occurred += 'write ';
 
@@ -74,13 +72,12 @@ function run_test_1() {
 
 
 function run_test_2() {
-  var file, buffer, options;
 
-  buffer = new Buffer('123456');
+  const buffer = Buffer.from('123456');
 
-  options = { start: 10,
-              flags: 'r+' };
-  file = fs.createWriteStream(filepath, options);
+  const options = { start: 10,
+                    flags: 'r+' };
+  const file = fs.createWriteStream(filepath, options);
   console.log('    (debug: start         ', file.start);
   console.log('    (debug: pos           ', file.pos);
 
@@ -94,10 +91,10 @@ function run_test_2() {
     console.log('    (debug: start         ', file.start);
     console.log('    (debug: pos           ', file.pos);
     assert.strictEqual(file.bytesWritten, buffer.length);
-    var fileData = fs.readFileSync(filepath, 'utf8');
+    const fileData = fs.readFileSync(filepath, 'utf8');
     console.log('    (debug: file data   ', fileData);
     console.log('    (debug: expected    ', fileDataExpected_2);
-    assert.equal(fileData, fileDataExpected_2);
+    assert.strictEqual(fileData, fileDataExpected_2);
 
     run_test_3();
   });
@@ -116,13 +113,12 @@ function run_test_2() {
 
 
 function run_test_3() {
-  var file, options;
 
   const data = '\u2026\u2026';    // 3 bytes * 2 = 6 bytes in UTF-8
 
-  options = { start: 10,
-              flags: 'r+' };
-  file = fs.createWriteStream(filepath, options);
+  const options = { start: 10,
+                    flags: 'r+' };
+  const file = fs.createWriteStream(filepath, options);
   console.log('    (debug: start         ', file.start);
   console.log('    (debug: pos           ', file.pos);
 
@@ -139,7 +135,7 @@ function run_test_3() {
     const fileData = fs.readFileSync(filepath, 'utf8');
     console.log('    (debug: file data   ', fileData);
     console.log('    (debug: expected    ', fileDataExpected_3);
-    assert.equal(fileData, fileDataExpected_3);
+    assert.strictEqual(fileData, fileDataExpected_3);
 
     run_test_4();
   });
diff --git a/test/parallel/test-fs-non-number-arguments-throw.js b/test/parallel/test-fs-non-number-arguments-throw.js
index 8f34a1fcbb92b1..0ff37b62f418b5 100644
--- a/test/parallel/test-fs-non-number-arguments-throw.js
+++ b/test/parallel/test-fs-non-number-arguments-throw.js
@@ -15,17 +15,20 @@ const saneEmitter = fs.createReadStream(tempFile, { start: 4, end: 6 });
 
 assert.throws(function() {
   fs.createReadStream(tempFile, { start: '4', end: 6 });
-}, "start as string didn't throw an error for createReadStream");
+}, /^TypeError: start must be a Number$/,
+   "start as string didn't throw an error for createReadStream");
 
 assert.throws(function() {
   fs.createReadStream(tempFile, { start: 4, end: '6' });
-}, "end as string didn't throw an error");
+}, /^TypeError: end must be a Number$/,
+   "end as string didn't throw an error for createReadStream");
 
 assert.throws(function() {
   fs.createWriteStream(tempFile, { start: '4' });
-}, "start as string didn't throw an error for createWriteStream");
+}, /^TypeError: start must be a Number$/,
+   "start as string didn't throw an error for createWriteStream");
 
-saneEmitter.on('data', function(data) {
+saneEmitter.on('data', common.mustCall(function(data) {
   assert.strictEqual(sanity, data.toString('utf8'), 'read ' +
                      data.toString('utf8') + ' instead of ' + sanity);
-});
+}));
diff --git a/test/parallel/test-fs-read-file-sync.js b/test/parallel/test-fs-read-file-sync.js
index d34bf7748cea89..45d08f40111f78 100644
--- a/test/parallel/test-fs-read-file-sync.js
+++ b/test/parallel/test-fs-read-file-sync.js
@@ -1,13 +1,13 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var path = require('path');
-var fs = require('fs');
+const common = require('../common');
+const assert = require('assert');
+const path = require('path');
+const fs = require('fs');
 
-var fn = path.join(common.fixturesDir, 'elipses.txt');
+const fn = path.join(common.fixturesDir, 'elipses.txt');
 
-var s = fs.readFileSync(fn, 'utf8');
-for (var i = 0; i < s.length; i++) {
-  assert.equal('\u2026', s[i]);
+const s = fs.readFileSync(fn, 'utf8');
+for (let i = 0; i < s.length; i++) {
+  assert.strictEqual('\u2026', s[i]);
 }
-assert.equal(10000, s.length);
+assert.strictEqual(10000, s.length);
diff --git a/test/parallel/test-fs-read-stream-err.js b/test/parallel/test-fs-read-stream-err.js
index 1bc2b6f0b0239c..32e9b02455e20a 100644
--- a/test/parallel/test-fs-read-stream-err.js
+++ b/test/parallel/test-fs-read-stream-err.js
@@ -1,43 +1,42 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var fs = require('fs');
+const common = require('../common');
+const assert = require('assert');
+const fs = require('fs');
 
-var stream = fs.createReadStream(__filename, {
+const stream = fs.createReadStream(__filename, {
   bufferSize: 64
 });
-var err = new Error('BAM');
+const err = new Error('BAM');
 
-stream.on('error', common.mustCall(function errorHandler(err_) {
-  console.error('error event');
-  process.nextTick(function() {
-    assert.equal(stream.fd, null);
-    assert.equal(err_, err);
-  });
+stream.on('error', common.mustCall((err_) => {
+  process.nextTick(common.mustCall(() => {
+    assert.strictEqual(stream.fd, null);
+    assert.strictEqual(err_, err);
+  }));
 }));
 
-fs.close = common.mustCall(function(fd_, cb) {
-  assert.equal(fd_, stream.fd);
+fs.close = common.mustCall((fd_, cb) => {
+  assert.strictEqual(fd_, stream.fd);
   process.nextTick(cb);
 });
 
-var read = fs.read;
+const read = fs.read;
 fs.read = function() {
   // first time is ok.
   read.apply(fs, arguments);
   // then it breaks
-  fs.read = function() {
-    var cb = arguments[arguments.length - 1];
-    process.nextTick(function() {
+  fs.read = common.mustCall(function() {
+    const cb = arguments[arguments.length - 1];
+    process.nextTick(() => {
       cb(err);
     });
     // and should not be called again!
-    fs.read = function() {
+    fs.read = () => {
       throw new Error('BOOM!');
     };
-  };
+  });
 };
 
-stream.on('data', function(buf) {
-  stream.on('data', common.fail);  // no more 'data' events should follow
+stream.on('data', (buf) => {
+  stream.on('data', () => common.fail("no more 'data' events should follow"));
 });
diff --git a/test/parallel/test-fs-read-stream-inherit.js b/test/parallel/test-fs-read-stream-inherit.js
index 2b3a2f8f48584d..3616ae2ddb5a4f 100644
--- a/test/parallel/test-fs-read-stream-inherit.js
+++ b/test/parallel/test-fs-read-stream-inherit.js
@@ -1,22 +1,22 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
-var path = require('path');
-var fs = require('fs');
-var fn = path.join(common.fixturesDir, 'elipses.txt');
-var rangeFile = path.join(common.fixturesDir, 'x.txt');
+const path = require('path');
+const fs = require('fs');
+const fn = path.join(common.fixturesDir, 'elipses.txt');
+const rangeFile = path.join(common.fixturesDir, 'x.txt');
 
-var callbacks = { open: 0, end: 0, close: 0 };
+const callbacks = { open: 0, end: 0, close: 0 };
 
-var paused = false;
+let paused = false;
 
-var file = fs.ReadStream(fn);
+const file = fs.ReadStream(fn);
 
 file.on('open', function(fd) {
   file.length = 0;
   callbacks.open++;
-  assert.equal('number', typeof fd);
+  assert.strictEqual(typeof fd, 'number');
   assert.ok(file.readable);
 
   // GH-535
@@ -48,19 +48,17 @@ file.on('end', function(chunk) {
 
 file.on('close', function() {
   callbacks.close++;
-
-  //assert.equal(fs.readFileSync(fn), fileContent);
 });
 
-var file3 = fs.createReadStream(fn, Object.create({encoding: 'utf8'}));
+const file3 = fs.createReadStream(fn, Object.create({encoding: 'utf8'}));
 file3.length = 0;
 file3.on('data', function(data) {
-  assert.equal('string', typeof data);
+  assert.strictEqual(typeof data, 'string');
   file3.length += data.length;
 
-  for (var i = 0; i < data.length; i++) {
+  for (let i = 0; i < data.length; i++) {
     // http://www.fileformat.info/info/unicode/char/2026/index.htm
-    assert.equal('\u2026', data[i]);
+    assert.strictEqual(data[i], '\u2026');
   }
 });
 
@@ -69,57 +67,57 @@ file3.on('close', function() {
 });
 
 process.on('exit', function() {
-  assert.equal(1, callbacks.open);
-  assert.equal(1, callbacks.end);
-  assert.equal(2, callbacks.close);
-  assert.equal(30000, file.length);
-  assert.equal(10000, file3.length);
+  assert.strictEqual(callbacks.open, 1);
+  assert.strictEqual(callbacks.end, 1);
+  assert.strictEqual(callbacks.close, 2);
+  assert.strictEqual(file.length, 30000);
+  assert.strictEqual(file3.length, 10000);
   console.error('ok');
 });
 
-var file4 = fs.createReadStream(rangeFile, Object.create({bufferSize: 1,
-                                start: 1, end: 2}));
-assert.equal(file4.start, 1);
-assert.equal(file4.end, 2);
-var contentRead = '';
+const file4 = fs.createReadStream(rangeFile, Object.create({bufferSize: 1,
+                                  start: 1, end: 2}));
+assert.strictEqual(file4.start, 1);
+assert.strictEqual(file4.end, 2);
+let contentRead = '';
 file4.on('data', function(data) {
   contentRead += data.toString('utf-8');
 });
 file4.on('end', function(data) {
-  assert.equal(contentRead, 'yz');
+  assert.strictEqual(contentRead, 'yz');
 });
 
-var file5 = fs.createReadStream(rangeFile, Object.create({bufferSize: 1,
-                                start: 1}));
-assert.equal(file5.start, 1);
+const file5 = fs.createReadStream(rangeFile, Object.create({bufferSize: 1,
+                                  start: 1}));
+assert.strictEqual(file5.start, 1);
 file5.data = '';
 file5.on('data', function(data) {
   file5.data += data.toString('utf-8');
 });
 file5.on('end', function() {
-  assert.equal(file5.data, 'yz\n');
+  assert.strictEqual(file5.data, 'yz\n');
 });
 
 // https://github.com/joyent/node/issues/2320
-var file6 = fs.createReadStream(rangeFile, Object.create({bufferSize: 1.23,
-                                start: 1}));
-assert.equal(file6.start, 1);
+const file6 = fs.createReadStream(rangeFile, Object.create({bufferSize: 1.23,
+                                  start: 1}));
+assert.strictEqual(file6.start, 1);
 file6.data = '';
 file6.on('data', function(data) {
   file6.data += data.toString('utf-8');
 });
 file6.on('end', function() {
-  assert.equal(file6.data, 'yz\n');
+  assert.strictEqual(file6.data, 'yz\n');
 });
 
 assert.throws(function() {
   fs.createReadStream(rangeFile, Object.create({start: 10, end: 2}));
 }, /start must be <= end/);
 
-var stream = fs.createReadStream(rangeFile, Object.create({ start: 0,
-                                 end: 0 }));
-assert.equal(stream.start, 0);
-assert.equal(stream.end, 0);
+const stream = fs.createReadStream(rangeFile, Object.create({ start: 0,
+                                   end: 0 }));
+assert.strictEqual(stream.start, 0);
+assert.strictEqual(stream.end, 0);
 stream.data = '';
 
 stream.on('data', function(chunk) {
@@ -127,16 +125,16 @@ stream.on('data', function(chunk) {
 });
 
 stream.on('end', function() {
-  assert.equal('x', stream.data);
+  assert.strictEqual(stream.data, 'x');
 });
 
 // pause and then resume immediately.
-var pauseRes = fs.createReadStream(rangeFile);
+const pauseRes = fs.createReadStream(rangeFile);
 pauseRes.pause();
 pauseRes.resume();
 
-var file7 = fs.createReadStream(rangeFile, Object.create({autoClose: false }));
-assert.equal(file7.autoClose, false);
+let file7 = fs.createReadStream(rangeFile, Object.create({autoClose: false }));
+assert.strictEqual(file7.autoClose, false);
 file7.on('data', function() {});
 file7.on('end', function() {
   process.nextTick(function() {
@@ -154,18 +152,18 @@ function file7Next() {
     file7.data += data;
   });
   file7.on('end', function(err) {
-    assert.equal(file7.data, 'xyz\n');
+    assert.strictEqual(file7.data, 'xyz\n');
   });
 }
 
 // Just to make sure autoClose won't close the stream because of error.
-var file8 = fs.createReadStream(null, Object.create({fd: 13337,
-                                autoClose: false }));
+const file8 = fs.createReadStream(null, Object.create({fd: 13337,
+                                  autoClose: false }));
 file8.on('data', function() {});
 file8.on('error', common.mustCall(function() {}));
 
 // Make sure stream is destroyed when file does not exist.
-var file9 = fs.createReadStream('/path/to/file/that/does/not/exist');
+const file9 = fs.createReadStream('/path/to/file/that/does/not/exist');
 file9.on('data', function() {});
 file9.on('error', common.mustCall(function() {}));
 
diff --git a/test/parallel/test-fs-read-stream-resume.js b/test/parallel/test-fs-read-stream-resume.js
index abac0686c11944..3ff89644e5c018 100644
--- a/test/parallel/test-fs-read-stream-resume.js
+++ b/test/parallel/test-fs-read-stream-resume.js
@@ -1,13 +1,13 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
-var fs = require('fs');
-var path = require('path');
+const fs = require('fs');
+const path = require('path');
 
-var file = path.join(common.fixturesDir, 'x.txt');
-var data = '';
-var first = true;
+const file = path.join(common.fixturesDir, 'x.txt');
+let data = '';
+let first = true;
 
 var stream = fs.createReadStream(file);
 stream.setEncoding('utf8');
@@ -27,5 +27,5 @@ process.nextTick(function() {
 });
 
 process.on('exit', function() {
-  assert.equal(data, 'xyz\n');
+  assert.strictEqual(data, 'xyz\n');
 });
diff --git a/test/parallel/test-http-dns-error.js b/test/parallel/test-http-dns-error.js
index f1f144a60a24c0..5e15ab9a3fa0da 100644
--- a/test/parallel/test-http-dns-error.js
+++ b/test/parallel/test-http-dns-error.js
@@ -1,8 +1,8 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
-var http = require('http');
+const http = require('http');
 
 if (common.hasCrypto) {
   var https = require('https');
@@ -10,7 +10,7 @@ if (common.hasCrypto) {
   common.skip('missing crypto');
 }
 
-var host = '*'.repeat(256);
+const host = '*'.repeat(256);
 
 function do_not_call() {
   throw new Error('This function should not have been called.');
@@ -20,15 +20,15 @@ function test(mod) {
 
   // Bad host name should not throw an uncatchable exception.
   // Ensure that there is time to attach an error listener.
-  var req1 = mod.get({host: host, port: 42}, do_not_call);
+  const req1 = mod.get({host: host, port: 42}, do_not_call);
   req1.on('error', common.mustCall(function(err) {
-    assert.equal(err.code, 'ENOTFOUND');
+    assert.strictEqual(err.code, 'ENOTFOUND');
   }));
   // http.get() called req1.end() for us
 
-  var req2 = mod.request({method: 'GET', host: host, port: 42}, do_not_call);
+  const req2 = mod.request({method: 'GET', host: host, port: 42}, do_not_call);
   req2.on('error', common.mustCall(function(err) {
-    assert.equal(err.code, 'ENOTFOUND');
+    assert.strictEqual(err.code, 'ENOTFOUND');
   }));
   req2.end();
 }
diff --git a/test/parallel/test-http-status-reason-invalid-chars.js b/test/parallel/test-http-status-reason-invalid-chars.js
index 7a8564a906131a..9950eeeee9cdd2 100644
--- a/test/parallel/test-http-status-reason-invalid-chars.js
+++ b/test/parallel/test-http-status-reason-invalid-chars.js
@@ -3,10 +3,11 @@
 const common = require('../common');
 const assert = require('assert');
 const http = require('http');
+const net = require('net');
 
 function explicit(req, res) {
   assert.throws(() => {
-    res.writeHead(200, `OK\r\nContent-Type: text/html\r\n`);
+    res.writeHead(200, 'OK\r\nContent-Type: text/html\r\n');
   }, /Invalid character in statusMessage/);
 
   assert.throws(() => {
@@ -19,7 +20,7 @@ function explicit(req, res) {
 
 function implicit(req, res) {
   assert.throws(() => {
-    res.statusMessage = `OK\r\nContent-Type: text/html\r\n`;
+    res.statusMessage = 'OK\r\nContent-Type: text/html\r\n';
     res.writeHead(200);
   }, /Invalid character in statusMessage/);
   res.statusMessage = 'OK';
@@ -32,13 +33,15 @@ const server = http.createServer((req, res) => {
   } else {
     implicit(req, res);
   }
-}).listen(common.PORT, common.mustCall(() => {
-  const url = `http://localhost:${common.PORT}`;
+}).listen(0, common.mustCall(() => {
+  const addr = server.address().address;
+  const hostname = net.isIPv6(addr) ? `[${addr}1]` : addr;
+  const url = `http://${hostname}:${server.address().port}`;
   let left = 2;
   const check = common.mustCall((res) => {
     left--;
-    assert.notEqual(res.headers['content-type'], 'text/html');
-    assert.notEqual(res.headers['content-type'], 'gotcha');
+    assert.notStrictEqual(res.headers['content-type'], 'text/html');
+    assert.notStrictEqual(res.headers['content-type'], 'gotcha');
     if (left === 0) server.close();
   }, 2);
   http.get(`${url}/explicit`, check).end();
diff --git a/test/parallel/test-https-agent-session-reuse.js b/test/parallel/test-https-agent-session-reuse.js
index 01f161574b29db..73465aa5a98fb9 100644
--- a/test/parallel/test-https-agent-session-reuse.js
+++ b/test/parallel/test-https-agent-session-reuse.js
@@ -1,39 +1,39 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
 
-var https = require('https');
-var crypto = require('crypto');
+const https = require('https');
+const crypto = require('crypto');
 
-var fs = require('fs');
+const fs = require('fs');
 
-var options = {
+const options = {
   key: fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem'),
   cert: fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem')
 };
 
-var ca = fs.readFileSync(common.fixturesDir + '/keys/ca1-cert.pem');
+const ca = fs.readFileSync(common.fixturesDir + '/keys/ca1-cert.pem');
 
-var clientSessions = {};
-var serverRequests = 0;
+const clientSessions = {};
+let serverRequests = 0;
 
-var agent = new https.Agent({
+const agent = new https.Agent({
   maxCachedSessions: 1
 });
 
-var server = https.createServer(options, function(req, res) {
+const server = https.createServer(options, function(req, res) {
   if (req.url === '/drop-key')
     server.setTicketKeys(crypto.randomBytes(48));
 
   serverRequests++;
   res.end('ok');
 }).listen(0, function() {
-  var queue = [
+  const queue = [
     {
       name: 'first',
 
@@ -97,7 +97,7 @@ var server = https.createServer(options, function(req, res) {
   ];
 
   function request() {
-    var options = queue.shift();
+    const options = queue.shift();
     options.agent = agent;
     https.request(options, function(res) {
       clientSessions[options.name] = res.socket.getSession();
@@ -114,9 +114,9 @@ var server = https.createServer(options, function(req, res) {
 });
 
 process.on('exit', function() {
-  assert.equal(serverRequests, 6);
-  assert.equal(clientSessions['first'].toString('hex'),
-               clientSessions['first-reuse'].toString('hex'));
+  assert.strictEqual(serverRequests, 6);
+  assert.strictEqual(clientSessions['first'].toString('hex'),
+                     clientSessions['first-reuse'].toString('hex'));
   assert.notEqual(clientSessions['first'].toString('hex'),
                   clientSessions['cipher-change'].toString('hex'));
   assert.notEqual(clientSessions['first'].toString('hex'),
@@ -125,6 +125,6 @@ process.on('exit', function() {
                   clientSessions['before-drop'].toString('hex'));
   assert.notEqual(clientSessions['before-drop'].toString('hex'),
                   clientSessions['after-drop'].toString('hex'));
-  assert.equal(clientSessions['after-drop'].toString('hex'),
-               clientSessions['after-drop-reuse'].toString('hex'));
+  assert.strictEqual(clientSessions['after-drop'].toString('hex'),
+                     clientSessions['after-drop-reuse'].toString('hex'));
 });
diff --git a/test/parallel/test-https-truncate.js b/test/parallel/test-https-truncate.js
index 6baf77d0fbbef2..4101a8c974e736 100644
--- a/test/parallel/test-https-truncate.js
+++ b/test/parallel/test-https-truncate.js
@@ -1,34 +1,34 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var https = require('https');
+const https = require('https');
 
-var fs = require('fs');
+const fs = require('fs');
 
-var key = fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem');
-var cert = fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem');
+const key = fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem');
+const cert = fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem');
 
 // number of bytes discovered empirically to trigger the bug
-var data = new Buffer(1024 * 32 + 1);
+const data = Buffer.allocUnsafe(1024 * 32 + 1);
 
 httpsTest();
 
 function httpsTest() {
-  var sopt = { key: key, cert: cert };
+  const sopt = { key: key, cert: cert };
 
-  var server = https.createServer(sopt, function(req, res) {
+  const server = https.createServer(sopt, function(req, res) {
     res.setHeader('content-length', data.length);
     res.end(data);
     server.close();
   });
 
   server.listen(0, function() {
-    var opts = { port: this.address().port, rejectUnauthorized: false };
+    const opts = { port: this.address().port, rejectUnauthorized: false };
     https.get(opts).on('response', function(res) {
       test(res);
     });
@@ -38,14 +38,14 @@ function httpsTest() {
 
 function test(res) {
   res.on('end', function() {
-    assert.equal(res._readableState.length, 0);
-    assert.equal(bytes, data.length);
+    assert.strictEqual(res._readableState.length, 0);
+    assert.strictEqual(bytes, data.length);
     console.log('ok');
   });
 
   // Pause and then resume on each chunk, to ensure that there will be
   // a lone byte hanging out at the very end.
-  var bytes = 0;
+  let bytes = 0;
   res.on('data', function(chunk) {
     bytes += chunk.length;
     this.pause();
diff --git a/test/parallel/test-net-better-error-messages-listen-path.js b/test/parallel/test-net-better-error-messages-listen-path.js
index 41d22c3fb9a4b5..50ed80a5e3cd1e 100644
--- a/test/parallel/test-net-better-error-messages-listen-path.js
+++ b/test/parallel/test-net-better-error-messages-listen-path.js
@@ -1,10 +1,10 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var net = require('net');
-var fp = '/blah/fadfa';
-var server = net.createServer(common.fail);
+const common = require('../common');
+const assert = require('assert');
+const net = require('net');
+const fp = '/blah/fadfa';
+const server = net.createServer(common.fail);
 server.listen(fp, common.fail);
 server.on('error', common.mustCall(function(e) {
-  assert.equal(e.address, fp);
+  assert.strictEqual(e.address, fp);
 }));
diff --git a/test/parallel/test-net-better-error-messages-listen.js b/test/parallel/test-net-better-error-messages-listen.js
index 44adce71a7d541..15ef4036aaa89a 100644
--- a/test/parallel/test-net-better-error-messages-listen.js
+++ b/test/parallel/test-net-better-error-messages-listen.js
@@ -1,12 +1,12 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var net = require('net');
+const common = require('../common');
+const assert = require('assert');
+const net = require('net');
 
-var server = net.createServer(common.fail);
+const server = net.createServer(common.fail);
 server.listen(1, '1.1.1.1', common.fail);
 server.on('error', common.mustCall(function(e) {
-  assert.equal(e.address, '1.1.1.1');
-  assert.equal(e.port, 1);
-  assert.equal(e.syscall, 'listen');
+  assert.strictEqual(e.address, '1.1.1.1');
+  assert.strictEqual(e.port, 1);
+  assert.strictEqual(e.syscall, 'listen');
 }));
diff --git a/test/parallel/test-net-better-error-messages-port-hostname.js b/test/parallel/test-net-better-error-messages-port-hostname.js
index 23089baf448a39..b08c35f3e63ea5 100644
--- a/test/parallel/test-net-better-error-messages-port-hostname.js
+++ b/test/parallel/test-net-better-error-messages-port-hostname.js
@@ -1,14 +1,14 @@
 'use strict';
-var common = require('../common');
-var net = require('net');
-var assert = require('assert');
+const common = require('../common');
+const net = require('net');
+const assert = require('assert');
 
-var c = net.createConnection(common.PORT, '***');
+const c = net.createConnection(common.PORT, '***');
 
 c.on('connect', common.fail);
 
 c.on('error', common.mustCall(function(e) {
-  assert.equal(e.code, 'ENOTFOUND');
-  assert.equal(e.port, common.PORT);
-  assert.equal(e.hostname, '***');
+  assert.strictEqual(e.code, 'ENOTFOUND');
+  assert.strictEqual(e.port, common.PORT);
+  assert.strictEqual(e.hostname, '***');
 }));
diff --git a/test/parallel/test-net-better-error-messages-port.js b/test/parallel/test-net-better-error-messages-port.js
index 514e317fbb0b15..9d74438c5f923b 100644
--- a/test/parallel/test-net-better-error-messages-port.js
+++ b/test/parallel/test-net-better-error-messages-port.js
@@ -1,14 +1,14 @@
 'use strict';
-var common = require('../common');
-var net = require('net');
-var assert = require('assert');
+const common = require('../common');
+const net = require('net');
+const assert = require('assert');
 
-var c = net.createConnection(common.PORT);
+const c = net.createConnection(common.PORT);
 
 c.on('connect', common.fail);
 
 c.on('error', common.mustCall(function(e) {
-  assert.equal(e.code, 'ECONNREFUSED');
-  assert.equal(e.port, common.PORT);
-  assert.equal(e.address, '127.0.0.1');
+  assert.strictEqual(e.code, 'ECONNREFUSED');
+  assert.strictEqual(e.port, common.PORT);
+  assert.strictEqual(e.address, '127.0.0.1');
 }));
diff --git a/test/parallel/test-net-localerror.js b/test/parallel/test-net-localerror.js
index ed7c9471e0397f..1793a3de3b9171 100644
--- a/test/parallel/test-net-localerror.js
+++ b/test/parallel/test-net-localerror.js
@@ -1,19 +1,19 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var net = require('net');
+const common = require('../common');
+const assert = require('assert');
+const net = require('net');
 
 connect({
   host: 'localhost',
   port: common.PORT,
   localPort: 'foobar',
-}, 'localPort should be a number: foobar');
+}, /^TypeError: localPort should be a number: foobar$/);
 
 connect({
   host: 'localhost',
   port: common.PORT,
   localAddress: 'foobar',
-}, 'localAddress should be a valid IP: foobar');
+}, /^TypeError: localAddress must be a valid IP: foobar$/);
 
 function connect(opts, msg) {
   assert.throws(function() {
diff --git a/test/parallel/test-net-pingpong.js b/test/parallel/test-net-pingpong.js
index 33fbafd8f97861..b49b3a78778719 100644
--- a/test/parallel/test-net-pingpong.js
+++ b/test/parallel/test-net-pingpong.js
@@ -1,87 +1,87 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-
-var net = require('net');
-
-var tests_run = 0;
+const common = require('../common');
+const assert = require('assert');
+const net = require('net');
 
 function pingPongTest(port, host) {
-  var N = 1000;
+  const N = 1000;
   var count = 0;
   var sentPongs = 0;
   var sent_final_ping = false;
 
-  var server = net.createServer({ allowHalfOpen: true }, function(socket) {
-    console.log('connection: ' + socket.remoteAddress);
-    assert.equal(server, socket.server);
-    assert.equal(1, server.connections);
+  const server = net.createServer(
+    { allowHalfOpen: true },
+    common.mustCall(onSocket)
+  );
+
+  function onSocket(socket) {
+    assert.strictEqual(socket.server, server);
+    server.getConnections(common.mustCall(function(err, connections) {
+      assert.ifError(err);
+      assert.strictEqual(connections, 1);
+    }));
 
     socket.setNoDelay();
     socket.timeout = 0;
 
     socket.setEncoding('utf8');
-    socket.on('data', function(data) {
+    socket.on('data', common.mustCall(function(data) {
       // Since we never queue data (we're always waiting for the PING
       // before sending a pong) the writeQueueSize should always be less
       // than one message.
       assert.ok(0 <= socket.bufferSize && socket.bufferSize <= 4);
 
-      assert.equal(true, socket.writable);
-      assert.equal(true, socket.readable);
-      assert.equal(true, count <= N);
-      assert.equal(data, 'PING');
+      assert.strictEqual(socket.writable, true);
+      assert.strictEqual(socket.readable, true);
+      assert.ok(count <= N);
+      assert.strictEqual(data, 'PING');
 
-      socket.write('PONG', function() {
+      socket.write('PONG', common.mustCall(function() {
         sentPongs++;
-      });
-    });
+      }));
+    }, N + 1));
 
-    socket.on('end', function() {
-      assert.equal(true, socket.allowHalfOpen);
-      assert.equal(true, socket.writable); // because allowHalfOpen
-      assert.equal(false, socket.readable);
+    socket.on('end', common.mustCall(function() {
+      assert.strictEqual(socket.allowHalfOpen, true);
+      assert.strictEqual(socket.writable, true); // because allowHalfOpen
+      assert.strictEqual(socket.readable, false);
       socket.end();
-    });
+    }));
 
-    socket.on('error', function(e) {
-      throw e;
-    });
+    socket.on('error', common.fail);
 
-    socket.on('close', function() {
-      console.log('server socket.end');
-      assert.equal(false, socket.writable);
-      assert.equal(false, socket.readable);
+    socket.on('close', common.mustCall(function() {
+      assert.strictEqual(socket.writable, false);
+      assert.strictEqual(socket.readable, false);
       socket.server.close();
-    });
-  });
+    }));
+  }
 
 
-  server.listen(port, host, function() {
+  server.listen(port, host, common.mustCall(function() {
     if (this.address().port)
       port = this.address().port;
-    console.log(`server listening on ${port} ${host}`);
 
-    var client = net.createConnection(port, host);
+    const client = net.createConnection(port, host);
 
     client.setEncoding('ascii');
-    client.on('connect', function() {
-      assert.equal(true, client.readable);
-      assert.equal(true, client.writable);
+    client.on('connect', common.mustCall(function() {
+      assert.strictEqual(client.readable, true);
+      assert.strictEqual(client.writable, true);
       client.write('PING');
-    });
+    }));
 
-    client.on('data', function(data) {
-      assert.equal('PONG', data);
+    client.on('data', common.mustCall(function(data) {
+      assert.strictEqual(data, 'PONG');
       count += 1;
 
       if (sent_final_ping) {
-        assert.equal(false, client.writable);
-        assert.equal(true, client.readable);
+        assert.strictEqual(client.writable, false);
+        assert.strictEqual(client.readable, true);
         return;
       } else {
-        assert.equal(true, client.writable);
-        assert.equal(true, client.readable);
+        assert.strictEqual(client.writable, true);
+        assert.strictEqual(client.readable, true);
       }
 
       if (count < N) {
@@ -91,20 +91,16 @@ function pingPongTest(port, host) {
         client.write('PING');
         client.end();
       }
-    });
-
-    client.on('close', function() {
-      console.log('client.end');
-      assert.equal(N + 1, count);
-      assert.equal(N + 1, sentPongs);
-      assert.equal(true, sent_final_ping);
-      tests_run += 1;
-    });
-
-    client.on('error', function(e) {
-      throw e;
-    });
-  });
+    }, N + 1));
+
+    client.on('close', common.mustCall(function() {
+      assert.strictEqual(count, N + 1);
+      assert.strictEqual(sentPongs, N + 1);
+      assert.strictEqual(sent_final_ping, true);
+    }));
+
+    client.on('error', common.fail);
+  }));
 }
 
 /* All are run at once, so run on different ports */
@@ -114,11 +110,3 @@ pingPongTest(0);
 pingPongTest(0, 'localhost');
 if (common.hasIPv6)
   pingPongTest(0, '::1');
-
-process.on('exit', function() {
-  if (common.hasIPv6)
-    assert.equal(4, tests_run);
-  else
-    assert.equal(3, tests_run);
-  console.log('done');
-});
diff --git a/test/parallel/test-next-tick-when-exiting.js b/test/parallel/test-next-tick-when-exiting.js
new file mode 100644
index 00000000000000..1bb4c914d01869
--- /dev/null
+++ b/test/parallel/test-next-tick-when-exiting.js
@@ -0,0 +1,14 @@
+'use strict';
+
+const common = require('../common');
+const assert = require('assert');
+
+process.on('exit', () => {
+  assert.strictEqual(process._exiting, true, 'process._exiting was not set!');
+
+  process.nextTick(() => {
+    common.fail('process is exiting, should not be called.');
+  });
+});
+
+process.exit();
diff --git a/test/parallel/test-os-homedir-no-envvar.js b/test/parallel/test-os-homedir-no-envvar.js
index cb4be4e6efcd4e..94d8ab5a08fa14 100644
--- a/test/parallel/test-os-homedir-no-envvar.js
+++ b/test/parallel/test-os-homedir-no-envvar.js
@@ -1,28 +1,28 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var cp = require('child_process');
-var os = require('os');
-var path = require('path');
+const common = require('../common');
+const assert = require('assert');
+const cp = require('child_process');
+const os = require('os');
+const path = require('path');
 
 
 if (process.argv[2] === 'child') {
   if (common.isWindows)
-    assert.equal(process.env.USERPROFILE, undefined);
+    assert.strictEqual(process.env.USERPROFILE, undefined);
   else
-    assert.equal(process.env.HOME, undefined);
+    assert.strictEqual(process.env.HOME, undefined);
 
-  var home = os.homedir();
+  const home = os.homedir();
 
-  assert.ok(typeof home === 'string');
-  assert.ok(home.indexOf(path.sep) !== -1);
+  assert.strictEqual(typeof home, 'string');
+  assert(home.includes(path.sep));
 } else {
   if (common.isWindows)
     delete process.env.USERPROFILE;
   else
     delete process.env.HOME;
 
-  var child = cp.spawnSync(process.execPath, [__filename, 'child'], {
+  const child = cp.spawnSync(process.execPath, [__filename, 'child'], {
     env: process.env
   });
 
diff --git a/test/parallel/test-process-execpath.js b/test/parallel/test-process-execpath.js
new file mode 100644
index 00000000000000..5ac8a3f2238a7c
--- /dev/null
+++ b/test/parallel/test-process-execpath.js
@@ -0,0 +1,28 @@
+'use strict';
+const common = require('../common');
+const assert = require('assert');
+const child_process = require('child_process');
+const path = require('path');
+const fs = require('fs');
+
+assert.strictEqual(process.execPath, fs.realpathSync(process.execPath));
+
+if (common.isWindows) {
+  common.skip('symlinks are weird on windows');
+  return;
+}
+
+if (process.argv[2] === 'child') {
+  // The console.log() output is part of the test here.
+  console.log(process.execPath);
+} else {
+  common.refreshTmpDir();
+
+  const symlinkedNode = path.join(common.tmpDir, 'symlinked-node');
+  fs.symlinkSync(process.execPath, symlinkedNode);
+
+  const proc = child_process.spawnSync(symlinkedNode, [__filename, 'child']);
+  assert.strictEqual(proc.stderr.toString(), '');
+  assert.strictEqual(proc.stdout.toString(), `${process.execPath}\n`);
+  assert.strictEqual(proc.status, 0);
+}
diff --git a/test/parallel/test-punycode.js b/test/parallel/test-punycode.js
index abd495e4a9957b..e869e6a33bf064 100644
--- a/test/parallel/test-punycode.js
+++ b/test/parallel/test-punycode.js
@@ -1,153 +1,224 @@
 'use strict';
 require('../common');
-var punycode = require('punycode');
-var assert = require('assert');
+const punycode = require('punycode');
+const assert = require('assert');
 
-assert.equal(punycode.encode('ü'), 'tda');
-assert.equal(punycode.encode('Goethe'), 'Goethe-');
-assert.equal(punycode.encode('Bücher'), 'Bcher-kva');
-assert.equal(punycode.encode(
+assert.strictEqual(punycode.encode('ü'), 'tda');
+assert.strictEqual(punycode.encode('Goethe'), 'Goethe-');
+assert.strictEqual(punycode.encode('Bücher'), 'Bcher-kva');
+assert.strictEqual(punycode.encode(
     'Willst du die Blüthe des frühen, die Früchte des späteren Jahres'),
     'Willst du die Blthe des frhen, die Frchte des spteren Jahres-x9e96lkal');
-assert.equal(punycode.encode('日本語'), 'wgv71a119e');
+assert.strictEqual(punycode.encode('日本語'), 'wgv71a119e');
 
-assert.equal(punycode.decode('tda'), 'ü');
-assert.equal(punycode.decode('Goethe-'), 'Goethe');
-assert.equal(punycode.decode('Bcher-kva'), 'Bücher');
-assert.equal(punycode.decode(
+assert.strictEqual(punycode.decode('tda'), 'ü');
+assert.strictEqual(punycode.decode('Goethe-'), 'Goethe');
+assert.strictEqual(punycode.decode('Bcher-kva'), 'Bücher');
+assert.strictEqual(punycode.decode(
     'Willst du die Blthe des frhen, die Frchte des spteren Jahres-x9e96lkal'),
     'Willst du die Blüthe des frühen, die Früchte des späteren Jahres');
-assert.equal(punycode.decode('wgv71a119e'), '日本語');
+assert.strictEqual(punycode.decode('wgv71a119e'), '日本語');
 
 // http://tools.ietf.org/html/rfc3492#section-7.1
-var tests = {
+const tests = [
   // (A) Arabic (Egyptian)
-  'egbpdaj6bu4bxfgehfvwxn':
-      '\u0644\u064A\u0647\u0645\u0627\u0628\u062A\u0643\u0644\u0645\u0648' +
-      '\u0634\u0639\u0631\u0628\u064A\u061F',
+  {
+    encoded: 'egbpdaj6bu4bxfgehfvwxn',
+    decoded: '\u0644\u064A\u0647\u0645\u0627\u0628\u062A\u0643\u0644\u0645' +
+      '\u0648\u0634\u0639\u0631\u0628\u064A\u061F'
+  },
 
   // (B) Chinese (simplified)
-  'ihqwcrb4cv8a8dqg056pqjye':
-      '\u4ED6\u4EEC\u4E3A\u4EC0\u4E48\u4E0D\u8BF4\u4E2D\u6587',
+  {
+    encoded: 'ihqwcrb4cv8a8dqg056pqjye',
+    decoded: '\u4ED6\u4EEC\u4E3A\u4EC0\u4E48\u4E0D\u8BF4\u4E2D\u6587'
+  },
 
   // (C) Chinese (traditional)
-  'ihqwctvzc91f659drss3x8bo0yb':
-      '\u4ED6\u5011\u7232\u4EC0\u9EBD\u4E0D\u8AAA\u4E2D\u6587',
+  {
+    encoded: 'ihqwctvzc91f659drss3x8bo0yb',
+    decoded: '\u4ED6\u5011\u7232\u4EC0\u9EBD\u4E0D\u8AAA\u4E2D\u6587'
+  },
 
   // (D) Czech: Pro<ccaron>prost<ecaron>nemluv<iacute><ccaron>esky
-  'Proprostnemluvesky-uyb24dma41a':
-      '\u0050\u0072\u006F\u010D\u0070\u0072\u006F\u0073\u0074\u011B\u006E' +
-      '\u0065\u006D\u006C\u0075\u0076\u00ED\u010D\u0065\u0073\u006B\u0079',
+  {
+    encoded: 'Proprostnemluvesky-uyb24dma41a',
+    decoded: '\u0050\u0072\u006F\u010D\u0070\u0072\u006F\u0073\u0074\u011B' +
+      '\u006E\u0065\u006D\u006C\u0075\u0076\u00ED\u010D\u0065\u0073\u006B\u0079'
+  },
 
   // (E) Hebrew
-  '4dbcagdahymbxekheh6e0a7fei0b':
-      '\u05DC\u05DE\u05D4\u05D4\u05DD\u05E4\u05E9\u05D5\u05D8\u05DC\u05D0' +
-      '\u05DE\u05D3\u05D1\u05E8\u05D9\u05DD\u05E2\u05D1\u05E8\u05D9\u05EA',
+  {
+    encoded: '4dbcagdahymbxekheh6e0a7fei0b',
+    decoded: '\u05DC\u05DE\u05D4\u05D4\u05DD\u05E4\u05E9\u05D5\u05D8\u05DC' +
+      '\u05D0\u05DE\u05D3\u05D1\u05E8\u05D9\u05DD\u05E2\u05D1\u05E8\u05D9\u05EA'
+  },
 
   // (F) Hindi (Devanagari)
-  'i1baa7eci9glrd9b2ae1bj0hfcgg6iyaf8o0a1dig0cd':
-      '\u092F\u0939\u0932\u094B\u0917\u0939\u093F\u0928\u094D\u0926\u0940' +
-      '\u0915\u094D\u092F\u094B\u0902\u0928\u0939\u0940\u0902\u092C\u094B' +
-      '\u0932\u0938\u0915\u0924\u0947\u0939\u0948\u0902',
+  {
+    encoded: 'i1baa7eci9glrd9b2ae1bj0hfcgg6iyaf8o0a1dig0cd',
+    decoded: '\u092F\u0939\u0932\u094B\u0917\u0939\u093F\u0928\u094D\u0926' +
+      '\u0940\u0915\u094D\u092F\u094B\u0902\u0928\u0939\u0940\u0902\u092C' +
+      '\u094B\u0932\u0938\u0915\u0924\u0947\u0939\u0948\u0902'
+  },
 
   // (G) Japanese (kanji and hiragana)
-  'n8jok5ay5dzabd5bym9f0cm5685rrjetr6pdxa':
-      '\u306A\u305C\u307F\u3093\u306A\u65E5\u672C\u8A9E\u3092\u8A71\u3057' +
-      '\u3066\u304F\u308C\u306A\u3044\u306E\u304B',
+  {
+    encoded: 'n8jok5ay5dzabd5bym9f0cm5685rrjetr6pdxa',
+    decoded: '\u306A\u305C\u307F\u3093\u306A\u65E5\u672C\u8A9E\u3092\u8A71' +
+      '\u3057\u3066\u304F\u308C\u306A\u3044\u306E\u304B'
+  },
 
   // (H) Korean (Hangul syllables)
-  '989aomsvi5e83db1d2a355cv1e0vak1dwrv93d5xbh15a0dt30a5jpsd879ccm6fea98c':
-      '\uC138\uACC4\uC758\uBAA8\uB4E0\uC0AC\uB78C\uB4E4\uC774\uD55C\uAD6D' +
-      '\uC5B4\uB97C\uC774\uD574\uD55C\uB2E4\uBA74\uC5BC\uB9C8\uB098\uC88B' +
-      '\uC744\uAE4C',
+  {
+    encoded: '989aomsvi5e83db1d2a355cv1e0vak1dwrv93d5xbh15a0dt30a5jpsd879' +
+      'ccm6fea98c',
+    decoded: '\uC138\uACC4\uC758\uBAA8\uB4E0\uC0AC\uB78C\uB4E4\uC774\uD55C' +
+      '\uAD6D\uC5B4\uB97C\uC774\uD574\uD55C\uB2E4\uBA74\uC5BC\uB9C8\uB098' +
+      '\uC88B\uC744\uAE4C'
+  },
 
   // (I) Russian (Cyrillic)
-  'b1abfaaepdrnnbgefbadotcwatmq2g4l':
-      '\u043F\u043E\u0447\u0435\u043C\u0443\u0436\u0435\u043E\u043D\u0438' +
-      '\u043D\u0435\u0433\u043E\u0432\u043E\u0440\u044F\u0442\u043F\u043E' +
-      '\u0440\u0443\u0441\u0441\u043A\u0438',
+  {
+    encoded: 'b1abfaaepdrnnbgefbadotcwatmq2g4l',
+    decoded: '\u043F\u043E\u0447\u0435\u043C\u0443\u0436\u0435\u043E\u043D' +
+      '\u0438\u043D\u0435\u0433\u043E\u0432\u043E\u0440\u044F\u0442\u043F' +
+      '\u043E\u0440\u0443\u0441\u0441\u043A\u0438'
+  },
 
   // (J) Spanish: Porqu<eacute>nopuedensimplementehablarenEspa<ntilde>ol
-  'PorqunopuedensimplementehablarenEspaol-fmd56a':
-      '\u0050\u006F\u0072\u0071\u0075\u00E9\u006E\u006F\u0070\u0075\u0065' +
-      '\u0064\u0065\u006E\u0073\u0069\u006D\u0070\u006C\u0065\u006D\u0065' +
-      '\u006E\u0074\u0065\u0068\u0061\u0062\u006C\u0061\u0072\u0065\u006E' +
-      '\u0045\u0073\u0070\u0061\u00F1\u006F\u006C',
+  {
+    encoded: 'PorqunopuedensimplementehablarenEspaol-fmd56a',
+    decoded: '\u0050\u006F\u0072\u0071\u0075\u00E9\u006E\u006F\u0070\u0075' +
+      '\u0065\u0064\u0065\u006E\u0073\u0069\u006D\u0070\u006C\u0065\u006D' +
+      '\u0065\u006E\u0074\u0065\u0068\u0061\u0062\u006C\u0061\u0072\u0065' +
+      '\u006E\u0045\u0073\u0070\u0061\u00F1\u006F\u006C'
+  },
 
   // (K) Vietnamese: T<adotbelow>isaoh<odotbelow>kh<ocirc>ngth
   // <ecirchookabove>ch<ihookabove>n<oacute>iti<ecircacute>ngVi<ecircdotbelow>t
-  'TisaohkhngthchnitingVit-kjcr8268qyxafd2f1b9g':
-      '\u0054\u1EA1\u0069\u0073\u0061\u006F\u0068\u1ECD\u006B\u0068\u00F4' +
-      '\u006E\u0067\u0074\u0068\u1EC3\u0063\u0068\u1EC9\u006E\u00F3\u0069' +
-      '\u0074\u0069\u1EBF\u006E\u0067\u0056\u0069\u1EC7\u0074',
+  {
+    encoded: 'TisaohkhngthchnitingVit-kjcr8268qyxafd2f1b9g',
+    decoded: '\u0054\u1EA1\u0069\u0073\u0061\u006F\u0068\u1ECD\u006B\u0068' +
+      '\u00F4\u006E\u0067\u0074\u0068\u1EC3\u0063\u0068\u1EC9\u006E\u00F3' +
+      '\u0069\u0074\u0069\u1EBF\u006E\u0067\u0056\u0069\u1EC7\u0074'
+  },
 
   // (L) 3<nen>B<gumi><kinpachi><sensei>
-  '3B-ww4c5e180e575a65lsy2b':
-      '\u0033\u5E74\u0042\u7D44\u91D1\u516B\u5148\u751F',
+  {
+    encoded: '3B-ww4c5e180e575a65lsy2b',
+    decoded: '\u0033\u5E74\u0042\u7D44\u91D1\u516B\u5148\u751F'
+  },
 
   // (M) <amuro><namie>-with-SUPER-MONKEYS
-  '-with-SUPER-MONKEYS-pc58ag80a8qai00g7n9n':
-      '\u5B89\u5BA4\u5948\u7F8E\u6075\u002D\u0077\u0069\u0074\u0068\u002D' +
-      '\u0053\u0055\u0050\u0045\u0052\u002D\u004D\u004F\u004E\u004B\u0045' +
-      '\u0059\u0053',
+  {
+    encoded: '-with-SUPER-MONKEYS-pc58ag80a8qai00g7n9n',
+    decoded: '\u5B89\u5BA4\u5948\u7F8E\u6075\u002D\u0077\u0069\u0074\u0068' +
+      '\u002D\u0053\u0055\u0050\u0045\u0052\u002D\u004D\u004F\u004E\u004B' +
+      '\u0045\u0059\u0053'
+  },
 
   // (N) Hello-Another-Way-<sorezore><no><basho>
-  'Hello-Another-Way--fc4qua05auwb3674vfr0b':
-      '\u0048\u0065\u006C\u006C\u006F\u002D\u0041\u006E\u006F\u0074\u0068' +
-      '\u0065\u0072\u002D\u0057\u0061\u0079\u002D\u305D\u308C\u305E\u308C' +
-      '\u306E\u5834\u6240',
+  {
+    encoded: 'Hello-Another-Way--fc4qua05auwb3674vfr0b',
+    decoded: '\u0048\u0065\u006C\u006C\u006F\u002D\u0041\u006E\u006F\u0074' +
+      '\u0068\u0065\u0072\u002D\u0057\u0061\u0079\u002D\u305D\u308C\u305E' +
+      '\u308C\u306E\u5834\u6240'
+  },
 
   // (O) <hitotsu><yane><no><shita>2
-  '2-u9tlzr9756bt3uc0v':
-      '\u3072\u3068\u3064\u5C4B\u6839\u306E\u4E0B\u0032',
+  {
+    encoded: '2-u9tlzr9756bt3uc0v',
+    decoded: '\u3072\u3068\u3064\u5C4B\u6839\u306E\u4E0B\u0032'
+  },
 
   // (P) Maji<de>Koi<suru>5<byou><mae>
-  'MajiKoi5-783gue6qz075azm5e':
-      '\u004D\u0061\u006A\u0069\u3067\u004B\u006F\u0069\u3059\u308B\u0035' +
-      '\u79D2\u524D',
+  {
+    encoded: 'MajiKoi5-783gue6qz075azm5e',
+    decoded: '\u004D\u0061\u006A\u0069\u3067\u004B\u006F\u0069\u3059\u308B' +
+      '\u0035\u79D2\u524D'
+  },
 
   // (Q) <pafii>de<runba>
-  'de-jg4avhby1noc0d':
-      '\u30D1\u30D5\u30A3\u30FC\u0064\u0065\u30EB\u30F3\u30D0',
+  {
+    encoded: 'de-jg4avhby1noc0d',
+    decoded: '\u30D1\u30D5\u30A3\u30FC\u0064\u0065\u30EB\u30F3\u30D0'
+  },
 
   // (R) <sono><supiido><de>
-  'd9juau41awczczp':
-      '\u305D\u306E\u30B9\u30D4\u30FC\u30C9\u3067',
+  {
+    encoded: 'd9juau41awczczp',
+    decoded: '\u305D\u306E\u30B9\u30D4\u30FC\u30C9\u3067'
+  },
 
   // (S) -> $1.00 <-
-  '-> $1.00 <--':
-      '\u002D\u003E\u0020\u0024\u0031\u002E\u0030\u0030\u0020\u003C\u002D'
+  {
+    encoded: '-> $1.00 <--',
+    decoded: '\u002D\u003E\u0020\u0024\u0031\u002E\u0030\u0030\u0020\u003C' +
+      '\u002D'
+  }
+];
+
+let errors = 0;
+const handleError = (error, name) => {
+  console.error(
+    'FAIL: %s expected %j, got %j',
+    name,
+    error.expected,
+    error.actual
+  );
+  errors++;
 };
 
-var errors = 0;
+const regexNonASCII = /[^\x20-\x7E]/;
+const testBattery = {
+  encode: (test) => assert.strictEqual(
+    punycode.encode(test.decoded),
+    test.encoded
+  ),
+  decode: (test) => assert.strictEqual(
+    punycode.decode(test.encoded),
+    test.decoded
+  ),
+  toASCII: (test) => assert.strictEqual(
+    punycode.toASCII(test.decoded),
+    regexNonASCII.test(test.decoded)
+      ? `xn--${test.encoded}`
+      : test.decoded
+  ),
+  toUnicode: (test) => assert.strictEqual(
+    punycode.toUnicode(
+      regexNonASCII.test(test.decoded)
+        ? `xn--${test.encoded}`
+        : test.decoded
+    ),
+    regexNonASCII.test(test.decoded)
+      ? test.decoded.toLowerCase()
+      : test.decoded
+  )
+};
 
-for (var encoded in tests) {
-  var decoded = tests[encoded];
-  try {
-    assert.equal(punycode.encode(decoded), encoded);
-  } catch (e) {
-    console.error('FAIL: expected %j, got %j', e.expected, e.actual);
-    errors++;
-  }
-  try {
-    assert.equal(punycode.decode(encoded), decoded);
-  } catch (e) {
-    console.error('FAIL: expected %j, got %j', e.expected, e.actual);
-    errors++;
-  }
-}
+tests.forEach((testCase) => {
+  Object.keys(testBattery).forEach((key) => {
+    try {
+      testBattery[key](testCase);
+    } catch (error) {
+      handleError(error, key);
+    }
+  });
+});
 
 // BMP code point
-assert.equal(punycode.ucs2.encode([0x61]), 'a');
+assert.strictEqual(punycode.ucs2.encode([0x61]), 'a');
 // supplementary code point (surrogate pair)
-assert.equal(punycode.ucs2.encode([0x1D306]), '\uD834\uDF06');
+assert.strictEqual(punycode.ucs2.encode([0x1D306]), '\uD834\uDF06');
 // high surrogate
-assert.equal(punycode.ucs2.encode([0xD800]), '\uD800');
+assert.strictEqual(punycode.ucs2.encode([0xD800]), '\uD800');
 // high surrogate followed by non-surrogates
-assert.equal(punycode.ucs2.encode([0xD800, 0x61, 0x62]), '\uD800ab');
+assert.strictEqual(punycode.ucs2.encode([0xD800, 0x61, 0x62]), '\uD800ab');
 // low surrogate
-assert.equal(punycode.ucs2.encode([0xDC00]), '\uDC00');
+assert.strictEqual(punycode.ucs2.encode([0xDC00]), '\uDC00');
 // low surrogate followed by non-surrogates
-assert.equal(punycode.ucs2.encode([0xDC00, 0x61, 0x62]), '\uDC00ab');
+assert.strictEqual(punycode.ucs2.encode([0xDC00, 0x61, 0x62]), '\uDC00ab');
 
-assert.equal(errors, 0);
+assert.strictEqual(errors, 0);
diff --git a/test/parallel/test-regress-GH-897.js b/test/parallel/test-regress-GH-897.js
deleted file mode 100644
index 1b46994dc37d94..00000000000000
--- a/test/parallel/test-regress-GH-897.js
+++ /dev/null
@@ -1,15 +0,0 @@
-'use strict';
-require('../common');
-var assert = require('assert');
-
-var t = Date.now();
-var diff;
-setTimeout(function() {
-  diff = Date.now() - t;
-  console.error(diff);
-}, 0.1);
-
-
-process.on('exit', function() {
-  assert.ok(diff < 100);
-});
diff --git a/test/parallel/test-repl-envvars.js b/test/parallel/test-repl-envvars.js
index 759b4e15a12f46..b08f6cbaf621e6 100644
--- a/test/parallel/test-repl-envvars.js
+++ b/test/parallel/test-repl-envvars.js
@@ -2,7 +2,7 @@
 
 // Flags: --expose-internals
 
-require('../common');
+const common = require('../common');
 const stream = require('stream');
 const REPL = require('internal/repl');
 const assert = require('assert');
@@ -46,6 +46,10 @@ function run(test) {
 
   REPL.createInternalRepl(env, opts, function(err, repl) {
     if (err) throw err;
+
+    // The REPL registers 'module' and 'require' globals
+    common.allowGlobals(repl.context.module, repl.context.require);
+
     assert.equal(expected.terminal, repl.terminal,
                  'Expected ' + inspect(expected) + ' with ' + inspect(env));
     assert.equal(expected.useColors, repl.useColors,
diff --git a/test/parallel/test-repl-history-perm.js b/test/parallel/test-repl-history-perm.js
index c7d2852539a01d..4a374cb0ab12e8 100644
--- a/test/parallel/test-repl-history-perm.js
+++ b/test/parallel/test-repl-history-perm.js
@@ -35,6 +35,10 @@ const replHistoryPath = path.join(common.tmpDir, '.node_repl_history');
 const checkResults = common.mustCall(function(err, r) {
   if (err)
     throw err;
+
+  // The REPL registers 'module' and 'require' globals
+  common.allowGlobals(r.context.module, r.context.require);
+
   r.input.end();
   const stat = fs.statSync(replHistoryPath);
   assert.strictEqual(
diff --git a/test/parallel/test-repl-persistent-history.js b/test/parallel/test-repl-persistent-history.js
index e8b6d416f00ec4..29ca0d56344bc9 100644
--- a/test/parallel/test-repl-persistent-history.js
+++ b/test/parallel/test-repl-persistent-history.js
@@ -262,6 +262,12 @@ function runTest(assertCleaned) {
       throw err;
     }
 
+    // The REPL registers 'module' and 'require' globals.
+    // This test also registers '_'.
+    common.allowGlobals(repl.context.module,
+                        repl.context.require,
+                        repl.context._);
+
     repl.once('close', () => {
       if (repl._flushing) {
         repl.once('flushHistory', onClose);
diff --git a/test/parallel/test-repl-reset-event.js b/test/parallel/test-repl-reset-event.js
index eee61ac17356f4..190aa2227de9a3 100644
--- a/test/parallel/test-repl-reset-event.js
+++ b/test/parallel/test-repl-reset-event.js
@@ -1,52 +1,49 @@
 'use strict';
-var common = require('../common');
+const common = require('../common');
 common.globalCheck = false;
 
-var assert = require('assert');
-var repl = require('repl');
+const assert = require('assert');
+const repl = require('repl');
 
 // Create a dummy stream that does nothing
 const dummy = new common.ArrayStream();
 
 function testReset(cb) {
-  var r = repl.start({
+  const r = repl.start({
     input: dummy,
     output: dummy,
     useGlobal: false
   });
   r.context.foo = 42;
-  r.on('reset', function(context) {
+  r.on('reset', common.mustCall(function(context) {
     assert(!!context, 'REPL did not emit a context with reset event');
-    assert.equal(context, r.context, 'REPL emitted incorrect context');
-    assert.equal(context.foo, undefined, 'REPL emitted the previous context' +
-                 ', and is not using global as context');
+    assert.strictEqual(context, r.context, 'REPL emitted incorrect context');
+    assert.strictEqual(
+      context.foo,
+      undefined,
+      'REPL emitted the previous context, and is not using global as context'
+    );
     context.foo = 42;
     cb();
-  });
+  }));
   r.resetContext();
 }
 
-function testResetGlobal(cb) {
-  var r = repl.start({
+function testResetGlobal() {
+  const r = repl.start({
     input: dummy,
     output: dummy,
     useGlobal: true
   });
   r.context.foo = 42;
-  r.on('reset', function(context) {
-    assert.equal(context.foo, 42,
-                 '"foo" property is missing from REPL using global as context');
-    cb();
-  });
+  r.on('reset', common.mustCall(function(context) {
+    assert.strictEqual(
+      context.foo,
+      42,
+      '"foo" property is missing from REPL using global as context'
+    );
+  }));
   r.resetContext();
 }
 
-var timeout = setTimeout(function() {
-  common.fail('Timeout, REPL did not emit reset events');
-}, 5000);
-
-testReset(function() {
-  testResetGlobal(function() {
-    clearTimeout(timeout);
-  });
-});
+testReset(common.mustCall(testResetGlobal));
diff --git a/test/parallel/test-repl.js b/test/parallel/test-repl.js
index 23a5a3d59fa3cb..1e84297ee75159 100644
--- a/test/parallel/test-repl.js
+++ b/test/parallel/test-repl.js
@@ -1,6 +1,6 @@
 /* eslint-disable max-len, strict */
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 common.globalCheck = false;
 common.refreshTmpDir();
@@ -19,7 +19,7 @@ var server_tcp, server_unix, client_tcp, client_unix, replServer;
 
 
 // absolute path to test/fixtures/a.js
-var moduleFilename = require('path').join(common.fixturesDir, 'a');
+const moduleFilename = require('path').join(common.fixturesDir, 'a');
 
 console.error('repl test');
 
@@ -30,7 +30,7 @@ global.invoke_me = function(arg) {
 
 function send_expect(list) {
   if (list.length > 0) {
-    var cur = list.shift();
+    const cur = list.shift();
 
     console.error('sending ' + JSON.stringify(cur.send));
 
@@ -72,7 +72,7 @@ function error_test() {
       if (read_buffer !== client_unix.expect) {
         var expect = client_unix.expect;
         if (expect === prompt_multiline)
-          expect = /[\.]{3} /;
+          expect = /[.]{3} /;
         assert.ok(read_buffer.match(expect));
         console.error('match');
       }
@@ -330,8 +330,8 @@ function tcp_test() {
     client_tcp = net.createConnection(this.address().port);
 
     client_tcp.on('connect', function() {
-      assert.equal(true, client_tcp.readable);
-      assert.equal(true, client_tcp.writable);
+      assert.strictEqual(true, client_tcp.readable);
+      assert.strictEqual(true, client_tcp.writable);
 
       send_expect([
         { client: client_tcp, send: '',
@@ -399,8 +399,8 @@ function unix_test() {
     client_unix = net.createConnection(common.PIPE);
 
     client_unix.on('connect', function() {
-      assert.equal(true, client_unix.readable);
-      assert.equal(true, client_unix.writable);
+      assert.strictEqual(true, client_unix.readable);
+      assert.strictEqual(true, client_unix.writable);
 
       send_expect([
         { client: client_unix, send: '',
diff --git a/test/parallel/test-require-dot.js b/test/parallel/test-require-dot.js
index 2fb161486a9241..26733c7fc438a1 100644
--- a/test/parallel/test-require-dot.js
+++ b/test/parallel/test-require-dot.js
@@ -1,17 +1,17 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var module = require('module');
+const common = require('../common');
+const assert = require('assert');
+const m = require('module');
 
-var a = require(common.fixturesDir + '/module-require/relative/dot.js');
-var b = require(common.fixturesDir + '/module-require/relative/dot-slash.js');
+const a = require(common.fixturesDir + '/module-require/relative/dot.js');
+const b = require(common.fixturesDir + '/module-require/relative/dot-slash.js');
 
-assert.equal(a.value, 42);
-assert.equal(a, b, 'require(".") should resolve like require("./")');
+assert.strictEqual(a.value, 42);
+assert.strictEqual(a, b, 'require(".") should resolve like require("./")');
 
 process.env.NODE_PATH = common.fixturesDir + '/module-require/relative';
-module._initPaths();
+m._initPaths();
 
-var c = require('.');
+const c = require('.');
 
-assert.equal(c.value, 42, 'require(".") should honor NODE_PATH');
+assert.strictEqual(c.value, 42, 'require(".") should honor NODE_PATH');
diff --git a/test/parallel/test-require-exceptions.js b/test/parallel/test-require-exceptions.js
index e7a191b47ad6f2..2ca57b98f1e2e7 100644
--- a/test/parallel/test-require-exceptions.js
+++ b/test/parallel/test-require-exceptions.js
@@ -1,16 +1,16 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 // A module with an error in it should throw
 assert.throws(function() {
   require(common.fixturesDir + '/throws_error');
-});
+}, /^Error: blah$/);
 
 // Requiring the same module again should throw as well
 assert.throws(function() {
   require(common.fixturesDir + '/throws_error');
-});
+}, /^Error: blah$/);
 
 // Requiring a module that does not exist should throw an
 // error with its `code` set to MODULE_NOT_FOUND
diff --git a/test/parallel/test-require-extensions-main.js b/test/parallel/test-require-extensions-main.js
index 0376082262dd78..e8420cd26cd512 100644
--- a/test/parallel/test-require-extensions-main.js
+++ b/test/parallel/test-require-extensions-main.js
@@ -1,4 +1,10 @@
 'use strict';
-var common = require('../common');
+const assert = require('assert');
+const common = require('../common');
+const fixturesRequire = require(`${common.fixturesDir}/require-bin/bin/req.js`);
 
-require(common.fixturesDir + '/require-bin/bin/req.js');
+assert.strictEqual(
+    fixturesRequire,
+    '',
+    'test-require-extensions-main failed to import fixture requirements'
+);
diff --git a/test/parallel/test-require-extensions-same-filename-as-dir.js b/test/parallel/test-require-extensions-same-filename-as-dir.js
index 41051dad45e10f..ff95a47b9a83bf 100644
--- a/test/parallel/test-require-extensions-same-filename-as-dir.js
+++ b/test/parallel/test-require-extensions-same-filename-as-dir.js
@@ -1,9 +1,9 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
-var content = require(common.fixturesDir +
+const content = require(common.fixturesDir +
   '/json-with-directory-name-module/module-stub/one/two/three.js');
 
-assert.notEqual(content.rocko, 'artischocko');
-assert.equal(content, 'hello from module-stub!');
+assert.notStrictEqual(content.rocko, 'artischocko');
+assert.strictEqual(content, 'hello from module-stub!');
diff --git a/test/parallel/test-require-resolve.js b/test/parallel/test-require-resolve.js
index 13897c74da1752..202f3c5ef87f3d 100644
--- a/test/parallel/test-require-resolve.js
+++ b/test/parallel/test-require-resolve.js
@@ -1,18 +1,18 @@
 'use strict';
-var common = require('../common');
-var fixturesDir = common.fixturesDir;
-var assert = require('assert');
-var path = require('path');
+const common = require('../common');
+const fixturesDir = common.fixturesDir;
+const assert = require('assert');
+const path = require('path');
 
-assert.equal(
+assert.strictEqual(
     path.join(__dirname, '../fixtures/a.js').toLowerCase(),
     require.resolve('../fixtures/a').toLowerCase());
-assert.equal(
+assert.strictEqual(
     path.join(fixturesDir, 'a.js').toLowerCase(),
     require.resolve(path.join(fixturesDir, 'a')).toLowerCase());
-assert.equal(
+assert.strictEqual(
     path.join(fixturesDir, 'nested-index', 'one', 'index.js').toLowerCase(),
     require.resolve('../fixtures/nested-index/one').toLowerCase());
-assert.equal('path', require.resolve('path'));
+assert.strictEqual('path', require.resolve('path'));
 
 console.log('ok');
diff --git a/test/parallel/test-signal-unregister.js b/test/parallel/test-signal-unregister.js
index b65ade73db9422..88c6a367a9cb37 100644
--- a/test/parallel/test-signal-unregister.js
+++ b/test/parallel/test-signal-unregister.js
@@ -1,13 +1,13 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var spawn = require('child_process').spawn;
+const common = require('../common');
+const assert = require('assert');
+const spawn = require('child_process').spawn;
 
-var child = spawn(process.argv[0], [common.fixturesDir + '/should_exit.js']);
+const child = spawn(process.argv[0], [common.fixturesDir + '/should_exit.js']);
 child.stdout.once('data', function() {
   child.kill('SIGINT');
 });
 child.on('exit', common.mustCall(function(exitCode, signalCode) {
-  assert.equal(exitCode, null);
-  assert.equal(signalCode, 'SIGINT');
+  assert.strictEqual(exitCode, null);
+  assert.strictEqual(signalCode, 'SIGINT');
 }));
diff --git a/test/parallel/test-stdin-from-file.js b/test/parallel/test-stdin-from-file.js
index d6e3afeae6fdee..f3a78192e5e5aa 100644
--- a/test/parallel/test-stdin-from-file.js
+++ b/test/parallel/test-stdin-from-file.js
@@ -1,44 +1,40 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var join = require('path').join;
-var childProcess = require('child_process');
-var fs = require('fs');
-
-var stdoutScript = join(common.fixturesDir, 'echo-close-check.js');
-var tmpFile = join(common.tmpDir, 'stdin.txt');
-
-var cmd = '"' + process.argv[0] + '" "' + stdoutScript + '" < "' +
-          tmpFile + '"';
-
-var string = 'abc\nümlaut.\nsomething else\n' +
-             '南越国是前203年至前111年存在于岭南地区的一个国家，国都位于番禺，' +
-             '疆域包括今天中国的广东、广西两省区的大部份地区，福建省、湖南、贵州、' +
-             '云南的一小部份地区和越南的北部。南越国是秦朝灭亡后，' +
-             '由南海郡尉赵佗于前203年起兵兼并桂林郡和象郡后建立。前196年和前179年，' +
-             '南越国曾先后两次名义上臣属于西汉，成为西汉的“外臣”。前112年，' +
-             '南越国末代君主赵建德与西汉发生战争，被汉武帝于前111年所灭。南越国共存在93年，' +
-             '历经五代君主。南越国是岭南地区的第一个有记载的政权国家，' +
-             '采用封建制和郡县制并存的制度，' +
-             '它的建立保证了秦末乱世岭南地区社会秩序的稳定，' +
-             '有效的改善了岭南地区落后的政治、##济现状。\n';
+const common = require('../common');
+const assert = require('assert');
+const join = require('path').join;
+const childProcess = require('child_process');
+const fs = require('fs');
+
+const stdoutScript = join(common.fixturesDir, 'echo-close-check.js');
+const tmpFile = join(common.tmpDir, 'stdin.txt');
+
+const cmd = '"' + process.argv[0] + '" "' + stdoutScript + '" < "' +
+            tmpFile + '"';
+
+const string = 'abc\nümlaut.\nsomething else\n' +
+               '南越国是前203年至前111年存在于岭南地区的一个国家，国都位于番禺，' +
+               '疆域包括今天中国的广东、广西两省区的大部份地区，福建省、湖南、贵州、' +
+               '云南的一小部份地区和越南的北部。南越国是秦朝灭亡后，' +
+               '由南海郡尉赵佗于前203年起兵兼并桂林郡和象郡后建立。前196年和前179年，' +
+               '南越国曾先后两次名义上臣属于西汉，成为西汉的“外臣”。前112年，' +
+               '南越国末代君主赵建德与西汉发生战争，被汉武帝于前111年所灭。南越国共存在93年，' +
+               '历经五代君主。南越国是岭南地区的第一个有记载的政权国家，' +
+               '采用封建制和郡县制并存的制度，' +
+               '它的建立保证了秦末乱世岭南地区社会秩序的稳定，' +
+               '有效的改善了岭南地区落后的政治、##济现状。\n';
 
 
 common.refreshTmpDir();
 
 console.log(cmd + '\n\n');
 
-try {
-  fs.unlinkSync(tmpFile);
-} catch (e) {}
-
 fs.writeFileSync(tmpFile, string);
 
-childProcess.exec(cmd, function(err, stdout, stderr) {
+childProcess.exec(cmd, common.mustCall(function(err, stdout, stderr) {
   fs.unlinkSync(tmpFile);
 
   if (err) throw err;
   console.log(stdout);
-  assert.equal(stdout, 'hello world\r\n' + string);
-  assert.equal('', stderr);
-});
+  assert.strictEqual(stdout, 'hello world\r\n' + string);
+  assert.strictEqual('', stderr);
+}));
diff --git a/test/parallel/test-stdout-to-file.js b/test/parallel/test-stdout-to-file.js
index bd1d97b3d8d278..ccff5caf36f114 100644
--- a/test/parallel/test-stdout-to-file.js
+++ b/test/parallel/test-stdout-to-file.js
@@ -1,13 +1,14 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var path = require('path');
-var childProcess = require('child_process');
-var fs = require('fs');
+const common = require('../common');
+const assert = require('assert');
+const path = require('path');
+const childProcess = require('child_process');
+const fs = require('fs');
 
-var scriptString = path.join(common.fixturesDir, 'print-chars.js');
-var scriptBuffer = path.join(common.fixturesDir, 'print-chars-from-buffer.js');
-var tmpFile = path.join(common.tmpDir, 'stdout.txt');
+const scriptString = path.join(common.fixturesDir, 'print-chars.js');
+const scriptBuffer = path.join(common.fixturesDir,
+                               'print-chars-from-buffer.js');
+const tmpFile = path.join(common.tmpDir, 'stdout.txt');
 
 common.refreshTmpDir();
 
@@ -24,22 +25,22 @@ function test(size, useBuffer, cb) {
     fs.unlinkSync(tmpFile);
   } catch (e) {}
 
-  console.log(size + ' chars to ' + tmpFile + '...');
+  console.log(`${size} chars to ${tmpFile}...`);
 
-  childProcess.exec(cmd, function(err) {
+  childProcess.exec(cmd, common.mustCall(function(err) {
     if (err) throw err;
 
     console.log('done!');
 
     var stat = fs.statSync(tmpFile);
 
-    console.log(tmpFile + ' has ' + stat.size + ' bytes');
+    console.log(`${tmpFile} has ${stat.size} bytes`);
 
-    assert.equal(size, stat.size);
+    assert.strictEqual(size, stat.size);
     fs.unlinkSync(tmpFile);
 
     cb();
-  });
+  }));
 }
 
 var finished = false;
diff --git a/test/parallel/test-stream-pipe-unpipe-streams.js b/test/parallel/test-stream-pipe-unpipe-streams.js
index 8858ac57334e59..428ff8bc70133f 100644
--- a/test/parallel/test-stream-pipe-unpipe-streams.js
+++ b/test/parallel/test-stream-pipe-unpipe-streams.js
@@ -27,6 +27,9 @@ source.unpipe(dest2);
 assert.strictEqual(source._readableState.pipes, dest1);
 assert.notStrictEqual(source._readableState.pipes, dest2);
 
+dest2.on('unpipe', common.fail);
+source.unpipe(dest2);
+
 source.unpipe(dest1);
 
 assert.strictEqual(source._readableState.pipes, null);
diff --git a/test/parallel/test-stream-unshift-empty-chunk.js b/test/parallel/test-stream-unshift-empty-chunk.js
index 0da979e337486e..c9df62b73b7b21 100644
--- a/test/parallel/test-stream-unshift-empty-chunk.js
+++ b/test/parallel/test-stream-unshift-empty-chunk.js
@@ -12,7 +12,7 @@ var chunk = new Buffer(10);
 chunk.fill('x');
 
 r._read = function(n) {
-  setTimeout(function() {
+  setImmediate(function() {
     r.push(--nChunks === 0 ? null : chunk);
   });
 };
diff --git a/test/parallel/test-stream2-objects.js b/test/parallel/test-stream2-objects.js
index e67359eff2b29e..52fb01228857eb 100644
--- a/test/parallel/test-stream2-objects.js
+++ b/test/parallel/test-stream2-objects.js
@@ -33,7 +33,7 @@ function run() {
 
 // ensure all tests have run
 process.on('exit', function() {
-  assert.equal(count, 0);
+  assert.strictEqual(count, 0);
 });
 
 process.nextTick(run);
@@ -210,16 +210,16 @@ test('high watermark _read', function(t) {
 
   var v = r.read();
 
-  assert.equal(calls, 0);
-  assert.equal(v, '1');
+  assert.strictEqual(calls, 0);
+  assert.strictEqual(v, '1');
 
   var v2 = r.read();
-  assert.equal(v2, '2');
+  assert.strictEqual(v2, '2');
 
   var v3 = r.read();
-  assert.equal(v3, '3');
+  assert.strictEqual(v3, '3');
 
-  assert.equal(calls, 1);
+  assert.strictEqual(calls, 1);
 
   t.end();
 });
@@ -232,7 +232,7 @@ test('high watermark push', function(t) {
   r._read = function(n) {};
   for (var i = 0; i < 6; i++) {
     var bool = r.push(i);
-    assert.equal(bool, i === 5 ? false : true);
+    assert.strictEqual(bool, i !== 5);
   }
 
   t.end();
@@ -309,7 +309,7 @@ test('buffers finish until cb is called', function(t) {
   var called = false;
 
   w._write = function(chunk, encoding, cb) {
-    assert.equal(chunk, 'foo');
+    assert.strictEqual(chunk, 'foo');
 
     process.nextTick(function() {
       called = true;
@@ -318,7 +318,7 @@ test('buffers finish until cb is called', function(t) {
   };
 
   w.on('finish', function() {
-    assert.equal(called, true);
+    assert.strictEqual(called, true);
 
     t.end();
   });
diff --git a/test/parallel/test-stream2-push.js b/test/parallel/test-stream2-push.js
index e4603e688ecf55..a9c624ea79f112 100644
--- a/test/parallel/test-stream2-push.js
+++ b/test/parallel/test-stream2-push.js
@@ -111,7 +111,7 @@ function end() {
   source.emit('end');
   assert(!reading);
   writer.end(stream.read());
-  setTimeout(function() {
+  setImmediate(function() {
     assert(ended);
   });
 }
diff --git a/test/parallel/test-stream2-transform.js b/test/parallel/test-stream2-transform.js
index 8554c965e9481b..39862b1ae28a87 100644
--- a/test/parallel/test-stream2-transform.js
+++ b/test/parallel/test-stream2-transform.js
@@ -106,6 +106,14 @@ test('object passthrough', function(t) {
   t.end();
 });
 
+test('passthrough constructor', function(t) {
+  const pt = PassThrough();
+
+  assert(pt instanceof PassThrough);
+
+  t.end();
+});
+
 test('simple transform', function(t) {
   var pt = new Transform();
   pt._transform = function(c, e, cb) {
diff --git a/test/parallel/test-timers-clear-null-does-not-throw-error.js b/test/parallel/test-timers-clear-null-does-not-throw-error.js
new file mode 100644
index 00000000000000..a15072a4c63f46
--- /dev/null
+++ b/test/parallel/test-timers-clear-null-does-not-throw-error.js
@@ -0,0 +1,18 @@
+'use strict';
+require('../common');
+const assert = require('assert');
+
+// This test makes sure clearing timers with
+// 'null' or no input does not throw error
+
+assert.doesNotThrow(() => clearInterval(null));
+
+assert.doesNotThrow(() => clearInterval());
+
+assert.doesNotThrow(() => clearTimeout(null));
+
+assert.doesNotThrow(() => clearTimeout());
+
+assert.doesNotThrow(() => clearImmediate(null));
+
+assert.doesNotThrow(() => clearImmediate());
diff --git a/test/parallel/test-timers-unenroll-unref-interval.js b/test/parallel/test-timers-unenroll-unref-interval.js
new file mode 100644
index 00000000000000..aade1c5b2e4e6e
--- /dev/null
+++ b/test/parallel/test-timers-unenroll-unref-interval.js
@@ -0,0 +1,63 @@
+'use strict';
+
+const common = require('../common');
+const assert = require('assert');
+const timers = require('timers');
+
+{
+  const interval = setInterval(common.mustCall(() => {
+    clearTimeout(interval);
+  }), 1).unref();
+}
+
+{
+  const interval = setInterval(common.mustCall(() => {
+    interval.close();
+  }), 1).unref();
+}
+
+{
+  const interval = setInterval(common.mustCall(() => {
+    timers.unenroll(interval);
+  }), 1).unref();
+}
+
+{
+  const interval = setInterval(common.mustCall(() => {
+    interval._idleTimeout = -1;
+  }), 1).unref();
+}
+
+{
+  const interval = setInterval(common.mustCall(() => {
+    interval._onTimeout = null;
+  }), 1).unref();
+}
+
+{
+  const interval = setInterval(common.mustCall(() => {
+    // This case is only necessary / valid prior to
+    // c8c2544cd9c339cdde881fc9a7f0851971b94d72
+    // which is not on the v4.x branch.
+    assert.strictEqual(typeof interval._repeat, 'function');
+
+    process.nextTick(common.mustCall(() => {
+      interval._repeat = null;
+    }));
+  }), 1).unref();
+}
+
+// Use timers' intrinsic behavior to keep this open
+// exactly long enough for the problem to manifest.
+//
+// See https://github.com/nodejs/node/issues/9561
+//
+// Since this is added after it will always fire later
+// than the previous timeouts, unrefed or not.
+//
+// Keep the event loop alive for one timeout and then
+// another. Any problems will occur when the second
+// should be called but before it is able to be.
+setTimeout(common.mustCall(() => {
+  setTimeout(common.mustCall(() => {}), 1);
+}), 1);
diff --git a/test/parallel/test-tls-client-verify.js b/test/parallel/test-tls-client-verify.js
index e566cafc8ca33b..983d88296eb26f 100644
--- a/test/parallel/test-tls-client-verify.js
+++ b/test/parallel/test-tls-client-verify.js
@@ -1,17 +1,17 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var fs = require('fs');
+const fs = require('fs');
 
-var hosterr = /Hostname\/IP doesn\'t match certificate\'s altnames/g;
-var testCases =
+const hosterr = /Hostname\/IP doesn't match certificate's altnames/g;
+const testCases =
     [{ ca: ['ca1-cert'],
        key: 'agent2-key',
        cert: 'agent2-cert',
@@ -52,16 +52,16 @@ function loadPEM(n) {
   return fs.readFileSync(filenamePEM(n));
 }
 
-var successfulTests = 0;
+let successfulTests = 0;
 
 function testServers(index, servers, clientOptions, cb) {
-  var serverOptions = servers[index];
+  const serverOptions = servers[index];
   if (!serverOptions) {
     cb();
     return;
   }
 
-  var ok = serverOptions.ok;
+  const ok = serverOptions.ok;
 
   if (serverOptions.key) {
     serverOptions.key = loadPEM(serverOptions.key);
@@ -71,37 +71,37 @@ function testServers(index, servers, clientOptions, cb) {
     serverOptions.cert = loadPEM(serverOptions.cert);
   }
 
-  var server = tls.createServer(serverOptions, function(s) {
+  const server = tls.createServer(serverOptions, common.mustCall(function(s) {
     s.end('hello world\n');
-  });
+  }));
 
-  server.listen(0, function() {
-    var b = '';
+  server.listen(0, common.mustCall(function() {
+    let b = '';
 
     console.error('connecting...');
     clientOptions.port = this.address().port;
-    var client = tls.connect(clientOptions, function() {
-      var authorized = client.authorized ||
-                       hosterr.test(client.authorizationError);
+    const client = tls.connect(clientOptions, common.mustCall(function() {
+      const authorized = client.authorized ||
+                         hosterr.test(client.authorizationError);
 
       console.error('expected: ' + ok + ' authed: ' + authorized);
 
-      assert.equal(ok, authorized);
+      assert.strictEqual(ok, authorized);
       server.close();
-    });
+    }));
 
     client.on('data', function(d) {
       b += d.toString();
     });
 
-    client.on('end', function() {
-      assert.equal('hello world\n', b);
-    });
+    client.on('end', common.mustCall(function() {
+      assert.strictEqual('hello world\n', b);
+    }));
 
-    client.on('close', function() {
+    client.on('close', common.mustCall(function() {
       testServers(index + 1, servers, clientOptions, cb);
-    });
-  });
+    }));
+  }));
 }
 
 
@@ -109,7 +109,7 @@ function runTest(testIndex) {
   var tcase = testCases[testIndex];
   if (!tcase) return;
 
-  var clientOptions = {
+  const clientOptions = {
     port: undefined,
     ca: tcase.ca.map(loadPEM),
     key: loadPEM(tcase.key),
@@ -118,10 +118,10 @@ function runTest(testIndex) {
   };
 
 
-  testServers(0, tcase.servers, clientOptions, function() {
+  testServers(0, tcase.servers, clientOptions, common.mustCall(function() {
     successfulTests++;
     runTest(testIndex + 1);
-  });
+  }));
 }
 
 
diff --git a/test/parallel/test-tls-connect-address-family.js b/test/parallel/test-tls-connect-address-family.js
index 05e81304b6a379..aae1fc7bfdc968 100644
--- a/test/parallel/test-tls-connect-address-family.js
+++ b/test/parallel/test-tls-connect-address-family.js
@@ -14,10 +14,10 @@ function runTest() {
   const ciphers = 'AECDH-NULL-SHA';
   tls.createServer({ ciphers }, common.mustCall(function() {
     this.close();
-  })).listen(common.PORT, '::1', common.mustCall(function() {
+  })).listen(0, '::1', common.mustCall(function() {
     const options = {
       host: 'localhost',
-      port: common.PORT,
+      port: this.address().port,
       family: 6,
       ciphers: ciphers,
       rejectUnauthorized: false,
diff --git a/test/parallel/test-tls-connect-simple.js b/test/parallel/test-tls-connect-simple.js
index 5b18f7693ff7df..a6bcfcab519fdf 100644
--- a/test/parallel/test-tls-connect-simple.js
+++ b/test/parallel/test-tls-connect-simple.js
@@ -1,58 +1,43 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var fs = require('fs');
+const fs = require('fs');
 
-var clientConnected = 0;
-var serverConnected = 0;
-var serverCloseCallbacks = 0;
-var serverCloseEvents = 0;
+let serverConnected = 0;
 
-var options = {
+const options = {
   key: fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem'),
   cert: fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem')
 };
 
-var server = tls.Server(options, function(socket) {
+const server = tls.Server(options, common.mustCall(function(socket) {
   if (++serverConnected === 2) {
-    server.close(function() {
-      ++serverCloseCallbacks;
-    });
-    server.on('close', function() {
-      ++serverCloseEvents;
-    });
+    server.close(common.mustCall(function() {}));
+    server.on('close', common.mustCall(function() {}));
   }
-});
+}, 2));
 
 server.listen(0, function() {
-  var client1 = tls.connect({
+  const client1options = {
     port: this.address().port,
     rejectUnauthorized: false
-  }, function() {
-    ++clientConnected;
+  };
+  const client1 = tls.connect(client1options, common.mustCall(function() {
     client1.end();
-  });
+  }));
 
-  var client2 = tls.connect({
+  const client2options = {
     port: this.address().port,
     rejectUnauthorized: false
-  });
-  client2.on('secureConnect', function() {
-    ++clientConnected;
+  };
+  const client2 = tls.connect(client2options);
+  client2.on('secureConnect', common.mustCall(function() {
     client2.end();
-  });
-});
-
-process.on('exit', function() {
-  assert.equal(clientConnected, 2);
-  assert.equal(serverConnected, 2);
-  assert.equal(serverCloseCallbacks, 1);
-  assert.equal(serverCloseEvents, 1);
+  }));
 });
diff --git a/test/parallel/test-tls-destroy-whilst-write.js b/test/parallel/test-tls-destroy-whilst-write.js
index 4f6ede968be408..b4f9766d998630 100644
--- a/test/parallel/test-tls-destroy-whilst-write.js
+++ b/test/parallel/test-tls-destroy-whilst-write.js
@@ -1,26 +1,26 @@
 'use strict';
-var common = require('../common');
+const common = require('../common');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
-var stream = require('stream');
+const tls = require('tls');
+const stream = require('stream');
 
-var delay = new stream.Duplex({
+const delay = new stream.Duplex({
   read: function read() {
   },
   write: function write(data, enc, cb) {
     console.log('pending');
-    setTimeout(function() {
+    setImmediate(function() {
       console.log('done');
       cb();
-    }, 200);
+    });
   }
 });
 
-var secure = tls.connect({
+const secure = tls.connect({
   socket: delay
 });
 setImmediate(function() {
diff --git a/test/parallel/test-tls-friendly-error-message.js b/test/parallel/test-tls-friendly-error-message.js
index c53dd7cbc07205..9ae69f4016e319 100644
--- a/test/parallel/test-tls-friendly-error-message.js
+++ b/test/parallel/test-tls-friendly-error-message.js
@@ -1,26 +1,26 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var fs = require('fs');
+const fs = require('fs');
 
-var key = fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem');
-var cert = fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem');
+const key = fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem');
+const cert = fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem');
 
-tls.createServer({ key: key, cert: cert }, function(conn) {
+tls.createServer({ key: key, cert: cert }, common.mustCall(function(conn) {
   conn.end();
   this.close();
-}).listen(0, function() {
+})).listen(0, common.mustCall(function() {
   var options = { port: this.address().port, rejectUnauthorized: true };
   tls.connect(options).on('error', common.mustCall(function(err) {
-    assert.equal(err.code, 'UNABLE_TO_VERIFY_LEAF_SIGNATURE');
-    assert.equal(err.message, 'unable to verify the first certificate');
+    assert.strictEqual(err.code, 'UNABLE_TO_VERIFY_LEAF_SIGNATURE');
+    assert.strictEqual(err.message, 'unable to verify the first certificate');
     this.destroy();
   }));
-});
+}));
diff --git a/test/parallel/test-tls-junk-closes-server.js b/test/parallel/test-tls-junk-closes-server.js
index f12393515cbe47..38f90498f84e92 100644
--- a/test/parallel/test-tls-junk-closes-server.js
+++ b/test/parallel/test-tls-junk-closes-server.js
@@ -1,34 +1,30 @@
 'use strict';
-var common = require('../common');
+const common = require('../common');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
 
-var fs = require('fs');
-var net = require('net');
+const tls = require('tls');
+const fs = require('fs');
+const net = require('net');
 
-var options = {
+const options = {
   key: fs.readFileSync(common.fixturesDir + '/keys/agent2-key.pem'),
   cert: fs.readFileSync(common.fixturesDir + '/keys/agent2-cert.pem')
 };
 
-var server = tls.createServer(options, function(s) {
-  s.write('welcome!\n');
-  s.pipe(s);
-});
+const server = tls.createServer(options, common.fail);
 
-server.listen(0, function() {
-  var c = net.createConnection(this.address().port);
+server.listen(0, common.mustCall(function() {
+  const c = net.createConnection(this.address().port);
 
-  c.on('connect', function() {
+  c.on('connect', common.mustCall(function() {
     c.write('blah\nblah\nblah\n');
-  });
+  }));
 
-  c.on('end', function() {
+  c.on('end', common.mustCall(function() {
     server.close();
-  });
-
-});
+  }));
+}));
diff --git a/test/parallel/test-tls-key-mismatch.js b/test/parallel/test-tls-key-mismatch.js
index f0eb8121bd68e5..65cac6f07a296c 100644
--- a/test/parallel/test-tls-key-mismatch.js
+++ b/test/parallel/test-tls-key-mismatch.js
@@ -1,15 +1,15 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
-var fs = require('fs');
+const assert = require('assert');
+const tls = require('tls');
+const fs = require('fs');
 
-var options = {
+const options = {
   key: fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem'),
   cert: fs.readFileSync(common.fixturesDir + '/keys/agent2-cert.pem')
 };
diff --git a/test/parallel/test-tls-no-sslv3.js b/test/parallel/test-tls-no-sslv3.js
index fde54aff2c9b26..1220b8d09de307 100644
--- a/test/parallel/test-tls-no-sslv3.js
+++ b/test/parallel/test-tls-no-sslv3.js
@@ -1,30 +1,30 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var fs = require('fs');
-var spawn = require('child_process').spawn;
+const fs = require('fs');
+const spawn = require('child_process').spawn;
 
 if (common.opensslCli === false) {
   common.skip('node compiled without OpenSSL CLI.');
   return;
 }
 
-var cert = fs.readFileSync(common.fixturesDir + '/test_cert.pem');
-var key = fs.readFileSync(common.fixturesDir + '/test_key.pem');
-var server = tls.createServer({ cert: cert, key: key }, common.fail);
-var errors = [];
-var stderr = '';
+const cert = fs.readFileSync(common.fixturesDir + '/test_cert.pem');
+const key = fs.readFileSync(common.fixturesDir + '/test_key.pem');
+const server = tls.createServer({ cert: cert, key: key }, common.fail);
+const errors = [];
+let stderr = '';
 
 server.listen(0, '127.0.0.1', function() {
-  var address = this.address().address + ':' + this.address().port;
-  var args = ['s_client',
+  const address = this.address().address + ':' + this.address().port;
+  const args = ['s_client',
               '-ssl3',
               '-connect', address];
 
@@ -32,14 +32,14 @@ server.listen(0, '127.0.0.1', function() {
   if (common.isWindows)
     args.push('-no_rand_screen');
 
-  var client = spawn(common.opensslCli, args, { stdio: 'pipe' });
+  const client = spawn(common.opensslCli, args, { stdio: 'pipe' });
   client.stdout.pipe(process.stdout);
   client.stderr.pipe(process.stderr);
   client.stderr.setEncoding('utf8');
   client.stderr.on('data', (data) => stderr += data);
 
   client.once('exit', common.mustCall(function(exitCode) {
-    assert.equal(exitCode, 1);
+    assert.strictEqual(exitCode, 1);
     server.close();
   }));
 });
@@ -50,7 +50,7 @@ process.on('exit', function() {
   if (/unknown option -ssl3/.test(stderr)) {
     common.skip('`openssl s_client -ssl3` not supported.');
   } else {
-    assert.equal(errors.length, 1);
+    assert.strictEqual(errors.length, 1);
     assert(/:wrong version number/.test(errors[0].message));
   }
 });
diff --git a/test/parallel/test-tls-ticket-cluster.js b/test/parallel/test-tls-ticket-cluster.js
index 4d1667a7adcab2..fa630f4ec251bd 100644
--- a/test/parallel/test-tls-ticket-cluster.js
+++ b/test/parallel/test-tls-ticket-cluster.js
@@ -1,29 +1,29 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var cluster = require('cluster');
-var fs = require('fs');
-var join = require('path').join;
+const cluster = require('cluster');
+const fs = require('fs');
+const join = require('path').join;
 
-var workerCount = 4;
-var expectedReqCount = 16;
+const workerCount = 4;
+const expectedReqCount = 16;
 
 if (cluster.isMaster) {
-  var reusedCount = 0;
-  var reqCount = 0;
-  var lastSession = null;
-  var shootOnce = false;
+  let reusedCount = 0;
+  let reqCount = 0;
+  let lastSession = null;
+  let shootOnce = false;
 
   function shoot() {
     console.error('[master] connecting');
-    var c = tls.connect(common.PORT, {
+    const c = tls.connect(common.PORT, {
       session: lastSession,
       rejectUnauthorized: false
     }, function() {
@@ -41,7 +41,7 @@ if (cluster.isMaster) {
   }
 
   function fork() {
-    var worker = cluster.fork();
+    const worker = cluster.fork();
     worker.on('message', function(msg) {
       console.error('[master] got %j', msg);
       if (msg === 'reused') {
@@ -56,27 +56,27 @@ if (cluster.isMaster) {
       console.error('[master] worker died');
     });
   }
-  for (var i = 0; i < workerCount; i++) {
+  for (let i = 0; i < workerCount; i++) {
     fork();
   }
 
   process.on('exit', function() {
-    assert.equal(reqCount, expectedReqCount);
-    assert.equal(reusedCount + 1, reqCount);
+    assert.strictEqual(reqCount, expectedReqCount);
+    assert.strictEqual(reusedCount + 1, reqCount);
   });
   return;
 }
 
-var keyFile = join(common.fixturesDir, 'agent.key');
-var certFile = join(common.fixturesDir, 'agent.crt');
-var key = fs.readFileSync(keyFile);
-var cert = fs.readFileSync(certFile);
-var options = {
+const keyFile = join(common.fixturesDir, 'agent.key');
+const certFile = join(common.fixturesDir, 'agent.crt');
+const key = fs.readFileSync(keyFile);
+const cert = fs.readFileSync(certFile);
+const options = {
   key: key,
   cert: cert
 };
 
-var server = tls.createServer(options, function(c) {
+const server = tls.createServer(options, function(c) {
   if (c.isSessionReused()) {
     process.send('reused');
   } else {
diff --git a/test/parallel/test-tls-ticket.js b/test/parallel/test-tls-ticket.js
index 8457b15e0cd325..0fa0c057f3e573 100644
--- a/test/parallel/test-tls-ticket.js
+++ b/test/parallel/test-tls-ticket.js
@@ -1,29 +1,29 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var fs = require('fs');
-var net = require('net');
-var crypto = require('crypto');
+const fs = require('fs');
+const net = require('net');
+const crypto = require('crypto');
 
-var keys = crypto.randomBytes(48);
-var serverLog = [];
-var ticketLog = [];
+const keys = crypto.randomBytes(48);
+const serverLog = [];
+const ticketLog = [];
 
-var serverCount = 0;
+let serverCount = 0;
 function createServer() {
-  var id = serverCount++;
+  const id = serverCount++;
 
-  var counter = 0;
-  var previousKey = null;
+  let counter = 0;
+  let previousKey = null;
 
-  var server = tls.createServer({
+  const server = tls.createServer({
     key: fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem'),
     cert: fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem'),
     ticketKeys: keys
@@ -49,13 +49,13 @@ function createServer() {
   return server;
 }
 
-var naturalServers = [ createServer(), createServer(), createServer() ];
+const naturalServers = [ createServer(), createServer(), createServer() ];
 
 // 3x servers
-var servers = naturalServers.concat(naturalServers).concat(naturalServers);
+const servers = naturalServers.concat(naturalServers).concat(naturalServers);
 
 // Create one TCP server and balance sockets to multiple TLS server instances
-var shared = net.createServer(function(c) {
+const shared = net.createServer(function(c) {
   servers.shift().emit('connection', c);
 }).listen(0, function() {
   start(function() {
@@ -64,11 +64,11 @@ var shared = net.createServer(function(c) {
 });
 
 function start(callback) {
-  var sess = null;
-  var left = servers.length;
+  let sess = null;
+  let left = servers.length;
 
   function connect() {
-    var s = tls.connect(shared.address().port, {
+    const s = tls.connect(shared.address().port, {
       session: sess,
       rejectUnauthorized: false
     }, function() {
@@ -87,15 +87,15 @@ function start(callback) {
 }
 
 process.on('exit', function() {
-  assert.equal(ticketLog.length, serverLog.length);
-  for (var i = 0; i < naturalServers.length - 1; i++) {
-    assert.notEqual(serverLog[i], serverLog[i + 1]);
-    assert.equal(ticketLog[i], ticketLog[i + 1]);
+  assert.strictEqual(ticketLog.length, serverLog.length);
+  for (let i = 0; i < naturalServers.length - 1; i++) {
+    assert.notStrictEqual(serverLog[i], serverLog[i + 1]);
+    assert.strictEqual(ticketLog[i], ticketLog[i + 1]);
 
     // 2nd connection should have different ticket
-    assert.notEqual(ticketLog[i], ticketLog[i + naturalServers.length]);
+    assert.notStrictEqual(ticketLog[i], ticketLog[i + naturalServers.length]);
 
     // 3rd connection should have the same ticket
-    assert.equal(ticketLog[i], ticketLog[i + naturalServers.length * 2]);
+    assert.strictEqual(ticketLog[i], ticketLog[i + naturalServers.length * 2]);
   }
 });
diff --git a/test/parallel/test-tls-timeout-server-2.js b/test/parallel/test-tls-timeout-server-2.js
index a054f41f623455..1613e9fc4e06d6 100644
--- a/test/parallel/test-tls-timeout-server-2.js
+++ b/test/parallel/test-tls-timeout-server-2.js
@@ -1,32 +1,32 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (!common.hasCrypto) {
   common.skip('missing crypto');
   return;
 }
-var tls = require('tls');
+const tls = require('tls');
 
-var fs = require('fs');
+const fs = require('fs');
 
-var options = {
+const options = {
   key: fs.readFileSync(common.fixturesDir + '/keys/agent1-key.pem'),
   cert: fs.readFileSync(common.fixturesDir + '/keys/agent1-cert.pem')
 };
 
-var server = tls.createServer(options, function(cleartext) {
-  var s = cleartext.setTimeout(50, function() {
+const server = tls.createServer(options, common.mustCall(function(cleartext) {
+  const s = cleartext.setTimeout(50, function() {
     cleartext.destroy();
     server.close();
   });
   assert.ok(s instanceof tls.TLSSocket);
-});
+}));
 
-server.listen(0, function() {
+server.listen(0, common.mustCall(function() {
   tls.connect({
     host: '127.0.0.1',
     port: this.address().port,
     rejectUnauthorized: false
   });
-});
+}));
diff --git a/test/parallel/test-tls-writewrap-leak.js b/test/parallel/test-tls-writewrap-leak.js
index cc55192229531d..b1a6d6a1058a65 100644
--- a/test/parallel/test-tls-writewrap-leak.js
+++ b/test/parallel/test-tls-writewrap-leak.js
@@ -20,7 +20,7 @@ const server = net.createServer(common.mustCall((c) => {
   });
 
   c.write('hello', common.mustCall((err) => {
-    assert.equal(err.code, 'ECANCELED');
+    assert.strictEqual(err.code, 'ECANCELED');
     server.close();
   }));
 }));
diff --git a/test/parallel/test-vm-static-this.js b/test/parallel/test-vm-static-this.js
index a3cf2d820c3423..c4f10c183b6ef2 100644
--- a/test/parallel/test-vm-static-this.js
+++ b/test/parallel/test-vm-static-this.js
@@ -5,21 +5,21 @@ var vm = require('vm');
 
 common.globalCheck = false;
 
-console.error('run a string');
+// Run a string
 var result = vm.runInThisContext('\'passed\';');
-assert.equal('passed', result);
+assert.strictEqual('passed', result);
 
-console.error('thrown error');
+// thrown error
 assert.throws(function() {
   vm.runInThisContext('throw new Error(\'test\');');
 }, /test/);
 
 global.hello = 5;
 vm.runInThisContext('hello = 2');
-assert.equal(2, global.hello);
+assert.strictEqual(2, global.hello);
 
 
-console.error('pass values');
+// pass values
 var code = 'foo = 1;' +
            'bar = 2;' +
            'if (typeof baz !== \'undefined\') throw new Error(\'test fail\');';
@@ -28,11 +28,11 @@ global.obj = { foo: 0, baz: 3 };
 /* eslint-disable no-unused-vars */
 var baz = vm.runInThisContext(code);
 /* eslint-enable no-unused-vars */
-assert.equal(0, global.obj.foo);
-assert.equal(2, global.bar);
-assert.equal(1, global.foo);
+assert.strictEqual(0, global.obj.foo);
+assert.strictEqual(2, global.bar);
+assert.strictEqual(1, global.foo);
 
-console.error('call a function');
+// call a function
 global.f = function() { global.foo = 100; };
 vm.runInThisContext('f()');
-assert.equal(100, global.foo);
+assert.strictEqual(100, global.foo);
diff --git a/test/parallel/test-vm-syntax-error-stderr.js b/test/parallel/test-vm-syntax-error-stderr.js
index 7c3c5ff1351da2..43ed8d882804ca 100644
--- a/test/parallel/test-vm-syntax-error-stderr.js
+++ b/test/parallel/test-vm-syntax-error-stderr.js
@@ -1,22 +1,22 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
-var path = require('path');
-var child_process = require('child_process');
+const common = require('../common');
+const assert = require('assert');
+const path = require('path');
+const child_process = require('child_process');
 
-var wrong_script = path.join(common.fixturesDir, 'cert.pem');
+const wrong_script = path.join(common.fixturesDir, 'cert.pem');
 
-var p = child_process.spawn(process.execPath, [
+const p = child_process.spawn(process.execPath, [
   '-e',
   'require(process.argv[1]);',
   wrong_script
 ]);
 
 p.stdout.on('data', function(data) {
-  assert(false, 'Unexpected stdout data: ' + data);
+  common.fail('Unexpected stdout data: ' + data);
 });
 
-var output = '';
+let output = '';
 
 p.stderr.on('data', function(data) {
   output += data;
diff --git a/test/pseudo-tty/pseudo-tty.status b/test/pseudo-tty/pseudo-tty.status
index 27c6f75e10648c..e16bb28cd7be61 100644
--- a/test/pseudo-tty/pseudo-tty.status
+++ b/test/pseudo-tty/pseudo-tty.status
@@ -3,3 +3,4 @@ prefix pseudo-tty
 [$system==aix]
 # test issue only, covered under https://github.com/nodejs/node/issues/7973
 no_dropped_stdio           : SKIP
+no_interleaved_stdio       : SKIP
diff --git a/test/sequential/test-next-tick-error-spin.js b/test/sequential/test-next-tick-error-spin.js
index 7a76ab1e12df68..911d99d7416db5 100644
--- a/test/sequential/test-next-tick-error-spin.js
+++ b/test/sequential/test-next-tick-error-spin.js
@@ -1,24 +1,23 @@
 'use strict';
-var common = require('../common');
-var assert = require('assert');
+const common = require('../common');
+const assert = require('assert');
 
 if (process.argv[2] !== 'child') {
-  var spawn = require('child_process').spawn;
-  var child = spawn(process.execPath, [__filename, 'child'], {
+  const spawn = require('child_process').spawn;
+  const child = spawn(process.execPath, [__filename, 'child'], {
     stdio: 'pipe'//'inherit'
   });
-  var timer = setTimeout(function() {
+  const timer = setTimeout(function() {
     throw new Error('child is hung');
   }, common.platformTimeout(3000));
-  child.on('exit', function(code) {
-    console.error('ok');
-    assert(!code);
+  child.on('exit', common.mustCall(function(code) {
+    assert.strictEqual(code, 0);
     clearTimeout(timer);
-  });
+  }));
 } else {
 
-  var domain = require('domain');
-  var d = domain.create();
+  const domain = require('domain');
+  const d = domain.create();
   process.maxTickDepth = 10;
 
   // in the error handler, we trigger several MakeCallback events
@@ -40,10 +39,8 @@ if (process.argv[2] !== 'child') {
   }
 
   f();
-  setTimeout(function() {
+  setImmediate(function() {
     console.error('broke in!');
-    //process.stdout.close();
-    //process.stderr.close();
     process.exit(0);
   });
 }
diff --git a/test/sequential/test-regress-GH-897.js b/test/sequential/test-regress-GH-897.js
new file mode 100644
index 00000000000000..7b1297efd5a1b7
--- /dev/null
+++ b/test/sequential/test-regress-GH-897.js
@@ -0,0 +1,17 @@
+'use strict';
+
+// Test for bug where a timer duration greater than 0 ms but less than 1 ms
+// resulted in the duration being set for 1000 ms. The expected behavior is
+// that the timeout would be set for 1 ms, and thus fire more-or-less
+// immediately.
+//
+// Ref: https://github.com/nodejs/node-v0.x-archive/pull/897
+
+const common = require('../common');
+const assert = require('assert');
+
+const t = Date.now();
+setTimeout(common.mustCall(function() {
+  const diff = Date.now() - t;
+  assert.ok(diff < 100, `timer fired after ${diff} ms`);
+}), 0.1);
diff --git a/tools/doc/addon-verify.js b/tools/doc/addon-verify.js
index 299d4847ef3eb3..86a81935892745 100644
--- a/tools/doc/addon-verify.js
+++ b/tools/doc/addon-verify.js
@@ -65,8 +65,8 @@ function verifyFiles(files, blockName, onprogress, ondone) {
   files = Object.keys(files).map(function(name) {
     if (name === 'test.js') {
       files[name] = `'use strict';
-require('../../common');
-${files[name]}
+const common = require('../../common');
+${files[name].replace('Release', "' + common.buildType + '")}
 `;
     }
     return {
diff --git a/tools/doc/generate.js b/tools/doc/generate.js
index 077e740432c837..31b23c52a08ba7 100644
--- a/tools/doc/generate.js
+++ b/tools/doc/generate.js
@@ -13,14 +13,14 @@ let inputFile = null;
 let nodeVersion = null;
 
 args.forEach(function(arg) {
-  if (!arg.match(/^\-\-/)) {
+  if (!arg.match(/^--/)) {
     inputFile = arg;
-  } else if (arg.match(/^\-\-format=/)) {
-    format = arg.replace(/^\-\-format=/, '');
-  } else if (arg.match(/^\-\-template=/)) {
-    template = arg.replace(/^\-\-template=/, '');
-  } else if (arg.match(/^\-\-node\-version=/)) {
-    nodeVersion = arg.replace(/^\-\-node\-version=/, '');
+  } else if (arg.match(/^--format=/)) {
+    format = arg.replace(/^--format=/, '');
+  } else if (arg.match(/^--template=/)) {
+    template = arg.replace(/^--template=/, '');
+  } else if (arg.match(/^--node-version=/)) {
+    nodeVersion = arg.replace(/^--node-version=/, '');
   }
 });
 
diff --git a/tools/doc/html.js b/tools/doc/html.js
index 3b60116b1ba422..daa230cb926e4a 100644
--- a/tools/doc/html.js
+++ b/tools/doc/html.js
@@ -263,7 +263,7 @@ var BSD_ONLY_SYSCALLS = new Set(['lchmod']);
 // Returns modified text, with such refs replace with HTML links, for example
 // '<a href="http://man7.org/linux/man-pages/man2/open.2.html">open(2)</a>'
 function linkManPages(text) {
-  return text.replace(/ ([a-z]+)\((\d)\)/gm, function(match, name, number) {
+  return text.replace(/ ([a-z.]+)\((\d)\)/gm, function(match, name, number) {
     // name consists of lowercase letters, number is a single digit
     var displayAs = name + '(' + number + ')';
     if (BSD_ONLY_SYSCALLS.has(name)) {
diff --git a/tools/doc/json.js b/tools/doc/json.js
index a194c7f7231423..a782c54028d756 100644
--- a/tools/doc/json.js
+++ b/tools/doc/json.js
@@ -545,12 +545,12 @@ function deepCopy_(src) {
 // these parse out the contents of an H# tag
 var eventExpr = /^Event(?::|\s)+['"]?([^"']+).*$/i;
 var classExpr = /^Class:\s*([^ ]+).*?$/i;
-var propExpr = /^(?:property:?\s*)?[^\.]+\.([^ \.\(\)]+)\s*?$/i;
-var braceExpr = /^(?:property:?\s*)?[^\.\[]+(\[[^\]]+\])\s*?$/i;
+var propExpr = /^(?:property:?\s*)?[^.]+\.([^ .()]+)\s*?$/i;
+var braceExpr = /^(?:property:?\s*)?[^.\[]+(\[[^\]]+\])\s*?$/i;
 var classMethExpr =
-  /^class\s*method\s*:?[^\.]+\.([^ \.\(\)]+)\([^\)]*\)\s*?$/i;
+  /^class\s*method\s*:?[^.]+\.([^ .()]+)\([^)]*\)\s*?$/i;
 var methExpr =
-  /^(?:method:?\s*)?(?:[^\.]+\.)?([^ \.\(\)]+)\([^\)]*\)\s*?$/i;
+  /^(?:method:?\s*)?(?:[^.]+\.)?([^ .()]+)\([^)]*\)\s*?$/i;
 var newExpr = /^new ([A-Z][a-zA-Z]+)\([^\)]*\)\s*?$/;
 var paramExpr = /\((.*)\);?$/;
 
diff --git a/tools/gyp/AUTHORS b/tools/gyp/AUTHORS
index 9389ca0a23e48f..dcd231ceb2d341 100644
--- a/tools/gyp/AUTHORS
+++ b/tools/gyp/AUTHORS
@@ -1,9 +1,10 @@
 # Names should be added to this file like so:
 # Name or Organization <email address>
 
-Google Inc.
-Bloomberg Finance L.P.
-Yandex LLC
+Google Inc. <*@google.com>
+Bloomberg Finance L.P. <*@bloomberg.net>
+IBM Inc. <*@*.ibm.com>
+Yandex LLC <*@yandex-team.ru>
 
 Steven Knight <knight@baldmt.com>
 Ryan Norton <rnorton10@gmail.com>
diff --git a/tools/gyp/PRESUBMIT.py b/tools/gyp/PRESUBMIT.py
index dde025383c3276..f6c8a357afe149 100644
--- a/tools/gyp/PRESUBMIT.py
+++ b/tools/gyp/PRESUBMIT.py
@@ -73,23 +73,15 @@
 ]
 
 
-def CheckChangeOnUpload(input_api, output_api):
-  report = []
-  report.extend(input_api.canned_checks.PanProjectChecks(
-      input_api, output_api))
-  return report
-
-
-def CheckChangeOnCommit(input_api, output_api):
-  report = []
-
+def _LicenseHeader(input_api):
   # Accept any year number from 2009 to the current year.
   current_year = int(input_api.time.strftime('%Y'))
   allowed_years = (str(s) for s in reversed(xrange(2009, current_year + 1)))
+
   years_re = '(' + '|'.join(allowed_years) + ')'
 
   # The (c) is deprecated, but tolerate it until it's removed from all files.
-  license = (
+  return (
       r'.*? Copyright (\(c\) )?%(year)s Google Inc\. All rights reserved\.\n'
       r'.*? Use of this source code is governed by a BSD-style license that '
         r'can be\n'
@@ -98,8 +90,18 @@ def CheckChangeOnCommit(input_api, output_api):
       'year': years_re,
   }
 
+def CheckChangeOnUpload(input_api, output_api):
+  report = []
+  report.extend(input_api.canned_checks.PanProjectChecks(
+      input_api, output_api, license_header=_LicenseHeader(input_api)))
+  return report
+
+
+def CheckChangeOnCommit(input_api, output_api):
+  report = []
+
   report.extend(input_api.canned_checks.PanProjectChecks(
-      input_api, output_api, license_header=license))
+      input_api, output_api, license_header=_LicenseHeader(input_api)))
   report.extend(input_api.canned_checks.CheckTreeIsOpen(
       input_api, output_api,
       'http://gyp-status.appspot.com/status',
diff --git a/tools/gyp/pylib/gyp/generator/make.py b/tools/gyp/pylib/gyp/generator/make.py
index 3aa8526b5b566e..ef00eba4c28ad4 100644
--- a/tools/gyp/pylib/gyp/generator/make.py
+++ b/tools/gyp/pylib/gyp/generator/make.py
@@ -92,7 +92,10 @@ def CalculateVariables(default_variables, params):
     if flavor == 'android':
       operating_system = 'linux'  # Keep this legacy behavior for now.
     default_variables.setdefault('OS', operating_system)
-    default_variables.setdefault('SHARED_LIB_SUFFIX', '.so')
+    if flavor == 'aix':
+      default_variables.setdefault('SHARED_LIB_SUFFIX', '.a')
+    else:
+      default_variables.setdefault('SHARED_LIB_SUFFIX', '.so')
     default_variables.setdefault('SHARED_LIB_DIR','$(builddir)/lib.$(TOOLSET)')
     default_variables.setdefault('LIB_DIR', '$(obj).$(TOOLSET)')
 
@@ -1349,7 +1352,10 @@ def ComputeOutputBasename(self, spec):
       if target[:3] == 'lib':
         target = target[3:]
       target_prefix = 'lib'
-      target_ext = '.so'
+      if self.flavor == 'aix':
+        target_ext = '.a'
+      else:
+        target_ext = '.so'
     elif self.type == 'none':
       target = '%s.stamp' % target
     elif self.type != 'executable':
diff --git a/tools/run-valgrind.py b/tools/run-valgrind.py
deleted file mode 120000
index 07935ad7d4fc08..00000000000000
--- a/tools/run-valgrind.py
+++ /dev/null
@@ -1 +0,0 @@
-../deps/v8/tools/run-valgrind.py
\ No newline at end of file
diff --git a/tools/run-valgrind.py b/tools/run-valgrind.py
new file mode 100755
index 00000000000000..ae1a3194cac4a6
--- /dev/null
+++ b/tools/run-valgrind.py
@@ -0,0 +1,65 @@
+#!/usr/bin/env python
+#
+# Copyright 2009 the V8 project authors. All rights reserved.
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions are
+# met:
+#
+#     * Redistributions of source code must retain the above copyright
+#       notice, this list of conditions and the following disclaimer.
+#     * Redistributions in binary form must reproduce the above
+#       copyright notice, this list of conditions and the following
+#       disclaimer in the documentation and/or other materials provided
+#       with the distribution.
+#     * Neither the name of Google Inc. nor the names of its
+#       contributors may be used to endorse or promote products derived
+#       from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+from os import path
+import subprocess
+import sys
+
+NODE_ROOT = path.dirname(path.dirname(path.abspath(__file__)))
+
+VALGRIND_ARGUMENTS = [
+  'valgrind',
+  '--error-exitcode=1',
+  '--smc-check=all',
+  # Node.js does not clean up on exit so don't complain about
+  # memory leaks but do complain about invalid memory access.
+  '--quiet',
+]
+
+if len(sys.argv) < 2:
+  print 'Please provide an executable to analyze.'
+  sys.exit(1)
+
+executable = path.join(NODE_ROOT, sys.argv[1])
+if not path.exists(executable):
+  print 'Cannot find the file specified: %s' % executable
+  sys.exit(1)
+
+# Compute the command line.
+command = VALGRIND_ARGUMENTS + [executable] + sys.argv[2:]
+
+# Run valgrind.
+process = subprocess.Popen(command, stderr=subprocess.PIPE)
+code = process.wait()
+errors = process.stderr.readlines()
+
+# If valgrind produced an error, we report that to the user.
+if code != 0:
+  sys.stderr.writelines(errors)
+  sys.exit(code)