►
From YouTube: 2021-04-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
Okay,
so
we
are
live
with
the
node.js
release,
work
group
meeting
on
the
22nd
of
april
2021
and
we'll
be
working
from
the
agenda,
which
is
in
the
node.js
release
repository
issues
659,
but
start
the
call.
Are
there
any
announcements
anyone
would
like
to
make.
A
I
guess
I
should
call
out:
node
16
was
released
on
tuesday
as
planned
and
you'll
find.
You
should
find
that
there
are
now
apple
silicon
cars
and
also
multi
architecture
binary
now.
So
it's
great
that
great
that
we've
got
that
platform
covered
now
and
you
should
also
be
able
to
find
like
the
node.js,
medium
release,
blog
and
also
the
regular
release
blog
on
the
node.js
or
website.
If
you
want
more
details
about
the
16
release,.
A
Yeah.
Okay,
so
can
you
all
see
the
agenda
issue
now?
I
hope
yep
awesome.
Yes,
okay!
So
on
our
list,
oh,
I
should
probably
untag
15,
because
now
15s
and
maintenance,
we
will
only
be
doing
releases
on
a
nas
need
basis,
so
security
or
some
really
critical,
bugs
and
so
I'll
start
by
going
through.
The
16
schedule
looks
like
we,
the
next
one's
due
4th
of
may
and
michael's
volunteered,
for
that
one
so
sounds
good,
so
yeah,
any
any
volunteers
for
those
current
releases.
Just
add
your
name.
A
If
you'd
like
good
news,
is
that
I
don't
see
anything
as
of
today
needing
an
immediate
patch,
which
is
unusual
for
a
major
release.
So
looking
good
for
that,
so
next
release
4th
of
may.
A
A
Okay,
sure,
probably
not
much
more
to
say
on
that
14.
So
this
one
this
is
the
long
awaited
seven
miner.
There
are
quite
a
lot
of
things
on
the
branch
now
and
there
are
quite
a
few
open,
pr's
it'd
be
good
to
get
merged.
I
haven't
had
time
to
open
up
a
proposal.
I
don't
know
if
anyone
else
thinks
they
will
get
time
soon.
C
I
could
probably
work
on
something
this
weekend,
so
we
haven't
had
a
release
for
14
since
february.
Is
that
one
that
said,
we
might.
A
Not
have
added
the
security
release,
but
we
haven't
had
like
okay,
we
haven't
had
a
feature
full
release
for
quite
a
while.
Well
since
it
went
lts
actually
so,
okay.
C
A
Honest,
I
think
at
this
point,
if
that's
going
to
be
like
a
blocker
to
just
getting
a
release
out,
I
think
we
should
just
maybe
skip
that
open
it,
as
in
as
far
in
advance
as
we
originally
can,
and
maybe
focus
a
bit
more
on,
like
citrium
tests
and
just
to
double
check
things
there,
because
I
it's
been
so
like
so
deferred
because
of
our
availability,
and
I
do
think
having
to
like
crack
it.
Three
weeks
in
advance
does
add
pain
to
trying
to
find
the
availability.
A
B
C
Yeah,
so
for
this
one
does
I
haven't
seen
looked
at
the
stitching
smoker
in
a
while?
Is
that,
like
what
type
of
I
guess
like
air
threshold,
are
we
looking
at?
Is
it?
Does
it
have
to
pass
everything
or
do
I
just
need
to
make
sure
that
everything
that
there
aren't
any
more
failures
than
there
were
before.
A
Yeah,
I
think
I
think
you'll
probably
have
to
just
do
the
delta
and
compare
the
two
and,
if
you
about
all
of
us,
I'm
sure
we
can
dig
in
and
take
a
look
at
what
and
help
out.
I
definitely
can
but
yeah
because
sichuan's
not
in
a
very
green
state
across
the
board
at
the
moment,
so
yeah,
okay,
that
sounds
good,
really
helpful
and
yeah.
I
wanna
absolutely
put
my
name.
C
Down
and
then
just
yeah
I'll
do
it
after
this,
I'm
not
sure
what
the
security
patch
was
so
yeah
I'll,
like
probably
add
it
in
there
and
then
add
my
name.
A
A
B
B
A
B
A
We
might
be
able
to
close
this
one
I'll
double
check
after,
let's
see,
if
I
don't
open
this.
B
A
I
I
don't
see
anything
needing
like
immediate
release,
but
I
guess
maybe,
when
we
do
our
next
round
of
patch
releases
after
the
14
minus
gone
out,
it
might
make
sense
just
to
align
them.
A
Yeah,
especially
as
that
marks
asm
is
stable,
doesn't
it.
B
Yes,
I
believe,
you're
right.
I
think
I
think
we've
done
a
12
release
where
that
happened,
but
not
a
14
release.
E
A
That
sounds
good
10.
We
will
not
have
to
worry
about
after
a
few
days
time
when
it
goes
end
of
life,
and
so
I
will
close
that
issue
when
that
happens,
that's
good
and
that's
everything
on
the
schedule.
So
we've
got
some
volunteers
for
the
upcoming
16
releases,
danielle's
volunteered
to
help
get
the
miner
out
and
15.
We
will
only
do
like
treat
the
same
as
12
really
and
treat
it
as
if
it's
in
maintenance
and
only
on
a
nas
need
basis
until
june.
A
I
believe
it
is
so
that
sort
of
schedules-
I
guess
one
thing-
does
make
sense
to
raise
while
we're
here
is
the
I
extended
the
schedule
because
now,
like
the
last
one
we
had
included,
was
node
16.
It
makes
sense
to
extend
it
a
bit
so
folks
know
what's
coming
next
and
in
terms
of
the
dates
I
stuck
down,
I
sticked
with
stuck
with
the
similar
what
we've
done
so
the
release
is
always
the
third
tuesday.
A
I
believe
it
is
in
the
month
of
the
release
and
then
the
lts
happens
to
week
later
so
that
that
was
the
discussion.
We've
had
for
quite
a
while
around
the
order
of
promoting
to
lts
versus
releasing
the
new
current,
and
I
think
that
was
the
way
we
opted
to
do
it.
So
I
accounted
for
that
and
for
now
I've
kept
the
same
like
maintenance,
duration
and
active
lts
duration
as
before,
so
don't
necessarily
if
it
makes
sense
to
keep
it
as
that
for
now
and
then
edit
closer
to
the
time.
A
And
yeah
for
now
the
timetable,
I
know
that's
probably
terribly
small.
A
It's
got
a
lot
more
versions
in
it,
but
I
did.
I
did
include
that
so
people
can
see
10
and,
like
the
end,
so
I
think
that's
useful
to
keep
for
now
and
then,
maybe
in
a
month
or
so
time,
we
will
move
it
forwards
and
drop
10
and
potentially
15
as
well.
So
for
now
it's
going
to
be
a
bit
of
a
longer
timeline.
A
A
I
guess,
while
we're
here
makes
sense
to
skim
through
some
open
issues,
one
that
I
did
spot.
You
know
the
imminent
issue
for
the
time
zone
data.
I
think
at
this
point
we
can
just
close
this
one
because
we
kind
of-
but
it's
not
so
imminent,
anymore,
yeah,
exactly
so
yeah.
I
don't
know
if
there's
anything
that
needs
cherry
pick
like
an
update
to
the
time
zone,
data
on
12
or
14.
B
Yeah,
I
wouldn't
wouldn't
know
without
further
investigation
yeah
need
to
check.
I
think,
while
I
remember
that
the
icu
updates
in
the
lts
branches
may
be
blocked
on
the
availability
of
the
full
ice
full
icu
package
right.
So
I
think
since
since
the
more
recent
releases
have
full
icu,
we've
stopped
publishing
or
we
haven't
had
packages
published
of
the
full
icu
data.
B
So
it
might
not
be
an
issue,
but
I
I
guess
I
might
just
bring
that
up
since
we've
mentioned
icu,
you
know
if
we
do
want
to
bump
icu
in
the
older
release
lines,
we
might
need
to
look
at
getting
the
full
ic
npm
package
updated,
which
I
think
is
in
the
process
of
being
transferred
into
the
organization.
B
But
I
don't
know
what
the
state
of
actual
people
being
able
to
to
pop.
You
know
to
actually
actively
work
on
it
and
publish
new
new
packages
are.
A
A
One
of
the
other
ones
was
the
manual
back
ports
with
compatibility
patches.
This
was
a
suggestion
from
reuben,
quite
a
while
back
now,
a
couple
of
years,
and
so
when
opening
a
back
port,
you'd
open,
you'd
open
it
with
the
same
commits
and
then
you'd
probably
have
like
some
fix
up
commits
on
top
with
the
idea
of
it
would
make
it
easier
to
see
what
we've
had
to
do
to
backport
it
or
what
the
contributors
had
to
do
to
backport
it
and
how
it's
diverged
from
the
original
commit.
A
I
don't
know
if
folks
thinks
that
that's
still
something
we
want
to
do
going
forward
or
something
we
can
close
off,
because
we've
not
we've
not
really
pushed
it
forwards.
In
the
past
couple
of.
A
A
I
guess
if
there's
no
comments
on
it,
should
that
be
taken,
as
we
should
just
close
this
and
if
we
consider
like
instead
of
reviewing
back
ports,
is
a
problem
in
future.
We
can
consider
this
as
an
option
it
seems
like
for
now,
if
we're
not
very
plus
one
on
it.
Maybe
it's
not
necessary.
A
Yeah
I'll
leave
that
on
there
for
now,
I'm
not
sure
there's
anything
else
on
this
list
that
needs
addressing
so
invite
anyone
else
to
raise
any
topics
today,.
B
While
we
were
talking
about
porter's,
I
think
I
remember
miles
put
branch
protection
on
yes,
so
I
think
it
was
initially
back
quarters
only
and
I
I
haven't
looked
to
see
whether
it
was
expanded
out
to
releases
as
well,
because
I
don't
think
every
releaser
is
in
the
back
of
the
team
or
that
it
wasn't
at
the
time
that
mild
protection
on.
So
that's
something
to
bear
in
mind.
If
anyone
encounters
issues
pushing
to
the
staging
branches.
C
Okay,
yeah
I'll
look
out
for
that.
I'm
not
sure
if
I'm
on
the
back
porter's
team
I'll
have
to
check.
B
I
I
don't
know
if
the
branch
protection
rules
were
expanded
to
include
more
teams.
I
I
can't
see
those
have
to
be
someone
someone
in
the
tsu
or
an
admin.
I
guess
the
com
com
has
had
permissions
as
well.
Who
can
who
can
see
the
permissions
and
branches.
A
If,
if
you
have
any
issues,
I'm
sure
let
me
or
miles
known
will
be
able
to
tweak
it.
A
Okay,
one
one
last
thing
I
didn't
mention
it
last
time,
but
that
was
off
stream
around
potentially
creating
of
releases
at
nodejs.org,
alias
the
reason
being
that,
when
there's
a
request
for
a
security
release
from
the
people
investigating
the
patches,
they
could
maybe
email
that
and
just
get
flag
it
to
the
top
of
our
inbox
kind
of
thing
that
they
need
a
call
for
volunteers,
because
it's
scary
to
release,
because
we
can't
we
can't
talk
about
this
in
slack.
So
it
needs
all
public
issues.
C
A
The
alias
exists
now
or
it
doesn't
exist
it
doesn't,
it
doesn't
exist.
The
idea
was
to
create
one
so
that
when
there
was
something
semi-urgent
for
releases
to
volunteer
or
take
a
look
at
that
it
would
be
much
okay,
yeah.
That
makes
sense,
I
think
yeah
I
I
guess
I
guess
it's
just.
We
all
get
a
flood
of
github
notifications,
so
whether
we
think
it'd
be
valuable
in
the
case
when
there
is
something
urgent
to
get
an
email
to
our.
A
A
B
As
far
as
I
know,
you
can
just
add
add
something
pr
into
the
repo
it
requires
someone
to
actually
deploy
it
onto
the
server,
but
I
can
do
that.
Okay,
so
I
guess
the
question
is
a
pr
and
I
guess,
get
people
to
look
at
it
and
make
sure
they're
happy
to
be
on
that
list.
A
Yeah,
that's
what
I
was
gonna
say.
Would
anyone
be
opposed
to
it,
but
I
guess
I
can
raise
an
issue
and
if
people
are
happy
to
be
included
link
to
the
pr
and
if
they
they
want
to
review
to
remove
themselves
or
such.
A
Okay
sounds
good
and,
and
that
should
simplify,
so
the
security
releases
have
like
a
steward
on
the
security
side,
and
dan
has
done
it
recently,
and
it
does
mean
when
they're
calling
for
volunteers,
they
can
just
send
an
email
to
say:
hey,
we've
got
these
upcoming
vulnerabilities
that
need
to
be
patched
and
can
we
have
volunteers
and
they
don't
need
to
know
like
the
specific
names
of
us.
They
can
just
email
us
as
a
group.
B
A
Okay,
anything
else
to
raise
today.
B
I
guess
we
might
mention
the
the
plan
for
apple
silicon
binaries
is
that
we
we
do
have
support
in
node
14
for
compiling
on
apple
silicon,
but
for
the
binaries,
we're
probably
going
to
wait
and
see
how
it
how
16
pounds
out
and
make
sure
there's
sort
of
nothing,
nothing
that
comes
up
with
the
binaries
there.
B
We
may
not
do
the
package
builds
for
14,
because
that
involved
us
moving
the
entire
to
a
completely
different,
build
machine
so
for
for
an
lts
release
that
might
be
a
bit
risky,
but
we
could
potentially
add
the
table
the
the
apple
silicon
table
that
could
potentially
be
done,
14
relatively
low
risk.
But
again
I
think
we
probably
do
want
to
wait.
B
Wait
a
little
bit
to
see
if
anything
comes
up
with
16
and
we
we
are
behind
and
14
anyway.
So
we
should
try
and
catch
walton
up
first
before
we
look
at
into
adding
more
stuff
there,
but
yeah
just
in
case
everyone's
viewing.
The
recording
of
this
call
and
have
questions
about
that
quality
and
the
apple
silicon
support
it's
mainly
16
onwards,
and
then
we
might
look
in
later
on.
A
Yeah,
I
think
I
think
it's
good
plan
like
if,
if
everything
goes
well
with
16,
considering
I
post
adding
the
table
shouldn't
break
anyone
as
is,
but
we
probably
definitely
don't
want
to
mess
with
the
installer
on
14
to
include
another
architecture,
changing
things
underneath
people
on
lts,
but
at
least
adding
that
additional
tar
and
once
we've
we've
seen
everything's
fine
with
16.
That
would
enable
things
like
nvm,
which
I
think
would
be
very
useful.
So
that's
a
good.
A
Okay,
if
that's
all
speak
to
you
all
in
a
couple
of
weeks,
thank
you.
Thanks
for
joining
bye.