►
From YouTube: Kubernetes Release Team Meeting (v1.25) for 20220804
Description
Kubernetes Release Team Meeting (v1.25) for 20220804
A
This
meeting
is
being
recorded
hi
everyone
welcome
to
our
daily
burn
down
meeting.
We
are
today
at
kubernetes
1.25
release
week,
11
thursday
4th
august,
and
let's
just
move
to
the
open
discussion.
If
we
don't
have
any
topic
in
open
discussion,
let's
directly
move
to
the
team
updates,
then
enhancement
from
mark.
B
A
A
If
no,
let's
move
to
ci
signal
arch
looks
like
csgo
didn't,
update
the
status
and
sorry
I
forgot
to
check
in
the
daily
in
the
release
report,
but
I
guess
from
yesterday,
if
I
remember
correctly,
there
is
one
fitting
for
the
master
blocking
and
I'll
double
check
later
to
see.
If
there
is
further
failures,
looks
like
okay
cool
and,
let's
move
to
bug
triage.
C
You're
here
yes,
apparently,
we
are
yellow.
So
it's
because
of
on
the
blocking
issue
is
regarding
log
check
plugin,
which
is
failing
at
the
moment
and
as
teams
mentioned
in
the
issue,
it's
gonna
be
fixed
with
golang
119
ga.
So
if
yeah
beside
that,
there's
nothing
news.
Since
yesterday
we
are
tracking
everything
and
yeah.
Thank
you,
cece
for
opening
this
yeah.
As
mentioned,
it's
gonna
be
fixed
when
jay
comes
out
yeah
it's
because
of
that
we
are
yellow
beside
that.
We
are
all
fine
with
the
release
cut.
D
I
don't
see
kristin
on,
but
I
actually
added
this
update
here
so
so
they
asked
me.
The
doc
seemed
to
ask
me
just
top
out
a
little
bit,
so
I
went
through
the
tracking
sheets
for
the
docs
tab
and
reviewed
pr
is
open
to
the
dev
125
branch
and
on
okay
website
also
to
the
to
the
k
website,
main
branch
as
well,
so
we're
tracking
41
docks
out
of
38
enhancements.
D
Only
because
there's
some
doc
prs
for
enhancements
are
no
longer
being
tracked
or
in
the
milestone,
but
we
also
know
that
there's
some
exception
requests
going
on
as
well
as
well.
So
I
think
by
next
next
week
we
will
have
a
clearer
picture
of
which
docs
to
close
dock
prs
to
close
are
no
longer
tracked
for
125.
D
A
Thanks
for
adding
that
today's
the
dogs,
please
hold
up
your
deadline,
so
I
guess
they
should
be
aware
of
that
line
things
we
send
it
out
like
multiple
times
and
let's
move
to
release
notes.
If
anyone
from
release
notes
are
in
the
call
now,
yeah
dipto
reached
it
out
to
me
before
meeting
and
seeing
they
are
working
on
the
major
themes,
so
I'll
assume,
let's
start
working
on
that
and
they
will
be
referenced
to
the
future
blog
spreadsheet
as
well
for
collecting
major
sims
and
yeah.
E
Hey
so
the
mid
cycle
blog
is
imo
ready
to
go,
it
just
needs
approval
tags,
but
there
was
some
some
waffling
over
moving.
All
of
the
like
entry
driver,
removals
and
deprecations
into
one
header
item,
but
I
just
went
ahead
and
did
that
so
it's
good
to
go
the
two
outstanding
placeholder
pr's,
those
two
blog
owners-
have
decided
to
opt
out
of
feature
blogs.
A
A
F
F
Several
tasks
updates
one
of
the
pr's
that
I
linked
here
just
merged
and
the
second
one
I
think
it's
waiting
for
one
job
to
complete
dc
knows
like
that.
Since
last
night
we
have
been
struggling
with
a
lot
of
issues,
hopefully
crossing
our
fingers,
that
this
is
the
last
thing
on
the
list,
but
in
case
I
I
just
need
to
mention
it
in
case
things
go
wrong,
but
we
started
contemplating
the
possibility
of
not
doing
119
just
as
a
possibility
we're
still
working
or
like
all
the
release.
F
Managers
are
on
it
and
and
all
the
stakeholders
are
in
it,
but
in
case
it
doesn't
go.
Okay,
we're
we
have
enough
consensus
to
to
just
roll
back
to
180
at
this
point,
because
it's
been
a
lot
of
work
so
well
waiting
for
that
and
I'll
sync
with
ci
signal.
After
this
call
to
see
if
we
can
cut
the
beta
release
but
I'll
keep
you
updated.
F
A
D
Folks,
once
again,
the
mid
cycle
shadow
survey
is
out,
please
fill
out
by
end
update
tomorrow.
The
link
is
on
the
agenda.
I
live
notes.
I've
also
as
also
muscle,
partisan
docs,
so
I
did
ping
the
sig
docs
blog
reviewers
to
take
a
look
at
the
125
deprecation
and
removal
blog,
so
hopefully
that
gets
merged
today,
I'll
reach
out
by
dms
as
well
to
those
reviewers.
But
and
that's
I
started
thinking
about
succession.
D
I've
mentioned
this
a
few
times
and
reach
out
to
a
few
of
the
world
of
rural
leads
already
so
I'll
reach
out
to
some
more
today
and
tomorrow
or
today,
I'll
be
out
most
of
the
day
tomorrow,
so
I'll
be
slow
to
on
slack.
But
I
will
be
around
early
very
early
in
the
morning
for
tomorrow.
So
and
that's
it.
A
A
If
we
do
not
get
further
information
from
the
sick
lease,
I
guess
we'll
still
go
ahead
and
approve
it,
since
it's
a
super
low
risk
exception
and
with
like
minimum
days
asked
on
three
days
asked.
So
I
guess,
even
without
further
information
from
like
this
I'll
just
go
ahead
and
prove
it
and
we
just
look
forward
to
beta
card
today
and
hope
go
1.19
goes
well
and
I'm
also
worked
on
the
release
themes
and
I
have
a
few
candidates.
A
Yeah
green
awesome,
so
I
I
will
assume
there's
no
further
changes
since
yesterday
and
thank
you
for
scalability
for
updating
those
stackers
and
for
our
broad
project
project
board.
I
don't
think
it
will
be
any
different
from
yesterday,
but
let's
just
double
check,
yes
and
before
we
end
the
meeting
any
questions
or
any
concerns.