►
Description
Kubernetes Release Team BI-Weekly Meeting For 20220419
A
A
A
If
you
are
an
attendee,
please
note
yourself
down
on
the
attendees
list,
other
than
that
we
will
start
with
open
discussion.
I
don't
think
we
have
any
particular
items
there,
although
I
do
have
one
thing
to
mention,
which
is,
I
believe
since
last
week
the
shadow
application
for
the
125
release
for
next
release
has
gone
out.
So
if
you
are
not
a
lead
on
the
next
release,
then
you
should
submit
a
shadow
application
if
you
wish
to
shadow
again.
B
C
So
yeah,
hello,
everyone.
We
have
zero
feeling
on
the
master,
blocking
and
no
release
blocker
issue
as
of
the
current
movement.
So
that's
why
our
current
status
is
breathing
and
we
are
good
to
go
for
the
today's
release
cut
beside
that.
We
have
three
flakes
on
the
master
blocking
one
sailing
on
the
master
informing
which
we
have
already
reported
and
five
clicks
on
the
master
forum
so
yeah.
That's
it.
D
Yeah,
so
our
current
status
is
yellow.
We
have
no
blocking
issue
dot
prs,
just
two
issues
are
there?
One
is
the
one
point.
Two
four
release
notes
issue
and
the
other
is
the
signal,
critical
important
issue.
So
the
signal
issue
there
is
no
like
pr
which
will
close
it.
There
are
a
couple
of
pr's
in
it,
but
it's
still
like
seems
in
state
of
discussion
and
investigation.
So
that's
why
we
have
cryptography.
A
A
A
Okay,
the
last
update
in
threads
in
slack
back
on
on
thursday,
I
think,
was-
was
positive.
I
know
that
they
have
a
doc's
docker
shim
meeting
this
afternoon,
I'll
be
along
too
so.
Hopefully,
they'll
they'll
have
a
little
bit
more
detail
there,
but
I
think
things
are
okay:
over
in
docksand
moving
on
release,
notes,
proof.
C
A
C
E
Hey
everyone,
so
we
are
green
right
now.
I
checked
that
there
are
no
release
blocking
issues
also,
as
we
saw
in
the
bacteria's
updates.
We
don't
have
anything
else.
I'll
still
wait
for
a
formal
go,
no
call
signal
from
the
cia
signal
team
just
in
case
if
something
goes
wrong
before
six,
like
in
in
one
hour
and
twenty
minutes.
E
A
A
A
I
just
need
to
get
the
vectors
together
and
a
couple
of
other
bits,
I'm
probably
going
to
share
it
with
the
team
lead
and
release
and
lead
shadows
first
and
then
can
I
go
from
there
and
I
imagine
that
like
comes
and
releases
notes,
we
need
to
see
it
before
others
in
general,
I'm
probably
not
going
to
do
a
public
announcement
or
anything
until
the
actual
release
day,
because
that
seems
to
be
what
we've
done
in
the
past,
but
yeah.
That's
all
fine.
I
think
what
else
we
need
to.
A
A
I
think
we
did
that
in
a
previous
cycle,
and
I
didn't
like
it
very
much
so
I
might
have
to
talk
about
that,
but
yeah
we
can
discuss
that
in
slack
yeah
other
than
that.
We
are
expecting
to
be
on
slack
updates
for
the
rest
of
this
week
until
next
tuesday
yeah
any
questions
for
me
or
anything
else
from
anyone.
Oh
no
update
from
sixth
graders.