►
Description
Kubernetes Release Team Weekly Meeting (1.25) for 20220629
B
Hi
everyone
hope
my
voice
looks
like
it's
fine
and
hi
everyone
Welcome
to
our
weekly
1.25
kubernetes
release
meeting
and
we
are
currently
at
week.
Six
today
is
Wednesday
29th,
June
2022,
and
this
meeting
is
under
the
code
of
a
sense
of
code
of
conduct
which
could
be
brought
down
to
this
place,
be
nice
to
each
other
and
be
respectful
for,
and
please
will
feel
free
to
register
your
attendees
in
the
link,
I
shared
and
we'll
start
the
meeting
shortly.
Let's
first
go
over
the
open
discussion.
B
I
have
one
topic
here,
which
is
the
doodle
link
for
the
Friday
APAC
friendly
meeting,
which
will
happen
starting
the
first
Friday
of
July
I,
guess:
oh,
it's,
the
second
Friday
of
July
or
July,
8th
I,
believe
yeah.
So
please
feel
free
to
pick
your
favorite
time
there
and
hopefully
to
see
some
of
you
in
the
Apec
friendly
meetings
and
let's
move
to
the
team
updates
first
enhancements
Jason.
C
Hey
so
I
covered
from
my
got
a
message
from
him:
his
internet
went
down.
Our
overall
status
is
clean.
We
had
the
enhancements
freeze
last
week,
so
the
email
went
down,
I've
linked
it
there,
and
over
this
week
we
received
one
exception:
request
for
cap,
two,
two
three
eight,
which
was
approved
and
is
now
marked
as
tracked
yeah.
B
B
If
no
I'll
just
read
it
through
the
updates
I,
please
interact
me
if
you're
here
and
the
current
status
was
marked
as
yellow
I
guess,
because
we
have
the
feeling
on
Master
blocking
when
filling
and
it's
really
flicky
and
the
master
informing
becomes
green,
no
fitting
at
least
and
I'm,
not
sure.
If
the
one
failing
job
is
being
tracked,
I
guess
it
should
be.
E
Yes,
hello,
everyone
for
bacteria,
we
are
overall
say
this
is
green.
There
is
no
blocking
issues
or
PRS.
The
team
has
successfully
started
migrating
from
spreadsheet
to
GitHub
projects
thanks
to
Heba
and
Hassan
for
the
effort,
and
we
started
using
it
as
Shadow
to
assign
the
responsible
team
member
for
each
bug
and
on
each
PR.
So
that's
also
something
that
will
adapt
to
moving
forward.
F
This
week
the
enhancements
have
been
assigned
to
all
the
shadows
and
to
the
lead
so
we'll
be
we'll
be
starting
to
reach
out
to
the
owners
to
determine
the
doc's
status
and
then
last
update
is
the
pr
to
keep
the
branch
in
sync
that
was
opened
by
DD
has
been
merged.
Another
one
will
be
opened
probably
next
week
around
Tuesday
quick
question.
Actually,
if
that's
all
right
to
the
group,
sure
there's
also
a
there's.
F
B
F
B
G
A
Cons,
okay,
hello,
there
so
I
have
dropped
in
all
of
the
relevant
Sig
channels.
The
feature
blog
opt-in
tracking
sheet
and
ask
for
people
to
opt
in
also
been
looking
at
the
enhancements
spreadsheet
to
get
an
idea
of
which
caps
really
really
need
a
feature
blog,
so
I
can
chase
down
somebody
specific.
The
Shadows
are
also
going
to
be
giving
their
input
on
which
caps,
they
think
are
important
enough
for
us
to
be
chasing
down
specifically,
but
I've
also
been
talking
to
Tabitha
Sable
about
a
Blog
for
the
PSP
removal.
A
A
Is
that,
like
typically,
the
mid-cycle
blog
is
about
deprecations
and
removals,
but
we
only
have
one
removal
so
this
this
blog
will
be
titled
slightly
differently
and
will
probably
also
involve
just
like
calling
out
mage
your
changes,
whether
it's
a
removal
or
or
not,
just
because
I,
don't
I,
don't
want
the
blog
to
feel
like
awkward
like
calling
it
deprecations
and
removals,
but
it's
like
literally
just
a
Blog
about
PSP.
So
it's
going
to
be
a
little
bit
differently,
flavored
this
cycle
than
usual,
but
we,
we
are
all
good
we're
we're
green.
B
Cool,
thank
you
so
much
for
the
updates.
That's
a
great
work
and
just
one
comment
on
the
mid-cycle
blog.
If
you
want
to
include
other
like
features,
instead
of
only
like
a
PSP
removal
kind
of
thing,
like
other
major
changes,
maybe
regarding
this,
like
the
current
enhancement
which
has
been
obtained,
but
the
code
hasn't
been
merged,
so
it
might
be
risky
because
there
is
a
like
there's.
B
A
A
D
B
H
Don't
see
her
on
so
I
will
tackle
it.
We
cut
the
125
Alpha
2
yesterday
seemed
to
go
pretty
good,
there's
a
couple
of
things
that
we
need
to
fix
in
the
tooling.
It's
not
like
it's
not
blocking
anything
but
it'll.
We
want
to
get
it
tested
before
the
the
beta
cuts
and
stuff.
So
we're
going
to
try
to
do
a
lot
of
that
in
the
one
in
the
alpha
three
cut
that
Joseph's
gonna
do
so
we'll
we'll
be
working
towards
that.
H
D
If
you
have
any
questions
on
the
release
team
or
if
you
want
to
do
like
another
session
as
well
on
them
and
for
your
intro
anyway
upcoming
for
for
me
in
the
next
few
weeks,
I'm
going
to
send
out
a
check-in
survey,
just
see
how
Shadows
are
doing
well,
I'm,
also
going
to
check
in
with
shadows
one-on-one
as
well.
So
look
out
for
that
anyways.
If
you
have
any
questions,
just
feel
free
to
reach
out.
B
Thank
you.
Thank
you
for
the
update
and,
let's
move
to
release
late.
The
update
is
pretty
much
covered
by
the
previous
discussion
and
we
had
the
husband
phrase
last
Thursday
and
we
received
by
exception,
request
and
approved
I
believe
it's
merged
already
and
the
place
fill
the
doodle
link
for
the
APAC
friendly
meeting.
So
we
could
go
ahead
and
schedule
that
and
that's
it,
and
today
we
get
the
update
from
six
scalability.
B
If
anyone
from
six
scalability
want
give
an
update,
oh
it's,
okay,
we
just
do
really
throw
weight
cool.
If
nobody
from
seek
scalability
is
in
the
meeting,
I
guess
the
person,
whoever
is
on
call
just
provided
the
update,
it's
all
green,
it
looks
nice
and
I
guess,
that's
all.
Do
we
need
to
go
over
the
walk
project
board?
B
Let's
take
a
look
to
see.
I!
Guess
it's
updated
it's
seven
days
ago
the
beta
releases
scalability
test
is
running
and
flick
test.
The
template
and
in
progress
is
refining
the
way
we
communicate
to
project.
Okay
looks
like
it's
nothing
specific
for
the
current
release:
yeah!
That's
it
before
I
end
up
the
recording.
Is
there
any
questions?