►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220411
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220411
B
Yeah,
I
can
see
it
perfectly
thanks.
James
and
hello.
Everyone
welcome
to
our
release
meeting.
We
are
at
week
14
now
on
monday,
11th
april
2022,
and
this
meeting
is
under
the
same
staff
code
of
conduct,
which
could
boil
down
to
place
just
to
be
nice
to
each
other,
and
we
are
supposed
at
the
last
few
weeks
of
the
release
cycle,
so
cheer
up
everyone
and
yeah
as
like.
There
are
only
one
more
topic.
B
C
B
E
D
B
F
Hello,
everybody
and
our
current
status
is
yellow.
We
still
have
this
one
release
blocker,
which
we
all
worry
about,
but
besides
that
everything
is
looking
fine
right
now
we
have
a
lot
of
flaky
tests,
freaky
jobs
on
master
blocking,
as
you
can
see
quite
a
few.
We
are
currently
investigating,
so
we
might
have
a
few
more
issues
coming
up
soon.
I'm
reporting
those,
but
besides
that
it's
looking
fine,
I
guess
we
have
an
eye
on
all
of
those
and
yeah.
B
G
Hello,
everyone,
our
current
status,
is
yellow.
We
have
a
one
blocking
issue
with,
which
is
the
golang
and
another
pr
issue
related
to
the
same
thing
and
the
the
only
issue
it's
still
like
a
bug,
but
so
it's
like
an
important
soon
be
ours,
which
is
related
to
some
tests.
I
believe
so
other
than
that.
Nothing
like
as
a
red
flag,
instead
of
you
know
like
except
except
the
golang
for
sure
yeah.
That's
it.
B
A
Yep,
we
actually
moved
from
yellow
green
to
green
we're
in
pretty
good
shape.
Right
now
we
have
11
that
have
not
merged
yet
11
docs
prs,
but
mostly
we're
looking
for
reviews
and
approvals
right
now.
I'm
sorry
more
approvals
and
lgtms
and
actual
you
know
full
reviews
on
most
of
those.
So
hopefully
we'll
get
that
done
by
the
deadline
which
is
tomorrow.
A
If
not,
it
will
be
close
other
than
that
we
still
have
some
docker
shim
work
to
do
and
the
one
actually
draft
pr,
that's
still
open
is-
is
really
an
umbrella
issue
for
docker
shim.
So
there's
still
several
things
that
need
to
be
done
there,
but
I
think
we're
in
good
shape.
That's
it
cool
sounds
great.
H
B
H
B
B
I
B
E
B
D
And
I'm
in
a
good
mood
on
a
monday,
so
I'll
take
that
as
a
positive.
So
as
we're
getting
close
to
the
end
of
the
cycle,
as
you
probably
noticed,
last
week
we
have
opened
up
the
nominations
for
the
125
release
team.
That's
still
in
progress.
I
think
we
have
one
or
two
areas
where
we
need
to
kind
of
like
solidify
what
what
those
nominations
will
look
like
so
stay
tuned.
For
that
the
other
thing
that
happens
at
the
end
of
the
cycle
is,
I
start
to
work
on
two
forms.
D
One
of
them
is
going
to
be
for
the
majority
of
the
team.
Here,
where
shadows
they
kind
of
find
out
like
what
went
well,
what
areas
could
have
been
improved
but
really
just
it's
a
really
way
for
you
to
discretely,
provide
guidance
to
hopefully
improve
that
next
cycle,
and
then
this
will
also
be
a
separate
form
that
will
be
for
the
release
team
leads.
They
also
play
a
critical
part
in
the
release
team,
and
we
also
want
to
see
how
can
we
take
their?
D
B
E
Not
sure
about
awesome,
but
thank
you,
okay.
So
what
a
couple
of
things
that
come
up
we're
getting
some
clarity
about
a
change
we've
ejected.
This
was
a
code
freeze,
exception
request
and
we
said
no
largely
because
we
wanted
to
focus
on
stability,
but
that
was
predicated
with
the
idea.
It
was
a
bug
fix
and
therefore
it
could
ship
in
124
1..
E
But
there
was
some
question
about
that
because
it
was
tagged
with
kind
feature
which
generally
are
not
accepted
in
patch
releases
and
then
they'd
have
to
wait
to
125
and
they
didn't
want
that.
So
there's
been
some
discussion
about
is
a
bug.
Fix
is
a
feature.
I
think
it
was
tagged
incorrectly
as
kind
feature,
but
there's
just
finding
consensus
that
it's
actually
a
mistake
and
it's
actually
just
a
bug
fix.
E
E
I
just
wanted
to
clarify
for
people
that,
in
the
event
that
the
release
is
delayed,
I
could
appreciate
that
people
may
not
be
able
to
stay
on,
because
you
know
people
signed
on
for
a
15-week
release
and
if
we
end
up
being
16
or
more
weeks,
then
if
people
need
to
like
cycle
off
the
team
because
of
that
early.
That
is
completely
fine.
If,
if
you
have
any
concerns
or
issues
speak
to
your
role,
lead
or
speak
to
joseph
or
myself
about
it,
and
you
know
we
can
help
you
out
but
like
absolutely
no
problem.
E
D
E
Cool
beyond
that,
just
a
couple
of
a
couple
of
small
things:
the
logo
theme
stuff.
I've
been
a
bit
cagey
about
this,
because
you
know
every
lead
is
a
little
bit
spooky
about
the
secretive
about
the
the
theme
and
logo
and
stuff,
I'm
probably
gonna
start
showing
that
at
least
to
the
kind
of
our
leads
over
the
next
couple
of
days.
In
order
to
get
things
ready,
just
in
case
we
do
manage
to
release
some
time,
which
would
be
nice.
E
I
think
I
have
a
final
version
of
the
logo
for
taking
down
somewhere,
which
is
nice,
and
then
I
think
another
piece
of
everything
I
need
to
do
is
produce
the
times
like
doodle
poll
for
the
last
two
retros.
I
don't
think
we
have
time
for
those
yet
any
double
choker
schedule,
because
it's
retro
part
two
retro
part
three,
which
are
after
the
release
and,
of
course,
if
release
gets
delayed,
those
will
need
to
be
moved
so
or
maybe
they
won't
need
to
do
it.
We
need
to
decide.
E
B
E
F
D
E
We're
gathering
the
joy
of
each
other's
company.
No,
no!
I
I
see
the
point
I
see
the
point
I
mean
this
is
something
that's
I
believe.
A
retro
item
is:
do
we
really
need
daily
burn
downs
and
the
answer
is
probably
no
most
of
the
time,
so
it's
just
trying
to
figure
that
out.
Okay,
let's,
let's
make
a
thread
on
sig
release
to
discuss
further,
I
take
this
offline.
I
think
that's
that'd
be
good.
That.