►
From YouTube: 2022-07-28 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
C
A
Okay,
yeah,
it's
been
a
very,
very
constant
time
for
many
years
now,
so
it's
not
nice
to
keep
it
ordered
this
stop
spot
from
everyone
else
in
the
project
for
long
enough,
so
cool.
So
if
you
like,
have
you
run
other
meetings.
C
A
Cannot
win
everything
I
can
support
you
through
that
and
help
you
get
started
on
that
things,
really
what
it
what
it
should
be.
Is
you
get
granted
the
permission
on
the
google
group,
I
think
and
added
to
an
extra
email
list
on
the
node.js
emails,
because
they
send
two
factor
off
codes
to
our
gmail
or
our
emails,
and
then
it's
really
just
clicking
a
button
to
go
live
once
you've
got
all
the
missions
set
up,
so
it
should
be,
should
be
too
hard.
So
I
can
work
with
you
on
that.
A
I
I
don't
know
yet
I
might
be
able
to
step
in
and
host
some
of
them.
I'm
I'm
not
sure.
I
just
I'm
not
sure
yet.
Moving
on
to
the
next
item
in
the
agenda
is
we
won't
go
through
schedules.
We'll
go
straight
to
periodic
table
does
not
have
an
element
starting
with
jq
or
w.
A
We
talked
about
this
last
meeting.
We
went
through
the
list
of
all
the
suggestions
and
our
last
comment
or
and
discussion
kind
of
the
output
was
the
only
name
that
we
felt
comfortable
with
was
jod.
I
think.
A
A
Yes,
the
only
name
we
all
felt
suitable
was
judd,
and
I
said
at
the
time
in
the
issue,
I
pasted
a
link
to
the
comment.
If
there
were
no
further
suggestions
for
us
to
consider
or
objections
to
the
name
judge,
then
we
would
just
pr
this
into
the
code
names
after
this
meeting.
A
That
just
solves
solves
it
and
stops
bike
shedding
and
things
so
sounds
good.
I
can
peel
that
in
after
the
meeting
and
say
no
objections.
We
left
open
well
like
long
enough.
I
think
that
and
I'm
sure,
if
someone
felt
really
really
strongly,
they
could
open
a
pr
to
edit
it
in
advance
of
the
node
24
or
22
release,
whatever
one
it
will
be,
but
yeah.
C
A
A
So
I'd
like
to
step
back
a
bit
from
doing
some
of
the
major
release
work.
It's
a
lot
of
work,
burnout
inducing
james
did
it
for
a
long
period
of
time.
I
did
it
for
a
long
period
of
time.
I
think
both
of
us
got
to
the
point
where
we
were
pretty
burnt
out
from
it
so,
and
it
is
something
that
requires
more
commitment
than
say
a
regular
release.
A
So
I
was
wondering
about
proposing
a
like
a
major
release
schedule
and
just
so
people
could
put
their
names
to
volunteer
to
do
to
stu
kind
of
steward
or
lead
the
next
major
release
and
releases
after
that.
B
A
True,
on
the
other
hand,
like
in
theory,
but
I've
tried
to
reduce
it
over
time
because
it's
been
kind
of
pointless
like
our
earlier
steps
for
the
major
release
were
like
three
months
in
advance.
You
must
create
the
branches,
but
then
I
was
like
no
one's
using
the
branches
until
like
maybe
a
month
before
the
release.
So
I
shrunk
that
window
down,
I
think.
Still
in
there
we
tried
to
open
the
proposal
six
weeks
in
advance,
so
we
would
need.
B
I
definitely
think
we
need
to
decide
who's
doing
the
release
in
advance
of
the
release.
I
just
don't
know
how
easy
a
rotation
is
going
to
work
like
say
the
next
two,
maybe
two
releases.
B
Because
so
what
we've
got
no
19
and
no
20
and
then.
B
Even
though
20
it's
kind
of
like
you're
planning
for
maybe
next
april,
wouldn't
it.
A
C
And
yeah
like-
and
I
personally
would
not
be
looking
forward
to
it,
but
if,
but
at
the
same
time
like
there's
also
the
good
side
of
things.
If
we
get
more
people
like
up
to
speed
and
doing
the
major
release
the
better,
it
is
better
so
yeah
just
to
consider
that
too
right.
It
might
be
really
overwhelming.
For.
C
A
It
will
almost
certainly
be
overwhelming,
like
it
was
very
overwhelming
for
me
yeah.
I,
like
even
thinking
about
the
time
during
18
release
like
I
can't
think
about
it,
because
I
reminded
how
much
stress
it
was,
but
I
I'm
happy
to
be
like,
like
mental
folks
or
ping
folks
and
help
folks
out
on
the
first
time
and
air
I
would
so
I
I
can
be
around
james-
can
probably
still
help,
I
think,
even
some
of
the
other
members.
A
The
release
group
are
probably
familiar
enough
of
what
was
happening,
that
we
should
all
be
able
to
step
in
and
help,
so
you
won't
just
be
left
on
completely
left
on
your
own
if,
if
you
did
decide
to
pick
it
up,
but
on
the
other
hand
it
is
a
lot
of
work
and
I
was
being
paid
to
do
this
as
part
of
my
day
job
I
I
wouldn't
you
know
I
wouldn't
want
someone
to
sign
up
to
do
it
permanently
to
you
know,
take
that
on
in
their
free
time
forever,
because
that
that
that's
just
I
just
don't
think
that's
you
know
a
reasonable
expectation.
A
A
So
now
for
node
19,
we
open
an
issue
called
node.js19
prep
and
in
there
maybe
we
have
some
blank
spots
for
who
is
doing
the
release,
who's,
helping
with
the
release
and
maybe
just
go
from
there.
We
just
open
the
issue
like
a
quarter
in
advance.
B
Yeah,
that
sounds
good.
I
mean
we
could
perhaps
like
time
box
it.
So
you
know
we
need
to
decide
who's
doing
this
by
such
a
date
or
something
if
there's
some
lead
up
time
to
you
know
we're
saying
we
should
be.
You
know
at
least
six
weeks
before
the
release
date.
We
should
know
who's,
doing
who's
who's
gonna,
be.
B
A
So
I
can
open
that
for
note,
19
and
it'd
be
like
node.js
19
release
prep.
Maybe
that
can
be
our
a
place
where
we
hang
all
of
the
stuff
related
to
release
prep
from
now
on,
because
that
makes
sense
and
in
there
have
really
steward,
I
guess,
we'd
call
it
and
then
maybe
supporters
of
the
release-
and
I
am
happy
to
list
myself
in
19.
It's
like
someone
supporting
release,
but
I
don't
think
I'm
gonna
sign
up
to
it
overall
but
happy
to
list
myself
as
a
supporter
of
the
relief.
B
C
A
Yeah,
we
can
go
through
them
and
now,
okay,
we'll
run
through
them
I'll
share
the
screen
and
we
can
open
the
schedules
up.
But
yeah
are
people
all
okay
with
that
approach
for
19
we're
just
opening
an
issue
this
month.
Well
I'll
open
it
today
and
say:
node.js
19
prep,
and
then
we
can
use
that
to
source
and
release
a
source
and
start
work
and
figure
out
what
needs
to
be
done
and
where
the
gaps
are.
C
A
A
Oh
so
that
went
out,
we
do
have
a
gap
for
the
next
releaser,
so
we'll
just
see
if
anyone
can
fill
that
in
and
pick
that
one
up
to
be
honest,
we
do
18
so
frequently
it's
probably
not
worth
us
desperately.
You
know
doing
a
shout
out
saying
please
please
do
this
release,
but
if
anyone
does
have
time
feel
free
to
sign
up.
A
A
A
What
that
does
mean
is
that
this
semver
miner
is
probably
gonna,
be
the
last
semba
miner
of
note
16
well,
the
last
feature
for
sum
for
miner,
because
after
that
it
goes
into
maintenance
and
we're
a
bit
more
picky
from
there
on.
A
A
A
C
Yeah,
there's
a
core
pack
there's
something.
I'm
also
not
sure
what
this
is
doesn't
tell
if
it's
ready
either
yeah.
B
I've
got
a
feeling
I
put
an
lts
watch
label
on
some
other
pr
that
hadn't
landed
in
18
or
it
may
have
just
gone
out
this
week.
Okay,
but
I
can't
remember
what
that
was.
A
Just
so
people
know
we've
not
abandoned
that
release
line
yet,
but
we'll
probably
do
another
patch
release
at
some
point,
but
that's
when
as
and
when
we
need
it.
So
that's
all
cool
so
really
not
much
to
schedule.
Thank
you,
danielle
and
rafael
for
signing
up
for
some
of
the
18s
that
are
coming
up
all
good.
I've
got.
A
I
think,
two
actions
to
do
after
this
call,
which
is
to
pr
jot
into
the
code
names
as
we
had
no
objections
to
that,
and
it's
been
sitting
there
for
a
month
or
so
and
also
to
open
an
issue
planning
note
19
to
see
if
there's
anyone
who
wants
to
take
the
lead
on
that
and
just
get
get
ourselves
sorted
for
that.
C
A
B
I
don't
have
any
feelings,
I
I
mean
it
will
be
extending
the
left-hand
side
of
the
graph
backwards.
Wouldn't
it
because
the
reason
it's
disappeared
is
our
start
date
on
the
graph
is
beyond
the
end
of
life
date.
B
A
C
B
I
think
it's
always
a
balancing
thing
about
how
much
stuff
is
on
this
graph.
I
do
wonder
whether
we
should
flip
it
so
that
it
goes
like
master
and
then
like
the
current
and
then
the
lts
in
sort
of
descending
order.
But
I
don't
know
it's
sort
of
you.
You
jump
from
the
sort
of
master
branch
to
14,
which
is
the
oldest
yeah.
A
But
a
bit
weird
does
master
even
need
to
be
on
this
graph.
A
C
B
We
we
have
not
at
least
built
from
nine
okay
yeah.
B
A
C
A
A
C
A
B
A
Maybe
we
should
comment
in
there
just
saying
hey:
we
talked
about
this,
we're
not
sure
because
the
way
our
graphs
generated
it
may
make.
What's
the
information,
that's
already
there
more
cluttered
or
hard
to
follow.
B
A
B
A
A
B
A
A
Okay
with
that,
I
think
we
need
to
rapidly
close
up
so
sorry
for
the
shorter
call,
but
we
seem
to
have
got
for
everything
on
the
agenda,
even
if
it
was
very
quickly.
So
thanks
for
joining
everyone,
thanks
for
signing
up
for
the
releases,
doing
the
releases
and
I'll
catch
you
all
soon,.