►
From YouTube: 2023-07-27 - 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
Think
we
are
live.
Okay,
awesome!
Thank
you
so
yeah
welcome.
Everyone
today
is
the
27th
July
23,
and
this
is
the
node.js
release
working
group
meeting
and
we're
here
to
follow
a
small
agenda.
But
before
we
start
anyone
has
any
announcement
they'd
like
to
share.
A
Oh
just
one
thing
is
not
in
the
meeting
so
we'll
mentioned
here:
I
I
have
a
request
for
the
node
for
uchus.
I
have
recently
released
one
to
fix
a
git
node
security
release.
So
you
know
when
you
you
create
a
proposal
for
secret
release.
You
should
be
able
to
do
that
and
this
request.
The
second
pull
request.
I
will
send
in
the
chat.
If
it
opens
it's
not
opening.
So
I
will
start
in
the
release.
A
Basically,
we'll
add
a
new
security,
a
new
release
comment.
This
will
create
the
the
next
secret
release
issue,
plus
getting
all
the
hacker
one
reports
treated
and
putting
the
in
the
readme.
So
it
will
automate
a
few
things
for
secret
releases.
B
B
C
C
B
Can
go
and
start
with
the
regular
agenda
here.
I
know.
The
first
item
here
is
a
session
of
the
collaborator
Summit,
which
yeah
I
guess
we
can
maybe
start
the
question
with
the
who
who's
planning
to
be
there,
because
personally,
I
am
not
going
to
be
there
this
time,
so
I,
don't
think
I'll
be
planning
to
kind
of
you
know
run
that
session
as
I
did
the
last
couple
of
times.
B
So
if
anyone
is
there
and
want
to
do
that,
but
if
also
if
you,
if
you
just
feel
like
not
comfortable,
it's
also
fine
to
just
skip
I
guess
but
yeah
Raphael.
A
I
think
you
might
be
there
right.
I
will
be
there,
but
the
problem
is
that
I
will
speak
at
the
open
ssf,
which
is
in
the
same
day
as
the
node.js
collab
Summit.
So
if
my
talk
is
not
in
the
same
time
of
the
release
session,
I
can
join
otherwise,
but.
C
B
B
It's
just
meant
to
say
like
it's
fine,
if
we
decide
to
just
not
have
one
session
this
time,
like
I,
don't
think
it's
a
it's
good
to
raise
overall
right,
like
just
talk
to
other
collaborators,
about
the
group
and
try
to
motivate
more
people
to
kind
of
participate
and
try
to
become
a
releaser
I.
Think
that's
always
like
the
the
mango
for
collaborous
Summit,
but
I.
B
A
A
You
wanna,
maybe
yeah
it's
just
just
because
I've
mentioned
I,
think
in
the
release
private
channel.
That
might
be
good
to
take
a
look
on
that.
Considering
that
we
haven't
selected
the
new
major
releaser,
we
received
the
notification
on
the
slack
six
six
months
prior
to
the
release
itself,
but
no
one
volunteered
and
I'm
afraid
that
I
I
I
lose
some
hair
to
do
the
next
one
so
and
anyway,
I
think
would
be
great.
A
Considering
that
L
20
will
be
LTS
soon,
I
think
we
have
already
a
name
for
for
20
right.
E
Yeah
I
think
we've
got
the
names
up
to
charge
right,
there's
two
yeah
at
least
the
next
two
releases,
maybe
three
okay,
but
in
terms
of
the
code
names
the
last
time
we
basically
as
a
group,
decided
we'll
just
PR,
we'll
just
PR
what
looks
like
the
most
likely
suggestions-
and
you
know
rather
than
if
we
just
keep
discussing
it
in
the
issue.
It
will
never
get
closed
out
because
yeah.
A
E
It's
like
a
there's
like
a
code
names
I,
don't
know
so.
We've
got
22
beside
it.
E
A
E
22
is
planned
to
be
Judd.
That
was,
we
had
a
whole
discussion
in
in
that
issue
about
what
to
do
with
G8.
A
E
A
Would
be
only
for
2025,
then.
E
B
E
We
we
normally
try
to
make
sure
that
we
have
a
name
for
the
release
for
the
long
term
release
before
we
actually
released
the
current
version.
The
Dot,
zero
version
of
that,
because
I
think
some
of
the
marketing
material
does
sort
of
say
this
is
version,
let's
say
22,
for
example,
and
it
will
be
LTS
in
October
with
the,
and
it
will
have
the
code
name
whatever
when
it
becomes
long-term
support.
So
we
try
and
have
that
all
decided
before.
A
E
It
assuming
we
haven't
change
the
formatting
so
greatly
on
the
change
log
that
it
can't
find
the
things
to
update,
but
yeah
I
mean
it
should
be
more
or
less
automated.
E
We
also
have
that
policy
that
the
LTS
transition
doesn't
actually
contain
changes,
so
it
is
literally
a
flip
of
a
the
the
flag
in
the
version
header
so
that
the
automation
should
take
care
of
that
and
reformatting
the
changelogs
to
add
a
new
column
for
the
LTS
release.
So
in
theory
that
OTS
transition
release
shouldn't
be
a
lot
of
work,
but.
B
B
A
I
mean
if
no
one
takes
it,
I'll
take
it,
but
I
I
mean
at
least
if
we
have
more
releasers,
we
can
pair
I
can
pair
with
either
or
leases
or
other
new
releaser
So.
Eventually,
2022
can
be
a
different
one,
but
yeah
anyway,
I.
E
A
Wrote
not
anything
we
have
I
did
the
pair
with
Hui.
E
A
By
the
way,
I
have
opened
an
issue
when
performing
the
no,
no
just
20
release
about
highlight
notable
changes
in
a
TSC
meeting
I
sent
in
the
chat.
I,
don't
know
exactly
what
action
should
we
take
for
it?
Actually,
there
is
the
release
agenda
label,
but
it
was
not
tracked
because
I
think
the
air
is
NOT
capitalized
right.
E
That
sounds
like
an
obvious
bug.
If
it's
true
yeah,
we
yeah
that's
interesting
that
it's
not
loaded
onto
the
agenda.
Okay,
yeah,
if
it's
a
capitalization,
maybe
we
should
just
need
to
change
the
label
in
the
TSC
repo
to
not
the
correct,
correct.
A
Yeah
we
need
to
do
that
because
there
is
another
other.
There
is
another
issue:
how
to
handle
experimental
status
when
adoption
is
significant.
I
remember
that
issue,
but
I
don't
remember.
We
have
discussed
it.
E
A
So
what
do
you
guys
think
about
this
issue
itself
or
like
I,
should
be
highlighted
in
at
the
same
meeting
or
let
run
it
in
the
same
way
we
do
regularly.
The
only
problem
is
we
work,
we
as
a
releaser.
We
normally
think
that
that
change
log
is
is
good,
but
when
we
open
the
progress
run,
all.ci
everything
is
green.
A
Someone
suggests
to
change
or
to
include
to
remove
so
I
thought
that,
in
case
of
major
release
would
be
great
to
have
a
prior
definition
before
the
meeting
or
maybe
follow
the
alphabet
or
as
any
kind
of
starting.
C
I
think
one
thing
would
be
to
like
the
second
The
Proposal
was
opened,
have
it
on
the
TSC
agenda,
just
to
you
know,
trigger
feedback
like
and
if
it's
mentioned
every
single
time
in
a
TSC
meeting,
you
catch
your
chance
a
bit
earlier
if
getting
the
feedback
rather
than
at
the
last
minute.
I
feel
like
step
one
for
that.
That
could
be
a
reasonable
thing
to
do.
E
Yeah
and
it
might
try
and
encourage
people
to
yeah
like
actual
release,
notes
or
highlight
things
that
need
release
notes
earlier
than
my
recollection
has
been
the
change
look
through.
You
know
not
not
necessarily
throughout
you
know
any
full
of
the
release
team,
but
but
there's
always
last
minute,
editing,
wordsmithing
rewriting
and
it's
it's
it's
maybe
trying
to
get
earlier.
Visibility
might
well
hopefully
make
that
a
bit
easier
and
less.
E
C
Think
there
is
a
bit
of
strictness
on
the
releases
part
like
I
think
in
a
few
times
like
the
day
before,
someone's
asked
something
to
go
in
and
if
it's
not
simva
major
I
think
our
response
has
been
nope.
It
can
go
into
like
20.1
like
in,
like
maybe
just
raising
the
bar.
If
something
can
land,
even
even
a
tiny
typo
fix
like
it's,
not
the
end
of
the
world,
if
the
builds
are
done
and
they're
ready
to
go,
we
can
just
say:
look
we'll
land
it
the
second.
C
You
know
and
bundle
it
into
the
next
following
release.
It's
not
you
know.
Maybe
we
can
try
and
raise
the
bar
for
What
lands
in
the
day
before
and
push
things
along
to
the
0.1
release,
but
I
think
we
got
bad
like
Raphael
got
you
got.
You
got
stung
with
some
unfortunate
timing,
this
time
that
maybe
hopefully,
wouldn't
repeat
as
bad
this
time,
because
some
big
PR's
got
only
got
finished
at
the
last
minute.
A
Okay,
so
I
think
we
can
move
forward.
I
will
I
recommend
in
that
issue
mentioning
that,
instead
of
do
a
tier
submitting
specifically
for
that,
we
will
just
include
the
TSC
label,
so
it
will
be
mentioned
in
the
in
the
meetings.
So
as
a
reminder,
I
don't
know
prior
one
one
more
for
once
the
the
change
log
is
is
done
or
we
have
a
draft
or
something
and
remove
the
label.
E
A
C
E
You
know
in
the
TSC
meetings,
I
I,
believe
you
know,
someone
from
the
group.
The
police
group
will
be
there
to
to
to
highlight
anything.
That's
you
know
significant.
That
needs
to
be
called
out
or
then
people
might
you
know,
take
a
look
and
ask
questions
about
The
Proposal
as
is
and,
and
it
might
feed
into
other.
You
know
areas
that
have
been
taught
the
TSC
meetings.
So,
for
example,
if
if
we're
waiting
like
a
V8
update
or
something.
B
B
E
A
Yeah
Beth
have
sent
the
document.
I
was
in
the
chat.
I
was
reading
it
a
few
minutes
ago,
but
basically,
once
all
the
the
release
thing
approved
the
new
releaser
we
when
anime
or
should
be
sent
to
the
TSC
and
if
the
TSC
approves,
then
we
can
proceed.
So
no
someone
will
will
Mentor
you
in
your
first
course
first
and
the
second
release.
A
And
after
that,
basically
you
create
a
proposal,
but
the
releaser
will
sign
and
then
your
keys
will
be
added
to
the
server
and
then
it
will
be
the
releaser.
Does
that
require
correct.
C
Yeah
pretty
much,
the
only
thing
is
with
the
pairing
I
think
like
how
many
releases
you
pair
on
it's
really
just
dependent
on.
You
know
how
comfortable
you
get
in.
D
E
But
yeah
I
think
a
lot
of
the
valley
was
in
some
of
the
parent
sessions
where
something
didn't
merge
cleanly
or
you
know
the
automation
didn't
quite,
do
it
automatically,
and
then
you
had
the
discussions
about
right.
D
Yeah,
that's
okay,
any
recommendation,
also
in
like
operative
system
or
something
to
use
as
a
base
for
releases
or
anything
works
like
in
terms
of
tooling
and
so
on.
I.
E
I
I
I
I
have
no
reason
to
believe
it
wouldn't
work.
I,
just
I'm,
not
confident
that
it
would
without
I
I,
do
know
that
some
people
on
the
release
team
run
Linux
and
some
people
run
Windows,
certainly
Mac
OS
and
as
far
as
I
know,
where
it
hasn't
been.
E
A
complete
blocker
I
think
there
might
be
one
or
two
things
on
Mac
OS
that
are
not
really
specific,
so
I
think,
for
example,
if
you're
running
tests,
I
think
in
the
past
what
Mac
was
firewall
has
been
an
issue
and
there
are
things
somewhere
that
describe
how
to
deal
with
that,
but
other
than
that
it
should
be
possible
and.
D
A
Mention
Bravo,
no,
no
I,
just
I
just
said
that
I
think
we
have
discussed
that
everything
that
is
not
in
the
the
calendar
already
right.
B
A
Can
already
send
the
email
I
think
it's
pretty
much
the
same
as
when
someone
nominates
a
new
TSC
member
like
they
sent
the
email
and
once
we
get
enough
plus
one
I
think
we
can
move
forward
and
eventually
that
will
be
mentioned
in
the
TSC
meeting
a
private
session
and
then
I
need
to
go
public
and
I.
Think
is.
Is
this
process
right.
B
B
D
B
B
We
have
enough
people
here
so
that
it
should
be
good
to
say
we
all
approve,
but
we
can
also
send
a
message
in
the
chat
just
for
from
our
lady
right
and
also
giving
people
a
chance
to.
If
anyone
wants
to
say
something,
we
can
send
a
message
in
the
private
Channel
and
like
go
forward
from
that
yeah.
But.
B
C
B
Cool,
so
moving
on
I
had
I
added
another
topic
here
that
I
talking
about
the
upcoming
major
release.
I
feel
that
we
need
to
look
into
is
the
updating
the
release,
schedule,
image,
you're,
writing
in
the
repo
I
know.
The
entire
world
refers
to
that
image
when
they
want
to
talk
about
node
releases,
so.
E
Oh,
the
the
the
sort
of
bar
chop,
thingy
yeah,.
B
E
A
C
C
I
I
remember
at
pring
it
in
just
need
to
find
it
might
be
in
Doc
or
something
and
guides,
or
something
awesome.
E
But
it's
it's
a
module
in
the
node.js
or
that
you,
you
run,
you
pass
it
the
release
Json.
So
as
long
as
the
dates
in
the
Json
file
are
correct
and
then
you
give
it
a
start
and
end
date,
so
you
we
usually
allow
a
little
bit
a
bit
of
time
by
the
way.
E
E
Nodes
module
that
you
know
is
in
the
organization
that
you
run
and
it's
a
case
of
just
tweaking
the
parameters.
It's
basically
a
start
and
end
date
and
the
release
Json.
And
then
it
will
automatically
draw
the
the
chart
based
on
the
information
from
the
release
and
the
starting
end
dates.
But.
C
On
that
note,
you've
got
to
be
very
particular
with
the
start
and
end
dates
to
get
the
intervals
rendered
correctly,
because
if
you
give
it
certain
start
and
end
dates,
all
of
the
like
month
just
overlap
in
the
SVG.
So
it
can
be
a
bit
finicky.
You
have
to
just
like
keep
trying
adding
a
date
as
if
the
Windows
start
aligning
better
so
be
warned.
It's
not
like
it
looks
easy,
but
like
sometimes
you
have
to
fiddle
with
it
a
bit
to
get
it.
Looking.
C
B
E
E
D
B
B
A
Yeah
sure
we
just
need
to
get
back
the
the
the
TSC
answer,
but
I
think
it.
It
would
be
on
time
yeah.
B
B
Yeah
so
it
looks
like
there
is
a
available
spots,
end
of
August.
If
anyone
wants
to
volunteer
for
current.
D
B
C
B
C
E
E
Something
like
that
yeah
just
for
awareness.
There
was
a
question
that
there's
a
an
issue
about
one
of
the
ICU
locales
that
was
updated
in
icu73.2,
so
someone
just
asked
about
when
that
would
be
going
into
node
18.
It
probably
should
be
probably
should
automatically
show
up
in
the
automation
because
it
did
go
out
in
notes
when
the
last
note
20
release.
So
by
the
time
you
start
preparing
the
next
18,
it
should
have
been
out
in
current
at
least
two
weeks.
E
So,
just
just
remember,
when
someone
was
asking
when
that
ICU
update
is
okay,
Beth.
C
A
A
E
Have
this
it
might
be.
A
E
I
think
the
confusion
was
there's
like
two
or
three
competing
vrs
that
were
opened.
I
think
this
was
the
one
they
settled
on,
because
I
think
it
was
a.
There
was
an
original
PR
to
like
revert
a
different
commit,
and
then
they
said
you
should
back
up
this
one.
Instead
right
there
may
be.
There
may
be
another
issue
open
about
some
other
issue
to
do
the
something
that
requires
a
later
Ada
version.
So.
B
B
A
Well:
okay,
it
is
Faith
fixing
just
yarn,
install
and
URL
Parts.
Okay,
that
seems
visible,
yeah.
C
C
B
Yeah
I
might
try
to
expeditate
a
little
bit,
so
maybe
what
I
can
do
like,
maybe
somewhere
in
the
middle
I,
can
maybe
see
if
I
can
do
the
release
mid
almost
rather
than
end
of
August,
so
maybe
like
around
the
15
or
something
yeah.
But
one
thing
I
was
going
to
bring
up
here.
Is
there
is
no
one
assigned
for
the
upcoming
18
releases,
so
that's
also
a
different
subject,
but
also
kind
of
ties
up
in
which,
like
we
don't
have
a
lot
of
people
right
now
available
for
the
LTS
releases.
B
B
B
A
I
think
we'll
it's
better
to
do
it
in
a
regular
release
in
the
next
month,
like
in
the
next
two
weeks,
I
guess
more
or
less
and
for
for
the
next
month.
18.19
we'll
have
another
release
session
and
I
I
believe
that
Marco
will
join
the
next
one
to
to
as
a
participant,
eventually
trying
to
to
be
a
releaser
and
yeah.
We
can
get
some
help.
I
guess.
D
E
Right,
you
can
put
monitor
for
16
release.
I
think
there
might
be
enough
to
do
a
release
sometime
in
August.
I
need
at
some
point
to
have
a
look
and
see
what's
what's
been
labeled
but
I
I
have
an
intention
to
do
a16
release
before
it
goes
into
play.
E
So
yeah
I
can
put
my
name
down
in
there
later
or
you
can
do
it
now
either
way,
but
yeah
that
will
probably
be
August,
and
then
that
will
give
us
time
just
in
case.
We
need
to
correct
anything
for
September,
but
I'm
not
planning
to
do
something
in
September
unless
it's
not
really
desperate
So.
The
plan
is
try
and
do
your
sort
of
wrap
up
final
node
16
release
in
August
yeah.
E
E
Can
you
remember,
did
we
discuss
npm's
plan
for
npm
10
in
a
previous
meeting?
Oh.
A
Think
we
didn't
have
the
last
meeting
because
because
I
don't
I
don't
remember
or.
E
I
don't
have
a
particular
concern
other
than
the
same
things
that
came
up
the
last
time
they
tried
to
put
a
a
you
know:
do
December
major
npm
upgrade
in
the
LTS
note
line
and
out
that
we
had
a
whole
bunch
of
additional
checks
that
were
going
to
be
run
and
Brian
have
more
communication
as
the
breaking
changes,
I
think
Roy.
You
did
mention
one
or
two
things
that
might
be
problematic
for
landing
in
node
18.,
so
I
guess
maybe
for
now.
E
E
C
E
To
but
yeah
I
I
guess
we
should
make
sure
that's
the
agenda.
I!
Guess
then,
just
over
aware
of
it
and
track
it
through
it's
going
to
be
a
non-issue
for
like
node
21,
but
we're
going
into
the
LTS
releases
or
even
no
20,
which
is
going
to
be
LTS.
E
We
need
to
be
aware
of
it.
You
know,
guide
the
npm
team
to
try
and
have
minimal
breakage.
As
far
as
we
can
ascertain
at.
E
B
No
yeah,
I
think
I
think
the
device
plan
for
that
came
out
of
the
the
whole
discussion
for
npm9,
like
is
okay,
but
I,
would
still
prefer
to
see,
like
the
the
in
people
releases,
more
aligned
with
that
or
release
schedule
right.
So
it's
kind
of
just
easier
to
plan,
but
even
then
there
is
still
the
issue
of
updating
on
LTS
right,
but
but
at
least
we
have
a
plan
for
that
now
at
least
there's
an
API
agreed
upon
and
it
should
not
break
and
they're
running
it.