►
From YouTube: Kubernetes Release Team Meeting (v1.25) 20220801
Description
Kubernetes Release Team Meeting (v1.25) 20220801
B
C
C
Also,
I
have
sent
out
an
invite
for
coach
police
party
for
august
2
18
pacific
time.
Please
let
me
know
if
you
have
not
received
the
invitation.
Also,
there
are
three
open
exception
requests
which
are
awaiting
decisions
so
two
of
them
we
already
have
a
slap
thread
running
and
one
of
them
thanks
to
ray.
I
just
got
to
know
about
that.
So
maybe
I'll
go
ahead
and
create
a
thread
yeah.
B
C
B
D
No
just
a
few
comments
it
just
for
those
who
aren't
familiar
with
the
code
freeze
party
that
takes
place
at
the
start
of
code
phrase.
We
do
that
so
that
there's
not
one
person
kicking
an
enhancement
out
of
a
release
or
taking
someone
out.
So
we
kind
of
do
it
as
as
a
team.
So
there's
multiple
people
involved
in
that
process
or
who,
who
can
agree
upon
like
if
announcement,
should
be
untracked
for
125,
so
that
just
gives.
I
just
want
to
give
a
little
context
to
that.
B
Or
anyone
from
ci
signal
or
want
to
give
an
update
if
no
I'll,
just
read
through,
looks
like
someone
already
updated.
The
notes
and
the
the
status
for
cs
scanner
now
is
yellow.
We
have
one
following
test
for
master
blocking
and
it's
been
tracked
in
the
issue
linked
below,
and
I
saw
a
few
discussion
happening
in
say
a
signal
channel
as
well,
so
we
have
people
on
that
and
for
master
informing.
We
have
two
failing
jobs.
The
issue
also
created
regarding
mr
fittings.
B
E
Yes,
so
currently
we
are
green,
so
there
is
no
plugging
issues
or
pr's
for
the
release
cuts.
Beside
that
you
know
we
are
reaching
the
code
phrase,
so
we
are
reaching
out
the
owners
of
the
pull
requests
or
issues
and
telling
them
yeah
if
they
are
still
on
the
track
to
to
get
to
them
to
the
125
milestone.
That's
our
status.
F
B
A
A
A
G
Hello,
so
most
of
our
feature,
blogs
have
placeholder
pr's
ahead
of
the
deadline.
They're,
just
a
few
stragglers,
there's
there's
one
that
I
think
might
not
get
us
a
placeholder
pr
and
unfortunately
it's
an
important
one,
but
I
am
looking
for
different
avenues
to
bother
the
assigned
owner
or
find
a
new
owner
for
it.
It's
the
the
pod
security
admission
blog,
but
I'm
going
to
keep
hustling
on
that
and
find
them,
and
if
not,
I
can.
I
know
who
I
can
get
to
write
it
instead.
G
Also
thanks
everybody
who
reviewed
the
deprecations
and
removals
blog.
There
are
a
couple
of
things
that
I
have
left
that
I
need
to
add
to
it
now,
especially
now
that
the
gluster
fs
thing
has
an
exception.
So
that's
that's
is
important
enough
to
mention
in
that
blog
imo.
After
the
freeze,
we
will
start
figuring
out
which
blogs
go
out
when
aiming
to
get
that
done,
or
at
least
start
work
on
it
later
this
week.
H
Veronica's
not
here
this
is
joseph
so
for
release
bands
management.
We
are
yellow,
currently
we're
keeping
an
eye
on
the
ci
signal
report
as
we're
getting
ready
to
this
thursday
cut
the
125.0
beta0.
So
we
do
notice
that
there's
a
failing
test
on
master
blocking.
Hopefully
it's
going
to
get
resolved
by
thursday
and
then
the
other
thing.
Obviously,
what
we
just
discussed
earlier
is
code.
Freeze
is
tomorrow,
so
we
will
post
up
that
pr
in
the
morning
and
then
release
the
whole
later
that
day,
so
that
everybody
can
have
a
code
free
party.
B
D
D
B
We
currently
already
have
three
exception
requests
received
and
we
are
reviewing
each
of
them
on
sake,
release
channel
if
you're
interested
please
participate
in
the
discussion
thread
and
we're
still
waiting
for
some
import
from
sick
leads
and
chairs.
Other
than
that.
I
think
most
of
the
requests
should
be
good
and
also
we
are
also
waiting
for
the
go
1.19
ga
card,
which
will
getting
hopefully
our
beta
card
yeah.
That's
the
currently
standards
and
we'll
get
more
updates
tomorrow,
hopefully,
and
we
don't
have
any
input
from
sig
scalability
today.