►
From YouTube: Kubernetes Release Team Meeting (v1.25) for 20220808
Description
Kubernetes Release Team Meeting (v1.25) for 20220808
A
This
meeting
is
being
recorded,
hi
everyone
good
morning,
good
afternoon,
good
evening.
Welcome
to
the
kubernetes
1.25
release
meeting.
We
are
currently
at
week,
12.,
it's
monday,
8th
august,
and
this
meeting
is
under
the
censor
code
of
conduct,
which
could
be
boiled
down
to
just
please
be
nice
and
respectful
to
each
other.
A
B
A
B
A
B
I
didn't
have
a
chance
to
update
the
spreadsheet.
I
don't
really
think
that
there's
any
updates
since
last
friday,
I'll
fill
in
the
agenda,
though.
B
A
A
Okay
cool,
thank
you
so
much
for
the
update
and
I'll
talk
briefly
on
my
husband
exception
later,
but
we
do
receive
like
an
extreme
exception
last
thursday,
friday
and
it's
been
approved
and
merged
yeah.
So
far
we
are
good
any
questions
for
enhancements
team.
A
If
no,
let's
go
to
the
ci
signal,
is
admin
from
ci
signal
team
here
can
give
us
an
update
if
no,
I
just
quickly
checked
the
master
blocking,
since
we
don't
have
any
failure.
We
do
have
a
flaky
regarding
this
sig
storage
and
the
issue
has
been
created,
but
it
seems
like
back
to
grain
now,
so
we
don't
have
any
blocking
issuing
the
master
blocking
and
master
informing.
A
We
have
faders
it's
also
in
sig
storage
area
and
I
believe
the
ci
signal
team
members
reach
out
to
the
owners
of
this
and
in
questions
for
ci
signal.
A
Is
no
before
we
move
I'll
mark
it
as
yellow,
since
we
have
like
the
failures
in
the
room
and,
let's
move
to
bug
triage,
anyone
from
bug
triage
could
give
us
an
update.
C
C
C
yeah,
I
think,
will
be
that's
all
about.
We
are
in
the
green
status
carmen.
A
D
Yeah,
I
just
want
to
highlight
that
we
have
a
docs
ready
to
review
deadline
by
tomorrow,
so
all
the
so
the
12
doc
prs
they're
in
drafts.
I
think
it'll
be
good
just
to
offer
the
dogs
and
just
check
on
them,
see
if
they're
ready
to
be
reviewed,
if
they're
not
just
to
remind
the
authors
that
to
get
them
at
a
state,
that's
ready
for
review
by
an
update
tomorrow.
E
Hey
good
morning
left
and
we're
beginning,
our
current
status
is
green
and
we
are
going
to
process
nodes
for
the
new
tag
beta0
this
week.
Also,
we
are
going
to
start
the
final
draft
for
release
notes
and
we
are,
we
will
add,
the
major
team
section
that
we
collected
this
week
across
the
different
six.
E
A
Cool.
Thank
you.
So
much
I'll
definitely
take
a
look
after
this
maybe,
and
any
questions
for
release
notes
tim.
F
Hi,
I
am
here
good
morning,
so
I've
reached
out
last
week
to
the
cncf
about
scheduling
the
live,
webinar
and
the
press
interviews.
They
need
a
couple
things
from
me
for
the
the
pr.
A
lot
of
this
is
around.
You
know,
figuring
out
when
people
are
available,
but
that
is
rolling
and
we
are
this
week
finalizing
the
release,
blog
order
and
informing
owners
of
the
release,
dates
at
which
point
I'll
get
with
sig,
doc's
blog,
hopefully
late
this
week
to
make
sure
everybody
stays
on
top
of
things.
F
I
do
have
a
question
around
the
pr
like
the
the
press
interview
for
cece.
There
is
no
documentation
within
the
comms
team
for
what
is
expected
of
the
release
lead
for
this,
and
I
think
that
there
probably
should
be
so
ray
if
you
have
time
to
talk
to
me
later
about
like
what's
involved
in
this
I'm
reaching
out
to
mickey
and
karen
too
so
that
we
can
document
this
and
make
sure
that
cc
is
not
going
in
blind.
D
Good
points
I
actually
chatted
with
cc
earlier,
so
I'll
just
copy
and
paste
most
of
it
over
to
you.
Thank
you.
A
Yeah
river's
kind
enough
to
give
provided
some
information
on
that
and
yeah.
I
think
that
will
be
good
if
we
documented
it
somewhere
for
the
future.
F
A
Cool
any
questions
for
comms
team
before
we
moving
forward.
No,
let's
move
to
release
branch
management.
If
veronica
is
here
or
anyone
from
the
branch
management
team.
G
A
D
Hey
folks,
thank
you
for
those
who
filled
out
the
shadow
surveys,
so
I
close
the
forms
out
for
them.
I'm
gonna
I'm
willing
to
anonymize
that
and
send
a
summary
to
the
seek
release
leads
and
all
if
there's
any
like
concerning
topics.
Don't
think
there
are
comments.
I
don't
think
there
were
anything
I
I
normally.
I
would
put
them
in
the
retro,
but
I
don't
think
there.
There
is
any
and
that's
once
again
think
of
succession
for
126.
D
I've
kind
of
did
a
round
of
pings
this
morning
to
roll
aids.
On
that
another
note
I
will
be
out
on
vacation
at
the
end
of
the
week
so
thursday
friday
I'll
be
out
technically
wednesday,
I'm
actually
on
vacation,
but
I'm
still
just
prepping
stuff.
So
thursday
friday,
I
will
not
have
internet
access,
so
I'm
gonna
be
out
in
big
sur.
D
So
definitely
no
internet
access
there,
so
just
fill
just
feel
free
to
ping
me
those
days
anyway
and
I'll
come
back
and
next
week
up
and
I'll
reply
to
those
messages.
So
and
that's
I
think,
that's
it
for
me
once
again,
we're
kind
of
in
the
last
few
weeks
of
the
release
it
just
kind
of
just
lots
of
things
happen
last
few
weeks
it
released
so
and
things
happen
in
a
marine,
so
just
feel
free
to
reach
out
to
me
and
film
any
questions
once
again
and
yeah.
A
If
no
I'll
just
give
a
brief
update
on
this
week's
highlights,
and
we
so
far
we
have
received
11
exceptions
and
it's
a
huge
number,
but
it's
kind
of
expected,
since
we
moved
the
enhancement
by
two
weeks
and
we
are
already
one
week
shorter,
so
which
for
some
of
the
cap
owners
might
lead
up
to
like
three
weeks
shorter
of
implementation
time.
So
it's
kind
of
expected
and
we
have
approved
six
of
them
and
all
of
them
have
been
tracked
now
all
the
related
kkprs
have
been
merged
last
week.
A
So
it's
been
going
great
and
we
are
going
to
have
the
test
phase
tomorrow
at
8,
00
pm,
pd
tea
time
and
also
the
docs
deadline
for
pr
ready
for
reviewer
is
also
tomorrow,
and
if
I
also
look
forward
to
rc
the
record
tomorrow,
yeah,
that's
basically
the
major
highlights
for
this
week.
Any
questions.
A
No,
I
think
we
all
like
keep
the
previous
updates
from
six
scalability,
which
is
green,
and
I
don't
believe
we
will
have
anything
in
the
project
board,
but
it's
worth
checking
cool.
So
any
other
questions
or
comments
before
I
go
ahead
and
end
the
recording.