►
From YouTube: Node.js Release Working Group Meeting - 2020-01-30
Description
A
A
A
So
the
release
has
been
prepared.
I
saw
meiosis
added
a
few
more
commits
to
it
last
night
and
and
I
guess.
The
main
thing
to
call
out
on
this
release
is
that
it's
actually
been
delayed
due
to
the
February
20
2008
releases
that
have
been
announced
and
they
should
be
being
released
around
next
Tuesday,
so
they're
grateful
and
I'm
kind
of
volunteered
to
prepare
those.
So
that's
why
the
1252
release
has
been
delayed.
A
The
bus
give
us
some
more
time
to
review
December
miners
and
last
last
meeting
Rubin
actually
kind
of
broke
down
the
list
of
new
miners
and
to
just
peers,
rather
than
looking
at
all
the
individual
commits.
So
this
is
the
list
of
minor
commits
that
will
be
going
into
the
next
12
release
and
so
CMI
add
trace
exit
option
and
the
wait
list
new
v8
flag
and
the
trace
on
court
flag.
So
they're
all
assume
they're
all
additive
flags.
A
A
A
B
B
A
A
A
A
A
And
the
next
item
on
the
agenda
was
the
defining
word,
all
current
releases,
so
so
reference
this
in
the
PR
I
might
not
run
I
just
go
straight
today,
so
I
had
a
work
in
progress,
PR
and
release
phases.
I
think
we've
had
a
few
issues
raised
over
the
past
year
or
so
saying
it's
not
entirely
clear
what
each
of
the
release
phases
means
in
terms
of
what
will
go
into
them.
So
just
try
to
add
a
short
paragraph
into
I.
A
Read
me
to
say:
current
should
incorporate
most
of
the
non
major
breaking
changes
or
no
major
or
non
breaking
changes,
or
that
Landmaster
active
OTS
can
contain
new
features,
bug
fixes
and
updates
that
have
been
ordered
by
the
OTS
team,
who
have
even
determined
to
be
appropriate
and
stable
for
the
release,
life
and
then
maintenance
was
in
general.
It's
critical
bug,
fixes
and
security
updates
over
me
and
at
the
the
exception,
where
new
features
may
be
added
at
the
discretion
of
the
OTS
team.
I.
A
A
A
Yeah
I
think
it
makes
sense
for
that
team
either
because
the
rest
of
the
steps
so
we've
added
the
steps
for
major
release.
It's
all
ready
to
do
a
release,
it's
empty,
so
adding
this
I
think
make
sense
and
the
LTS
staging
branches,
potentially
so
I,
think
I
think
there
was
another
bit
someone
referenced.
Okay,
we
have
some
information
here
about
once
or
release
moves
into
maintenance.
A
What
I
could
do
is
I
can
I
can
raise
an
issue
on
their
release,
repo
to
move
those
items
out
and
to
release
its
MD
and
maybe
give
it
a
label
of
good
first
issue.
That's
probably
something
for
released
at
some
like
didn't
help
out
with
I
know.
We
had
quite
a
few
people
interested
in
getting
involved
in
the
future,
so
I
might
do
that.
A
A
A
Last
thing
actually
I
mentioned
no
Jess
release
mentoring
such
streaming,
so
I
I
have
added
to
the
schedule
the
no
Jess
calendar,
the
sessions
I
think
it
was
last
Tuesday.
I
did
kick
it
off,
but
I
think
there
was
just
one
attendee,
so
I
think
I'll
try
it
again.
Next
Tuesday,
if
we
don't
have
attendees,
maybe
counselor
and
set
up,
do
the
polls
to
maybe
do
like
ad
hoc
mentoring
rather
than
a
scheduled,
because
it
doesn't
look
like
the
schedule
is
working
just
yet,
but
I
still
trying
progresses.
A
And
one
other
thing
to
mention
over
in
is
it
and
I
call
you
toes.
We
have
the
PR
to
help
landing
help
land
faculty
us
that's
being
worked
on.
So
if
anyone
had
interest
in
that,
please
take
a
look
and
add
your
thoughts.
This
came
from
think
of
one
of
the
last
releases.
I
missed
off
PR
Europe,
because
I
labeled
it
back
port
PR.
You
are
instead,
and
so
this
would
actually
automate
the
landing
of
the
inserting
of
the
back
called
PR
euro
metadata,
it's
being
actively
worked
on
at
the
moment.
A
A
A
A
A
Ten,
so
we
have
a
ten
nineteen
release
free
for
anyone
to
pick
up.
It
got
bumped
from
January
because
of
the
upcoming
security
releases.
This
will
be
the
last
seven
four
minor
of
my
ten
so
giving
ourselves
some
more
time
to
prepare.
It
probably
makes
sense
it's
something
that
I
could
potentially
pick
up.
That
I
would
commit
to
that
until
after
we've
got
the
security
releases
out
and
I
can
see
how
much
time
I've
got.
If
anyone
else
came
voluntarily,
I
will
not
be
great.