►
From YouTube: Kubernetes 1.14 - Week 11 - Burndown 2019-03-21
Description
A
A
A
A
B
B
B
B
B
B
B
B
Okay,
it
is
heat
one
and
I
see.
Jorge
is
here
probably
to
talk
to
us
about
CI
signal,
so
we'll
go
ahead
and
get
started.
Hi
everybody
today
is
Thursday
March
21st
I
am
Aaron
of
apparently
Aaron
of
signal
Elise.
Let's
change
that
real
quick
I
am
Aaron
of
cig
beard,
your
friendly
released,
the
welcoming
we
go
to
today's
114
burn
down
meeting
and
encouraging
you
all
to
adhere
to
the
kubernetes
code
of
conduct.
So
please
don't
be
jerks
and
you
can
go
watch
yourself
not
be
jerks
on
YouTube
later
as
soon
as
I
post.
B
D
Absolutely
so
let
me
see
so
I'm
gonna
say
that
everything
is
yellow
right
now.
Currently,
114
blocking
is
passing.
There's
therefore,
a
let
me
see,
let
me
check
real
quick.
There
are
four
jobs
are
flaking
right
now,
the
most
a
most
of
the
most
of
the
jobs
just
need
to
get
the
latest
runs
on
all
day
or
all
of
the
jobs
are
green,
so
we
will
not
monitor
them
closely
and
see
if
anything
else
comes
up
with
a
1:14
blocking
a
looks.
D
Zig
storage
lifecycle
test
switch
your
shut
up.
Besides
that
we
a
Widow's,
we
will
just
wait
and
see
if
anything
else
comes
up.
Hopefully
they
a
master
blocking
will
become.
It
will
have
a
lot
more
green,
as
time
goes
on.
Master
upgrade
is
similarly
a
similar
story.
Well,
everything
is
red
for
a
purplish,
a
master
of
gray
put
all
most
of
the
most
of
the
flaking
jobs
need
more
more
bills
to
to
label
the
failures.
A
trip.
D
All
the
failures
behind
a
one
of
the
big
contributors
to
failures
on
master
cake
has
been
a
sixth
Orage
every
test
failures
that
we've
been
monitoring
for
it
sometime
I
think
I
included
a
link
to
them
to
the
CI
signal
issue
in
there
and,
lastly,
a
I
added
some
a
I
added
a
couple
issues
for
discussion
on
how
CI
signal
has
been
using
a
priority
labels
and
how
we've
been
a
help.
We've
been
using
milestones
so
on
labels.
D
After
some
discussion,
we
will
we're
planning
to
stick
with
just
using
one
type
of
a
priority
along
the
release
cycle,
instead
of
changing
and
changing
priorities
as
we
go
from
the
beginning
to
burn
down
a
cold
freeze
and
so
on,
milestones,
I
think.
The
the
current
practice
is
that
we
will
assign
everything.
Every
issue
that
I
see
a
signal
creates
a
milestone.
We
will
let
opening
six
decide
whether
to
keep
the
milestone
or
remove
it,
depending
on,
depending
on
how
they
prioritize
work
would
see.
D
B
Not
so
much
a
question,
I
think
just
a
point
of
clarification
at
this
point:
I
don't
care
what
master
looks
like
at
all:
I
only
care
what
the
114
boards
look
like.
So
I
appreciate
your
extra
attention
to
detail
on
master,
but
you
don't
have
to
do
it
if
you
don't
want
to
the
only
thing
we
as
a
release
team
now
care
about
now
that
we
have
left
code
freeze
and
enter
code.
Thaw
is
all
of
the
signal
on
the
114
jobs,
which
does
look
good.
B
So
thank
you
for
that,
and
thank
you
for
continuing
the
conversation
on
consistent
use
of
priorities
and
milestones.
I
feel
like
there's
lots
of
ongoing
discussion
on
how
to
maybe
prepare
ourselves
to
use
those
more
effectively
for
the
115
cycle
and
I
know.
Nico,
has
lots
of
opinions
and
ideas
on
how
to
improve
issue
triage
overall,
so
when
I
have
bandwidth,
I
will
gladly
participate
in
those
discussions.
B
B
E
B
B
B
Well,
the
only
testing
for
a
related
thing
that
I
know
of
for
sure
is
that
we
cleared
out
the
backlog
of
PRS
after
code
thaw
in
less
than
24
hours,
which
I
believe
is
faster
than
we've
ever
cleared
through
a
backlog,
I
plan
on
go
going
back
and
taking
a
closer
look
at
that,
because
part
of
me
believes
this
is
I
mean
try.
It
is
great
that
batch
merging
is
awesome.
B
F
B
B
One
crazy
idea:
I
wanted
to
throw
out
to
this
audience,
since
you
are
people
who
are
willing
to
would
either
wake
up
at
8:00
a.m.
Pacific,
or
it
is
a
more
suitable
time
for
your
timezone
I
was
debating
whether
we
wanted
to
hold
Monday's
meeting
at
8:00
a.m.
and
then
start
actually
going
through
the
process
of
cutting
the
release.
C
B
Yeah
I
anticipate
the
things
that
come
up
are
generally
not
related
to.
Are
we
going
or
not,
but
how?
How
can
we
continue
to
move
forward?
Now
that
we've
decided
to
move
forward,
so
cool
I
will
drop
a
note
and
slack
I
will
send
out
an
email
to
the
release.
Team
and
I
will
raise
this
question
again
tomorrow,
but
unless
he
here
for
me
otherwise
look
for
that
calendar
invite
to
bump
back
by
2:00
hour
or
whatever
be
two
hours
earlier.
B
Awesomo
I
think
that
was
our
fastest
burndown
ever.
This
is
amazing.
Oh
right,
I
forgot.
So
for
those
of
you
who
aren't
at
the
community
meeting
the
t-shirt,
it's
like
a
little
dark
I.
They
didn't
print
it
as
light
as
I
wanted
them
to
so
I
have
not
talked
yet
for
all
the
francophones
out
there,
and
that
is
the
Thursday
burned
down.