►
From YouTube: 2022-04-14 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
So
we
are
live
with
the
node.js
release
working
group
meeting
of
april
14th
2022..
We
work
through
the
agenda,
which
is
in
the
node.js
release
repository
and
it's
issue
735,
but
I
guess,
starting
with
any
announcements,
I
guess
one
announcement
to
make
would
be
the
node.js
18
should
be
released
next
week.
We
have
some
rc
builds
hope
to
spin
a
new
one
today,
but
yeah
all
is
lined
up
to
do
the
1800
release
next
tuesday.
A
Okay,
I
assume
not
so
moving
on
to
the
agenda
as
we
typically
do.
I
start
going
through
the
discussion
points
and
then
maybe
review
the
release
schedules
afterwards.
Just
so
we
don't
keep
popping
back
and
forth,
and
so
the
first
item
on
the
agenda
is
a
process
for
unintentional
breaking
changes.
A
I
think
the
exact
pr
that
triggered
this
has
now
been
fixed
and
the
docs
have
been
updated
to
reflect.
What
was
the
unintentional
change,
which
is
good,
but
I
guess
the
question
for
this
call
is:
is
there
any
update
on
that
or
any
actions
we
need
to
take.
B
I
don't
think
there's
any
update.
One
thing
that
I've
kind
of
put
on
my
to-do
list
is
having
like
just
some.
B
A
B
A
Agreed
so
I
guess,
like
I'm
kind
of
in
the
same
state,
it's
like
it's
always
been
something
on
a
list.
I
assume
once
we
once
we
have
like
a
guide,
probably
in
the
node.js
release
repo.
We
can
just
extend
it
because
I
think
there's
a
few
other
issues
that
we'd
like
to
capture
in
there
like
what
to
do
when
we've
shipped
a
broken
release.
Some
other
bits
for
this
call
as
there's
no
update.
A
I
part
of
me
feels
like
let's
untag
it
from
the
agenda
and
just
put
a
comment
in
there
saying
you
know.
The
aim
is
to
create
a
dot
containing
some
of
this
information,
but
that'll
happen
when
we
all
have
time
to
make
it
happen.
Yeah
exactly
that
sounds
good.
Okay,
cool.
A
And
oh
and
then
following
one,
was
what
I
added,
which
is
what
to
do
when
I
release
its
broken
guide,
and
I
think
that
would
just
be
a
section
in
the
same
dock.
So
what
to
do
when
there's
an
unintentional
breakage,
what
to
do
when
an
actual
release
is
broken
and
we
need
to
respin
it.
So,
possibly
no
extra
discussion
required
on
that
one,
and
I
will
also
take
that
one
off.
A
Proposal
to
rename
the
sitching
team
to
release
automation.
Actually,
I
think
we
had
an
action
on
this
one
and
maybe
it
just
got
lost
because
we
didn't
pull
the
notes
in.
I
think
the
plan
was
just
grant.
A
So
it
may
just
be
us
needing
to
go
back
check
check
what
the
access
rights
are
on
those
and
the
publishing
rights
and
figuring
out.
I
think
the
exact
ask
to
rename
it
isn't
probably
going
to
happen.
C
I
saw
brian
open
some
pr's
to
to
fix
the
labeling
problem
with
changelog
maker,
which
is
great,
so
it
would
be
good
to
actually
have
access
so
that
we
could
actually
merge
that.
You
know
review
and
merge
that
yeah.
A
I'll
leave
the
release
agenda
item
on
this
one
until
I've
written
that
comment
and
if
that
comment
suffices
I'll,
remove
it,
and
I
don't
want
to
forget
and
keeping
the
label
on
that
will
remind
me
work
out
a
policy
around
reverse
lts
branches.
Again,
I
think
this
is
part
of
the
same
thing.
So
once
we
have
a
starting
guide,
I
can
see
us
having
sections
on
what
to
do
with
unintentional
breakages,
what
to
do
when
a
release
is
broken
and
then
also
another
section
which
is
a
policy
around
revert.
A
A
Assume
not
it
probably
be
easier
for
us
to
figure
out,
as
we
are
writing
this
document.
So
I'm
gonna
pull
open
the
schedules
now
and
we
can
take
a
look
at
those.
A
Okay,
so
starting
with
the
release
plan,
which
is
what
you
should
see
right
now,
we
have
node
12
node
12,
going
end
of
life
at
the
end
of
this
month,
so
fingers
crossed
no
more
releases.
C
A
Sense,
cool
s
where'd,
the
fourteen
one
go.
A
We
still
have
a
couple
of
weeks
left
of
this
month,
so
it
is
still
possible.
We
might
do
a
patch
release
if
we
get
a
volunteer
for
that
one.
Would
anyone
like
to
volunteer
here
today
not
to
put
anyone
on
the
spot.
A
No,
so
I'll
just
update
that
when
we
get
volunteer,
we
get
volunteer,
I'm
assuming
there's
nothing
too
major.
That's
driving
us
to
do
a
release,
so
it's
probably
okay.
If
it
just
gets,
pushed
back
slightly.
A
Oh
awesome,
yeah
no
feel
free
to
choose
whatever
date
works
for
you
for
14,
because
it's
in
maintenance.
It's
just
a
case
of
like
cherry
picking
the
things
labeled
lts
watch,
14
and
checking
for
any
open
back
ports.
So
in
theory
there
should
only
be
like
20
30
commits
max
and
that
kind
of
ballpark,
so,
okay,
okay,
I'll
put
you
down,
feel
free
to
fiddle
with
the
dates
it's
whenever
you
get
ready
and
if
you
need
any
help
and
getting
through
that
process-
and
let
me
know
thank.
D
A
Thank
you
for
volunteering,
16.
danielle.
I
seen
you
been
working
on
this.
Would
you
like
to
just
share
the
update.
B
I'm
still
working
on
it.
I
I
think
I
had
posted
that
I
was
gonna,
try
to
get
it
out
today,
so
someone
opened
a
back
porch
for
that
big
asm
pr
that
was
kind
of
like
had
a
bunch
of
stuff
dependent
on
it.
So
I'm
gonna
wait
for
that
to
go
through,
so
I
don't
have
an
eta.
I
I
mean,
I
guess
like
tuesday
or
before
is
probably.
A
B
Good,
that's
what
I
could
say
about
that,
but
yeah.
A
That's
no
worries
I
think,
like
tuesday
or
even
later
next
week
would
be.
You
know
completely
reasonable,
considering
they're
like
holidays
and
things
so
yeah
yeah
so
pushing
after
the
holidays,
big
plus
one.
For
me,
one
note
on
those
two
pr's
I
don't
know:
if
there's
more
people,
we
need
to
act
in
them
because
I
think,
like
suddenly
putting
https
imports
and
unflagging
json
modules
in
node
16
seems
quite
significant.
So
we
I
I'm
trying
to
think
maybe
it's
worth
pointing
people
to
those
yards
to
yeah.
B
Yeah,
I
think
that
one
had,
let
me
see
for
some
reason,
the
link
from
the
initial
pr
isn't
showing
up
in
the
in
the
back
port,
which
I
thought
was
weird.
But
let's
see
here
it
is
yeah
originally
antoinette
tagged,
a
bunch
of
people,
but
now
I
don't
see
them
so
maybe
I'll
just
or
like
added
requested
reviews
from
them
pretty
much
everyone
that
was
an
author
and
or
contributor
to
the
other
pr.
B
B
A
Sounds
good
but
yeah
thanks
for
all
the
work
on
release
and
be
good
to
get
that
one
yeah
so
note
17!
Now
we
don't
actually
have
any
more
releases
planned.
So
I
think
michael's
also
said:
there's
nothing
in
the
strategic
branch.
So
I
suggest
we
close
this.
Are
there
any
objections
to
closing
this.
A
Cool
all
right
click
the
button,
and
I
also
made
a
note,
18
release
plan.
I
see
michael's
associates
volunteered
for
the
next
one.
I've
kept
the
same
like
two
week
cadence.
We
can
also
always
do
additional
releases
if
needed,
often
with
the
1800
release,
we
sometimes
have
to
do
an
1801
shortly
after
so
at
least
there's
room
to
do
that
a
couple
of
weeks
ago,
business
as
usual,
there
feel
free
to
volunteer
for
any
of
those,
probably
not
much
more
needed
to
be
said
on
that.
One.
A
And
I
think
that's
everything
that
was
on
the
agenda
today
got
through
in
20
minutes.
I
guess
one
thing
that
should
possibly
be
mentioned
is
that
we
have
a
repository
where
we're
crafting
the
node
18
release
announcement
and
there's
been
some
great
contributions
from
various
folks
across
the
project
and
just
fyi.
If
you'd
like
to
review
I'll,
make
sure
that
you
have
access
to
the
repository.
A
Any
other
updates
discussion
needed
today.
E
So,
with
the
fixes
to
branch
diff
that
richard
was
mentioning
earlier,
if
folks
could
have
a
look
and
actually
give
that
a
go,
there's
there's
not
really
tests
in
branch
diff.
I
did
test
it
locally.
It
didn't
seem
to
work
for
me,
but
yeah.
If
folks
could
have
a
look
at
that,
that'd
be
great.