►
From YouTube: Kubernetes 1.14 - Week 11 - Burndown 2019-03-19
Description
B
A
B
C
D
B
C
I
was
a
bit
certain
with
that
too,
because
we
we
started
we
up
with
opening
one
for
all
the
subtle
failures,
but
then,
when
down
the
route
of
like
actually
breaking
them
down
per
driver
and
per
graceful
or
forceful
deletion,
I
think
I,
don't
know
if
that
made
things
better
or
worse,
but
yeah
there's
a
bit
of
okay.
This
much
thing.
B
C
Sort
of
got
them
kind
of
rolled
up.
In
my
I
we
can
talk
about
it,
we
can
definitely
I
cannot
get
up
and
open
an
umbrella
thing
sure
we
can
help
and
hold
up
in
an
issue
if
that
helps.
But
I
am
also
monitoring.
The
polls
pull
requests,
I
think
there
is
one
remaining
and
then
that's
it
for
Jerry
fix
at
least
anyways
yeah
about
that
in
the
meeting
yeah.
B
I
guess
I'll
go
ahead
and
save
the
thing
I,
don't
see
anybody
from
any
she
triage
here
right
now.
That's
my
only
thing,
but
we
can
get
there.
Okay,
so
hi
everybody
know
today
is
Tuesday
March
the
19th.
This
is
the
kubernetes
114
earned
down
meeting
European
time
zone,
friendlies
dition
I.
Am
your
host
Aaron
of
wait?
I'm
not
constantly
I.
Am
your
host
there
in
a
severe
and
you
are
all
being.
B
You
are
all
not
being
jerks,
and
so
that's
how
your
hearing
to
the
kubernetes
code
of
conduct,
which
you
can
go
verify
by
watching
yourselves
on
YouTube
later
once
this
recording
is
posted.
So,
let's
run
through
the
meeting
notes,
which
I
will
paste
in
the
agenda.
If
you
want
to
sign
yourselves
in
and
start
with
Claire
to
talk
to
us
about
enhancements
for
114.
C
So
things
are
looking
better
than
yesterday
and
better
than
the
few
days
before
that
we
last
time
I
checked.
We
had
no
failing
jobs
in
master
blogging
or
114
blogging.
There
is
one
job
failing
in
master
upgrade,
but
it
is
down
to
frequent
flakes
that
we
know
from
previously
and
I
think
most
of
them
are
being
worked
on.
With
the
exception
of
the
resource
usage
fest.
C
Think,
that's
mostly
my
updates
I.
We
talked
a
bit
about
having
adding
a
story
for
the
blog
in
terms
of
CI
signal
and
bug
triage
yesterday,
I'm
still
looking
for
a
little
bit
of
inspiration,
I
was
going
down.
The
path
of
this
is
what
it
looked
like
in
terms
of
issues
and
PRS
and
what
sort
of
areas
we
worked
on
in
terms
of
coverage
and
stability,
so
that
sort
of
the
story
that
I'm
putting
together.
C
C
C
B
It's
it's
just
my
like
anti
spreadsheet
bias
where
it'd
be
cool.
If
we
could
point
people
at
the
board
and
say
like
this
is
the
column
that
describes
all
of
the
like
that
were
watching,
and
then
all
of
those
issues
describe
like
what's
going
on,
but
I
mean
this.
You
know
this
spreadsheet
shows
you
your
scratch
notes
and
maybe
a
little
bit
more
effectively
for
your
purposes.
B
C
It
is
intended
to
be
temporary.
The
only
I
think
I
feel,
like
the
only
content
that
this
makes
it
easier
to
see.
That's
not
just
immediately
visible
from
a
list
of
github
issues
is
kind
of
the,
but
first
of
all
the
type
of
error
that
is
okay
to
see
and
it's
down
to
just
a
flaky
test
setup
and
what,
if
any,
is
the
impact
from
the
release?
If
we
somehow
figure
out
a
way
to
express
that
within
the
board,
then
I'm
definitely
up
for
consolidating
the
I,
also
don't
like
to
have
additional
spreadsheets
around.
B
If
you
don't
mind
me
diving
deep
on
this,
just
for
a
second,
that's
like
all
right,
sorry
for
the
dark
mode
like
there
are
a
lot
of
columns
here.
It's
really
like
a
lot
to
take
in
at
a
glance,
so
I
was
wondering.
If
perhaps
we
wanted
to
merge
these
two
columns
here,
one's
talking
about
waiting
before
resolving
for
just
things
that
had
PRS
and
one's
talking
about
waiting
on
flakes,
and
then
we
have
more
columns
related
to
stuff
that
was
resolved.
B
C
B
Interior
suggestion
of
like
we
want
to
know
like
what
are
our
no
flakes
versus
like
what
are
the
really
bad
ones
to
me.
I
would
say
no
no
like
can
live
in
the
flakes
column.
They
can
have
priority
important
whatever,
but
if
they're
worth
the
bad
ones,
then
we
could
have
the
priority
critical,
urgent
label
applied
to
them,
and
that
way
like
this
column
of
flakes
this
stuff
that,
like
we
know
about,
but
who's
actually
happening.
C
Yeah
I
mean
I
can
talk
a
little
bit
about
what
the
intention
was
with
the
columns
and
then
we
can
also
see
if
this
is
a
good
format
for
us
to
keep
I
kind
of.
Have
it
picking
us
two
separate
things
in
my
head,
so
we
we
set
up
the
board
just
so
it's
easier
for
us
to
keep
an
eye
on
things
as
they
moved
through
the
release,
the
list
that
I
was
going
to
build
next,
it's
just
the
stuff
that
we
didn't
get
to
resolution
with
the
stuff.
That's
still
open
at
this
point.
C
Do
we
know
about
them?
Do
we
know
what
is
okay
to
see
and
do
we
know
what
it's
not
okay,
to
see
kind
of
thing,
you're,
absolutely
right
that
I,
don't
expect
I
mean.
Hopefully
we
won't
see
anything
big,
that's
not
already
present
in
this
board
as
an
issue
somewhere,
the
only
additional
information
would
be.
How
often
does
this
thing
happen?
How
often
this
is
just
like,
for
example,
and
how
much
of
a
reason
does
it
give
us
to
worry?
C
Is
it
something
that
we
know
it's
just
like
Ian
flakes
I,
don't
know
once
every
five
times
and
we
just
expect
to
see
a
timeout
and
it's
fine
or
is
it
something
that
if
we
see
it
happening,
it's
maybe
raise
me
quite
raising
questions
as
to
whether
it's
a
stable
release?
So
that's
the
only
information
that
I
come
and
still
figured
out
how
to
capture
within
sport.
C
B
Totally
fair,
I
think
what
I've
tried
to
do
for
issues
in
the
past
is
just
drop
a
screenshot
of
what
our
triage
stealing
on
a
given
issue
yeah
so-
and
this
was
one
of
the
ones
where
Michelle's
like
hey.
If
you
actually
take
a
look
at
your
screen,
shots
from
triage
you'll
notice
that
most
of
these
new
failures
are
happening
on
versions
of
kubernetes
that
haven't
been
cherry
picked
back
so
when
I
get
it
like,
it's
tough
to
see
at
a
glance
what's
happening.
B
I've
been
trying
to
keep
an
eye
on
the
trickle
of
pull
requests,
like
my
name.
A
little
bit
of
paranoia
here
is
to
make
sure,
like
all
the
pull
requests
are
gone,
that
we
think
need
to
be
merged
in
prior
to
kotha.
So
looks
like
they're
two
outstanding
right
now,
one
of
them's,
not
super
clear
to
me.
I,
will
chase
down
that,
but
yeah
looking
good.
B
Okay,
yeah,
that's
that's
super
helpful.
The
the
order
I've
been
trying
to
walk
through
things
is
like
PRS
first,
because
those
are
important
for
thaw,
then
any
issues
that
are
not
kind,
failing
tests
or
kind
of
like
to
see
if
there's
any
outstanding
like
bugs
or
work
that
remains
to
be
done
and
then
for
failing
test
and
flight.
That's
all
CI
signals
left,
so
I've
been
trying
to
walk
through
the
board,
so
I
never
got
a
color
status
from
you.
Are
you
green
or
yellow,
or
red,
burning?
B
B
B
A
B
D
B
A
B
Okay,
so
next,
let's
talk
comms
I'm,
gonna
scroll
down
to
the
yesterday's
update
and
paste
the
release
blog
in
here,
so
I
have
gone
ahead
and
tried
to
get
approval
from
all
of
the
state
people
that
I'm
aware
of
how
to
get
approval
from
I
will
get
in
contact
with
somebody
from
cig
windows.
This
morning,
then
Claire
we
need
sign-off
from
you
on
this
blog
and
I
also
need
to
sign
off
on
this
particular
blog
post.
B
To
me,
it
all
looks
good
I,
as
I
started
to
review
the
state
of
like
what
things
were
going
stable
versus
beta
versus
alpha,
comparing
the
enhancement
tracking
issues
in
the
enhancement
spreadsheet,
I
found
things
were
a
little
bit
out
of
date,
so
I
had
to
shuffle
things
around
so
the
line
about
the
number
of
enhancements.
The
number
is
the
same,
but
they're
slightly
I
think
less
stable
and
more
betta,
and
somehow
the
net
new
number
disappeared.
I
will
have
to
figure
that
out.
B
Otherwise
looks
okay,
the
thing
that
I'm
confused
about
is
insert
themes
here
for
media
messaging
doc.
It's
like
okay.
So
what
are
the
themes
where
do
I
go,
find
that
so,
if
I
copy
paste
the
messaging
doc
in
here
messaging
doc
is
where
what
I
have
filled
out.
Thus
far
is
like
what
we
have
done
differently
than
the
last
release
and
Eclair
has
super
helpfully
filled
in
with
this
release.
B
B
So
Maria
in
terms
of
stories
related
to
CI
signal
I
feel
like
the
best
place
to
make
those
contributions.
If
you
would
like
to
would
be
to
describe
how
is
this
release
different
from
past
releases?
You
know
what
are
you
doing
this
release
that
you
have
not
seen
CI
signal
do
in
past
releases
or,
what's
you
know,
what's
changed
what's
different
and
give
me
like?
B
B
Yeah,
like
I
I,
feel
like
like
for
the
kind
of
tricky
stories
like
gee.
Things
have
really
been
flaky.
This
release
lately,
but
I
also
feel
like
the
team
has
done
a
tremendously
good
job,
bringing
attention
to
that
and
getting
movement
on
the
appropriate
issues.
So,
like
I
know,
we
used
a
project
board
this
time.
I,
don't
believe
we
have
used
a
project
board
in
times
past.
It's
unclear
to
me
whether
or
not
there's
enough
of
the
story.
There.
B
Yeah
I
think
that's
really
all
I
had
so.
The
main
thing
for
me
is
like
go
no-go
on
comms
I'm,
not
ready
to
say
Natasha.
Please
click
send
and
tell
all
your
journalist
friends
to
read
all
of
this
and
treat
it
as
the
source
of
truth
with
zero
lies
in
it
or
mistakes.
I
think
is
maybe
the
better
phrase
there
so
I
kind
of
want
at
least
the
next
two
hours
to
get
that
right
home.
D
B
B
B
B
D
B
Cool
and
then
maybe
thinking
a
little
bit
further
out
right
now.
The
blog
also
talks
about
panel
happening
on
April
23rd,
where
people
are
invited
to
join
members
of
the
114
release
team.
So
if
you
don't
necessarily
get
yourself
cleared
now,
perhaps
you
can
get
yourself
cleared
to
show
up
and
talk
about
fun
stuff
on
April
23rd
I
have
not
I
did
something
in
person
at
John
for
113,
and
if
this
is
something
similar,
it
was
like
four
or
five
people.
It
was
pretty
informal.