►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200722
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
There
we
go,
we
are
now
recording
today
is
we
are
into
week.
15.
today
is
july
22nd,
and
I
think
things
have
been
a
little
exciting,
but
before
we
dive
in
too
much
into
that,
this
is
the
sorry
119
burn
down
meeting
I'll,
be
the
host
today,
bob
killen
and
just
to
get
the
normal
stuff
out
of
the
way
we
these
calls
are
recorded
and
we
abide
by
the
cncf
code
of
conduct,
which
can
essentially
be
boiled
down
to.
A
Please
be
excellent
to
each
other
with
that,
let's
kick
things
off
with
enhancements.
Labrun.
B
Hello,
everyone,
I
hope
you
all
are
having
an
amazing
wednesday,
so
enhancements
is
currently
yellow
I'll,
come
to
the
reason
shortly,
we
are
tracking
35
enhancements
right
now.
Sorry,
34
announcements
right
now
with
nine
graduating
to
alpha
15
enhancements,
graduating
to
beta
and
10
graduating
to
stable.
B
So
we
had
overall,
two
in
two
exception
requests
over
the
past
10
days
and
we
have
accepted
one
of
the
two
and
rejected
the
other,
the
one
which
has
been
accepted.
The
implementation
pr
has
been
properly
milestone
and
labeled
just
that
the
tests
are
flaking
right
now,
and
this
is
the
sole
reason
that
the
status
is
yellow
for
enhancements.
It
is
kind
of
between
green
and
yellow.
B
I
prefer
to
go
with
yellow
just
to
be
a
bit
more
cautious,
and
one
good
thing
here
is
the
dox
pr
has
been
created
merged
in
the
last
one
day,
so
the
like,
the
velocity
has
been
great
on
that
enhancements
part
and
that's
all
on
my
side,
any
questions,
comments
or.
A
D
Yeah
hi
everyone
so
happy
wednesday,
and
so
today
we
moved
from
red
to
yellow,
and
today
the
there
has
been
a
couple
of
tests
which,
like
so
really
went
green.
So
we
went
green
this
in
last
last
two
days
and
so
in
master
blocking.
We
have
two
failing,
one
of
which
is
gc
cosmos.
Alpha
features
where
dan
tracked
down
the
possible
pr
changes
which
could
basically
introduce
that
failure.
D
On
the
other
side,
we
just
got
a
failure,
a
couple
of
minutes
back
on
confirmation
only
for
which
we
tracked
the
issue
fight
the
issue.
We
have
five
flaky
and
twelve
passing
out
of
which
in
gc
cost
master
scalability
hundred.
We
are
so
there's
an
issue
that
is
ongoing
and
there
are
discussions
going
on,
and
this
is
this
would
be
coming
down
in
1.19
blocking
as
well
now,
moving
ahead
to
master
informing,
we
have
five
failings:
seven
flaky,
five,
passing
and
16..
D
So
in
failing,
we
have
a
cluster
api,
conformance
failure
that
has
been
happening.
So
we
filed
an
issue
and
there
has
been
work
going
on
into
looking
for
the
issue
for
the
cube
adm
kinder
mastered.
There
is
a
potential
pr
that
was
raised
yesterday,
I
guess
and
there's
so.
The
pr
is
open
right
now
and
other
than
that
we
have
the
windows
failures,
which
I
recall
that
dan
looked
into
it,
but
there
was
not
much
update
on
it.
D
Moving
on
to
1.19
blocking
we
have
a
three
flaky
and
12
passing
and
which
is
primarily
like
the
gc
cos.
1.19
thing
that
I
mentioned
earlier
and
ending
with
in
the
1.19
informing.
We
have
the
three
failing
in
which
we
have
the
windows,
failure
and
there's
one
cube,
adm
kind
of
which
I
have
not
looked
into
much,
but
I'm
looking
into
it
on
what
is
wrong
with
it
yeah,
and
we
have
one
passing
in
that
and
five
flicking
yeah.
So
that's
all
from
my
side.
C
Do
those
failures
have
owners
assigned
to
them?
I
see
a
lot
of
issues
around
flaky
tests,
but
most
of
the
issues
don't
have
owners
assigned
who's
driving
resolution
of
those.
D
A
few
of
them
don't
have
owners
so
probably
like
a
few
of
them
were
created
in
last
one
day,
so
we'll
just
create,
maybe
assign
it.
After
this
meeting.
C
Okay,
it'd
be
good
if,
if
all
the
things
that
we
consider
blocking
have
owners
and
those
owners
could
maybe
report
status
back,
the
next
burn
down
that'd
be
helpful.
A
Thanks,
if
you,
if
you
need,
help
sorry
a
little
bit
of
feedback
there,
if
you
need
help
tracking
down
owners,
please
feel
free
to
ping
myself,
taylor
or
jeremy.
A
A
Next
up
bug
triage.
E
All
of
our
all
of
our
numbers
are
down
from
two
days
ago
way
down.
Unfortunately,
I
think
most
of
those
are
probably
prs
that
have
just
been
pushed
until
until
one
1
20..
It's
still
red,
though,
because
you
know
we're
still
pausing
on
code
freeze,
so
hopefully
we'll
get
those
last
eight.
I
think
yeah
eight
open,
pr's,
either
merged
or
pushed
today.
E
F
Hey
everyone.
We
are
green.
We
had
all
our
pr's
merch
done
to
our
branch
and
branches
healthy.
We
did
have
an
exception
that
was
approved
yesterday,
which
number
and
talked
about,
and
the
docs
is
merged
for
that
one
as
well.
So
we
are
green.
G
Hello
release
notes
is
green,
the
markdown
release,
notes
for
rc2
were
were
cut
and
the
pr
was
merged
overnight.
Also,
the
real
notes
website
was
patched
up
to
rc2
as
well,
and
we
continued
to
contact
sick
chairs
to
gather
any
enhancements
for
the
major
themes
for
the
final
release,
notes
and
that's
it
for
me.
A
Awesome,
let's
see
thank
you.
Comms
is
anyone
from
comms
on
the
line
by
chance.
G
Yeah
joseph's
here:
okay,
cool
first,
okay,
congrats
bob
on
your
your
transitions
on
twitter.
Thank
you!
So
nothing's
changed
since
monday.
We're
just
finalizing
the
release
blog,
just
making
sure
that
you
know
everything
is
accurate
and
we're
green.
A
That's
good
to
hear
when
you
get
a
chance
to
do
your
mind,
just
updating
the
meeting
status
or
the
thanks.
H
A
A
So
I
think-
and
I
think
that's
for
the
the
most
part
I
don't
doesn't
there's
any
other
updates
from
sixth
scalability
either.
C
I
know
there
was
an
open
issue
called
out
last
time
around
scalability.
Let's
see
if
I
can
find
okay,
we
go
that
open
issue
is
being
investigated.
C
A
Notes,
okay,
yep
coming
down
two
hours
ago,
so
it's
definitely
still
still
being
looked
into.
Okay!
Well,
I
guess
with
that,
is
there
anything
else
that
people
would
like
to
discuss
or
toss
out
at
this
point
in
time.
C
C
There
are
a
couple
in
there
like
the
go
115
issue
in
pr
which
I
know
will
not
block
governing
master.
It
would
be
good
to
know
of
those
eight
issues
and
two
issues
and
aprs
which
we
consider
to
be
blocking.
Can
we
accumulate
that,
after
this
meeting.
A
A
Well,
okay,
I
think,
with
that
we're
through
everything.