►
From YouTube: 2021-07-01 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
Welcome
to
the
node.js
release
working
group
meeting
on
the
1st
of
july
2021
and
we
will
work
through
the
agenda
which
is
in
issue
681,
but
realize
it's
not
been
populated,
so
we're
working
through
everything.
Everything
with
the
label
release
agenda,
which
is
the
release
schedules,
plus
the
release
keys
discussion.
A
So
the
node
16
we're
actually
not
got
any
volunteers
from
july
onwards.
I
should
be
able
to
pick
up
one
of
these
in
july
and
potentially
one
over
august
two.
I
guess
just
to
call
out
the
ask
for
volunteers.
B
A
Have
availability,
and
if
we,
if
not,
we
will
have
to
adjust
the
schedule
accordingly,.
A
A
A
C
A
Perfect,
thank
you
awesome.
I
can
probably
do
another.
C
B
A
Okay
sounds
good,
I
guess
that's,
so
it
gives
enough
time
to
start
working
on
the
minor
afterwards,
which
will
be
slightly
larger
right.
B
Okay,
we
need
to
look
at.
We
have
an
issue
at
the
moment
with
the
vhci
and
the
version
of
gn
that
we're
using
on
some
of
the
platforms
so
that
that's
something
I
need
to
look
at
from
a
sort
of
build
release
perspective
so
that
that
will
either
be
a
back
port
to
the
lts
branches.
B
So
that's
14
and
12
to
patch
the
v8
build
scripts
to
work
with
the
newer
gn
or
I'm
going
to
have
to
do
something
on
the
build
side
to
use
an
older
gn
for
the
lts
branches
and
the
newer
gn4
sort
of
current
there's
been
a
there's,
been
an
incompatible
change
in
some
version
of
gn
somewhere
in
the
middle,
and
we
can't
the
old
versions
are
not
new
enough
to
build
v8
9.2
so
that
pr
we
updated
gn4,
but
the
new
gn
doesn't
build
the
lts,
the
version
of
v8
in
the
lts
releases
at
the
moment.
B
Yeah,
I'm
down
for
a
patch
release,
so
I'll
do
that
after
the
after
this
security
release,
yeah
yeah,
remember,
I
don't
really
have
a
fixed
time
frame,
so
it
might
be
near
the
end
of
july,
but
yeah.
B
It's
just
we
haven't
really
done
one
since
yeah
since
sort
of
march
april.
So
it's
not
desperate
that
we
need
one
but
there's
there
is
a
couple
of
things
that
probably
could
be
nice
to
get
in.
A
A
Okay
sounds
good
okay,
so
I
can
do
one
of
the
upcoming
16s,
because
this
one
is
quite
small,
one,
that's
the
security
release
and
then
we've
got
two
of
those,
so
pretty
much
everything
should
be
scheduled
for
july.
So
that's
good
and
now
the
last
other
item
on
agenda
was
about
the
release
keys.
B
I
can
summarize
so
for
as
long
as
I
can
remember,
we've
been
uploading.
Our
gpg
signing
keys
that
were
used
to
sign
releases
to
the
sks
key
servers
network,
and
that
was
about
a
week
ago.
Now
I
think,
or
maybe
a
bit
longer
than
that
that
that
stopped
working
now
so
they've
stopped
publishing
dns
entries
for
the
key
server
pool.
So
you
basically
cannot
get
to
them
anymore
to
download
keys.
B
I
don't
know
if
maybe
some
individual
servers
in
the
pool
are
available,
but
the
pool
itself
doesn't
return
any
ip
addresses.
So
if
you
try
and
connect
to
the
to
the,
if
you
try
and
follow
the
instructions
we
currently
have
for
verifying
keys
the
key
server
and
that
doesn't
work.
So
there's
been
a
couple
of
issues:
there's
one
in
docker,
node,
there's
one
where's
this
one!
Is
this
the
one
docker
node
or
is
this
now?
This
is
the
one
in
node
yeah.
B
So
there's
been
a
couple
of
issues
open
because
people
have
found
it
doesn't
work
anymore
and
I
think
most
of
us
have
our
keys
in
other
key
servers.
So
I
think
some
people,
some
people-
have
posted
in
this.
These
issues
saying
they've
used
either
the
ubuntu
key
server
or
there's
a
another
one.
Is
it
open,
pgp.
A
B
There's
some
other,
but
I
don't
it's
a
bit
hard
to
say
for
certain
whether
all
of
our
keys
are
in
both
of
those
repositories,
but
then
I
guess
with
the
distributed
key
servers.
It
was
always
also
not
obvious
if
the
keys
had
propagated
to
all
the
servers
in
the
pool.
B
So
we've
had
a
long-standing
issue
to
actually
put
our
keys
into
a
repository.
So
there
is
a
new
repository.
That's
been
set
up,
release
keys
under
the
node.js
org
and
we
are
we've
finally
managed
to
go
through
the
steps
and
transfer
that
into
the
organization
we're
going
through
the
process
of
trying
to
update
the
keys
on
that,
but
that's
not
quite
ready
yet
so
this
is
basically
the
status.
B
We're
in
is
that
the
current
instructions
don't
work,
you
may
be
able
to
get
keys
from
other
key
servers
and
the
eventual
replacement
will
be
this
new
repository
we're
setting
up,
but
that's
not
quite
ready
at
this
moment
in
time.
So
this
is
kind
of
unfortunate.
Given
security
releases
are
coming
out
today.
If
you
already
have
the
keys
locally,
they
will
still
be.
You
know
we
haven't
changed
our
keys
themselves.
It's
just
the
path
of
getting
the
keys.
A
Yeah
the
there
is
a
couple
of
pr's
open
to
update.
What's
in
the
release
keys,
I
think
the
ask
is
for
us
to
check
and
or
at
least
the
ones
that
have
changed
to
check.
A
Yeah
shouldn't
have,
I
know
we
had
some
problems
with
comparing
the
ascii
output
and
it
being
different.
So
I
need
to
look
into
that
a
bit
more,
but
it
looks
like
it's.
A
canterbury
has
added
a
script
that
we
can
run
to
just
add
it
and
then
do
a
git
commit.
So
I'll
probably
try
doing
that
and
see
what
happens.
A
Is
there
anything
more
for
us
to
add
on
this
one,
or
is
it
just
knowing
that
we
need
to
get
these
things
updated
and
release
keys?
I
guess
afterwards
we
will
need
to
amend
the
verification
guidance,
that's
in
no
core
repo
and
also
amend
any
onboarding
type
guidance
to
make
sure
instructs
to
use
this
repository.
A
B
A
B
So
I
guess
the
only
the
only
other
question
is
access
on
this
repo.
So
I
guess
the
plan
will
be
to
give
the
releases
access
to
this
as
an
admin
access.
A
Yes,
but
I
guess
we'd
also
like
to
preserve
canterbury's
access
to
as
the
person
kind
of
leading.
B
At
least
one
at
least
when
we're,
while
we're
getting
it,
set
up-
yeah,
probably
probably
eventually
we
might
revoke
it,
but
yeah
I
mean
I
think
at
the
moment.
I
think
it's
you
and
you
and
canterbury
that
have
administration.
A
B
A
Add
the
release
working
group
after
this
school
at
least
or
releases
free.