►
From YouTube: Node.js Release Working Group Meeting - January 31 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Welcome
to
31st
of
January
release
were
current
meeting
and
we've
got
an
agenda
over
on
github.
It's
no
Jess
release
issue
for
one
one.
The
first
one
we've
got
on.
There
is
a
v6
dot,
X
backcourt,
which
is
I,
think
it's
for
any
P
I
is
from
Gabriel's,
so
maybe
Michael.
You
comment
on
that
one.
Do
you
know
why
it
was
added
to
release
agenda
yep.
A
A
D
Believe
it's
on
the
agenda
because
this
is
targeted
at
6:00
and
we
have
no
scheduled
further
right.
So
the
question
is:
are
we
taking
this?
You
know
for
a
potential
buy.
There
are
specific
six
release
or,
for
example,
if
there
was
another
security
release,
but
every
row
is
that
with
it
or
is
it
just
too
late
for
six
to
say
you
know
this
is
not
going
to
happen
so
one
way
or
the
other
we
have
to
make
a
decision.
Is
this
kind
of
going
to
six
or
not
great.
E
A
A
A
So
this
you
know
it's
really
we're
in
a
tough
we're
in
a
tough
state
that
you
know
either
either
we
add
it
to
six,
which
brings
us
back
into
consistency
which
is
kind
of
what
we
were
arguing
for
or
we
leave
it
in
a
broken
state.
And
if
people
come
to
us
and
say
well,
why
isn't
this
part?
Wasn't
this
there?
We
don't
have
a
good
story
or
a
you
know,
good
rationale
for
why
it's
not.
B
A
I'm
not
gonna,
it's
not
gonna
affect
migration
like.
Basically,
this
is
an
addition
right.
So
if
you're
not
using
it
now,
when
you
migrate,
it
doesn't
make
any
difference.
It's
more.
If
you
write
your,
if
you
write
your
you
write
your
add-on
and
you're
using
you
know
eight
or
ten
to
validate
it
and
you
say:
okay
I'm
good,
and
then
you
try
and
actually
roll
it
out
on
sex.
It's
not
gonna
work
because
it'll
say
hey.
This
is
a
missing
function.
B
A
It's
yeah
it's
kind
of
like
they
would
notice
the
problem
if
they're
developing
on
sex
and
they
might
come
and
say,
you're
missing
a
function.
The
doc
says
this
function
is
there:
why
isn't
that
function
there
right?
So,
if
you're
developing
on
the
lowest
one
you're,
actually
gonna
notice
it
and
you
know
you'll,
either
work
around
it
or
won't
use
it.
If
you
work
the
other
way
and
say:
okay,
I'm
gonna
write
my
module
and
then
say
well.
This
now
should
be
should
work
because
it's
the
same
ABI
across
all
the
releases.
A
You
know,
because
we
declare
there's
nothing.
That
says
we
can't
add
new
functions
in
in
later
versions,
but
we
have
a
versioning
scheme
than
where
we
would
bump
a
version.
Number
that
says:
okay,
this.
This
now
supports
1.4.
So
if
you're
using
it
you
only,
you
know
you
can
only
use
it
on
the
versions
that
support
1.4
and
things
like
our
pre
chip
story.
A
Do
try
and
you
know,
look
at
that
and
if
there's
multiple
versions
like
you
can
build
add-ons
that
support
different
versions
of
an
API,
and
you
know
it
will
try
and
pick
the
right
binary
based
on
which
version
you've
targeted.
So
somebody
could
rightly
say
well:
I've
targeted
one.
Three
I've
got
a
single
binary,
four
that
I
didn't
need
anything
newer,
but
this
function
is
missing.
A
C
I
mean
I
guess.
The
question
here,
it
seems
is
just
that
like
do
is
the
work
that
it
would
take
to
release
assembler
minor
on
six,
so
close
to
a
growing
out
of
service
worth
the
benefit
that
we
get
from
doing
it
so
like.
How
much
do
we
care
about
the
you
know
the
consistency
of
our
any
API
versioning
and
the
way
that
that
you
know
that
story
seems
to
end
users
like?
Is
it
worth
the
effort
cuz
like
it
definitely
would
be
some
effort
to
releases.
Oh.
A
Yes,
yeah
I
mean
it's
it's
it's
important
because
we're
you
know
what
the
adoption
phase,
where
we
don't
want
to
turn
people
off
and
have
them
not
have
confidence
that
it's
gonna
be
stable
and
consistent,
but
but
I,
but
you
know
it's
been
it's
been
since
August
as
well
right,
so
nobody
has
come
and
complain
since
then.
So
that's
clearly
an
indicator
that
you
know
not
to
me.
People
have
run
across
or
needed.
B
A
Yeah
I'm
kind
of
like
at
the
wait-and-see,
maybe
the
only
the
only
thing
that
bugs
me
a
bit
is
at
the
back
of
my
mind
is
that
you
know
people
may
still
try
and
support
6:00
later
on
and
but
I
guess.
At
that
point
we
just
say
sorry:
I
was
not
you
know.
If
we'd
found
it
then
we
definitely
would
do
it
so.
D
Are
commits
on
the
six
staging
that
haven't
actually
gone
out
in
a
release,
so
maybe
we
should
at
some
point
you
know.
Maybe
I've
started
me
to
go
through
the
go
through
those
Canadian
see.
If
any
of
those
warrant
a
release
of
six
I
mean
I
would
be
doubtful,
but
that
may
be
something
worth
doing
just
to
see
if
there's
any
yeah.
B
D
F
B
B
B
F
B
C
So
Michael
I
can
sync
up
with
you
later
potentially
but
yeah
I'm
a
heel
to
take
that
over
okay.
B
B
F
B
And
then
we've
got
doc,
update
the
Lisa
onboarding
process
and
bras.
So
I
think
this
is
what
we
are
that's
open
in
know,
Jeff's,
release
and
I
think
it
covers
the
point
we
raised
last
meeting
about
you
have
to
promote
a
current
before
you
do
an
LCS
release,
so
I
guess
what
just
needs
to
happen
here
is
get
a
few
more
reviews
on
it
before
it
lands
I
think
that's,
probably
one
miles
put
on
the
agenda
just
to
draw
our
attention
to
it
before.
B
I
guess
once
we've
got
a
few
more
reviews,
we
will
go
ahead.
It's
been
open
for,
while
no
preventing
those
Klaus
isn't
here
to
say
why
he
had
it
to
release.
So
guess.
We'll
move
on
and
last
item
on.
Our
agenda
is
update
to
reflect
an
API,
so
I
guess
Michael
you're
the
best
person
to
talk
through
this
one
right.
A
So
we
just
we
talked
about
this
last
week
and
the
suggestion
was
that
I
do
a
PR
which
basically
says
tweaks
the
process
for
an
API,
so
I
just
added
into
the
the
text
that
says
you
know
once
released
moves
into
maintenance
mode.
Only
critical,
secure,
bugs
security
fixes,
documentation,
updates
and
updates
to
ensure
consistent
usability
of
the
any
API
across
LTS
releases
will
be
permitted,
that's
and
then
I
another
section
down
below
it
says
you
know,
updates
to
ensure
consistent
usability.
A
The
NEP
across
the
LTS
releases
are
allowed,
as
it
is
important
to
ensure
that
any
PII
native
modules
can
be
used
across
Celsius
versions
in
order
to
support
adoption
and
that's
was
sort
of
in
support
of
our
you
know
the
thoughts
of
you
know.
Okay,
we
could
do
a
quarterly
release,
but
to
make
it
explicit
one
of
the
reasons
why
we
didn't
well,
we
would
include
fixes
that
you
know
might
look
like
bug
fixes
or
whatever
that
weren't
as
critical,
but
because
of
the
consistency
needs
we
would
do
anyway.
A
B
A
B
A
I
think
that's
where
it
belongs,
because
it's
a
release
working
group
that
kind
of
outlines
the
what
goes
or
in
or
doesn't
go
in.
Okay,
so
I
mean
I,
don't
think,
there's
any
objections
in
the
issue
itself
and
there's
a
number
of
approvals.
So
I
think
it's
probably
on
the
agenda
just
to
make
sure
that
you
know
the
release
team
agrees
and
it
are
we
ready
to
land.
If
that
is
the
case,.
B
Okay
and
that's
the
last
item
on
the
agenda,
what
I
will
quickly
hopper
to
is
the
ten
directs
release
schedule
and
so
I'm
find
up
to
do.
The
February
release,
which
is
to
you
out
on
the
26th
of
February
and
miles,
is
signed
to
do
December
minor,
which
comes
out
at
the
beginning
of
April,
and
there's
also
a
plan
for
a
note,
8
release
at
the
end
of
March
to
pick
up
all
of
the
open
back
ports
or
the
ones
we
deem
necessary
for
this
release
before
April
and
the
only
other
thing
is.