►
From YouTube: Kubernetes Release Bi-Weekly Team Meeting For 20220328
Description
Kubernetes Release Bi-Weekly Team Meeting For 20220328
A
A
A
If
you
are
with
us
in
this
meeting,
can
you
please
add
yourself
to
the
attendees
list
and
I
will
quickly
move
on
to
open
discussion
items
we
do
have
one
which
added,
which
is
that
this
week
we
are
beginning
daily,
burn
down
meetings,
that's
daily
work
day,
not
daily
forever.
You'd
have
to
do
this
in
the
weekends,
so
we
will
be
adding.
I
haven't
added
them
yet,
but
I
will
be
adding
meetings
to
the
calendar
for
thursday
and
tuesday.
A
My
current
intention
is
to
put
the
tuesday
ones
at
11am
utc,
which
is
the
kind
of
more
apac
eu
friendly
time
that
we
use
for
the
friday
meetings
and
then
at
the
thursday
ones,
at
the
normal
1600
utc,
which
is
the
same
as
this
meeting.
Another
thing
is
for
for
friends
in
in
europe.
Europe
most
of
europe
has
now
entered
daylight
savings
time,
and
so
the
meetings
will
adjust
for
them
as
well
all
right
with
that
thing.
B
Hello,
everyone
enhancement,
current
status
is
green.
We
have
29
tracked
and
ready
to
go
for
code
freeze,
a
handful
of
enhancement
have
opted
out
and
it
has
been
marked
as
such
on
our
sheet.
So
just
like.
I
think
doc
should
be
aware
of
that.
We
have
enhancement
meeting
this
thursday
under
sick
architecture,
to
discuss
the
new
progress
and
what
we
want
to
do
with
that.
B
A
A
C
Hi
I'm
reporting
for
ci
signal
this
week.
I
am
a
ci
signal
shadow
and
I'm
also
the
ci
signal.
Go
no
go
representative
for
the
release
cut
this
wednesday.
I
put
our
status
as
green.
We
have
no
failing
tests
right
now,
there's
a
one
flake
on
master
blocking
that
I've
called
out,
which
is
a
flaky
test
that
has
been
open
for
a
long
time.
We've
mentioned
other
meetings
too,
but
thank
you
to
sign
network
for
mentioning
that
this
is
not
a
meaningful
release.
Blocker.
C
So
we're
not
considering
this
an
issue
for
wednesday's
release
cut,
and
then
I
also
just
wanted
to
highlight
that.
There's
an
issue
open
for
the
go
118
update,
at
least
from
ci
signals
perspective,
there's
no
tests.
The
integration
tests
are
no
longer
failing.
So
it's
not
an
issue
for
the
for
the
release
or
for
the
release
on
wednesday.
C
C
And
I
think,
if
I
was
following
correctly,
like
the
tests
are
passing
from
some
like
sort
of
workaround,
like
maybe
environment,
variable
change
or
something
but
for
actual
124
release.
The
people
who
are
talking
on
it
seemed
to
need
or
require
want
to
require
something
from
118
one,
so
yeah,
I
think,
most
immediately.
I
just
wanted
to
bring
it
up
about
regarding
this
week's
beta
release
candidate,
which
I
think
it's
probably
not
a
blocker
but
just
confirming
with
the
group
and
then
if
that
needs
to
be
flagged
more
important
in
any
situation.
A
D
D
A
D
A
E
Not
a
question,
but
probably
something
that
you
should
note.
I
saw
that
those
four
issues-
jordan,
labelled
them
as
release
blockers.
I
think
we
should
seek
one
small
clarification:
whether
these
are
blockers
for
the
beta
release.
Only
I
believe
they're,
surely
blockers
for
rc,
but
for
media,
I'm
not
sure,
and
there
are
four
of
them,
which
are
attacked
as
a
bliss
blockers
by
jordan.
F
A
G
All
right
current
status,
I
think
we
are
yellow.
We
are
moving
in
a
good
direction.
We've
moved
some
prs
from
from
draft
pr
to
ready
to
review
and
move
something
into
completed,
but
with
the
placeholder
deadline
being
four
days
away
and
we
still
have
18
without
a
pr,
placeholder
or
otherwise.
I'm
still
a
little
bit
concerned.
We're
we're
in
a
good
we're
in
a
good
position.
I
think
we're
yellow
trending
green,
the
docker
shim
removal
project.
G
The
docs
removal
project
continues
it's
also
in
a
fairly
good
spot.
We've
had
some
movement
there
and
just
based
on
grace's
comment
earlier
in
this
meeting.
I've
got
to
go
through
and
double
check
that
all
the
caps
that
have
been
removed
from
the
milestone
are
also
no
longer
being
reflected
in
our
stats.
Here.
A
H
H
A
F
I
think
I've
peppered
every
channel
a
lot
in
the
last
couple
of
weeks,
but
I
think
we
need
to
reach
out
to
individual
owners
either
on
the
issues
themselves
or
directly
via
slack
aside
from
that,
we
are
finalizing
the
removals
blog.
This
week
we
got
some
good
feedback
on
the
blog
content,
and
so
that
will
ship
out
on
thursday,
the
31st.
A
F
F
A
I
A
A
No
all
right!
Thank
you.
I
don't
see
joseph
on
the
call
and
I
have
a
particular
update
from
him.
So,
let's
get
over
that
to
me,
as
I
mentioned
before,
daily
burn
down
start
from
today,
I'm
gonna
send
out
the
invites
in
a
bit
I've
drafted
the
final
reminder:
email
for
code
freeze,
I'm
going
to
send
out
tonight
of
this
evening,
depending
on
your
perspective,
which
will
be
24
hours
ahead
of
ahead
of
code
freeze.
That
draft
is
in
the
slack
channel
if
you're
happy
with
it.
A
A
Oh
and
one
other
thing
I,
along
with
some
staff
from
the
cncf,
did
an
interview
with
a
reporter
about
124.
It
was
quite
short
about
124
and
docker
shim
as
well.
So
that's
sounds
like
the
press.
Side
of
things
is
picking
up,
which
is
all
very
interesting,
so
yeah
and
I
have
no
particular
update
from
success.
Do
anyone
have
any
questions
for
me.
B
A
A
I
will
endeavor
once
we've
got
a
fully
finished
version
of
the
logo
to
try
and
get
all
these
stickers
out
and
some
other
stuff
exactly
what
this
will
look
like.
I
don't
know,
but
I
will
endeavor
to
get
everyone
something
depending
on
what
I
can
get.
So
we
will.
We
will
see
how
this
goes.
I
may
fail
with
this
endeavor,
but
I
will
try
my
hardest.