Node: Node.js Foundation Core Technical Committee (CTC) Meeting 2016-10-05

Created on 3 Oct 2016  Β·  17Comments  Β·  Source: nodejs/node

Time

UTC Wed 05-Oct-2016 20:00:

| Timezone | Date/Time |
| --- | --- |
| US / Pacific | Wed 05-Oct-2016 13:00 |
| US / Mountain | Wed 05-Oct-2016 14:00 |
| US / Central | Wed 05-Oct-2016 15:00 |
| US / Eastern | Wed 05-Oct-2016 16:00 |
| Amsterdam | Wed 05-Oct-2016 22:00 |
| Moscow | Wed 05-Oct-2016 23:00 |
| Tokyo | Thu 06-Oct-2016 05:00 |
| Sydney | Thu 06-Oct-2016 07:00 |

Or in your local time:

Links

Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • Intl: Consider deprecating Intl.v8BreakIterator #8865

  • net: multiple listen() events fail silently #8419

    nodejs/CTC

  • Scheduling Meetings #14

    Invited

  • Anna Henningsen @addaleax (CTC)

  • Bradley Meck @bmeck (observer/GoDaddy/TC39)
  • Ben Noordhuis @bnoordhuis (CTC)
  • Π‘ΠΊΠΎΠ²ΠΎΡ€ΠΎΠ΄Π° Никита АндрССвич @ChALkeR (CTC)
  • Chris Dickinson @chrisdickinson (CTC)
  • Colin Ihrig @cjihrig (CTC)
  • Evan Lucas @evanlucas (CTC)
  • Jeremiah Senkpiel @Fishrock123 (CTC)
  • Tracy Hinds @hackygolucky (observer/Node.js Foundation)
  • Fedor Indutny @indutny (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)
  • Rod Vagg @rvagg (CTC)
  • Seth Thompson @s3ththompson (observer/Google)
  • Shigeki Ohtsu @shigeki (CTC)
  • Steven R Loomis @srl295 (observer/IBM/ICU)
  • Myles Borins @TheAlphaNerd (CTC)
  • Sakthipriyan Vairamani @thefourtheye (observer)
  • Trevor Norris @trevnorris (CTC)
  • Rich Trott @Trott (CTC)

    Notes

The agenda comes from issues labelled with ctc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Uberconference; participants should have the link
& numbers, contact me if you don't.

Public participation

We stream our conference call straight to YouTube so anyone can listen
to it live, it should start playing at
https://www.youtube.com/c/nodejs+foundation/live when we turn it on.
There's usually a short cat-herding time at the start of the meeting and
then occasionally we have some quick private business to attend to
before we can start recording & streaming. So be patient and it should
show up.

Many of us will be on IRC in #node-dev on Freenode if you'd like to
interact, we have a Q/A session scheduled at the end of the meeting if
you'd like us to discuss anything in particular. @nodejs/collaborators
in particular if there's anything you need from the CTC that's not worth
putting on as a separate agenda item, this is a good place for it.

picture Trott

Most helpful comment

It may be possible to upgrade mid-cycle like we did in v6.50 with V8 5.0 -> 5.1. Depends on whether we can patch up the API and ABI breakage.

picture bnoordhuis on 4 Oct 2016
👍2

All 17 comments

The usual reminders that:

  • This meeting will take place in approximately 46 hours.
  • Standup section is all ready to go.
Trott picture Trott on 4 Oct 2016

I'm chaperoning a three day field trip for my two boys. I won't be back in
town until Thursday. Have fun everyone. Should be back on regular schedule
next week

On Monday, October 3, 2016, Rich Trott [email protected] wrote:

Time

_UTC Wed 05-Oct-2016 20:00_:
Timezone Date/Time
US / Pacific Wed 05-Oct-2016 13:00
US / Mountain Wed 05-Oct-2016 14:00
US / Central Wed 05-Oct-2016 15:00
US / Eastern Wed 05-Oct-2016 16:00
Amsterdam Wed 05-Oct-2016 22:00
Moscow Wed 05-Oct-2016 23:00
Tokyo Thu 06-Oct-2016 05:00
Sydney Thu 06-Oct-2016 07:00

Or in your local time:

Links

Agenda

Extracted from _ctc-agenda_ labelled issues and pull requests from the _nodejs
org_ prior to the meeting.
nodejs/node

nodejs/CTC

Invited

Notes

The agenda comes from issues labelled with ctc-agenda across _all of the
repositories in the nodejs org_. Please label any additional issues that
should be on the agenda before the meeting starts.
Joining the meeting

Uberconference; participants should have the link
& numbers, contact me if you don't.
Public participation

We stream our conference call straight to YouTube so anyone can listen
to it live, it should start playing at
_https://www.youtube.com/c/nodejs+foundation/live
https://www.youtube.com/c/nodejs+foundation/live_ when we turn it on.
There's usually a short cat-herding time at the start of the meeting and
then occasionally we have some quick private business to attend to
before we can start recording & streaming. So be patient and it should
show up.

Many of us will be on IRC in #node-dev on Freenode if you'd like to
interact, we have a Q/A session scheduled at the end of the meeting if
you'd like us to discuss anything in particular. @nodejs/collaborators
https://github.com/orgs/nodejs/teams/collaborators
in particular if there's anything you need from the CTC that's not worth
putting on as a separate agenda item, this is a good place for it.

β€”
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node/issues/8915, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa2eWh0sm8RkJkrV1EDMq1uhg7SgKhlks5qwXrdgaJpZM4KNFxZ
.

jasnell picture jasnell on 4 Oct 2016

I should be able to make it, but there’s a good chance I’m late, so don’t wait for me. ;)

addaleax picture addaleax on 4 Oct 2016

Sorry, I will miss this meeting. I will have to get up very early in the next day.

ChALkeR picture ChALkeR on 4 Oct 2016

I want to propose an agenda item. If this should be a separate issue just let me know.

Waiting for V8 5.5 for node 7

V8 5.5 comes with a flagless async/await, one of the most anticipated additions to ES. This will tremendously improve the quality of node development. It even has the potential to start a move away from transpilers. The slowdown in load times and additional hassle they add will no longer be outweighed by the pros of extra features they bring anymore, since after async/await, most of the necessary language features will be natively in, and the rest are just _nice to haves_ that justify transpilation only for developers that just have to live on the edge :)

It's already 2nd week V8 5.5 is being tested in Chrome Canary, and it'll be a few more weeks before it's released. Waiting these few weeks would mean the whole node community won't have to wait another half a year to get flagless async/await, which would be the best Christmas ever!

So please, wait a bit, so we don't have to wait a lot :)

darsain picture darsain on 4 Oct 2016

@darsain, -1 on that, it doesn't look a good idea to me to move Node.js v7 release to December, given that the schedule has been announced and that per schedule the release should happen in October.

ChALkeR picture ChALkeR on 4 Oct 2016

@ChALkeR and others: Since rescheduling releases is out of the question, do you see any other solution for getting V8 5.5 in sooner?

imyller picture imyller on 4 Oct 2016

It may be possible to upgrade mid-cycle like we did in v6.50 with V8 5.0 -> 5.1. Depends on whether we can patch up the API and ABI breakage.

bnoordhuis picture bnoordhuis on 4 Oct 2016
👍2

@imyller, not sure how we could get in V8 5.5 in a Node.js release sooner than December given that V8 5.5 is going to be released in December.

ChALkeR picture ChALkeR on 4 Oct 2016
👍1

I started working last week on the possible update to V8 5.5. For now it doesn't seem that there is much to do in order stay backward-compatible.

targos picture targos on 4 Oct 2016

@ChALkeR V8 5.5 landing soon-ish after it's released is pretty much all I'm asking for :) Don't know why I was under the impression that significant V8 bumps happen only on major node updates. My bad if that's not the case.

darsain picture darsain on 4 Oct 2016

@darsain It depends, e.g. (as @bnoordhuis mentioned above) in 6.5.0 V8 was bumped from 5.0 to 5.1.

But note that the estimated release date of V8 5.5 is not in few weeks, but is scheduled for December, so it won't get into any Node.js release before that.

ChALkeR picture ChALkeR on 4 Oct 2016

not sure how we could get in v8 5.5 in a Node.js release sooner than December

I didn't mean sooner than December, but sooner than next major Node.js release after v7.x.x. I think that was the main concern for @darsain.

As @bnoordhuis pointed out, there has been mid-cycle V8 upgrades in the past. I believe that just stating such possibility alleviates many concerns.

imyller picture imyller on 4 Oct 2016

but sooner than next major Node.js release after v7. I think that was the main concern for @darsain

Yes, precisely. Sorry for not being clear enough.

darsain picture darsain on 4 Oct 2016

Viewers today (max 10)
node_livestream_viewers-2016-10-05

Fishrock123 picture Fishrock123 on 5 Oct 2016

Chiming in: 5.5 is planned to be promoted to Chrome's Stable channel beginning/mid December. At that point it didn't have any Stable coverage yet.

Given that Async/await is a complete new feature (and an "intrusive" one) that sounds like a high risk to me. If people want to play around with it they can already activate it via a flag in 5.4 but obviously it is not finished there.

@ofrobots FYI

natorion picture natorion on 6 Oct 2016

cc @nodejs/v8

fhinkel picture fhinkel on 6 Oct 2016
Was this page helpful?
0 / 5 - 0 ratings

Related issues

addaleax picture addaleax  Β·  3Comments
akdor1154 picture akdor1154  Β·  3Comments
stevenvachon picture stevenvachon  Β·  3Comments
srl295 picture srl295  Β·  3Comments
vsemozhetbyt picture vsemozhetbyt  Β·  3Comments