►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220816
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220816
A
This
meeting
is
being
recorded,
hi
everyone
happy
tuesday
welcome
to
our
kubernetes
1.25
release
meeting.
Today
we
are
at
week
13
tuesday,
16th
of
august
and
as
euro,
this
meeting
is
under
saying
they
have
code
of
conduct
which
could
be
brought
down
to
please
be
nice
and
respectful
to
each
other.
I
have
added
the
meeting
notes
into
the
chat
box,
so
please
feel
free
to
register
your
attendees.
If
you
happen
to
do
so,
and
let's
first
take
a
look
at
the
open
discussion,
we
don't
have
any
topics
today.
A
B
Yeah,
so
we
are
green,
there
are
no
new
updates
from
enhancements
yep.
A
Thank
you
so
much
any
questions
for
enhancements.
A
Now,
let's
go
to
ci
signal,
I
just
saw
ci
signal,
gave
a
gold
signal
to
today's
rc
card,
so
the
stackers
should
be
green.
Anyone
from
ci
signal
plan
to
give
an
update
now,
if
no
I'll,
just
quickly
share,
seems
like
the
status
is
same
as
yesterday
with
there
is
no
failure
in
master
and
the
master
informing
filler
is
still
remain
non-blocking
so
which
will
not
block
today's
sd
card
and,
let's
move
to
bug
triage.
A
B
Hi,
so
our
status
is
still
yellow
because
we
have
seven
open,
pr's
and
a
couple
of
them.
They
didn't
reply
to
me
if
this
is
like
a
nice
blocker
or
not.
So
until
I
get,
I
had
the
feedback
from
them.
I
I
would
keep
the
current
status
as
yellow
as
yellow
other
than
that
no
blockers,
nothing,
nothing
else
to
be
to
be
reported.
Everything
looks
good
right,
so.
A
Far,
thank
you
so
much.
I
guess,
like
the
only
one
which
kind
of
worried
me
is
the
one
e3
tester
failure
for
the
csi
volume
thing
yeah.
I
guess
people
are
still
investigating
if
it
is
release
blocker
or
not,
and
working
on
the
fix
so
yeah.
Thank
you
so
much.
Hopefully
we
will
get
a
update
shortly.
A
C
Hi
hi,
so
our
current
status
is
red
and
kind
of
going
to
the
updates.
We'll
explain
why,
but
today
is
the
doc's
ready
deadline
right
now,
we're
still
tracking
40
docks.
A
good
amount
came
in
yesterday,
so
we
have
24
merged
and
now
14
are
left
ready
for
review
one
with
no
pr.
I
actually
need
to
move
this
is
here,
but
we'll
be,
I
think,
ray
will
be
opening
up
a
pr
on
their
behalf
and
then
a
one
that
doesn't
have
any
docs
required.
C
I
see
someone
just
answered
in
the
document.
A
question
that
came
up
was
that
who
can
approve
a
pr
any
from
the
right
sake
or
if
it
needs
to
be
someone
listed
in
the
the
capital
that
existed?
So
I
think
we
have
our
answer
there,
but
yeah.
That's
our
update.
D
Do
want
to
make
a
note
of
that
anyone
could
anyone
who's
has
a
kubernetes
org
membership
which
is
anyone's
release
team
could
actually
apply,
apply
an
lgtm
and
folks
on
that
sick,
docks
and
owners
section
can
do
the
approve.
It's
often
times
it's
hard
to
get
that
second
review,
so
supply
or
giving
an
lgtm.
Once
you
once
you've
reviewed.
It
helps
out
quite
a
bit
so.
C
Actually,
another
follow-up
question
that
came
up
was,
I
think,
the
the
the
bot
kind
of
will
specify
a
specific
person
that
they're
looking
to
get
an
approval
from.
I
think
that
came
up
in
our
in
our
discussion
separately
is
that
just
kind
of
a
a
not
required
can
be
ignored.
Kind
of
thing
like.
D
Only
because
it
kind
of
it
uses
either
folks
who
are
in
that
same
list
as
well,
but
most
of
the
time
folks
will
just
pay
attention
when
they're,
when
it's
their
time
to
wrangle,
pr's,
and
I
think
brad
topple's
on
that
pr
wrangler
for
the
week.
But
I've
been
doing
some
reviews
here
and
there
as
well
and
also
like.
Sometimes
they
would
actually
say
there
are
on
some
docs
web
pages.
D
There's
actual
like
on
the
header,
which
you
don't
see,
but
you
have
to
go
in
in
the
markdown
it'll
say
like
who
who
are
the
reviewers
for
that
page,
and
it
might
be
a
sig
network
expert,
something
like
that
for
for
a
special
for
a
very
specific
page.
A
D
Cool,
oh,
how
are
the
api
generation
or
reference
generation
docs
going.
C
Sorry,
I
think
the
plan
I
spoke
to
kristin
about
this
just
before
this.
I
think
we're
planning
on
setting
all
that
up
on
thursday
she's
been
swamped,
but
I
don't
want
to
set
up
a
meeting
to
kind
of
go
through
the
whole
group.
D
C
D
Sounds
good
just
to
warn
you.
We've
had
a
long
history
of
issues
with
with
with
those
creating
those
generation
docs.
So
some
folks
from
sick
docs
have
have
helped
out
so
once
those
pr's
are
up
I'll
tag.
Those
specific
bugs.
A
B
A
Thank
you
for
putting
so
many
effort
on
the
major
themes
section
and
in
questions
for
release
notes
before
we
move
forward.
B
If
not
yeah
so
sure,
so
it's
pretty
much
identical
to
yesterday.
We're
still
green
today
is
the
ready
for
review
deadline
and
we
are
reaching
out
for
all
the
vlog
owners
to
to
be
sure
that
everything
is
smooth.
There
are
a
couple
of
stragglers
here
and
there,
but
everything
under
control-
and
we
are
requesting-
suggest
suggestions
for
user,
highlight
section
of
the
release.
Blog.
A
Thank
you
so
much
yeah,
I
do
say,
like
a
lot
of
folks,
are
reviewing
in
the
release
blog.
That
is
awesome.
Please
feel
free
to
review
it.
If
any
of
you
are
interested.
Thank
you
any
questions
for
comms
team
before
we
move
forward.
A
If
no,
let's
move
to
release
branch
management
anime
from
release
branch
management.
Here
today
I
didn't
see
anyone,
but
I
saw
like
the
work
is
in
progress
and
the
standards
is
being
updated
in
the
slack
channel
for
anime.
If
you're
interested
I'm
watching
the
progress
as
of
now
it
seems
all
green
but
we'll
see
and
we'll
look
forward
to
the
rc1
card.
The
announcement
will
be
sent
out
after
the
card
is
ready.
Yeah.
D
Folks,
yeah,
I
did
see
the
rc
one
is
currently
being
cut
and
that
I
just
cc
is
going
to
touch
on
today's
milestones.
So
I'll
wait
for
that.
There's
gonna
be
another
release
retro,
so
we
are
still
on
track
for
august
to
cut
on
20
on
august
23,
which
is
a
week
from
today,
and
then
we'll
have
a
release
retro
one
or
two
shortly
after
that,
and
also
I'll
send
some
additional
surveys
out
for
some
post
release.
D
Surveys
as
well
to
all
parties
to
all
to
shadows
and
role
leads
as
well,
so
just
to
get
some
feedback
as
we're
always
trying
to
improve
the
process
improve
with
the
releasing
process
as
well.
So
all
right
just
look
out
for
that,
and
that's
it
for
me.
A
I
just
want
to
add
one
thing
for,
like
the
second
part
of
the
retro
we
currently
scheduled
a
week
after
our
release
week,
so
which
would
be
like
the
week
after
next
week
and
yeah,
the
detailed
date
hasn't
been
decided.
I
guess
we
will
work
on
that
or
like
we
could
work
on
that
together,
yeah,
so,
please
feel
free
to
add
any
topics
if
you
have
anything
want
to
mention
in
the
current
release
or
regarding
with
the
release
process-
and
I
do
want
to
mention
today
is
a
big
day.
A
We
have
a
lot
of
milestones
happening
this
day
today,
like
we
have
the
major
sim
complete
and
thanks
for
the
release,
notes
team,
the
pr
is
merging
and
we
have
the
dogs
compilation
deadline.
I
think
it's
all
on
track,
except
the
one
mentioned
earlier,
and
thanks
ray
for
jumping
out
to
help
and
our
future
blogs
ready
to
review
deadline
also
today,
but
I
do
see
some
of
the
feature:
blogs
are
not
ready
yet,
but
things
they
like.
A
We
already
assigned
the
public
kitchen
date
for
each
of
them,
so
it
should
not
blocking
anything
even
if
they
cannot
make
it.
That
should
be
fine
and
the
rc1
card
is
going
smoothly.
As
of
now,
we
do
have
another
deadline
for
release
no
steam
on
the
thursday.
The
day
after
two
days
after
the
rc1
card
for
the
release
notes
completion
thanks
for
releasing
those
team
again
for
on
doing
that,
and
also
I,
as
I
mentioned
earlier,
I
do
want
to
share
released
him
like
in
each
of
the
meetings.
A
Just
in
case
someone
didn't
join
like
every
day's
meeting,
so
I
will
release
them
as
of
now
set
to
combiner,
as
most
of
you
hopefully
already
know.
So,
in
this
release,
we
wish
to
honor
the
collaborative
open
spirit
that
takes
us
from
isolated
developers.
Writing
writers
and
users
spread
around
the
globe
into
the
combined
force
capable
of
changing
the
world.
Hopefully,
and
thank
you
for
like
everyone's
hard
work
into
the
release,
and
hopefully
we
will
have
a
smooth
release
next
tuesday,
a
week
after
any
questions
before
I
move
forward.
A
Thank
you.
If
no
on,
we
didn't
visions,
don't
have
the
update
from
c
scalability
today,
and
they
generally
will
provide
update
on
wednesday
or
like
every
two
weeks
on
monthly
basis,
so
it
should
be
fine.
I
guess-
and
I
will
not
check
the
project
board
today
since
we
didn't
use
it
much.
That's
all
the
updates
today
any
questions
before
I
end
the
recording.