►
From YouTube: 2022-10-20 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
Okay,
so
we
should
be
live
on
YouTube
now
so
welcome
everyone.
So
the
release
work
group
session.
Let
me
also
make
sure
I
share
the
minutes
again.
So
please
make
sure
you
add
your
name.
Do
it
and
you
can
follow
up
with
the
agenda
there
too.
So
yeah
before
we
start.
Is
there
anything
announcements,
anything
good
anyone
else
to
add
before
we
start
with
the
regular
attempt.
A
A
With
the
first
item
here
we
have
this
prune
system
from
Richard,
not
not
or
Richard
Richard.
So
but
I
I
see
you
commented
on
it
may
Richard
you
wanna,
maybe.
B
Yeah
I'm,
just
for
awareness,
rich
retro
is
I,
was
in
trimming
the
sit
gym
list
of
people
that
have
access
to
right
to
that
repository,
the
releases
or
all
releases
already
have
access
to
that.
So
a
follow-up
question
was
once
you
take
out
the
people
that
he
believes
and
no
longer
active.
The
only
people
left
are
releases.
B
So
then
the
question
was:
should
we
just
get
rid
of
the
septum
team,
I
kind
of
I've
kind
of
always
hoped
we
could
get
people
outside
of
the
releases
team
to
help
maintain
sichum,
but
maybe
the
reality
is
that
it
is
only
the
releases
that
are
doing
that
so
yeah.
We
don't
need
to
make
a
decision
here
right
now.
B
I
just
want
to
sort
of
raise
that
as
a
awareness
to
discussion,
whether
it's
even
feasible
that
people
outside
the
releases
team
are
even
gonna,
try
to
contribute
to
to
sit
gym
or
whether
you
know
we
just
say:
okay,
no
reality
is
it's
only
it's
only.
The
releases
are
actually
looking
off
that
module
I
mean
it
is
used
a
lot
as
part
of
people
Landing.
You
know
large
features
or
potentially
breaking
changes
or
changes
that
people
are
unsure
of.
B
So
Darcy
said
the
npm
team
are
asking
about
access
to
run
sitchum.
So
you
know
that
that
may
be
an
argument
for
keeping
the
system
team
and
maybe
we
add,
like
npm
people
that
are
not
releases
into
that
team
and
give
them
access
to
you
know
to.
B
Take
a
step
back
to
that
issue.
Just
thought
we'd
had
it,
given
that
it's
it's
sort
of
under
our
umbrella.
A
A
Now,
it's
in
a
not
too
great
shape,
and
it
would
be
awesome
if
we
have
like
a
a
sitting
that
is
in
good
shape
and
we
can
trust
someone
when
cutting
the
releases
so
but
I
I
think
one
of
the
points
we
should
highlight
here
like
and
I
think
one
of
the
reasons
bicycling
doesn't
get
a
lot
of
love
is
kind
of,
like
lack
of
you
know,
just
reconnaissance
for
for
the
work
contribute
there
like
it's
even
less.
A
You
know
even
less
visible
than
the
work
that
the
release
working
group
is
already
doing
so.
I,
don't
know
like
how
to
actually
get
people
excited
to
contribute
Basics.
You
know,
like
that's
a
yeah,
that's
a
difficult
like
question.
C
So
we're
looking
at
that
again
as
a
potential
future,
where
we
would
run
to
prior
to
opening
up
the
pr
versus
leveraging
our
relationship
with
nodes
to
be
running
these
tests
and
using
up
compute
on
your
side
and
yeah.
So
that
might
mean
that
folks
from
our
team
could
help
also
support
to
come
long
term.
C
Maybe
and
maybe
use
contributions
back
so
I
noted
Luke
Harris
from
our
team
is,
is
actually
got
a
call
with
Rich,
Strat
I
think
scheduled
next
week
and
I
think
part
of
the
reason
why
he
was
looking
at
the
ownership
or
maybe
the
teams
was
because
we've
been
having
conversations
about
what
it
would
look
like
to
get
our
team
access
to
suit
them
again,
because
we're
trying
to
also
make
sure
that
we're
keeping
that
that
TI
green
with
the
with
the
latest
release
of
npm.
C
So
yeah
I
can
comment
back
in
that
thread
and
also
see
if
we
can
get
some
resources.
You
know
dedicated
from
our
side
to
make
sure
that
this
stays
like
a
valuable
tool
right
thanks.
A
So
it's
plans
for
npm
9.,
okay,
yeah,
and
maybe
there
is
something
new
I
saw
that
there's
just
that's
an
update
and
we
also
me
and
Raphael.
We
just
release
I
mean
most
of
the
Raphael
I
was
helping
out,
but
19
went
out
so
now
I
guess
the
plan
is
getting
more
concrete.
Now,
at
least
like
we
have
our
new
current
person
out,
and
there
was
the
idea
of
lending
the
npm
update
on
it
so
Darcy.
Maybe
you
want
to
speak
a
little
bit
on
the
last
update
from
npm
here.
C
Yeah,
so
we
gave
two
updates
one
about
three
weeks
ago
tried
to
share
a
bit
of
a
plan
and
I
apologize
for
not
getting
involved
earlier
and
now
putting
this
on
the
releasers
radar
earlier
as
well.
I
apologize
for
that
I
guess
to
get
ahead
of
myself
or
the
future
team.
We
will
likely
be
cutting
a
major
version
of
npm
next
year
around
this
time.
So
so
we
can.
C
We
can
have
that
discussion
again
next
year
as
well
about
about
how
we
can
do
this
better
and
and
plan
better
to
collaborate
better.
C
But
right
now,
we'd
love
to
you
know,
try
to
see
what
the
the
widest
group
or
the
widest
LTS
support
we
can
get,
is
and
so
we're
taking
a
very
slow
rollout
and
phase
rollout
approach
to
this
release,
and
we
want
to
make
sure
that
this
version
is
is
non-breaking
for
for
node
and
and
ensure
that
it
can
be
backwards
as
many
LTS
versions
as
possible,
so
we're
letting
it
bake
right
now,
no
mpmv9
is
not
considered
latest.
C
At
this
point,
we
haven't
changed
the
disk
tags
on
the
registry,
so
it's
only
consumable
if
you
specifically
ask
for
v9
and-
and
this
gives
us
a
bit
more
testing
and
another
a
few
few
weeks
of
sort
of
Community
feedback
and
address
any
issues
that
we
see
and
then
we
plan
to
open
up
a
PR
at
that
point.
C
C
So
a
kind
of
decoupling
npms
really
scheduled
from
nodes
there,
but
in
a
way
that
hopefully
reduces
any
kind
of
issues
with
the
community,
the
ecosystem
and
and
hopefully
that
plan
all
makes
sense
to
everybody
and,
and
hopefully
it's
something
that
people
feel
confident
about
like
that
was
the
key
there.
We
want
to
give
lots
of
baking
time
and
yeah,
hopefully
just
you
trust
that
we
care
deeply
about
not
breaking
our
shared
users
set
of
users,
so
yeah
care
deeply
about
that.
C
So
I
have
somebody
on
our
team,
Nils
Nathan,
La
Premiere,
who
sit
on
the
PSC
of
happy
Advisory
Board
and
has
done
a
bunch
of
work
and
know
help
with
NSP
he'll,
probably
be
reaching
out
to
this
group
and
and
wants
to
also
help
within
this
next
couple
months,
even
and
maybe
set
up
a
plan
for
how
we
long
term
can
make
sure
that
majors
in
of
npm
can
land
safely
in
into
node
and
I'm
sure.
Some
folks
on
this
call
have
ideas
on
how
we
can
do
that.
C
Maybe
it's
just
the
checklist
of
exit
criteria.
We
sort
of
made
a
subset
list
of
exit
criteria
that
we
said
we'd
meet
in
that
in
that
post.
That
I
gave
there
as
well
in
that
issue
thread.
So
hopefully
that'll
make
sense
to
the
folks,
and
everybody
feels
comfortable
about
that
plan
and
yeah.
That's
pretty
much
it.
We
would
love
for
you
to
use
mpmv9
today.
C
If,
if
you
can,
if
you
can
upgrade
and
and
let
us
know,
if
you
find
anything
and
then
yeah
our
plan
is
to
open
up
the
PRS
and
and
over
the
next
coming
months
and
come
the
new
year,
we'll
we'll
hopefully
come
with
PR
to
open
and
back
Port
v9
and
to
node
19
and
then
hopefully,
node
18
as
well.
The
the
like
stress
goal
would
be
16,
not
16
if
possible.
That
would
be
amazing.
If
we
could
do
that.
C
I
know,
that's
a
lot
tougher,
probably
to
to
work
about,
but
yeah,
that's.
That
would
also
be
an
amazing
to
eventually
find
or
have
that
confidence
that
we're
not
breaking
a
large
set
of
the
community
by
by
backboarding.
That
version.
C
That's
a
I
think
a
bit
of
synopsis,
I'm
I'm
here
to
answer
any
questions
as
well
or
or
if
folks
have
any
comments
or
feedback
about
that.
Let
me
know.
A
Awesome,
hello,
that's
great
I,
appreciate
the
care
and
this
approach
here,
but
one
comment
on
the
I
believe
16
is
probably
not
worth
it
like.
It's
going
to
be
a
short
leave
version
right.
B
Yeah
six
days
only
until
September
next
year,
because
we
we
both
we
cut
the
life
cycle
short
to
come
inside
the
end
of
so
okay
yeah
may
not
be
worth
it
in
the
long
run.
Yeah
I
don't
know
yeah
on
16
there.
As
on
a
separate
note
that
there
was
an
issue
raised
saying
so
so
we
had
a
16
release
recently,
where
we
bumped
up
to
npm18
9,
something
and
and
we've
had
some
reports,
or
at
least
a
report
saying
that
it's
broken
get
SSH
URLs.
B
Maybe
it's
only
a
subset
of
those.
But
oh,
this
is
the
issue
here.
B
B
B
Cool
yeah
yeah,
it
didn't
look
like
there
was
anything
in
the
CLI
repo
that
again
indicated
whether
this
was
a
a
real
bug
or
some.
You
know
something
that
used
to
work
but
doesn't
work
but
was
never
guaranteed
to
work
or
whatever.
But
you
know,
we've
had
at
least
one
one
person
been
vocal,
there's
no
repo
about
it
and
yeah
it.
B
Just
it
went
out
in
an
LTS
release
and
they're
complaining
about
it
and
without
sort
of
further
advice,
it's
unclear
what
we
should
do
about
it,
like
I,
said
I'd,
probably
like
to
avoid
rolling
back,
because
I
think
it
was
quite
a
jump
from
I
think
we
were
on
8,
15
or
something
before
in
node
16.
So
you
know
it's
quite
a
few
versions
we
jumped
up,
but
anyway,
yeah
just
for
just
for
awareness.
A
B
All
we
want
from
release
is
whether
it's
a
don't
need
to
do
anything,
or
maybe
we
should
roll
back
temporarily
or
there'll
be
a
release
or
it
has
been
fixed
in
a
release,
and
you
know
this
is
the
risk
that
you're
going
to
note
16.
just
the
same
recommendation,
and
then
you
know.
C
So
I'm
it's
morning,
Eastern
time
for
me,
I'll
I'll
try
to
plus
back
with
some
clarity
or
or
exactly
what's
going
on
by
this
afternoon.
So.
A
C
Everybody's
too
kind
you
can
feel
free
to
DM
me
or
ask
questions
after
the
call
as
well
or
just
send
me
your
your
complaints
as
well
I'm
willing
to
listen
and
try
to
do
our
best
to
mitigate
the
post,
so
yeah.
Thank.
A
C
The
backboard
or
or
basically
Landing
v9
in
No
19,
would
open
in
early
December.
We
don't
have
an
expectation
of
when
it
would
land
like
that's
totally
on
you
like
the
plan
here
is
just
like
our
intent
to
open
up
PRS,
and
we
never
have
the
expectation
that
right
this
team
will
pull
them
in,
and
we
want
to
be
mindful
that
we
don't
want
to
ever
Force
this
team's
hand
to
pull
things
in
like
that's.
C
That's
probably
on
you
to
to
accept,
and
then
the
idea
would
be
roughly
six
weeks
later
so
about
a
month
and
a
half
later
after
landing
in
v9
like
open
up
another
another
PR.
The
reason
why
we're
doing
it
so
slowly
and
today's
approach
is
just
truly
to
to
give
folks
as
much
confidence
as
possible
if,
if
we
felt
good
in
early
December,
so
PR
is
to
also
a
land
that
release
and
not
juggle
these
serious
versions
of
npm
into
back
ported
into
node
18.
D
Based
on
you
know,
stability
and
things
in
that
I
I
was
wondering,
would
npm
be
inclined
to
land,
didn't
npm
9
update
earlier
in
node
19,
because
in
my
mind,
getting
it
into
people's
hands
sooner
via
current
and
increasing
the
window
between
when
it's
in
people's
hands
and
current,
and
it
going
back
into
LTS
may
give
some
more
feedback
and,
to
be
honest,
our
general
flow
for
current
is
once
it's
landed
on
the
main
branch.
If
it's
not
tagged
as
some
from
Asia,
it
will
end
up.
D
You
know
it
will
end
up
in
that
release
the
next
time
a
release
goes
out,
so
it
could
be
within
a
week
or
two
weeks,
and
maybe
maybe
that
would
be
better
for
getting
more
feedback
in
advance
about
yes,
but
no
like
if
you
want
to
keep
with
the
very
very
generous
blackboards,
go
for
it
and
if
that
works
for
your
schedules
perfect,
but
I
just
wanted
to
raise
that.
Maybe
it
could
happen
earlier.
C
Yeah
I
mean
we
want
to
give
everybody
as
much
like
confidence
and
and
and
and
time
to
let
this
bake
as
possible,
especially
because
we
truly
want
to
show
that
you
know
there's.
There
should
be
minimal,
breaking
changes
to
the
ecosystem
and
so
like.
If
sitcom
continues
to
pass,
then
we
really
want
to
show
that
like
B9
should
really
be,
it
could
be
considered
sort
of
like
almost
like
a
minor
upgrade.
Although
there
are
breaking
changes
in
it
there,
you
know
it
is,
hopefully
a
minor
update
in
the
endnote
consideration.
C
So
that's
why
we're
being
extra
cautious
here
and
all
also,
you
know
it
sort
of
felt
from
our
side
that
there
were
a
few
other
folks,
maintainers
and
collaborators
that
sort
of
this
Peaks.
The
this
initial
issue-
sort
of
Peak,
some,
some
Spidey,
sensors,
I,
guess
and-
and
we
want
to
you-
know
just
accommodate
folks
as
much
as
possible
here
so
I
I
would
be
okay
with
us.
C
You
know
moving
up
that
time
frame,
but
we've
said
it
now
like
we're
willing
to
stick
to
this,
and-
and
you
know
our
team
is
willing
to
to
sort
of
support
this
time
timeline
the
way
it
is
now
but
I
I
am
totally
understand
that
yeah
once
we
land
in
Maine,
the
expectation
could
be
the
no
updates
sooner
like
that's
that's
out
of
in
my,
in
my
opinion,
that's
out
of
my
team's
hands.
C
If
you,
if
you
folks,
want
to
update
npm
as
a
penalty,
you
can
fully
do
that
today
and
and
Pull
It
in
earlier.
If
you
also
feel
all
feel
confident
about
it,
so.
C
Yeah
I
think
you're
yeah.
That
probably
makes
sense.
We
didn't
really
know.
We
also
don't
have
great
data
about
how
many
people
are
going
to
be
using
it
v9
in
between
now
and
that
time
frame
as
well.
So
definitely
if
we
can
get
them
current
faster
than
that
helps
us,
you
know
obviously
get
more
feedback
and
yeah.
That
would
make
a
lot
of
sense.
C
So
we'd
be
totally
okay
with
it.
You
know
that
December,
roughly
I
think
it's
December
7th
was
the
idea
that
we
potentially
get
node,
B9
or
npm.
V9
backboard
are
into
current,
which
is
fee
19..
So
if
we
can
get
it
a
lot
sooner,
you
know
sometime
in
that
November
time
frame
or
or
maybe
we
may
get
that
that
November
9th
time
frame
that
would
be
great
between
November
9th
and
this
early
December
landing
and
current
would
be
awesome.
C
So
it
gives
us
almost
an
extra
month
of
taking
time
before
we
we
would
open
up
a
back
port
for
18.
D
Foreign,
maybe
maybe
we'll
only
be
able
to
come
to
this
decision-
that's
a
sense
like
a
reasonable
thing
to
do
after
the
PR's
been
opened
and
landed
on
Main
and
run
through
sit
gym
and
things,
and
if
everything
looks
good
there,
then
maybe
that
is
an
option
to
bring
it
forward,
but
we
might
as
well
wait
until
the
PR's
been
open.
We've
run
sit
gym
on
it.
It's
landed
on
Main
before
making
that
call
Maybe.
B
We
haven't
done
that
in
14.,
I'm
about
to
open
a
PR
later
this
afternoon
that
actually
updates
the
time
zone
database
of
note
14
to
the
latest,
one
which
is
2022e.
So
that's
some
versions
beyond
the
one
that
this
issue
was
originally
opened
for,
but
it
has
to
be
a
separate
PR
because
we
use
an
older
version
of
ICU
and
node
14.
So
we
can't
take
the
pr
of
PRS
that
landed
in
Maine
and
18
and
16
future
ICU
version
differences,
but
yeah.
B
My
intent
is
to
open
that
PR
and
then
we'll
have
time
zone,
updating
level
14
and
then
this
this
issue
can
be
closed
off.
B
No,
we
we've
got
a
workflow
now
that
will
update
main
when
new
versions
of
the
time
zone
database
comes
out.
So
hopefully
a
lot
of
it
will
now
be
automated,
and
the
only
issue
we'll
have
then
is
back
porting
to
the
14,
because
it's
just
on
a
different
version
of
ICU
or
maybe
we
would
have
to
back
port
to
18
and
16,
because
even
that
I
think
we're
about
to
move
Maine
to
the
next
version
of
ICU
when
it's
released
so
yeah,
there's
Automation
in
place.
B
A
D
I
think
I
don't
know
if
it's
written
down
anymore,
that
we
restrict
one
minor
per
quarter.
We
should
check
to
see
if
that's
written
down
and
delete
that
line,
but
I
think
we
were
mostly
going
to
put
this
in
action
via
the
schedules
and
just
change
the
schedules
to
be
like
monthly
minus,
just
predicted
for
OTS
just
change
the
numbers.
A
A
A
D
Okay,
yeah
I
think
somewhere.
We
should
just
probably
write
down
some
guidance
to
say
three
months
before
the
release
call
for
a
really
Steward
that
can
start
working
on
the
release
and
I
think
well,
maybe
maybe
five
minutes
before
I
don't
know.
We
just
like
in
advance
of
the
release,
figure
out
someone
who's
going
to
do
the
release.
That's
that's
about
all.
We
need
to
do
on
this,
so
I,
don't.
B
The
for
the
meetings-
and
hopefully
it
will
pop
up
in
a
meeting
with
enough
time
that
we
say.
Oh,
we
need
to
do
this
now.
I.
A
Yeah,
let's
give
it
a
try,
maybe
open
that
you
should
put
in
the
label
let's
see,
but
if
not
yeah,
it
would
be
nice
to
kind
of,
like
oh
I,
made
that
anyways
yeah,
so
yeah,
but
I
would
definitely
I
would
much
recommend
pairing
on
it.
I
would
have
been
a
very
bad
spot
if
I
was
trying
to
do
that
alone.
So
it
was
great
to
just
like
be
there
with
profile
like
ended
up
leading
most
of
the
release
so
but
I
kind
of
like
followed
up
with
all
the
steps.
D
A
Sorry
so
similar
to
the
19
release
me
and
Raphael
were
been
preparing
to
bear
on
it,
so
we
can
yeah
me
and
Rafael.
We
can
probably
think
after
the
this
meeting
here,
but
I
was
kind
of
hoping
to
maybe
open
the
pr
kinda
take
more
to
lead
on
this
one,
but
we
can
think
after
the
meeting.
B
E
B
So
yeah
you
yeah,
you
have
to
add
things
like
the
code
name
the
LTS
bit,
and
then
there
were
some
tables
in
the
change
logs
that
need
to
be
moved
around
and
then
re-headed
yeah
I
mean
yeah.
B
You
could
actually
build
request
today,
yeah
we
we
have
that
Target
date
for
next.
Is
it
next
Tuesday
yeah
next
Tuesday
yeah?
So
you
could
open?
You
could
open
the
pr
now,
because
it's
not
it's
unlikely
to
change
between
now
and
that
date,
because
the
only
thing
that's
being
updated
is
the
metadata.
There
should
be
no
other
functional
changes
going
in.
E
A
E
Oh
actually,
I
have
a
question
on
on
that
issue.
Is
that
we
mostly
finished
all
the
the
release
plan
when
18
is
correct,
but
now
looks
like
we
need
to
create
a
new
issue
for
18
LTS
right.
D
It's
I
think
what
I've
done
in
the
past
is
like
hidden
the
current
100
details,
twisty
and
then
created
a
new
table
above.
If
you
look
at
the
note,
16
one
you
can
probably
copy
from
that,
but
yeah.
E
D
D
A
A
B
So
I
mean
we
are
doing
occasional
relations,
but
there's
not
much
to
go
out
in
a
fortune.
Race
without
Daniel
is
preparing
one
so
that
one
is
still
in
preparation.
That's
kind
of
like
why
I
wanted
to
open
the
times
NPR
and
see
if
we
can
get
it
into
that
and.
E
Then
I
think
we
will
have
I,
don't
know
anytime
soon.
New
Secrets
release
and
probably
the
the
14
will
be
affected
too
right
right.
B
B
D
A
E
A
E
D
A
E
E
D
D
D
A
E
A
A
C
A
Awesome
yeah
so
before
we
leave
here,
I
yeah
I
was
a
terrible
host
and
I
forgot
to
announce
in
the
beginning
of
the
session
that
nine
things
out.
So
thank
you.
Thank
you
very
much
Rafael
for
leading
that
one,
and
that
also
happens
actually
yeah.
So
it's
great
so
I
wanted
to
make
sure
I
highlight
that
before
the
meeting
is
over
yeah
great,
so
yeah
thanks
everyone
for
who
showed
up
and
yeah
see
you
next
time.