►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20211123
Description
Kubernetes Release Team Bi-Weekly Meeting for 20211123
A
All
right,
everyone
welcome
to
a
kubernetes,
123
burn
down
meeting.
This
is
tuesday,
the
23rd
of
november
2021,
and
this
is
week
14
of
the
release.
A
Can
I
please
ask
everyone
to
note
down
their
attendance
in
the
attendees
list
on
the
notes
which
you
could
find
in
the
normal
place,
and
just
before
we
do
get
started.
I
want
to
remind
everyone
that
this
meeting
has,
with
all
of
our
meetings
covered
by
the
cncf
code
of
conduct.
So
please
refer
to
that
in
all
of
your
interactions
here
with
us
today,
all
right,
then
we
have
a
couple
of
open
discussion
items.
A
First
of
all,
ray
is
absent
today,
unfortunately,
he
has
a
few
notes
from
me
further
down,
but
in
particular
I
reminded
everyone
that
thursday's
meeting
this
week
is
cancelled
due
to
a
u.s
holiday,
which
is
thanksgiving
this
week
and
because
we
have
our
standing
open
discussion
item
of
please,
if
you
can
think
of
anything
to
add
to
the
retrospective
document,
please
do
add
that
as
we
go
along
does
anyone
else
have
anything
else
to
discuss
as
part
of
our
open
discussion
items
before
we
move
on
to
some
project
updates.
B
Yes,
nothing
really
significant
to
report
today,
like
no
change
from
yesterday
were
green,
all
active
exception
requests
have
been
addressed
and
and
they've
gotten
their
prs
merged.
So
at
this
point,
we're
green
and
just
waiting
to
see
if
there
are
additional
exception,
requests
that
surface.
A
C
D
Hello,
so
we
are
currently
yellow
so
yeah
due
to
two
failing
tests
in
mastering
forming,
so
we
have
one
less
failing
test
in
mastering
farming,
so
that's
the
good
news
yeah,
so
in
master
blocking
we
have
no
failings.
So
that's
a
really
good
and
green
light
for
the
current
release
cut
it's
happening
today
and
beside
that
yeah.
One
of
those
failing
tests
master
informing
just
got
a
pr
as
I
posted
there,
so
the
pr
is
open
and
hopefully
that
will
fix
the
failing
issue.
D
We
also
attended
in
the
release
engineering
meeting
today
with
lille,
so
yeah.
Then
we
went
through
this
discussion
about
like
how,
generally
you
know,
the
ci
signal
tool.
D
A
Excellent.
Thank
you
so
much
for
your
update.
Does
anyone
have
any
questions
or
comments
for
ci
signal.
A
C
Good
evening
hi,
I'm
currently
on
the
go
to
apologies.
For
the
background
noises,
our
current
status
is
yellow.
The
reason
for
this
is
that
we
still
have
a
couple
of
critical
issues
open
as
well
as
some
critical
pr's.
C
A
No
all
right
well,
thank
you
christoph.
We
will
keep
an
eye
on
those
things,
but
it's
looking
pretty
good
docs
jesse.
You
run.
E
I'm
actually
just
I'm
updating
things
as
we're
talking,
so
we
started
the
meeting
today
at
75
green
we're
more
like
86
green.
Now,
let
me
actually
see
yeah
we're
doing
we're
doing.
Okay,
so
today
is
the
docs
ready
for
review
deadline.
We
have
been
working
on
a
set
of
placeholder
pr's.
E
We
got
them
all
in
on
that
deadline
minus
one,
but
that
came
in
later
and
right
now
we're
trying
to
whittle
down
from
our
11
we're
now
at
seven,
which
is
good
and
we
expect
more
to
be
coming
in.
We
are
now
yes,
81
green.
I
will
be
accurate
and
green.
Just
means
we're
sort
of
ready
to
review
or
already
merged,
and
so
yeah
they're
they're
coming
in
we're
working
really
well
with
with
sig
docs
and
other
reviewers
the
integration
brand.
E
This
branch
is
healthy,
just
calling
out
everybody
looks
at
it.
We
do
have
that
easy,
cla
issue
where
it
looks
like
a
hot
mess,
but
everything
is
okay
and
yeah.
We're
working
towards
end
of
business
today,
having
everything
in
for
review
and
next
up
is
docs
ready
for
november
30th.
We
are
right
now
green,
just
keeping
in
mind
that
that's
a
very
tight
turnaround,
so
hopefully
we're
gonna
keep
on
trucking
and
yeah.
That's
it.
E
A
Okay,
yeah,
okay,
thanks
jesse
is
there
anything
that
we
can
do
to
help?
If
you
need
any
assistance
or
anything
do
let
us
know
it
sounds
like.
A
F
A
Excellent.
Thank
you
so
much
susie
any
questions
for
anyone.
A
G
Okay,
we
are
mostly
green,
I'm
finishing
up
our
release.
Vlog
draft
take
a
look
there.
It's
mostly
done
we're
just
using
a
few
more
details
that
I
need
to
lock
down
today,
but
I'm
hoping
to
have
this
done
by
end
of
day
and
then
in
terms
of
our
future
blogs,
the
volume
popular
data
source
blog
post
is
getting
dropped.
I
had
to
follow
up
with
them
yesterday
and
it
sounds
like
they're
aiming
for
1.24,
so
that
leaves
us
with
a
total
of
six
feature
blogs.
A
Perfect
fellas
great,
thank
you
so
much
does
anyone
have
any
questions
or
comments.
A
Nope
all
right,
thank
you
very
much.
Canon
release
french
management.
H
Yeah
well,
she
they
barrenka,
came
on
the
releasing
during
meeting
and
give
an
overall
update
so
they're
preparing
to
cut
the
release.
H
The
last
I
heard
from
them
is
that
veronica
is
going
to
start
the
work
and
then
hand
it
over
to
nebrun,
but
so
far
seems
to
be
going
everything
as
planned.
But
if
I
know
anything
I'll
update
on
the
channels.
A
A
No
okay,
all
sounds
good
great.
Thank
you,
adora.
I
don't
have
anything
from
jeremy
and
I
don't
believe
he's
on
the
call.
So
I
will
move
on.
I
have
some
things
from
ray.
Today
is
a
big
day.
We
have
a
lot
of
milestones
going
on
several
of
ben
have
alluded
to
already,
of
course,
we're
doing
a
branch
cut
as
mentioned
before
and
creating
the
release,
jobs
and
we're
cutting
the
release,
which
is
our
first
release
candidate.
A
We
also
have
test,
freeze
and
docks
ready
for
review,
as
mentioned
and
the
final
draft
release
notes
and
the
release
vlog,
as
mentioned
in
the
previous
parts
of
the
update,
so
a
lot
going
on,
so
it's
good
to
see
that
we're
in
a
good
state
for
all
of
that,
from
what
I
could
tell
and
yeah
just
another
note
about
the
draft
from
from
ray
there
yeah.
I
don't
have
any
questions,
questions
from
me
on
any
of
that.
A
No
okay,
then.
Finally,
we
just
have
a
a
green
update
from
because
six
scalability,
which
is
you
know,
no
use,
is
good
news
in
some
ways.
All
right,
then
I
think
that
is
everything
on
our
agenda.
Does
anyone
have
anything
else
to
discuss
or
bring
up
before
we
end
the
recorded
part
of
this
meeting.