►
From YouTube: 2020-10-08 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
So
we
are
live
with
the
node.js
release,
workgroup
meeting
for
the
8th
of
october
2020..
We
will
work
from
the
agenda,
which
is
in
the
node.js
release
repository
and
it's
issue
number
615..
B
I
would
like
to
make
a
quick
announcement.
I'm
thanking
you
beth
for
all
the
hard
work
on
the
15
release.
It
was
exciting
to
see
the
rc.1
go
out
yesterday,
including
npm
7.
A
Awesome
thanks
and
I'll
stick
a
link
to
that
in
a
minute
in
case
anyone
watching
the
stream
or
watching
back,
wants
to
download
and
try
it
out.
A
And
I
believe,
that's
probably
all
for
the
announcements
for
this
week,
so
we'll
move
straight
on
to
the
first
discussion
point
which
is,
I
know
miles
mentioned
it
just
down
here.
It's
the
discussion
around
pushing
out
the
maintenance
date
for
node
12
and
also
the
additional
seven
for
minor
that
we're
planning
to
do
so.
If
you
want
to
go
ahead
and
kick
off
discussion
there.
B
Yeah,
I
guess,
like
a
really
quick
one
was
like
we
ended
up
being
a
little
delayed
from
getting
this
12
sem
reminder
out
from
like
availability
in
life
and
then
also
it
got
pushed
by
some
security
releases,
so
we're
technically
kind
of
like
two
releases
behind
what
we
were
hoping
to
do,
and
especially
with
the
shortened
maintenance
period
of
the
shortened
shortened
active
period
of
12.
That's
a
little
less
than
ideal.
In
my
personal
opinion,
so
I
made
this
proposal
which
isn't
terrible.
B
In
my
personal
opinion,
it
only
really
delays
the
maintenance
date
by
a
month,
but
essentially
it
we
would
do
a
the
december
patch
on
the
27th
of
october,
an
assembler
minor
on
the
27th
of
november
and
moved
to
maintenance
on
the
30th,
we're
still
within
14
days
of
the
maintenance
date.
So
we
are,
you
know,
to
the
best
of
my
knowledge
completely
within
policy,
making
a
change
like
this.
B
And
I
guess
one
thing
to
add
here
as
well
is
like
this
will
ensure
that
we
get
the
remaining
modules
changes,
there's
two
more
features
that
didn't
make
it
into
1219
just
because
they
didn't
get
on
to
14
with
enough
time
to
bake,
and
so
you
know
it's
kind
of
important
and
I
think
it
would
be
good
to
get
that
patch
in.
We
could
choose
to
just
do
to
some
verminers,
but
I
know
that
there
are
some
bugs
that
there
are
some
open
pr's
for
that.
B
We
didn't
get
into
this
release,
including,
like
the
http
two
bug
that
had
that
we
just
recently
got
fixed.
I
think,
there's
a
streams,
one
that
I
just
saw
so
like
the
12
19
1
release
doesn't
even
need
to
be
like
to
borrow
shelley's
words
that
chunky,
but
I
think
that
this
would
be
good.
Obviously,
we
also
need
people
to
volunteer
to
do
these
two
releases,
but
maybe
we
could
start
with
just
like.
Does
anyone
have
concerns
with
the
schedule
and
pushing
out
the
maintenance.
C
C
I
would
say:
I'm
I'm
comfortable
with
it.
I
think
that
it's
definitely
important.
We
get
in
the
module
changes
and
I
think
getting
them
in
the
release
that
I
did
on
tuesday
would
have
been
a
little
too
risky.
B
It
would
be
the
27th
of
october
and
the
27th
of
november
would
be
the
two
releases.
I
guess
one
thing
to
talk
about
really
quickly.
Here,
I
guess
is
worth
recapping,
because
I
don't
think
we've
really
dug
into
this
in
a
while,
like
historically,
we've
had
the
lts
releases
and
releasers
and
backboarding
actually
being
kind
of
like
a
separate
thing
from
the
main
releasers.
A
D
B
E
A
E
D
B
C
A
A
That's
the
release
candidate.
They
are
we're,
gonna,
try
and
get
the
race
canada
out
a
bit.
A
A
A
Okay,
so
I
think,
as
I
think
you
mentioned
miles-
it's
possibly
not
the
end
of
the
world.
If
we
can't
find
someone
to
do
the
1219
one.
B
I
guess
like
I
guess
the
the
challenge
here
would
be,
and
maybe
we
just
do
a
12
20
and
we
don't
do
a
12
19
one
and
we
just
pick
a
day
right
now.
If
we
want
to
change
the
lts
date,
we're
supposed
to
give
like
14
days
notice
so
like
next
thursday
would
be
like
the
latest.
We
could
change
that
date,
so
I
think
opening
the
pr
to
change
that
date
now
is
kind
of
kind
of,
like
you
know,
makes
me
feel
a
little
more
comfortable.
A
B
A
Okay,
yeah,
I
think,
definitely
after
this
meeting
that
pr
we're
trying
to
open
and
to
get
that
locked
in
early,
and
that
gives
us
an
extra
month
to
play
with
in
terms
of
timings.
B
A
Call
so
in
terms
of
bringing
12
20
any
earlier.
Is
that
worth
penciling
in
now
or
just
leaving
it
that
date
and
see
how
we
go
over
the
next
week.
B
I
think
it
might
be
like
so,
let's
look
really
quickly
at
the
schedule,
so
you're
gonna,
say
24th
like
I'd
say
like
even
just
scheduling
it
for
the
17th.
B
B
Yeah-
and
I
mean
like
in
theory,
if
the
only
december
miners
that
were
landing-
and
this
is
a
conversation
that
we
could
have
before
we
do
the
release,
but
if
the
only
sember
miners
that
we're
landing
are
these
modules
changes,
like
modules,
is
experimental.
So,
like
I,
I
guess
it's
touching
common
js2,
though
so
yeah
they
could.
These
would
have
to
come
as
some
vermin.
A
Sure,
okay,
I
think
we
can
leave
that
as
it
is
for
now
we'll
open
the
pr
to
extend
by
one
month
and
if
we
do
get
time
to
do
a
release.
In
the
meantime
we
will,
if
not,
we
will
wait
until
then.
I
think
that
seems
reasonable.
A
So
just
hopping
back
to
the
14
release,
it
seems
like
we've
almost
done
our
last
14
release
that
will
have
new
features
in
it.
A
A
A
Yeah,
so
does
anyone
want
to
volunteer
for
that
one
to
do
release
with
just
one
commit.
E
A
E
Well,
we'll
have
a
we'll
have
15
two
weeks
after.
A
A
E
Yeah,
I
think,
if
there's
no,
no
one
has
any
any
reasons
to
change
that
and
I
guess
that's
what
we
go
with.
A
E
It's
mainly
for
the
nipi
updates,
so
this
this
release
will
add
an
api
seven
and
there's
a
commit
that
wasn't
that
ported
before
so,
there's
compatibility
fixed
as
well
okay,
so
it's
mainly
those
there's
one
small
v8
update
and
then
a
couple
of
minor
minor
pictures.
There's
the
update
to
allow
add-ons
to
be
debugged.
So
there's
the
an
entitlement
or
something
in
the
manifest
for
mac.
E
I
think
off
the
top
of
my
head:
that's
everything
currently
in
there.
So
it's
not
a
it's,
not
a
big
release,
but
it's.
E
So
I've
got
the
proposal
up
there,
so
as
long
as
no
one
comes
in
with
any
any
more
requests
or
find
anything
breaking
I'll
try
and
do
a
release
candidate
or
either
the
end
of
this
week
or
early
next
week,
and
I'm
paying
for
that
date
sure
but
yeah.
Hopefully,
hopefully
it's
sort
of
done
very
far
in
the
actual
release.
A
I
guess
another
action
out
of
this
meeting
as
well
as
trying
to
write
the
release
plan
for
14x
going
forwards.
We
probably
need
to
open
a
15x
release
plan
on
that.
Do
people
find
scheduling
one
release
every
two
weeks
works.
E
A
Yeah-
and
I
kind
of
like
the
two
weeks,
because
when
something
does
come
up
urgently,
we
tend
to
just
slot
that
in
as
an
additional
release
anyway,
so
it
kind
of
works
quite
nicely.
As
is
I
don't
I'll
go
with
that
when
I
open
the
issue,
the
release
plan.
A
A
A
E
No,
probably
just
for
awareness
there's
an
issue.
I
can't
remember
where
the
issue
is,
but
it
says
that
the
windows
installers
have
been
flagged
as
unsafe
and
I
think
that's
because
we
recently
changed
the
signing
certificate
because
the
old
one
was
expiring.
So
I
have.
I
have
pings
xiao
and
the
windows
team
to
see.
If
there's
anything
we
can
might
do
to
or
need
to
do,
to
try
and
get
microsoft's
stuff
to
to
not
not
treat
our
installers
as
suspicious.
E
But
I
guess
it's
just
worth
knowing
in
case
there
are
more
complaints.
A
B
E
I
don't
know
if
it's
something
we
need
to
do
or
if
it's
just
one
of
those,
because
we've
changed
the
certificate
it
takes
a
while
for
the
trust
to
build
up,
I'm
not
quite
sure
how
the
scanning
scanning
stuff
decides
to
trust
things
or
not.
E
So
I
think
I
don't
know
that
exactly.
I
think
the
certificate
changed
from
like
the
node.js
foundation
to
the
opengs
foundation.
There
is
a
brand
new
signing
certificate
and
some
things
in
that
have
changed.
So
I
don't
know
if
it's
anything
we've
done
wrong
or
whether
it's
just
the
fact
that
we've
got
a
new
certificate,
because
the
old
one
was
the
due
to.
E
A
E
A
Okay,
anything
else
to
add.
Finally,
before
we
close
out.