►
From YouTube: Kubernetes Release Team Meeting for 20230621
Description
Kubernetes Release Team Meeting for 20230621
A
Hello,
everyone-
this
is
Heba
I
will
I,
will
be
your
host
today
for
the
release
meeting
today
is
June
21st
and
I.
Well,
the
agenda
and
meeting
notes
Here
in
the
chat,
so
please
feel
free
to
add
your
name
pronounce
and
if
you
have
any
release
team
rule
to
the
attendees
before
starting
everything.
Let's,
let's
remind
everyone
that
this
meeting
is
running
under
a
cncf
code
of
conduct,
which
means
be
nice,
be
kind
to
each
other,
and
with
that,
I
will
share
my
screen
and
let's
get
started.
A
B
Hello,
so
the
announcements
phrase
is
now
an
effect
from
starting
from
16th
June.
So
we
are
currently
accepting,
in
the
exception,
requests
those
who
those
announcements
who
are
who
were
removed
from
my
son
or
those
who
still
want
to
obtain
the
currently
the
metrics
situations,
look
like
it's
around.
B
59
of
them
are
successfully
tracked
and
the
remaining
six
of
them
have
been
removed
from
Milestone
because
they
didn't
satisfy
the
criteria
and
two
were
referred
to
next
release,
and
so
as
for
till
now,
we
have
received
around
four
announcements
out
of
which
two
are
approved
and
one
was
rejected
and
the
left,
the
other
one,
is
still
in
progress
of
getting
approved
or
rejected.
So
yeah,
that's
the
current
status
and
the.
C
C
B
B
If
you
see
through
the
issue,
so
that's
kind
of
another
thing,
because
we
also
would
need
someone
to
have
lead
octadine
level
and
also,
even
though
the
all
the
work
has
been
done.
It
would
still
need
a
whole
PR
review
and
it
might
take
some
time
which,
at
the
current
moment,
at
the
current
time
frame,
we
might
not
accept
it.
D
A
E
Yep,
so
we're
looking
good
on
CI
signal.
You
can
see,
we've
got
the
four
flaky
and
the
one
failing
all
of
which
are
currently
being
worked
on.
They've
got
the
tickets
out
there,
so
we're
fully
green
and
ready
to
go
the
most.
The
one
failing
was
infrastructure
modification,
so
they
dropped
a
bunch
of
1804
images
and
so
they're
just
having
to
rip
out
the
references
there.
So
I
think
we'll
be
good
after
that
and
I
think
Maya
had
some
things.
I
should
want
to
update
outside
of
that
status.
Right.
F
Yes,
a
little
thing
like
that
got
unnoticed
in
the
initial
week.
So
yes,
I
wanted
to
get
an
attention
that
we
are
discontinuing
the
sending
weekly
CI
signal
report
for
this
release,
but
you
can
still
find
the
CI
signal
status
in
this
weekly
release.
Team
notes
are
also,
and
the
CI
signal
project
board,
and
this
decision
has
been
agreed
upon
in
the
1.27
retrospective
meetings
and
yes,
for
regarding
the
same
I
will
send
an
emails
to
the
appropriate
groups.
F
D
Thanks,
hey
folks,
outside
of
screen,
we
don't
have
any
blocking
issues
or
PRS.
On
the
update
side,
all
the
issues
and
PRS
are
assigned
to
the
team
members
and
being
tracked.
We
have
a
first
round
of
things
already
to
the
pr
owners
and
civics.
We
are
I
think
good.
On
that
side.
Another
update
is,
we
have
a
two
PRS
which
updates
the
back
trash
handbook.
Let's
take
a
look,
and
there
is
one
the
other
one
is
like.
G
Folks,
things
are
green
over
on
docs,
apps
have
been
assigned
to
all
of
the
shadows,
and
we
are
currently
reaching
out
to
everybody
to
make
sure
that
they
go
ahead
and
open
a
docs
placeholder
PR,
if
they,
if
they
need
it,
and
updating
the
tracking
board
as
we
go
accordingly.
So
we're
all
good
over
here.
H
Hello,
so
we're
good
as
well.
Current
status
is
green
and
the
version
128
zero
Alpha
2
PRS,
were
already
merged.
Last
week
we
have
reached
out
to
all
the
six
around
the
major
teams
collection
discussion
and
also
announced
the
the
the
deadlines
to
receive
the
feedback,
and
so
we're
planning
to
create
the
version.
128
Alpha
3
website
in
the
release
not
PR
shortly.
A
I
A
J
K
Hello,
everyone
so
I
have
just
one
topic,
which
is
about
the
mid-cycle
Retro,
so
every
release
cycle
we
have
two
or
three
Retros
and
during
the
Retro
we
will
just
talk
about
what
is
going
very
well.
What
can
we
improve
just
general
bringing
up
issues
talking,
maybe
about
changing
some
practices?
We
have
in
the
release
team
and
we
have
usually
one
retro
during
like
halfway
through
the
release
cycle,
which
is
usually
about
the
ninth
week.
K
Maybe
if
you
think
about
already
how
your
experience
was,
maybe
you
noticed
like
some
things
and,
for
example,
we
have
like
one
change:
one:
big
change
in
merging
the
bhaktriage
team
and
the
Cs
signal
team.
There's
also
like
one
change
which
I
saw.
We
are
posting
that
we
discontinued
the
Cs
signal
reporting.
So
I
think
this.
These
are
interesting
discussion
items.
We
could
talk
about
them
in
the
Retro.
C
C
C
Ci
signal
are
going
under
a
merge,
but
the
first
step
for
them
to
do
that
is
to
update
their
current
handbooks.
So
if
you
were
Shadows
on
this
team
in
previous
releases
or
current
Shadow,
we
would
love
your
help
here,
and
you
know
this
is
the
kind
of
work
that
has
really
long-term
impacts
and
then
lastly,
I
want
to
give
a
big
shout
out
to
the
enhancement
team
for
all
the
work
they've
done
to
later.
C
Foundation
of
this
release,
we
have
59
trapped
out
of
I,
think
almost
70,
which
is
the
highest
throughput
I've
ever
seen
like
usually
only
a
third
of
the
enhancement
make
it
through
enhancement
freeze,
and
so
we
are
doing
something
right
here
to
make
sure
that
the
enhancement
team
is
not
being
overworked,
but
we're
receiving
a
very
large
number
of
enhancements,
So
yeah.
Thank
you.
Enhancing
team.
A
B
You,
oh
thanks
for
all
the
works
of
the
Shadow,
really
that
was
a
great
help
and
also
shout
out
to
the
prr
team
as
well.
Getting
in
all
the
PR
reviews
done
before
the
freeze
and
yeah
they're
constant
and
thanks
to
the
leads
as
well,
you
Grace
and
Leo,
and
all
the
release
Shadows
yeah
kudos
to
all
of
you.
C
A
B
About
the
announcement
request,
exception
request
that
recorded
I
just
took
a
look
and
then
I
found
out
that
the
current
they
would
just
need
appear
review
done.
Otherwise
their
work
is
totally
done,
so
we
would
need
to
ping
one
of
the.
We
would
need
to
Ping
the
whole
prr
team.
Apart
from
that,
everything
else
seems
to
be
done
so
yeah.
B
C
B
B
B
K
Yeah,
so
I
I
have
not
checked
out
the
exception.
Requests
in
detail,
but
I
would
also
keep
in
mind
if
this
exception
request
covers
like
an
important
feature.
This
should
also
be
considered
I
think
in
general,
if
the
prr
team
and
I
I
just
wrote
this
also
in
chat.
If
they
don't
respond,
it's
a
response
for
us,
so
I
think,
and
we
should
not
like
push
them
into
picking
this
up.
If
they
don't
have
time
and
it's
a
very
busy
time
for
them,
so
yeah.
G
C
K
K
C
K
Not
to
this
topic,
but
just
something
maybe,
which
is
interesting
also
for
everybody
who
is
new
to
the
team.
Maybe
we
can
also
discuss
this
in
a
retro,
but
I
think
it
might
be
interesting.
So,
after
those
like
bigger
Milestones
to
briefly
talk
a
little
bit
more
about
what
the
enhancement
team
did
in
the
last
weeks,
so
everybody
who's,
maybe
not
on
the
team
but
in
general
interested
about
the
work
can
also
understand
more
closely
okay.
What
what
is
this
prr
team
and
so
on?
K
C
B
That's
good
yeah
yeah,
that's
a
great
one
yeah
also.
We
would
need
to
update
I
think
about
this
previously,
but
yeah.
We
would
need
to
update
the
PLL
guidelines
as
well.
It's
a
lot
of
gray
area
right
now
on
when
to
put
on
the
tracking
point
of
weather
2x
how
the
PRS
views
work
generally,
so
yeah.
It
would
need
to
switch
out
the
DPR
team
and
updates
some
make
the
guidelines
clear
for
them
as
well.