►
From YouTube: Kubernetes Release Team Meeting (1.27) for 2023031
Description
Kubernetes Release Team Meeting (1.27) for 2023031
A
All
rights,
hello,
everyone,
my
name
is
James
lavrak
I
am
the
kubernetes
127
release
team
Artemis
advisor
my
pronouns
are
here
him
and
it's
nice
to
see
you
all
here.
It
is
Wednesday
the
1st
of
March
2023
at
1800
UTC,
and
this
is
the
kubernetes
127
release
retrospective
part,
one
I'm
going
to
share
a
link
to
the
notes
in
the
chat.
A
If
you
want
to
take
a
look
at
that,
although
you'll
be
resting,
my
screen
as
well
I'd
like
to
remind
everyone
that
this
meeting,
as
with
all
of
our
meetings,
is
covered
by
the
kubernetes
contributor
code
of
conduct.
Please
give
that
a
read
if
you
have
not
already,
but
it
boils
down
to,
please
be
excellent
to
each
other
at
all
times,
I'd
like
to
thank
Laura
who
will
be
our
subscribe
today.
Thank
you
very
much
for
volunteering
Laura
all
right.
A
We
have
this
meeting
scheduled
until
1845,
so
41
minutes
from
now,
I'm
gonna
put
a
hard
ish
cut
off
at
that,
because
I,
don't
I,
know
everything's
going
to
go
over
and
if
we
need
to
schedule
more
sessions,
then
we
can
all
right
with
that
noted.
Let's
get
started
so
the
first
thing
which
we're
going
to
tentatively
time
box
to
10
minutes,
we'll
see
how
that
goes
is
previous
retro
follow-up.
A
B
B
A
There
we
go
cool.
Well,
that's
very
good.
All
right
bug,
triage
roll
handbook
updates
when
Master
blocking
jobs
fail,
post,
a
public,
Channel
and
DM
leads
confirm,
seeing
the
message
I'm,
not
sure.
If
we
have
do,
we
have
anyone
who
looked
after
this
from
before
on
is
this?
Is
this
current
practice?
Was
this
updated?
Does
anyone
know.
A
A
A
Okay,
very
well,
we
all
get
to
do
everything.
It
happens,
speaking
of
things
that
didn't
get
done,
that
lead
Handbook
of
a
section
of
what
happens
if
release
is
delayed.
This
was
actually
for
me
and
I
haven't
done
it.
So
that's
where
we
are
with
that.
I
still
just
need
to
do
it
there.
We
are
cat,
I.
Think
cat's.
Actually,
here
update
the
comms
handbook
more
details
from
removal
blog.
D
I
am
here
the
cons,
that's
that's
old,
I!
Think
that's
from
actually
like
three
releases
ago
and
the
comms
handbook
has
been
updated
a
couple
times
since
then.
However,
there
there
is
something
that
should
be
on
here.
That
was
an
action
item
from
the
last
release,
retro
of
mine
that
is
not
on
here,
and
that
was
with
respect
to
documenting
the
process
for
the
removal
or
replacement
of
a
shadow.
D
D
A
D
A
E
I,
don't
know
that
there's
been
any
follow-up,
but
we
should
continue
to
push
on
that.
I
I
was
in
the
the
policy
work
group
call
this
morning
and
they
were
talking
about
putting
a
cap
together
for
something
that
wasn't
entry
at
all
and
I
got
the
chance
to
say
like
well.
You
don't
actually
need
a
cup
for
that,
like
you've,
seen
a
sponsoring
sick
to
go
to
Granny
cigs,
but
I
I
do
think.
It's
been
a
point
of
confusion
in
previous
releases.
E
Like
do
out
of
three
things:
need
a
cap
and
I
think
I've
seen
a
lot
of
out
of
tree
caps
still
do
a
cap
as
a
means
to
try
and
get
included
as
a
major
theme
and,
and
things
like
that
when
you
know
yeah
a
summary
I
think
we
should
just.
We
should
have
some
more
documentation
around
what
that
means
and
yeah.
A
All
right
next,
one
very
similar
follow-up
for
overall
handbook
updates,
Rey
doesn't
look
to
be
on
the
call
and
I
don't
have
any
more
detail
on
what
this
means.
So
I
guess
I'll
I'll
ask
Ray
after
the
call,
if,
if
what
he
meant
with
this
so
I
know,
Ray
did
do
a
bunch
of
updates,
so
maybe
I
don't
know.
Does
anyone
know
anything
about
this
nope
okay,
I
will
I
will
follow
it
with
Ray
and
find
out.
A
A
F
A
A
A
A
E
A
A
Okay,
well
yeah,
absolutely
plus
one
to
this
scene
smooth.
This
is
the
smoothest
release
I've
ever
seen,
and
I've
done
eight
of
these.
Now
nine
of
these
I,
don't
remember
so,
but
yeah
great
work.
Everyone
for
for
making
this
as
as
seamless
as
it
has
been
so
far,
we'll
see
how
kofi's
goes
not
so
jinx
it
too
much
all
right.
Did
anyone
have
anything
else
to
kind
of
say
a
comment
on
on
Xander's
point
in
this
issue.
B
I
was
just
comparing
this
to
the
126
release,
which
was
the
first
release
that
we
use
the
enhancements
tracking
board
and
there
was
some
confusion
and
some
like
misconfiguration,
for
which
groups
needed
to
be
updated
so
that
the
label
lead
acted
in
would
be,
could
be
applied
by
leads
and
and
things.
But
this
year
or
this
release,
it
was
really
smooth
and
I
feel
like
six
pretty
much
started,
editing
their
enhancements
to
the
tracking
board
like
right
after
the
call
for
enhancements
mail
went
out,
which
is
very
helpful
for
the
enhancements
team.
So
is.
A
B
B
There
I
think
there's
agreement
to
do
something
like
this
there's,
not
quite
agreements
on
what
exactly
to
do
and
some
of
the
big
concerns
are
like.
We
still
want
people
to
feel
like
there's
humans
they
can
reach
out
to
for.
For
all
of
these,
which
I
think
is
important
and
kind
of
trying
to
find
a
balance
between.
A
B
A
A
B
Came
up
now
that
everything
is
in
the
enhancements
tracking
sheet
and
we
have
a
dedicated
like
status
column
that
says
you
know,
track
removed
from
Milestone
deferred
a
lot
of
enhanced.
Well,
some
enhancement
owners
or
some
saved
leads.
Were
you
know
questioning
like?
What's
the
significance
of
the
track?
Yes
or
no,
which
one
is
the
source
of
Truth?
Is
it
the
status
in
the
board
or
or
not,
and
I
didn't
really
have
a
good
answer,
so
I
thought
I
would
bring
it
up
here.
B
I
think
the
enhancements
team
is
mainly
using
the
board
and
those
columns
as
a
source
of
truth,
especially
because
we
can
have
historical
data
over
the
course
of
the
the
like
for
each
release.
There's
one
board
per
release,
whereas
the
tracked
yes
and
no
is
kind
of
got
removed
at
the
at
the
end
of
a
release
and
then
got
added
at
the
beginning
of
her
release.
B
F
Yeah
I
think
the
benefit
of
these
labels
were
for
the
point
in
with,
like,
after
enhancement,
freeze
and
right
before
code
freeze,
where
we
like
might
not
have
like
gone
through
and
updated
all
the
labels
yet,
but
like
totally
in
favor
of
removing
this,
because
it's
actually
it's
more
work
for
the
enhancement
lead
at
the
beginning
of
the
cycle
and
the
end
of
the
cycle
to
kind
of
go
through
and
make
sure
all
these
are
tracked.
So
I,
don't
I,
don't
see
a
problem
with
removing
them.
B
B
A
A
A
At
the
very
least,
my
experience
is
that
you
know
with
these
ideas
when
you,
when
you
take
it
to
sing
release
someone
will
pop
up
and
and
say
well
actually,
you
need
it
because
of
X
and
you'll
go
oh
yeah,
all
right.
Okay,
we
will
take
that
Mark.
Do
you
want
that
one
due
to
collect
all
these
action
items,
sure.
F
A
Excellent
all
right
consider
the
next
item.
Oh
was
there.
Did
anyone
have
anything
else
to
say
on
this
item
before
we
move
on
actually
nope
all
right,
Mark
again
consider
changing
the
format
for
the
release
webinar
for
126
at
least
126
release
the
lead
spent
15
minutes
per
enhancement
and
the
webinar
felt
both
rushed
and
more
like
most
of
the
information
could
have
been
it's
gotten
with
the
release.
Notes
that.
D
I
have
to
agree
on
this.
Like
it
I,
don't
know,
it
doesn't
feel
useful
to
just
basically
read
the
release,
notes
to
people
for
45
minutes.
You
know,
I
I,
don't
understand
what
the
benefit
is.
It's
it's
a
lot
of
work
for
like
really
questionable
payoff
and
I
think
it
would
be
more
useful
if
the
release
webinar
was
functionally
just
a
webinar
version
of
the
release.
Blog.
E
F
B
C
D
A
No
all
right
moving
on
Laura
want
to
confirm
the
utility
and
scope
of
a
CI
signal
report,
specifically
the
attached
generator
report
like
this
and
the
paired
job
details
suggesting
my
templates
so
happens,
generated
report
tool
needed
some
expected
maintenance
cycle
for
putting
for
putting
updating,
docs
training
on
it.
I'll
just
make
sure
the
output
is
still
useful.
C
C
E
C
E
C
Also,
like
I,
don't
know
if
everybody
who
has
the
most
investment
in
it
is
like
here
to
you,
know,
talk
about
it
or
defend
it,
its
utility
and
also
I'm,
not
sure
we
have
a
great
way
to
like
get
metrics
on
how
useful
it
is
so
I
kind
of
have
to
go
just
off
of
my
Intuition
or
you
know
what
the
what
we
can
all
agree
to
and
the
Retro.
Unless
someone
have
a
better
idea.
C
C
It's
my
starting
point:
I
know
that
there's
a
lot
of
people
who
have
worked
on
the
CI
signal
report,
tool
and
I
understand
from
like
past
retros
that,
like
needing
more
like
bursts
of
communication
to
the
larger
community,
was
of
interest,
and
this
was
like
a
platform
for
that.
I
think
the
scope
for
it
has
like
expanded
and
contracted
over
time.
And
so,
if
I,
don't
I
guess
like
I
want
to
figure
out
is
what
people
need.
C
An
update
on
like
the
CI
health,
for
this
release
is
what
people
need,
like
a
touch
point
to
know
that
the
release
is
still
happening,
which
doesn't
necessarily
need
as
much
work
from
the
CI
signal
team
to
like
provide
just
that
part.
If
they're
not
going
to
like
need
to
follow
up
with
all
the
like
details,
yeah,
that's
kind
of
like
the.
F
E
E
C
Okay,
all
right,
so
what
I'm
hearing
is
that
there's
some
confusion,
maybe
on
who
the
intended
audience
is
that
might
be
Branch
release,
management
or
Sig
release
leads
it
gets
sent
to
Dev
at
so
I.
Think,
there's
a
history
of
it
being
about
like
keeping
General
devs
up
to
date,
but
I
don't
know
that
it's
doing
that,
but
then
either
way
it
sounds
like
to
bring
that
up
and
figure
out
what
to
actually
do
goes
to
Sig
release.
Is
that
what
I'm
hearing.
A
A
F
D
A
D
Worries
so
the
that's
actually
Jeremy's
bad
I
think
because
he
was
running
this
ball
and
he's
not
here.
So
we
can.
We
can
absolutely
just
blame
Jeremy
for
this
one,
but
yeah.
Those
are
the
like.
The
the
issue
is
sitting
there.
It's
just
that,
like
it
didn't
get
any
attention
at
all.
None
of
the
people
I
tagged
in
it
weighed
in
so
I.
Don't
really
know
what
to
do
short
of
like
chucking
it
in
the
Sig
release,
slack
Channel
and
saying:
hey
can.
Can
we
please
talk
about
this.
A
D
B
G
D
I've
had
Shadows
who
were
straight
up
like
just
they.
They
never
did
anything
right.
They
showed
up
for
orientation
and
then
did
nothing
and
responded.
Nothing
on
slack
and
I've
had
a
shadow
who
was
like
fairly
active
on
slack
but
then
refused
to
do
any
like
actually
assigned
work
right
like
he
would
talk,
but
not
actually
do
anything.
So
there's
there
needs
to
be
like
a
a
definition
of
what
constitutes
inactive
and
that
that
requires
a
group
discussion,
I
think
yeah.
A
F
Yeah
sorry,
one
quick
note,
I
vaguely
remember
a
conversation
between
about
including
maybe
is
it
I
think
it's
comms
about
better,
including
it
on
the
board
and
like
Mark.
If
you
remember
like
how
do
we
make
the
board
better
for
other
teams,
because
it
was
quite
optimized
for
enhancement
at
that
point,
so
maybe
we
can
bring
that
back
up
and
get
again
like
see
how
folks
and
comms
are
doing
and
like
I,
don't
know
if
I
need
a
column
or
something
yeah.
B
But
Fred
was
the
composite
for
126
and
he's
on
the
call
so
yeah
he
can
weigh
in
I.
Did
there
there
are
a
lot
more
views
that
got
created
from
the
project
board
in
126,
like
after
even
after
enhancements,
freeze
and
I
carried
all
of
those
forward
when
I
created
the
127
board
and
it
looked
like
they
were
used,
but.
G
D
G
Yeah,
sorry,
it's
my
my
first
time
but
I
just
wanted
to
say,
like
there
seems
to
be
sort
of
a
communication
sprawl
between
the
Google
groups
and
the
slack
chat
and
the
emails
and
the
meetings
and
everything
and
I
was
just
hoping
for
maybe
some
way
to
understand
where
I
should
go
for
things
or,
if
I'm,
even
missing
a
form
of
communication.
That
would
be
beneficial
to
me
because
I
don't
know.
A
D
There's
there's
not,
maybe
maybe
there
should
be,
but
then
it
kind
of
I
don't
know
becomes
difficult
to
Define.
What
kind
of
conversation
is
appropriate
in
which
which
Avenue
like
in
my
experience,
the
slacks
are
generally
for
less
formal
or
more
time
sensitive
conversations
specific
to
like
releases
or
caps.
G
A
F
B
G
A
Well,
we
can.
We
can
bring
that
one
up
in
the
next
retro.
We
can
add
it
as
an
item
to
discuss
in
in
part
two.
We
are
very
nearly
at
the
end
of
a
time
anyway.
We
technically
have
about
three
minutes
left
excited
to
fit
everything
in
all
right
and,
if
ever
points
anything
else,
anyone
would
like
to
bring
up
anything
I've
missed
before
we
we
end
for
today.
A
No
all
right,
in
which
case,
thank
you
very
much
everyone
for
coming.
Thank
you.
Thank
you
to
everyone
who
contributed
to
this
speech
interaction
discussion.
Thank
you,
Laura
for
taking
some
excellent
notes
and
action
items
during
this
thing
and
yeah
I
will
stop
the
recording
now,
once
I
find
the
button.