►
From YouTube: 2020-09-24 - 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
couple
of
just
highlight
are
the
there
were
some
security
releases
that
went
out
this
month
and
you
should
check
those
out
and
try
and
upgrade
where
possible
and
also
node
15
is
due
to
be
released
on
the
20th
of
october
there's
the
first
release.
Canada
is
available
and
I
will
put
the
link
in
the
minutes
and
I
think
the
first
item
to
discuss
on
the
agenda
will
be
the
node.js
12
release.
B
Yeah,
I
can
talk
about
that
a
little
bit.
Do
we
have
a
link
to
this
in
the.
A
B
Somewhere,
okay,
you
have
it.
It
looks
like
from
what
I
recall
as
I'm.
Bringing
up
the
link
on
my
computer
now
is
that
it
doesn't
look
like
there's
been
anyone
assigned,
and
so
we've
skipped
the
last
one.
B
I
am
not
sure
that
I
have
time
to
do
all
of
the
auditing
myself,
but
I
am
happy
to
take
on
the
actual
release
and
do
some
of
the
auditing
for
sure.
If
that
sounds
potentially
good
to
people,
I
think
that
the
one
thing
we
would
need
to
work
out
because,
obviously,
like
the
schedule's,
all
wonky
now
is
what
date
we'd
like
to
do
that
release.
C
A
My
first
kind
of
thoughts
are
that
the
last
release
before
we
enter
maintenance
I
feel
like
it-
should
be
a
patch
so
that
we
can
put
the
miner
out
and
then,
if
there's
anything,
we
need
to
patch
up.
It
can
go
out
in
a
patch
to
just
rather
than
dropping,
a
load
of
new
features
in
just
before
it
hits
maintenance,
but
I
don't
know
how
that
would
work
with
timings.
A
A
I
think
I
believe
anna
has
landed
some
miners
on
the
12x
staging
branch,
so
the
next
release
will
be
a
minor.
I
think
we've
committed
to
that.
So
I
guess
really
it's
down
to
the
person
who
has
the
time
to
do
the
release
to
assign
dates
that
works
for
them,
if
they're
the
ones
gonna
have
to
do
the
promotion
etc
and
free
up
their
time
to
do
it.
B
Yeah
I
mean
I'm
super
happy
to
sign
myself
for
this
one,
or
at
least
the
next
one
I
can.
I
can
take
on
the
next
minor.
D
B
Oh
sorry,
I
just
I
got
a
ping
for
miles.
I
just
pinged
him
and
asked
him
if
he
could
make
this
meeting.
He
said
he
can't
make
the
meeting,
but
we
do
have
two
apparent
changes
that
we
want
on
12.,
the
one
that
hasn't
landed.
B
A
Okay,
sure,
I
guess
my
if
there
are
already
400
commits
including
miners
on
the
staging
branch,
then
we
should
probably
continue
with
two
miners
going
out
and
try
to
get
the
first
one
out
kind
of
as
soon
as
we
can
yeah
yeah
and
not
wait
for
the
modules
ones
to
land.
B
A
Yeah,
I'm
not
sure
I
guess
for
this
one
it's
whenever
we,
we
probably
won't
enforce
a
like
two
week,
rc
phase,
because
it's
kind
of
important
that
we
get
out
sooner.
I
think
in
this
case,
so
if
we
aim
for
what
they
use.
B
B
A
A
A
I
guess
if
those
modules
changes
do
land
in
time
to
make
it
into
your
release,
shall
we
on
the
6th
of
october?
We
may
not
need
to
do
this.
Second
minor
yeah,
maybe
not.
A
C
For
that,
isn't
it
I
don't
when's
the
next
14
release
queue
because
we
did
one
roy
just
did
one
recently
so.
C
C
A
A
So
I
think
the
best
thing
to
do
for
now
is
we've
got
the
next
miner
we'll
keep
an
eye
on
the
modules
changes.
If
they
do
land
we
can
soonish,
we
can
discuss,
I
don't
know,
maybe
reducing
the
baking
time
slightly
or
maybe
pushing
this
out
by
a
week
to
get
them
in.
So
we
don't
have
to
do
two
minors,
but
we
can.
A
A
C
A
So
I
guess
the
other
thing
is
like
the
current
release,
possibly
doesn't
have
to
happen
on
a
tuesday.
I
know
we
aim
for
tuesdays,
but
we
don't
often
sometimes
we
don't
release
on
a
tuesday
we
release
on
wednesday
or
thursday
just
because
things
happen.
So
we
can
consider
doing
that
once
it's
landed
just
spinning
out
release
to
get
out
as
quick
as
possible.
A
A
Yeah
and
we've
also
got
the
so
maintenance,
isn't
a
hard
restriction.
We've
always
left
some
freedom
within
the
guidelines
to
say
if
the
whole
lts
team
agrees
pulling
this
pr
back
is
important
for
migration
or
for
stability
or
on
across
release
lines.
Then
we
will
do
it,
so
I
think
we
should
be
okay,
we're
getting
these
modules
changes
in.
A
Okay,
I'll
probably
leave
that
one
there
and
the
next
item
to
discuss.
I
think
richard
you
mentioned
a
10
release.
We
don't
have
one
on
the
schedule
because
with
maintenance
we
kind
of
just
do
an
ad
hoc.
I
think
you
mentioned
at
the
moment
there
were
there
wasn't
an
api.
C
A
C
So
there's
a
an
api
pr
that
is
in
14
and
is
and
is
in
12,
but
it's
not
in
10,
and
it
adds
a
build
variable
that
the
add-ons
can
reference
and
they're
binding
files
and
it's
not
their
intent.
So
there's
at
least
one
module
out
there.
That
uses
an
api
that
tries
to
use
this
variable
and
then
because
it's
not
there,
it
fails
to
build
on
note
10..
C
C
A
C
I
don't
know
too
much
about
that
one,
so
there
might
be
a
little
bit
of
content.
I
guess
it's
just
sort
of
balanced
as
to
how
much
content
do
we
consider
enough
for
a
release
versus
you
know
just
putting
it
off
for
a
little
bit
and
just
to
let
them
accumulate.
A
Yeah,
I
kind
of
lean
towards
letting
them
accumulate
a
bit
more,
so
we're
not
doing
a
release
for
like
two
commits,
but
I
think,
maybe
to
try
and
be
a
bit
more
active.
Somehow
we
can
try
and
ask
the
question
to
the
other
collaborators
and
go
through
open
issues
or
something
to
try
and
see
if
there's
anything
else
that
needs
backboarding
and
if,
after
a
couple
of
weeks
or
maybe
a
month,
nothing
else
appears.
Maybe
we
do
just
a
release
with
reopen
commits
that
we
have.
A
C
A
Okay-
and
I
think
that's
all
we
had
on
a
list
to
discuss
for
14,
we
may
do
an
extra
release
next
week
for
12.
shelley's
volunteered
to
do
the
next
minor,
which
already
has
a
lot
of
commitment
to
be
a
big
release
for
10.
We're
gonna,
keep
track
and
try
and
build
up
some
more.
So
we
can
just
do
one
release
with
a
bunch
of
them
and
I
think,
that's
all
so
anything
else.
Anyone
wants
to
use
this
time
for
or
talk
about.
C
C
A
Okay
yeah,
I
might,
I
might
take
a
look
and
we'll
try
and
fix
that.
A
Probably
worth
I'm
just
giving
an
update,
so
15
did
the
first
release
candidate.
It's
got
the
throw
on
unhandled
rejections.
I
was
kind
of
waiting
for
that
to
land
into
the
release.
Before
I
shipped
out
the
first
rfc
and
the
eu
mask
runtime.
Deprecation
warning
is
still
firing
everywhere.
So
I
think
in
the
tsc
meeting
this
this
evening.
For
me
we're
gonna
discuss
reverting
that
to
a
doc
only
deprecation,
because
it
is
quite
widespread.
A
lot
of
modules
are
still
using
the
deprecated
umask
method.
A
A
Yeah,
I
think
one
thing
possibly
we
need
to
do.
I'm
not
sure
if
it's
already
been
done,
something
like
these
there's
the
list
of
expected
assets
for
15..
I
don't
know
if
we
need
to
pr
that
in
or
that
already
exists.
A
A
Yeah
and
for
15,
I
think
each
week
because
we're
past
december
major
cutoff
at
this
point
it's
a
case
of
cherry
picking,
everything
that's
patch
or
miner,
into
the
release
manually
and
then
just
updating
it
each
week
and
then
the
change
log
should
be
finalized
the
week
before.
I
hope
we
don't
have
to
drop
anything
in
in
the
last
week.
So
we
have
time
in
the
last
week
to
get
a
nice
full
change.
Log
written
up.
A
C
Just
for
awareness,
I
am
going
through
some
old
pending
issues
in
sit
gym
and
trying
to
close
some
of
those
off
I've
got
a
pr
visit
gym
to
fix
the
windows.
Sit
gym
runs,
so
I
don't
know
if
anyone's
noticed
for
a
long
time,
windows
has
not
been
posting
test
results
in
the
citrium
job,
so
the
good
news
is.
I've
got
a
patch
that
fixes
that
the
bad
news
is.
We
suddenly
see
failures
that
we
just
hadn't
spotted
before,
because.
A
C
It
was
bailing
out
early,
so
just
for
awareness.
If
anyone
runs
sichuan
after
I've
merged
the
fix
to
sit,
you
in
you
might
start
seeing
failures
or
windows
that
you
we
haven't
seen
before,
because
we
just
situation
was
just
about
in
before
it
wrote
out
the
result.
Files.
A
A
Okay,
thanks
richard
anything
else,
anyone
wants
to
raise
or
mention.
A
Okay;
okay,
if
that's
the
case
and
nicole
and
give
you
all
half
an
hour
back
all
right
sure
thanks.
Everyone.