|
| 1 | +# io.js TC Meeting 2015-04-29 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Public YouTube feed**: http://www.youtube.com/watch?v=-e675TT4WEA |
| 6 | +* **Google Plus Event page**: https://plus.google.com/events/cei87pqnichrtt4qggbbo656bpk |
| 7 | +* **GitHub Issue**: https://github.com/iojs/io.js/issues/1557 |
| 8 | +* **Original Minutes Google Doc**: https://docs.google.com/document/d/1C9nfm_5EhNz1jifITbtQcnGBX4R9vktoZ9KsFiCU7sQ |
| 9 | + |
| 10 | +## Agenda |
| 11 | + |
| 12 | +Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. |
| 13 | + |
| 14 | +* Release Proposal: v2.0.0 [#1532](https://github.com/iojs/io.js/pull/1532) |
| 15 | +* Forward-port from v1.x [#1559](https://github.com/iojs/io.js/pull/1559) |
| 16 | +* Convergence plan (https://github.com/jasnell/dev-policy/pull/66) |
| 17 | +* Combined node.js/io.js TC/core call about convergence doc [#1413](https://github.com/iojs/io.js/issues/1413) |
| 18 | + |
| 19 | +### Present |
| 20 | + |
| 21 | +* Ben (TC) |
| 22 | +* Bert (TC) |
| 23 | +* Brian |
| 24 | +* Chris (TC) |
| 25 | +* Domenic |
| 26 | +* Fedor (TC) |
| 27 | +* Jeremiah |
| 28 | +* Shigeki |
| 29 | +* Trevor (TC) |
| 30 | + |
| 31 | + |
| 32 | +### Review of last meeting |
| 33 | + |
| 34 | +* [#1130](https://github.com/iojs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC |
| 35 | +* [#1481](https://github.com/iojs/io.js/issues/1481) Nominating @mikeal to the TC |
| 36 | +* [#1500](https://github.com/iojs/io.js/issues/1500) Nominating Brian White @mscdex to the TC |
| 37 | +* [#1501](https://github.com/iojs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC |
| 38 | +* [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? |
| 39 | +* [#1413](https://github.com/iojs/io.js/issues/1413) Combined node.js/io.js TC/Core Call |
| 40 | +* [#1416](https://github.com/iojs/io.js/issues/1416) Diffing io.js and the Node.js Foundation |
| 41 | + |
| 42 | + |
| 43 | +### Quick stand-up |
| 44 | + |
| 45 | +* Ben: nothing |
| 46 | +* Bert: nothing |
| 47 | +* Brian: finished optimizations for JS HTTP parser, posted a few questions; other miscellaneous improvements in core HTTP. |
| 48 | +* Chris: upgraded V8 and documented the process; also did some work on the REPL so that classes (and let/const) work |
| 49 | +* Domenic: PR reviews for v2.0.0, starting on V8 extension work to improve startup time |
| 50 | +* Fedor: worked on fixing some TLS memory issues, so far appears to be a large improvement in memory usage. |
| 51 | +* 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 |
| 52 | +* Mikeal: connection too bad to stand up. |
| 53 | +* Shigeki: working on SSL issues; root cert updates. Chrome and Firefox do whitelist of CNNIC cert hashes. |
| 54 | +* Trevor: looking at bugs, streams compliance |
| 55 | + |
| 56 | +## Minutes |
| 57 | + |
| 58 | +### Release Proposal: v2.0.0 [#1532](https://github.com/iojs/io.js/pull/1532) |
| 59 | + |
| 60 | +* Domenic: |
| 61 | + - v8 changes merged |
| 62 | + - worried that we’re getting into a bad cycle of “wait a few more days” for things to land |
| 63 | + - process.send |
| 64 | + - open an rc, add to website for a few days, ship by friday |
| 65 | +* Bert/Ben: |
| 66 | + - talk of process.send |
| 67 | + - Ben: should not hold up release, windows tests break right now |
| 68 | + - less of a regression than a change |
| 69 | +* Domenic: |
| 70 | + - these releases are a train |
| 71 | + - don’t hold up the train for features |
| 72 | + - make sure it’s ready for 3 |
| 73 | +* url updates from petka: might be ready |
| 74 | + - ci run passes on all platforms but arm7 |
| 75 | +* Domenic recalls in the runup to 1.0 – “nobody tests rc's” was the consensus |
| 76 | + |
| 77 | +Chris, Trevor: discussion about how the `master` and `next` branches are used. |
| 78 | + |
| 79 | +* process.send changes will slip for v2.0 |
| 80 | +* waiting for Petka’s comment and review on url changes (https://github.com/iojs/io.js/pull/1561) |
| 81 | +* release 2.x asap (friday) |
| 82 | + |
| 83 | +After the release: |
| 84 | + |
| 85 | +* the master branch will contain version 2.x. |
| 86 | +* api-breaking changes will land on the ‘next’ branch alongside v8 upgrades. master will be merged into next regularly |
| 87 | +* fixes are backported to the maintenance (v1.x) branch |
| 88 | + |
| 89 | +### Forward-port from v1.x [#1559](https://github.com/iojs/io.js/pull/1559) |
| 90 | + |
| 91 | +Discussed current plan for backporting patches to maintenance patches. |
| 92 | + |
| 93 | +* Consensus that we should give the “land in master and backport” plan a go and see how it works out. |
| 94 | + |
| 95 | +### Convergence plan (https://github.com/jasnell/dev-policy/pull/66) |
| 96 | + |
| 97 | +### Combined node.js/io.js TC/core call [#1413](https://github.com/iojs/io.js/issues/1413) |
| 98 | + |
| 99 | +## Next meeting |
| 100 | + |
| 101 | +* April 6th |
0 commit comments