►
From YouTube: Kubernetes Release Team Meeting (v1.25) for 20220815
Description
Kubernetes Release Team Meeting (v1.25) for 20220815
A
A
Hope
everybody
enjoyed
the
release
progress
so
far
and
as
you
wrote,
this
meeting
is
under
the
CCF
code
of
conduct
so
which
could
be
summarized
to
please
just
be
nice
and
respectful
to
each
other
and
I
have
pasted
the
meeting
notes
into
the
chat
room.
So
please
feel
free
to
register
your
attendees
there
and
let's
go
to
the
open
discussion
since,
like
we
don't
have
any
open
discussion
opening
today
and
we'll
directly
go
to
the
team
updates
first
enhancements
Priyanka.
If
you
are
here
or
anyone
from
the
enhancement
team.
B
A
Cool
thank
you
so
much
for
showing
here
and
give
us
the
update
any
questions
for
enhancement
here.
A
Anyone
from
CI
signal
or
Arch,
if
you're
here,
if
no
thanks
I
saw
Leo,
is
typing
and
I
also
checked
the
yeah.
The
the.
B
Report
I'm
just
looking
at
the
test
scores
currently
there's
no
blocking
or
no
failing
on
Master
blocking
and
one
failing
on
mess
informing
so
yeah.
A
That
feeling
your
master,
the
Informer,
is
also
confirmed
as
non-blocker
for
the
release
and
which
will
be
fixed
later,
so
our
Market
has
green.
Thank
you
for
update.
Anyone
have
questions
for
CI
signal.
C
C
First
of
all,
I
wanted
to
thank
my
team
for
covering
my
my
absence
due
to
vacation,
so
thank
you
so
much
for
all
the
shadows
in
bacteria.
Next,
the
current
status
is
yellow,
and
this
is
because
we
have
a
couple
of
PRS
for
this
failing
and
I'd
like
to
discuss.
You
know
like
there
is
no
plucking
issues.
Label
on
these
br's
so
far,
but
I
started
to
reach
out
to
the
sake
leads
to
ask.
C
If,
if
this
will
consider
as
plugging
issue
or
not
and
while
I'm
discussing
this
this
morning
with
legit,
he
mentioned
that
there
is
no.
You
know
like
no,
nothing
nothing.
You
know
like
confirmed
that
the
blocking
issue
will
be
only
the
you
know
like
the
pr
the
issue
with
the
label
plucking.
So
this
is
a
little
bit
confusing
for
me
because
you
know
like
this
is
what
I
was
you
know
like
supposed
to
looking
for.
C
Otherwise,
I
will
just
remove
the
the
issue
and
the
pr
from
the
Milestone
I'm,
not
considering
the
Milestone.
As
you
know
like
this
is
a
plucking
issue.
We
need
to
have
this
in
in
the
Milestone.
So
can
we
have
this
agreement
or
you
know
like?
Can
we
update
what?
What
is
the
process
for?
You
know,
like
you
know,
like
Define,
define
the
pr
or
the
issue
as
a
plug-in
issue
or
the
clocking
the
release
yeah.
A
I
think
like
currently
I
pre
reviewed,
like
the
opening
issue
at
the
PRS,
seems
like
a
lot
of
drama
is
not
even
not
targeting
in
this
release
and
which
marked
the
current
Milestone
I
guess
those
are
safe
to
be
removed
and
for
the
blocking
issue.
I
guess
yeah,
as
you
said.
A
Sometimes
it's
not
maybe
it's
not
Marketing
in
the
current
Milestone
but
I'm
sure
like
any
major
release,
blocker
issue
or
will
be
discussed
over
slack
as
well,
so
that
might
be
worth
looking
and
also
I
think
currently
like,
especially
when,
after
a
pass
the
code
phrase
like
if
we
want
to
have
a
fix
into
the
PK
report
for
blocking
issue,
it
has
to
tag
it
as
the
current
milestone.
A
C
You
yeah
thank
you
so
much
other
than
that
no
blockers,
I
will
I
will
keep
tracking
the
the
issues
and
PRS
making
sure
to
communicate
with
the
leads
and
the
author
more
frequently,
but
I'd
love.
If
we
can
have,
you
know
like
just
you
know,
like
you
know,
like
a
common
agreement
between
between
all
of
us.
If
you
know
like,
we
need
to
highlight
it
as
a
clocker
issue,
or
just
you
know
like
reach
out
to
leads
that.
Thank
you.
Yeah.
A
A
C
A
D
Yes,
you
did
hi
everyone,
so
our
current
status
is
red.
That's
because
we
have
about
27
kids
that
have
still
not
been
merged
out
of
the
40
recording
tracking,
but
the
the
sixth
dog
team
and
the
release
team
are
also
actively
reviewing
this
PR.
So
hopefully,
before
the
end
of
the
week,
we
should
have
better
number.
D
As
you
can
see,
we
have
one
PR
that
we've
still
not
so
I
won't
keep
them
so
not
receive
the
pr
for
so
the
docs
lead
has
reached
out
to
this
person
via
the
GitHub
issue
and
also
via
slack
as
well
or
not
received
any
feedback
from
the
present.
So
we
are
still
hoping
that
we
get
that,
but
I
don't
know
what
the
best
route
would
be.
This
remove
it
from
the
release
or
something
I'm,
not
sure
yet,
but
yeah.
That's
that's!
Obviously!
Half
for
now.
A
Thank
you
and
I
also
saw
like
regardless
this
cap.
They
also
have
this
cap
raised
the
placeholder
PR
for
future
blog
as
well.
So
maybe
it's
worth
mentioning
in
the
future.
Blog
PR
iced
their
attentions
there
because,
like
I
believe
as
long
as
they
go
to
the
Future,
like
blog
ready,
it
should
be
super
easy
for
them
to
add
the
formal
documentation
into
kubernetes
documentation,
website
yeah.
D
A
B
Yeah
I
guess
this
is
an
an
obvious
question,
but
I
don't
see
it
in
the
sheet.
Do
you
have
reviewers
lined
up
for
these
27
that
are
ready
for
review.
D
C
D
Mentioned
not
a
combination
of
both
we
have
for
a
majority
of
them.
It
was
also
continue
to
keep
like
following
up
because
of
the
because
the
deadline
is
almost
here.
Yeah.
B
E
I'm
volunteering
to
review
as
well
the
docs
merger,
but
docs
complete
deadlines
tomorrow,
end
of
day
tomorrow,
so
I
will
make
sure
to
do
a
review
for
those
27.
I.
Believe
it's
a
little
bit
lower.
Now
I
did
see
a
few
merge
this
morning.
D
A
B
Hi,
my
name
is
Central
I'm,
covering
for
Carlos,
so
for
release.
Note,
it's
green
and
then
a
PR
for
the
major
things
is
opened
and
it's
it's
it's
under
review.
So
our
team
and
the
release
notes
team
has
reviewed
it
and
and
it's
waiting
for
the
release,
lead
to
review
and
merge.
That's
it.
A
Yeah,
thank
you.
So
much
I
have
pre-reviewed
the
major
Sim
before
the
PR
opened
and
I
think
I'll.
Take
a
second
a
look
on
it
like
later
after
this
meeting.
Thank
you
so
much
for
mentioning
that
and
any
any
questions
for
release,
notes,
Here
and
thank
you
for
handling
the
release
novels,
PR
oud.
Let's
move
to
comms
team.
B
Yes,
hello,
yes
I'm
here
hello,
so
our
status
continues
to
be
green.
We
have
the
release,
block,
draft,
PR,
App
and
being
reviewed
and
up
with
the
request
for
additional
comments
there.
B
We
have
the
feature
block
schedule
already
defined
and
assigned
to
all
the
individual
channels
for
follow-up
with
the
with
the
individual
authors
being
tracked
in
terms
of
the
of
the
the
planned
dates
we
do
have
one
specific
blog
that
is
not
100
there,
because
there
was
a
personal
tragedy
in
in
the
part
of
the
of
the
responsible
there,
but
we
are
on
on
top
of
it
and
we
don't
think
that
that
is
enough
to
change
the
status
from
from
grain.
So
that's
it
from
comms.
A
A
E
Hey
folks,
so
it's
the
last
full
week
of
the
release
so
they're
just
a
reminder.
I
know,
Cece
is
going
to
talk
about
the
upcoming
deadlines
and
Milestones
and
release
lead
section,
but
just
want
to
say
thank
you
very
much
for
you
know
for
all
your
efforts.
This
is
gonna.
This
last
week
tends
to
be
pretty
really
busy
as
well,
and
then
the
release
is
scheduled
for
next
for
a
week
from
Tuesday,
so
yeah
just
feel
free
to
ping
me
if
you
need
any
help
as
well
yeah.
E
If
you
need
to
just
reach
out
and
I'm
I
am
available
this
week.
That's
it
for
me.
A
Thank
you
so
much
and
yes,
I'm
going
to
talk
about
the
major
Milestones
this
week,
and
this
is,
as
we
said,
the
last
full
week
of
the
release
and
the
current
release
date
is
still
scheduled.
The
next
week
23rd
of
August,
and
this
week,
like
especially
tomorrow,
we
have
like
several
deadlines,
including
the
major
Sims
dogs,
future
blogs,
ready
to
review
and
also
we
should
be
expecting
the
RC
one
card,
which
is
the
last
release
candidate
card
before
the
formal
release
and
also
on
Thursday.
A
We
were
expecting
the
release,
notes
complete
after
the
last
RC
card
and
seems
like
a
busy
week.
Thank
you,
everyone
for
the
help
and
effort
for
making
it
happen
and
also
the
release
same
update,
I'm
sorry,
I
kind
of
delayed
on
this,
but
I
want
to
share
the
realism
with
inside
the
release
team
for
sure
before
it's
been
published
and
I
started
to
share
it.
Since
last
week's
meeting,
but
I
know
not,
everyone
joined
everything
committee,
so
I'll
keep
sharing
it
in
the
following
meetings
as
well.
A
So
the
initial
idea
it
comes
from
the
Transformers.
Of
course,
and
I
hope
like
we
can
use
this
really
Sim
to
honor
the
collaboration
and
open
spirits
of
the
community
together.
It
also
can
refers
like
kubernetes,
like
Jordan
force
from
not
only
like
multi-components,
but
also
like
hundreds
or
thousands
of
contributors
together,
especially
for
the
release
camp
like
without
any
of
you,
like
the
release
process
will
not
as
smooth
as
it
is
now.
So.
Thank
you
so
much
for
everyone's
effort,
yeah
and
I'm
still
working
on
the
logo.
A
It
was
running
into
some
I
expected
issues
last
week,
so
I
hope
it
would
be
ready
and
it
can
be
shared
with
all
of
you
within
this
week.
Thank
you
so
much
and
we
don't
have
the
oh
before
I,
move
forward
any
questions.
A
If
no
I
don't
see
any
updates
from
sex,
scalability
and
I,
don't
think
we
use
wall
project
board
now
so
I
guess
they
can
call
it
a
meeting
and
in
questions
before
I
end
the
recording
and
sharing,
if
no
I'll
go
ahead
and
the
recording.
Thank
you.
Everyone.