►
From YouTube: Kubernetes Release Team Weekly Meeting for 20220811
Description
Kubernetes Release Team Weekly Meeting for 20220811
A
This
meeting
is
being
recorded
hi
everyone
welcome
to
our
kubernetes
1.25
release
daily
burn
down
meeting
today
we
are
at
week
12
thursday,
11th
august,
and
if
anyone
wants
to
see
anything
before
the
meeting
before
we
give
the
updates,
if
no
we'll
just
go
to
the
open
discussion
section,
oh
before
that,
I
just
pasted
the
meeting
notes
into
the
chat,
so
please
feel
free
to
register
your
attendees.
If
you'd
like
and
for
open
discussion,
I
I
said
I
will
give
an
update
yesterday
on
the
object.
Storage
support
thing.
A
B
A
Thank
you
so
much
yeah
and
then
questions
for
enhancements.
If
no,
let's
move
to
ci
signal,
anyone
from
ci
signal
gonna
give
an
update
if
no
I'll
just
give
the
update.
Instead,
I
checked
the
release
master
and
released
a
master
informing
and
it
seems,
like
master,
is
all
green
and
we
do
have
one
failure
in
the
master
in
informing,
I
think,
which
is
the
node
e2e
conformance
test,
but
it's
been
confirmed,
not
a
release
blocker
so
currently
I'll
set
the
status
to
green
and
any
questions
for
ci
signal.
C
Morning
afternoon
evening,
everybody
bug
triage
is
currently
with
the
green
status
blocking
issue
zero,
blocking
pr,
zero
open
non-test.
We
have
11
currently
priority
critical
urgent
issues
is
zero,
a
priority
important
soon.
Six
we
have
in
kkk.
We
have
17
open
prs.
That's
down
two
from
yesterday
priority
critical
excuse
me
priority.
Critical
urgent
is
remaining
at
one
priority.
Important
soon
is
at
nine,
that's
down
one
from
yesterday
and
finally,
the
all
open
kk
issues
is
12,
including
we
have
another
query
that
shows
11,
and
that
is
us
any
questions.
A
B
Hi,
so
our
current
status
is
still
yellow
our
branch-
sync
pr
is
still
in
review.
I'm
not
sure
what
the
hold
up
is
on
that
is
I'll
check
with
sig
docs.
We
have
one
enhancement
3178
that
still
has
missing
dots.
They
were
pinged
again
yesterday
by
ray
and
no
response.
So
I
made
follow-up
on
slack
today
on
that
and
we're
still
at
the
same,
have
the
same
stats
that
we
did
at
yesterday's
meeting.
B
A
Our
update,
thank
you
for
the
updates.
I
think
I
also
pinned
the
cap
owner
in
the
slack
channel,
but
I
didn't
hear
any
response
regarding
his
basic
has
been
the
issue
of
turn
yeah
I
painted
in
the
thread
in
the
sig
dogs,
a
really
stocks
channel,
so
I'm
not
sure
if
they
didn't
solve
the
message
yet
or
not.
But
okay,
I
do
see
the
author
also
opting
for
the
feature
blog
and
they
have.
B
A
D
Our
current
status
is
jello,
since
the
deadline
for
the
major
teams,
vr
is
soon
is
next
tuesday,
but
we
are
collecting
comments
and
organizing
work
for
this
task.
So
I
think
we
can
do
it
before
the
deadline
and
also
the
release
notes
pr
for
beta0
was
merged
yesterday
today
morning.
Sorry-
and
we
are
working
on
the
release,
notes
pr
for
rc
0.
A
E
We're
looking
green
we're
going
to
be
passing
on
the
release
blog
over
to
cc's
hand,
and
then
everyone
else
then,
once
cc
gives
the
green
light.
We
can
pass
that
over
to
the
cncf
pr
team
and
we
are
currently
focusing
on
ranking
those
blog
posts
and
then
getting
those
assigned
to
the
shadows
for
tomorrow,
so
that
we
can
be
tracking
those
and
get
this
to
the
finish
line.
A
A
If
you
know,
let's
move
to
release
branch
management,
anyone
from
release
branch
management
here
today,
if
no
I'll
say
the
status,
is
growing,
just
follow
the
ci
signal
and
we
just
cut
our
rc
mirror
on
tuesday.
So
everything
looks
good
and
I
pasted
the
formal
announcement
in
yesterday's
updates
as
well.
A
I
think
one
release
on
tuesday
as
well
so
seems
like
a
busy
day
on
tuesday
and
also
we
have
another
deadline
on
thursday
next
week
regarding
the
release,
notes
complete
because
it's
of
course
was
expected
after
I
see
wireless
card,
so
we
can
get
all
the
release
notes
from
the
changes
in
between
and
that's
the
major
milestones
I
do
want
to
give
an
update
on
the
releasing.
We
have
the
really
same
topic
ready,
but
I'm
still
working
with
tim
bannister
on
the
detailed
design.
A
I
do
want
to
share
it
like
when
the
design
is
ready,
but
it
looks
like
it
might
be
as
early
as
the
coming
monday.
So
I'm
sorry
for
not
sharing
it
earlier
and
I'm
not
sure.
If
spell
alert,
I'm
not
sure
if
everyone
wants
to
know
the
release
name
now
I
can
I
I
definitely
can
share
it
briefly
without
the
detailed
design.
A
So
I'll
share
it
now
and
maybe
tomorrow,
and
if
monday
I
could
have
like
the
design
picture
I'll
just
paste
it
in
the
in
the
meeting
notes.
Maybe
so.
The
current
release
theme
I
currently
think
about
is
the
combiner
which
actually
comes
from
the
transformer
if
people
familiar
with
I'll,
just
maybe
paste
the
picture
here
yeah.
A
So
when
I
think
about
the
releasing,
I
think
about
the
combiner,
which
could
refer
to
the
kubernetes
being
built
by
merging
the
power
of
hundreds
of
contributors
across
the
global,
all
like
kubernetes
itself,
like
made
of
multiple
components
which
all
contribute
to
enhance
the
power
of
kubernetes,
especially
like
for
this
release.
We
got
like
15
alpha
features
being
tracked,
which
I
think
is
a
great
sign
of
the
green
power
of
kubernetes
and
also
I
do
want
to
take
this
chance
to
thank
everyone
in
the
kubernetes
1.25
release.
A
I
feel
like
the
release
will
definitely
not
as
smooth
as
it
is
like
if
without
any
of
you-
and
I
do
think
like
each
of
us
could
be
a
separate
transformer
together-
build
up
the
combiner.
So
that's
the
how
the
idea
came
from
and
also
like
I'll
be
honest.
The
idea
initially
was
inspired
by
my
son,
which
transformer
is
his
favorite,
so
I
do
want
to
share
further
on
the
sim
after
the
design
is
ready
but
yeah,
but
maybe
that
will
be
next
week
hopefully,
and
I'm
not
sure
if
anyone
has
any
questions.