►
From YouTube: 2021-02-11 - Node.js Release Working Group Meeting
Description
A
A
A
A
Nope,
I
guess
I've
just
had:
we've
had
a
few
releases
recently
in
node,
10
and
node
12
and
then
node
14
and
all
of
them
just
bundling
up
a
few
fixes
and
updates
so
check
those
out
and
moving
on
to
the
agenda.
The
main
item
on
the
agenda
is
to
run
through
our
schedules,
so
I'll
just
open
them
all
up
and
we'll
go
through
them.
One
by
one
so
for
15
looks
like
we're
scheduled
all
the
way
up
until
the
end
of
march.
So
we're
good
for
currents
and
that's
note
15.
A
A
B
A
B
A
C
A
A
It's
good,
and
I
believe
that
was
everything
that
was
on
the
agenda
to
go
through.
I
I
I
was
just
gonna
skim
to
our
pull
requests.
I
did
add
an
off-boarding
guidance.
It's
it's
an
issue
that
I
spotted
on
our
backlog
for
a
while,
and
I
thought
it
just
for
you
to
give
a
quick
pr,
just
the
actions
we
should
take
when
someone
no
longer
wishes
to
create
releases,
and
we
should
probably
off-board
them
from
the
release
team.
A
So
I
just
opened
a
very
draft
pr.
It's
it's
kind
of
the
opposite.
Most
of
it
is
kind
of
the
opposite
of
the
onboarding,
so
like
remove
from
x
team,
remove
from
move
your
key
that
kind
of
stuff,
the
one
bit
in
particular,
was
as
a
guideline
of
boarding
should
be
considered
if
a
releaser
is
not
prepared
or
released
in
the
past
18
months.
That
was
one
that
I
was
conscious
of
kind
of
writing
down,
because
I
don't
think
we
want
to
like
tell
people
you
must.
A
B
A
Yeah,
I
just
thought
that
was
generous
enough
to
yeah
and
I
didn't
say
like
you
would
be
automatically
off-boarded
like
as
a
guideline.
Maybe
that's
the
point
when,
like
we
are
school
or
as
a
personal
kind
of
thought,
like
oh
I've
not
had
time
to
prepare
one
in
the
last
18
months
or
so
perhaps
it's
time
for
me
to
step
down.
So
that
was
the
kind
of
angle
I
was
trying
to
approach
it
from.
A
Okay,
I'll
leave
that
open
for
more
consideration.
I
think
the
rest
of
it.
There
may
be
some
missing
steps
that
I've
skipped
here.
So
please
do
check
those,
but
we
can
push
that
and
maybe
review
in
the
next
meeting
in
terms
of
open
issues,
we
have
nominating
danielle
for
the
lts
team,
so
be
great
to
have
you
on
board
to
prepare
release
lts
releases.
A
And
oh
one
other
one
that
may
be
worth
mentioning.
There's
a
project
called
re
recall
that
kind
of
creates
like
a
release,
ledger
that
contains
like
the
url,
the
sha
and
the
public
key
that
was
used
to
sign
a
release
and
it's
kind
of
used
to
like
create
a
trust
like
a
trust
chain.
You
can
also
verify
against
they're
wondering
if
the
release
team
or
the
node.js
project
were
interested
in
like
supporting
one
of
these
by
and
by
supporting,
I
mean
more
endorsing
so
they've
actually
prototyped.
A
All
the
work
to
put
one
together,
so
they've
pulled
out
like
the
url
of
our
releases
to
shard
a
public
key
and
like
kind
of
produced,
a
ledger
that
people
could
verify
against
so
they're
willing
to
do
the
work
to
to
do
that,
but
they're
just
curious.
If
there
was
any
interest
in
us
endorsing
it
or
any
concerns,
and
at
the
moment
I
believe
they've
just
prototyped
it
on
their
own
servers,
but
it's
something
they
could
potentially
put
publicly
that
people
could
verify
against.
A
A
C
A
A
C
A
C
A
A
A
So
yeah
some
of
the
things
they
went
on
to
say
like
once,
you've
got
the
ledger
there
and-
and
you
can
also
start
like
alerting
kind
of
things,
so
that
if
an
old
key
that
we'd
marked
as
like
no
longer
used
suddenly
got
used
to
sign
a
release,
and
that
was
added
to
the
ledger.
We
would
we
would
be
able
to
get
an
alert,
so
there
may
be
some
benefits
to
it,
but
yeah.