►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20211112
Description
Kubernetes Release Team Bi-Weekly Meeting for 20211112
A
A
This
is
the
apac
eu
focused
meeting,
and
this
is
week
12
of
the
release
before
we
begin
I'd
like
to
remind
everyone,
this
meeting
is
recorded
and
will
be
uploaded
to
youtube
when
we're
all
done,
and
also
this
meeting,
as
with
all
of
our
meetings,
is
covered
by
the
kubernetes.
Sorry,
the
cncf
code
of
conduct.
So
everyone
please
be
mindful
of
your
interactions
with
everyone
today.
A
So
just
first
thing:
let's
get
on
with
open
discussion
items
ray,
has
an
update,
which
is
to
remind
everyone
that
friday
burn
down
meetings
start
next
week.
We've
had
a
little
bit
of
issue
with
some
people
having
these
filtered
into
spam,
folders
or
not
being
delivered.
A
A
We
also
have
our
general
standing
updates
about
adding
things
to
the
release
retrospective
document.
If
there's
anything
you
can
think
of
other
than
that,
does
anyone
have
any
general
updates
or
comments
I'd
like
to
make
navaroon
you're
holding
you
raise
your
hand.
B
So
I
I
had
a
question
regarding
the
spammy
invites
so
it
happens
almost
every
release
cycle,
because
the
release
lead
sends
an
email
to
so
many
people.
Someone
may
have
like
mark
this
marketers
man.
So
one
of
the
ways
I
think
you
can
do
is
you
can
add
it
to
the
release
team
calendar
and
ask
everyone
to
subscribe
to
that
calendar.
A
B
Just
an
idea,
you
don't
need
to
send
invites
individually.
A
Yeah:
okay
I'll
mention
that.
A
A
Okay,
all
right,
thank
you
much
nevermind
anything
else
for
anyone.
A
Nope
all
right,
then,
thank
you
for
that
idea.
I
think
it's
probably
a
good
one.
I'm
still
surprised
that
we
use
email
for
invites
these
these
days,
but
here
we
are:
let's
move
on
to
sub
project
updates
enhancements.
Do
we
have
anything
from
enhancements
here.
C
Yes
I'll
do
the
update,
hi
everyone.
The
overall
status
of
the
enhancements
team
is
green,
same
update.
We
have,
we
are,
as
per
the
code
freeze,
coming
closer,
we
have
started
reaching
out
to
the
enhancements
owner
to
remind
them
of
the
code
freeze
and
checking
if
all
the
prs
are
in
place.
C
Based
on
the
current
progress,
we
have
started
marking
some
of
the
enhancements
that
has
at
risk,
so
the
number
is
still
changing,
we'll
see
more
or
less
in
at
risk
status.
Currently
we
have
39
tracked
and
17
marked
at
at
risk.
Yeah,
that's
all
the
overall
status.
Thank
you.
A
That's
great,
thank
you.
So
much
is
there
anything
that
the
least
lead
team
or
anyone
can
do
to
to
help
with
this?
Are
you
just
kind
of
watching
and
monitoring
at
this.
C
Time
at
the
moment,
we
have
just
reached
out
to
owners
on
the
github
issues
only
and
we
are
still
receiving
some
asynchronous
updates
from
the
owners.
There
is
no,
I
mean
at
the
moment.
We
do
not
need
any
help,
but
definitely
will
reach
out
if
there
is
any
requirement.
Thank
you.
A
Excellent,
no
problem,
okay,
thank
you
very
much.
Does
anyone
have
any
questions
for
enhancements.
A
No,
in
that
case,
thank
you
very
much
for
that
update.
We
will
move
on
to
ci
signal.
D
Hi
folks,
so
the
current
status
of
the
ci
signal
team
is
yellow
for
master
blocking.
We
have
six
flaky
jobs
and
two
of
them
are
consistent
and
we
have
issues
for
both
of
them
and
are
tracking
them
in
master
informing.
We
have
two
failing
jobs
and
12
flaky
jobs
for
the
both
the
failing
jobs
for
one
the
pr
has
been
made
and
for
the
other
one.
A
D
B
I
have
a
question
from
a
branch
point
of
view.
What
is
your
thought
looking
at
this
week's
test
grid
like?
Would
we
be
able
to
cut
on
tuesday
it's
three
or
four
days
a
week?
That's
why
I'm
asking.
D
E
So
basically,
yeah
informing,
you
know
dashboard,
so
we
have
only
one
failing
the
other
one
should
be
fixed
soon,
because
it's
basically
it's
a
calico
upgrade
problem
yeah
caused
by
new
category
release,
but
the
other
one
shouldn't
be
a
problem
yeah.
It's
a
long-time
cigar
storage
topic,
but
generally
we
are
in
good
shape
for
new
release,
cut.
B
Awesome
thanks:
I
was
just
worried
about
about
the
sick
storage
test
on
master
informing.
Do
they
need
any
help
from
our
site
like
identifying
the
bug.
E
Yeah,
we
appreciate
any
help.
If
you
we
can
ping
some
guys
or
girls
from
the
storage.
But
generally
you
know
we
opened
one
issue
in
the
past
and
then
it
was
fixed
and
then
new
issue
came
up
so
and
it's
related
to
an
old
park
from
six
storage
and
we
are
continuing
closely
with
them.
But
we
appreciate
any
further
helps.
B
A
Cool
all
right.
Thank
you
very
much
navarro.
Thank
you.
Everyone
for
update,
if
we
have
nothing
further
for
ci
signal,
nope
go.
Thank
you.
Everyone
bug
triage.
F
Yeah,
hello,
everyone,
so
the
current
status
is
green
as
we
do
not
have
any
critical
issues
so
far
or
pr
so
far
and
the
as
you
can
see.
We
have
current
16,
open
and
flaking
issues
and
overall
we
have
like
20
open
issues
for
our
virgin
v1.23.
A
Okay,
all
sounds
pretty
good.
Thank
you
very
much
for
the
update
any
questions
or
comments
for
a
bug
reaction.
A
No
all
right,
thank
you
very
much.
Moving
on
docs.
G
So
hello,
everyone,
since
last
week
there
are
a
few
more
pr's
rolling
in,
and
things
are
picking
up.
So
we
are
hoping
to
get
some
of
this
landed
ahead
of
the
guidelines
and,
yes,
we
have
tried
56
enhancements
from
which
48.
E
G
Docks
and
eight
don't
need
dogs
and,
yes,
seven,
are
ready
for
review
and
we
have
mars
five
years
already
and
yes
at
last,
integration
branch
is
healthy.
So,
yes,.
A
Excellent,
that's
good
to
hear.
I
saw
that
in
rey's
email,
that's
went
out
which
we'll
talk
about
a
little
bit.
There
was
a
note
about
the
docs
deadline
as
well
in
there,
because
that
shortly
follows
code.
Freeze,
I
believe
right
any
questions
for
docs.
A
H
Yeah,
so
hey
everyone,
this
week's
status
for
release
notes
is
yellow
because
one
of
our
shadows
had
created
a
pr
for
the
alpha
cut
four,
but
that
seemed
to
had
some
oddities
and
that
was
closed
and
we
are
working
for
creating
another
pr
and
that
would
be
created
like
really
soon.
A
Yeah,
that's
that's
pretty
good
yeah.
I
saw
the
other
pr
come
through.
I
didn't
get
a
chance
to
review
it
yet,
but
if
it's
been
closed,
that's
fine.
Do
ping
me
when
the
next
one
is
open
and
we
can,
we
can
take
a
look
and
try
and
figure
it
out.
A
A
A
B
Yeah,
we
are
pretty
much
the
same
status
since
yesterday.
We're
still
monitoring
a
signal
that
looking
forward
to
a
signal
from
the
team
for
next
week's
branch
current,
so
more
updates
probably
will
have
better
judgment
on
whether
we
will
cut
the
release
order,
but
since
beta
not
much
risk
so
yeah.
A
Great
okay,
that's
good
to
hear
any
questions
for
release
branch
management.
A
No
all
right
well,
thank
you
very
much
for
the
update.
Moving
on
jeremy
hasn't
left
us
anything
and
isn't
on
the
call.
So
I
don't
believe
he
has
any
updates
release
lead.
I
have
some
updates
from
ray.
As
I
mentioned,
we
had
an
email
go
out
yesterday
to
the
community
about
the
upcoming
code,
freeze,
which
also
mentioned
the
docs
deadline.
A
Shortly
afterwards
we're
going
to
send
another
one
out
the
day
before
code
freeze
next
week,
there's
been
a
final,
a
final
poke
things
do
get
a
little
bit
busy
around
about
code.
Freeze
usually
so
this
might
be
a
bit
interesting
over
the
next
couple
of
days
and
early
next
week,
but
I
think
we,
it
certainly
looks
like
we're
in
a
pretty
good
shape.
So
that's
all
good.
A
I
don't
have
any
updates
from
from
ray
and
then
finally,
six
scalability
has
given
us
a
status
of
green
from
wednesday,
which
is
pretty
good.
Does
anyone
have
anything
else
to
mention
before
we
end
the
recording?
I
think
that's
everything
on
our
agenda.
B
And
then
trying
to
get
people
to
respond
to
you
over
the
course
of
my
time
in
the
release
like
release
cycles
over
the
years,
it
has
been
one
of
the
biggest
issues
and
a
lot
of
mental
energy
gets
drained
because
of
this.
So
I
thank
everyone
who
is
communicating
with
the
other
six
and
trying
to
get
some
response
from
them.
Enhancements
ci
signal
talks
forms
everywhere,
not
just
specific
teams.
Here.
A
Yeah,
a
huge
plus
one
to
that,
it's
always
it
it
can
be
challenging
at
times
to
to
get
responses
from
people
just
because
everyone's
so
busy
someone's
fault
just
is
what
it
is.
But
thank
you
everyone
for
your
efforts
here,
especially
as
we
approach
approach,
code,
freeze
and
and
ultimately
towards
the
end
of
this
cycle.
A
With
that,
I
think
we're
good.
So
I'm
going
to
end
the
recording.