►
From YouTube: Kubernetes 1.19 Release Team Meeting 0200624
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
and
welcome
to
the
Wednesday
burndown
meeting.
It
is
week
11
and
today
is
June.
24Th
pumpkin
I'll
be
the
host
first
meeting.
Just
as
a
reminder.
We
are
under
the
C
and
C
of
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other,
with
that,
let's
get
right
into
right
in
the
meat
of
things
and
kick
off
with
enhancements.
B
A
C
Folks
hope
everyone
is
doing
well,
so
we
don't
have
too
many
changes
from
Monday,
but
a
couple
updates.
We
do
have
a
couple
more
flaking
tests.
Most
of
them
are
not
much
of
an
issue,
though
the
conformance
GA
only
flakes
we
haven't
seen
any
sense.
Pyaare
bumped
the
CPU
requests
for
those.
So
looking
better
there.
It
should
report
green
pretty
soon.
The
new
flicks
are
on
skew
cluster
latest
and
they're
pretty
infrequent,
but
it's
a
CLI
test,
so
pinged
cube
control,
folks
to
take
a
look
at
that,
but
once
again
that's
not
happening
too
frequently.
C
The
other
thing
that's
different
from
Monday
is
verify.
Master
is
reporting
flaky
now,
which
is
a
bit
of
a
misnomer,
because
it
was
actually
failing,
but
hadn't
reported
so
on
Monday,
but
we
just
bumped
the
static
check
version
which,
if
you've
had
any
periodic
s--
that
are
running
verify
master
you've,
probably
seen
this
flaking
on
your
PRS
and
it's
been
very
frustrating,
so
we
haven't
seen
any
flakes
since
that
was
on
master
blocking
and
I
should
also
probably
help
with
some
of
your
PRS
as
well,
so
that
should
also
be
reporting
green
soon.
C
The
other
update
is
in
the
section
needs
to
be
changed,
so
if
I've
failing
now
on
master
informing,
so
there
is
a
some
new
failures
on
master
scale
performance
just
start
failing
yesterday.
This
runs
once
a
day,
so
it's
a
bit
hard
to
get
inside
into,
but
it
has
failed
twice
in
a
row
now
and
there
are
some
changes
so
pegged
pinged
sakes
scalability
this
morning.
Otherwise
the
other
jobs
OpenStack
now
has
a
PR
open.
C
E
Hey
everyone,
we
are
currently
green
and
we
are
currently
tracking
31
PR
and
six
of
them
are
ready
for
review.
Do
we
have
a
few
more
to
just
wait
for
and
we
have
been
reaching
out
for
the
deadline
for
the
upcoming
PR
ready
to
be
reviewed
deadline
and
we
did
come
across
a
question,
but
I
think
Bob
is
going
to
cover
it
during
his
update
right
honestly.
E
So
the
question
was
I
one
of
the
person
that's
working
on,
buy
enhancement
reached
out
to
us
and
asked
about
the
deadline
for
PR
ready
to
be
review
which
is
currently
set
to
before
the
code
freeze,
but
from
last
release
and
releases
before
it's
always
been
after
the
code
truth.
So
there
was
some
confusion
there
and
I
reached
out
to
sweep
out
the
docs,
lead
and
I
think
they
reached
out.
E
A
Actually,
Jeremy
I
think
you're
sort
of
on
top
of
this,
if
you
don't
mind
just
shorter
for
this
over
to.
F
You
so
this
one,
we
probably
missed,
bumping
that
one
Doc's
it
because
there's
two
right:
there's
the
one
where
the
pr's
are
ready
for
review
and
them
Docs
are
complete,
which
comes
after
pr's
ready
for
review.
I.
Think
at
this
point,
there's
not
much
point
in
us
making
a
PR
to
the
schedule
to
bump
it
again
and
like
notifying
everybody,
so
I
would
just
I
think
it's
gonna
resolve
itself
either
way.
F
There's
only
three
days
between
the
PR
is
ready
for
review
and
code
freeze,
so
hopefully
nothing
major
changes
between
then
I'm,
probably
good
to
know
if
it
does
and
I
think
that
at
this
point,
just
encourage
them
to
have
the
the
PR
is
ready
for
review
as
much
as
possible
by
that
that
date,
that's
right
before
code
freeze,
but
we're
not
gonna
push
anybody
or
kick
anybody
out
of
the
release
because
they
didn't
hit
that
date.
I
think
it'll,
look
the
the
PR
is
ready
and
like
dun
dun.
A
G
G
F
A
F
H
I
Cool
release
notes,
hi
Ron,
so
a
current
status
ranked
the
generation
of
the
notes
is
green
as
well,
since
there
have
enough
changes,
but
we
also
have
the
same
issue
with
the
dates
that
came
up
during
yesterday's
talk
about
that.
So
we
need
to
push
her
our
dates
of
contacting
the
Stiglitz
back
two
weeks
and
generating
the
Google
Doc
also
back
two
weeks,
but
we
haven't
started
anything
so
there
should
be
no
no
changes
and
also
the
only
thing
we
have
to
do
is
to
update
the
the
handbook.
A
H
Alright,
so
far,
everything
is
good.
We
are
in
contact
with
the
CN
CF
discussing
about
locking
some
dates
for
webinars
and
interviews,
and
whatever
else
will
be
after
this
really
long
release
cycle.
Maybe
there's
a
little
bit
higher
effort
to
have
some
discussions
about.
It
is
that
this
release
release
block
as
as
a
draft
shared,
also
with
Taylor
and
enhancement,
and
also
was
the
CN
CF
team
and
the
way
it
was
a
basically
shifted
timeline.
A
A
How
they
jelly
an
update
is
generally
a
good
update.
Yeah
with
that
I.
Don't
think
Tim
is
online,
there's
nothing
there
for
an
emeritus
update,
which
puts
it
over
to
me
for
the
really
slight
update.
The
big
thing
was
the
the
docs
thing
which
we
sort
of
already
discussed.
Then,
as
the
general
reminder,
we
have
code
freeze
until
July
9th
and
then
the
July
16th
as
the
follow-up
Doc's
date.
A
Next
is
the
six
scalability
updates
I,
don't
think
any
of
them
are
actually
on
the
line,
but
just
they
have
the
comments
that
these
get
ability.
Jobs
look
good
and
they
have
no
regrets
at
regressions
as
of
now,
and
that
takes
us
over
to
open
discussions.
There's
nothing
currently
there,
but
is
there
anything
people
want
to
discuss.
B
K
Alright,
so
now
I
am
putting
them
here,
so
this
really
quickly
so
that
everyone
has
idea
of
follow
up
on
the
prioritization
sessions
over
the
weekend,
I
took
all
of
the
comments
from
our
spreadsheet
and
put
them
in
a
magical
document.
So
now
they
are
kind
of
in
a
narrative
format,
and
the
next
step
is
kind
of
up
to
all
of
you.
I
put
a
comments
in
the
channel
over
the
weekend.
Just
to
say,
I
was
that
I
created
this
document.
K
I
will
throw
it
in
the
a
chat
so
that
everyone
can
see
it,
but
basically
we
kind
of
have
little
roadmaps
forming
now
around
the
topics
that
we
discussed.
So
what
do
we
do
next?
That
would
be
my
question.
So
I
don't
know
if
anybody
has
bound
with
to
actually
take
a
more
active
role
in
answering
that
question
or
driving
some
discussion
in
the
group
so
that
we
can
set
up
maybe
the
next
round
of
smaller,
shorter
breakout
sessions
or
approach
this
in
a
different
way.
K
But
if
you
would
like
to
be
a
part
of
driving
that
prioritization
sessions
discussion,
then
please
put
your
name
in
the
chat
and
I
will
follow
up
with
you
after
this
meeting.
I
also
want
to
call
out
that
we
have
a
specific
dock
around
the
tool
that
Jeremy's
been
working
on,
so
there
was
up
to
our
merge
last
week.
That
was
some
great
progress
and
I
think
now
we're
going
to
we're
talking
about
having
a
meeting
to
discuss
these
there's
a
bunch
of
user
stories
in
this
talk
that
I
just
shared
like.