►
From YouTube: 2021-09-22 - Node.js Release Working Group Meeting
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).
A
A
Now,
I
guess
a
couple
things
to
note
is
that
there
was
a
release
of
note
16
yesterday,
1610
so
check
it
out
and
also
preparation
is
happening
for
node,
17
and
note.
17
is
due
to
be
released
on
the
19th
of
october
and
I'll
add
the
link
to
the
minutes.
But
there
is
a
release
candidate
available
for
people
to
trail.
B
Yeah,
thank
you
beth,
and
so
I
just
wanted
to
inform
people
about
what
we're
planning
with
npm
eight
we're
planning
to
cut
a
release
in
about
two
weeks
time.
It's
not
going
to
be
anything
too
fancy.
In
fact,
the
only
real
major
breaking
changes
that
I
know
of
one
is
removing
support
for
node
10
and
the
other
is
removing
the
programmable
interface,
neither
of
which
should
be
breaking
changes
for
a
node
core
itself.
B
One
of
the
main
motivations
here
is:
we've
been
noticing
more
and
more
of
the
dependencies
within
npm
itself,
dropping
support
for
node
10,
which
is
putting
the
npm
team
in
a
really
awkward
position
of
how
do
we
kind
of
keep
things
going
if
we
want
to
maintain
this
for
the
lifetime
of
note
16's
lts,
so
the
idea
is
well
like:
let's
drop
node
10,
let's
cut
node
8.
B
B
And
we
had
opened
an
issue
on
the
core
repo
and
there's
also
an
rfc
over
at
the
npm
rfcs
repo.
So
far
you
know
everyone
who's
who's
seen.
It
seems
to
think
it's
a
good
idea
which
is
reassuring,
and
then
I
just
wanted
to
spread
the
word
about
it.
We'll
be
doing
you
know
more
information
as
we
get
closer
to
the
release
from
the
npm
team,
and
just
I
guess
like
does
anyone
have
any
questions.
B
A
Everyone
it
sounds
like
the
breaking
changes
are
quite
limited,
so
we
don't
expect
any
any
mass
breakages
or
anything
so
sounds.
A
That's
good
a
good
time
to
take
a
look
at
the
schedules
which
is
next
on
the
list,
and
that
includes
node
16
up
front
so
where
we
are
node
16
10
0
was
released
yesterday,
so
we
only
actually
have
two
more
releases
due
until
lts.
So
I
don't
know
going
back
to
your
discussion
because
now
miles.
Do
you
think
the
mpm8
stuff
will
be
ready
to
slot
into
one
of
those.
B
Sorry
you'll
have
to
bear
with
me
I'm
just
zooming
in
and
seeing
yeah.
I
believe
that
we
should
have
it
out
before
the
19th.
A
B
If
I
look
at
my
schedule
right
now,
we're
aiming
for,
but
don't
hold
me
accountable
to
the
seventh
as
the
date
that
we
want
to
get
the
release
out.
A
A
Yeah,
I
I
I
think,
typic
doing
the
release
of
16
on
the
same
day
of
17
makes
writing
the
change
log
a
little
bit
difficult,
because
the
change
logs
done
as
a
delta
between
the
latest
16
release
and
what's
new
in
17,
so
I'm
tempted
to
give
us
a
week's
gap
and
move
that
to
the
12th.
B
I
mean
I'm
not
the
one
doing
that
work,
so
I'm
quite
busy
right
here,
but
I
don't
see
any
problems
with
delaying
those
things
and
I
guess
one
question
would
be
for
the
lts
transition.
Are
we
still
doing?
I
can't
remember
where
we
landed,
but
once
upon
a
time
I
feel
like
it
was
a
minor
that
had
nothing
but
the
lts
transition.
But
then
I
feel
like
maybe
we
didn't
stick
to
that.
C
C
I
think
we
did
write
it
down,
but
I
can
I
can
check,
but
that
was
my
expectation.
D
Yeah
yeah,
that's
what
it
says:
okay
and
then
I
guess
that
means
the
last
14
before
maintenance.
Should
we
do
another
minor
in
october
or
do
you
think
this
will
be
the
last
one
then.
A
I
I
guess
I
kind
of
suspect
this
would
be
the
last
one,
because
it
will.
It
will
probably
do
a
nice
round
up
of
everything
that
needs
to
go
in
and
then
from
there.
Okay,
we'll
probably
just
do
ad
hoc
bug
or
patches
where
needed.
I
imagine.
A
D
In
that
case
yeah,
because
I
had
signed
up
for
the
last-
I
guess
that
would
have
been
the
last
patch
another
14
before
it
goes
into
maintenance
mode.
But
if
we
don't
need
that,
then
I
can
do
the
next
16.
yeah.
That
sounds
good.
That
sounds
good.
So.
A
Is
it
14
19.
michael's,
preparing.
A
He's
doing
18.,
oh
wait,
there
we
go
and
then
it's
got
the
28
from
there.
So
we
just
drop
those
yeah.
Okay
sounds
good
or
broken
a
table.
No
okay!
Leave
it
at
that.
I
think
I
think
that
makes
sense,
because
we
we
can
use
our
own
judgment
from
there
on
for
node
14
as
to
when
it
needs
a
release,
as
we
do
for
12.
A
A
No
okay
and
we're
all
good,
so
we
just
have
the
one
minor
couple
of
node
16s,
but
I
know
daniel
may
be
able
to
step
in
for
one
of
those-
and
I
guess
also
on
the
list
to
do
would
be
to
create
another
issue
for
the
node
17
plan
and
do
that
going
forwards.
A
That's
actually
everything
we've
covered
everything
quite
quickly.
I
guess
one
last
thing
to
mention
is:
we
are
looking
at
maybe
starting
up
some
release,
mentoring
sessions
again,
and
so
it's
on
my
to-do
list
to
create
a
a
doodle.
A
So
we
can
find
some
good
slots
for
folks
to
join
in
and
the
intent
would
be
when
myself
or
maybe
some
of
the
others
if
they
have
time
and
preparing
a
release-
and
we
could
use
the
session
to
just
show
some
of
the
process,
whether
it's
landing,
some
back
ports,
doing
some
cherry
picking
into
the
release
or
actually
doing
the
release
itself.
A
And
so
I
try
and
get
to
do
the
poll
together
and
I
did
try
to
get
last
week,
but
it
was
slightly
delayed,
so
I'll
try
to
get
that
together
and
hopefully
we
can
find
some
room
and
to
prepare
in
those
sessions.
B
Quick
question
on
this:
do
we
have
a
date
for
14
going
to,
or
for
would
it
be
14
going
to
maintenance.
A
A
What's
the
best
mechanism
for
doing
that,
I'm
wondering
whether
in
michael's
pr
for
the
last
miner,
we
do
a
call
out
like
that
collaborators
or
something.
B
A
Might
be
a
bit
visible.
B
We
could
add
the
members
list
or
like
use
the
team
chat
feature
I
mean
realistically,
we
may
want
to
just
do
it
everywhere.
We
can.
A
A
Oh
okay,
good
night,
anything
else
anyone
wants
to
discuss
today
and
in
the
public
section.
C
I
think
there's
been
a
few
proposals
to
drop
some
platforms.
I
think
one
was
to
drop
mac,
os
1014
from
cis
and
stuff
and
I
don't
think
anyone's
really
objected,
but
I
guess
I'll
just
mention
it
here.
From
my
point
of
view,
I've
always
found
1014
to
be
a
little
bit
awkward
on
things
like
citrine,
because
it
always
seems
to
time
out
and
in
stalls
and
things
yeah.
A
It
sounds
good
to
me
and
especially
if
it's
going
to
help
keep
sich
him
in
a
more
manageable
state.
That
sounds
good.
Hopefully,.
A
B
Yeah,
because
I
think
that,
like
we
were
relying
on
some
incorrect
behavior
for
the
way
it
was
grabbing
tarballs
is
there
do
we
need
someone
to
kind
of
dig
into
that
and
try
to
come
up
with
a
fix.
C
There
will
probably
help.
I
think
we
do
as
a
project
need
to
look
at
citrum
at
some
point,
because
we
do
have
quite
a
few
failures
that
are
just
there
in
sort
of
16,
and
I
guess
for
17
as
well,
and
there
are
quite
a
few
of
them
where
they're
not
installing,
presumably
because
of
this
yeah.
Because
of
that.
B
Okay,
yeah.
B
But
I
I
can
help
with
that.
I
don't
know
if
I
can
commit
to
the
broader
flailing
modules,
though.
A
B
A
Okay,
I'll,
let
it
as
in
action
to
the
minutes.
I
don't
think
today
is
probably
the
best
time
to
do
that,
but
if
we
can
get
those
sessions
that
happen,
if
we
have
more
time
in
the
next
release,
call
there's
two
options
of
using
the
time
there
to
go
through.
A
I
guess
we
just
need
to
remember
to
run
sichuan
in
advance
so
that
the
results
are
ready,
because
we
don't
want
to
be
waiting.
A
No
okay,
well
I'll
get
the
minutes
together
after
the
call
I'll
try
and
stick
all
the
links
in
there
to
the
recent
release
and
the
release
candidate
for
node
17
if
anyone's
interested,
and
that
I
guess,
speak
to
everyone
later
and
end.
The
stream.