►
From YouTube: 2022-02-10 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
B
Well,
we
have
that
release
17.50
coming
out,
probably
in
an
hour
or
so.
B
D
C
A
Oh,
and
I
suppose
we
also
had
some
releases
last
week,
both
a
16
and
a
14.
is
that
correct.
A
Lots
of
releases
for
one
top
grade
two
awesome,
so
I'm
going
to
start
the
agenda
with
the
the
issues
that
are
not
going
through
the
schedules
we'll
leave
schedules
towards
the
end.
So
the
first
one
was
the
imminent
issue
for
time
zone
data.
D
A
D
Think
that's
all
done
now.
Now
that
16
is
out,
so
I
think
we've
we
have
updated
the
lts
lines,
okay,
cool
I'll
check
afterwards,
but
I'm
I'm
pretty
sure
we
can
close
it
off.
There
sounds.
C
D
C
Yeah,
I
guess
what
I
was
going
to
suggest,
although,
like
we
don't
need
to
dig
in
too
much
today,
is
that
that
maybe
it's
worth
putting
some
cycles
into
thinking
about
how
to
automate
this,
and
maybe
that's
what
we
should
track
instead
of
this
kind
of
like
imminent
issue,
that
we
have
open
right
now,
yeah.
A
C
A
That's
good
job,
perfect.
The
next
item
that
was
on
the
agenda
was
the
proposal
to
rename
sichum
team
to
release
automation.
I
know
I
think
miles
you
said.
If
you
don't
want
to
move
forward,
we
should
close
this.
A
D
So
I
have
a
feeling
changelog
maker
and
branch,
if
maybe
build
oh
okay,
I
don't
know
I'd
have
to
check.
It's
definitely
not
got
a
lot
of
people
that
have
been
working
right,
I'm
pretty
sure
they
are
built
and
I'm
I'm
pretty
certain
that
rod
would
rather
like
release
to
come
over
and
considering
itself
mostly,
I
mean.
F
D
I
I
can
publish
new
releases
of
that,
but
I
mean
I
haven't
really
had
much
time
to
look
at
it.
I
know,
and
we
know
that
changelogmaker
is
currently
broken
and
I'd
like
to
find
some
time
to
look
at
it
but
yeah.
It's
kind
of.
D
A
No
yeah,
so
if,
if
there
are
no
objections
to
renaming,
I
suppose
that
could
just
be
an
easy
rename.
A
Suppose
it's
worth
and
never
reach
out
to
the
sitchin,
just
ping
say
any
concerns
with
renaming
at
first
kind
of
wanted
to
hold
up
on
auditing
the
current
sitchin
membership,
because
I
know
there
are
quite
a
few
folks
in
the
city
team
that
maybe
not
been
active
for
a
while
and
would
suddenly
be
giving
them
more
access.
So,
but
I
don't,
I
personally
don't
feel
comfortable
auditing
the
sichum
team,
as
it's
not
a
team,
I'm
actually
in.
A
C
A
Yeah,
it
makes
sense
yeah
I've,
write
down
notes
and
maybe.
C
A
Sounds
good
that
was
easy,
nice
to
close
one
off
a
quick
peek
at
schedules.
Next,
so
we
do
have
a
note
17
planned
for
the
22nd,
which
is
still
like
12
days
away.
So
I
think
that's
pretty
good.
Cadence
brian
is
hoping
to
be
able
to
prepare
that
as
his
first
like
release,
so
I'll
be
pairing
with
him
to
try
and
get
prepared.
It
would
be
signed
by
me.
A
So
that's
the
hope,
and
then,
after
that
I
did
put
another
new
release
a
hold
for
march
and
depending
on
whether
juan
the
timing
lines
up
for
him.
For
that
it's
just
as
they
need
to
do
current
releases.
Holding
a
couple
in
the
schedule
seemed
to
make
sense
for
them
to
be
able
to
be
on
board.
A
We're
pretty
much
planned
for
the
next
three
or
four
weeks.
I
I
don't
think
any
adjustments
needed
there
just
yet.
A
16.,
I
see
we
have
a
february
patch
release
planned.
I
I
guess,
we've
only
just
shipped
out
the
miner,
and
that
was
quite
a
quite
large
release.
So
I
wonder
if
this
could
wait
a
little
bit
longer
than
february.
E
Yeah,
how
long
do
we
usually
wait
between
these
like
active,
lts
ones,.
A
Typically
monthly,
like
tends
to
go
like
patch
patch
minor,
but
if
anything
comes
up
sooner,
you
know
a
couple
of
weeks
or
three
weeks
is
fine.
If
there's
anything,
you
know
imminent
that
we
need
to
ship
okay.
Now
we
can
even
just.
C
Then
the
one
thing
I
would
just
double
check
really
quickly
is
and
bear
with
me,
as
I
am
speaking
slowly
to
delay.
I
think
we're
fine.
Let
me
I'm
trying
to
figure
out
which
npn
is
installed
by
default
for
16.
yeah.
C
Okay,
great
yeah,
so
I
think
we're
fine
from
npm's
perspective.
Yeah,
it's
831.!
There
were
some
issues
related
to
like
npm
notice,
headers
printing,
the
way
that
we
were
expecting,
which
is
necessary
for
some
of
the
new,
like
2fa
stuff,
that
we're
rolling
out,
but
that
was
fixed
in
8.3.0.
A
A
Cool
okay
should
should
I
bump
that,
like
to
early
march,
maybe
yeah,
okay,
I'll
just
do
that.
A
C
No,
we
we
may
want
to
consider
another
minor
before
maintenance
if
there's
any
like
straggling
things
that
we
want
to
get
in.
Unless
we're
saying
that
this
minor
was
the
last
minor
release
of
14.
C
A
Okay,
I
guess
just
keep
an
eye
on
the
back
porch,
we'll
check
again
in
the
next
release,
call
and
if
anything
imminent
comes
up
like
reading
emergent
fix
we're
now
about
it.
So
if
that
is
and
12,
I
wonder
if
it's
possibly
worth
scheduling
a
patch
release
for
march,
just
as
you
know
the
last
opportunity
for
people
to
get
anything
in.
A
Okay,
that
sounds
good
yeah.
It's
really
only
17
and
16.
Taking
up
our
time
right
now,
so
sounds
good.
D
No
do
we
do
we
need
to
push
anyone
for
that
that
one
about
the
license
file,
I
don't
know
how
we
engage
or
who
we
need
to
engage
or
whether
we
just
pick
so
that
I
think
this
was
about
reusing
like
the
schedule,
information
and
the
sort
of
graphic
the
schedule
pick
picture.
A
F
A
Michael
and
mike
might
be
able
to
thumbs
up
or
maybe
ask
brian.
D
A
C
A
Yeah,
but
I
I
can,
I
can
ask
the
fakes.
I
know
that
so
I
can
take
an
action.
C
It
looks
like
michael's
pointing
at
the
foundation's
documentation
there,
though
so,
like
maybe
we
could
just
like
at
brian
or
something
like
that,
then
just
to
like
get
more
explicit
guidance,
yeah.
A
And
I
don't
think,
there's
anything
else
imminent
that
we
need
to
discuss
on
the
call
today
a
lot
of
asynchronous
things
we
can
figure
out.
So
without
end
the
public
sections.
We
did
want
to
reserve
some
time
for
some
private
discussion
and
thanks
for
watching
the
stream,
if
you
have
and
catch
you
all
next
time,.