►
From YouTube: Kubernetes 1.14 - Week 11 - Burndown 2019-03-22
Description
B
A
About
this
point,
how
where
I
can
do
what
is
it
I've
been
trying
to
practice?
I
guess:
I,
don't
know
what
the
word
for
it
is.
It's
like
a
fill
where
I
use
three
limbs
so
like
leg
left
right.
Something
like
that.
So
I
can
really
quickly
do
like
roll
between
the
kick
drum
and
the
snare
and
a
Tom
or
something
it
sounds
really.
Cool
I
can
travel
all
over
the
kit.
B
C
A
A
Yeah,
it's
super
weird
I
haven't
taken
lessons
in
a
little
bit,
I
used
to
take
lessons
on
a
weekly
basis
and
it
turned
into
something
where,
like
my
drum
teacher
and
I,
would
just
kind
of
like
jam
back
and
forth,
his
preferred
style
of
play
was
somewhere
in
the
Latin
and
jazz
area.
So
he
would
keep
trying
to
like
get
me
to
learn
some
of
the
fundamentals.
I
can
at
least
do
like
the
right
pattern
for
jazz
and
kind
of
have.
A
My
other
limbs
do
stuff,
they're,
still
kind
of
blocked
blocks
of
in
sync,
with
a
couple
other
things
that
I
wish
they
weren't,
but
he
kept
talking
about
like
yeah
they're,
just
like
swung
eighth
notes,
or
you
can
think
of
it
as
triplets.
It's
like
really
basic.
All
you
do
is
like
what
are
you
talking
about
like
I
understand
all
of
those
words
individually,
but
you
are
just
speaking
gobbledygook
right
now.
F
F
A
F
A
That's
pretty
amazing
I
keep
wanting
to
sort
of
like
Jase,
really
knows
his
stuff,
with
jazz
on
baritone
sax,
so
I
keep
wanting
to
like
just
get
into
a
jam
session
with
him,
because
I
can
at
least
hold
a
steady
beat
now
so
I'll,
just
let
him
like
drive
the
bus
or
whatever
it
is,
and
I'll
set
the
scent.
The
beat
okay,
okay,
I
think
we
have
everybody
here
that
we
need
to.
So
no,
this
isn't
Friday
jazz
discussion.
A
This
is
actually
the
kubernetes
114
burned-down
meeting,
which
you
are
all
at
and
being
publicly
recorded,
so
you'll
be
posted
to
YouTube
later,
where
you
can
watch
yourselves
adhering
to
the
kubernetes
code
of
conduct
by
not
being
a
bunch
of
jerks
did
I
say
today's
date.
It's
March,
22nd
and
I
am
Erin
of
cig
beard.
You
can
tell
like
how
on
the
ball,
I
am
today
because
it's
Friday
I,
don't
believe
that
Claire
or
any
of
her
shadows
are
here
for
enhancements.
But
last
I
checked
with
her
offline.
Everything
is
still
a
ok
there.
A
G
A
Will
say
on
that
refactor
P?
Are
you
talking
about?
I
dropped,
some
capital
home
opinions
that
we
can
discuss
offline,
but
I.
Think
the
question
for
relevant
to
this
group
is:
do
you
want
to
shuffle
around
the
dashboards
right
now,
or
would
you
rather
wait
until
after
the
release?
My
suggestion
would
be
that
you
wait
just
because,
even
though
some
of
the
dashboards
may
look
like
the
game
of
life
or
total
and
utter
noise,
your
brains
as
pattern-matching
machines
have
gotten
used
to
what
those
look
like
and
so
I
feel
like.
A
D
A
You
know
I've
had
like
so
many
people
ask
me
that
recently
I
got
a
trim
like
two
weeks
ago,
maybe
three
weeks
ago,
I
think
it's
just
because
I'm
wearing
my
hair
back
now,
so
you
can
actually
see
that
it
got
a
little
more
trim.
Well,
it's
looking
good.
Maybe
the
shirt
is
accent
accenting
it
today
and
so
I
have
to
fixate
your
attention
on
J.
Is
that
cool?
A
C
A
D
A
E
A
So
can
you
and
indoor
Hannes
walk
me
through
when
we
actually
press
the
button
to
cut
the
release?
What
happens
with
release
notes
like
how
do
how
does
all
of
the
fine
work
that
you're
doing
land
and
when
does
it
need
to
land
relative
to
a
button
being
pushed
or
a
tag
being
set,
or
anything
like
that?
So.
E
E
A
I
believe
it
is
over
github.
My
thought
process
goes
something
like
it'd
be
really
cool
if
the
changelog
about
114
was
up
to
date,
if
I
looked
at
the
114
tag,
rather
than
a
cherry-pick
that
landed
immediately
after
so
I,
don't
know
that
we
have
to
answer
it
on
this
call,
but
I
think
that
maybe
it
would
be
worth
looking
back
historically
to
see
the
order
of
creations
before
I'm.
A
I
think
the
reason
I'm
asking
is
because
somebody
had
a
PR
open
about
fixing
like
a
typo
in
the
change
log
file
on
the
release.
114
branch
I'm
like
I,
mean
thank
you
for
your
contribution,
but
it's
about
to
get
squashed
entirely
by
the
work
of
the
release,
notes
team
because
that's
where
all
the
work
has
been
happening
lately:
okay,
let's
move
on
to
comms
I,
think
Caitlyn
you're
here
to
talk
to
us
about
comms
today,.
F
A
B
B
E
B
A
Believe
the
way
that
that
works,
now
that
you
say
it
that
way
is
kicking
loose,
that
I
think
it
will
use
the
release,
notes
yeah
the
release
notes
draft
that
is
in
the
safe
release
repository
so
where
you've
been
committing
the
draft
lately
over
the
course
of
the
release.
It'll
pick
up
that
file.
So
when
you
feel
like
you,
have
the
Google
Doc,
totally
locked
in
place
and
no
more
changes,
you
commit
you
open
a
PR
to
that
file
in
the
sig
release
repo,
and
that
should
be
one
and
all
game
picks
up.
I.
E
H
A
A
Times
a
year,
I've
watched
it
happen
every
time,
I
think
right.
Regardless
of
that,
though,
it's
just
useful
for
us
to
I,
don't
think
we
have
to
go
through
it
all
today,
but
my
plan
for
Monday
for
what
it's
worth
is
for
after
us
all.
Giving
you
no
go
no
go
is
to
kind
of
try
and
put
down
step
by
step.
The
order
of
operations
I
think
it's
really
helpful
for
us
to
have
something
approximating
a
checklist
or
a
step-by-step
guide,
so
that
we
make
sure
we're
keeping
track
of
everything.
I.
E
E
B
A
Let's
see
here
so
I'm,
looking
at
my
my
handbook
now,
let
me
read
this
and
make
sure
this
makes
sense,
so
it
says,
go
no.
Go
should
generally
be
clear
before
the
release
and
I
am
feeling
like.
If
I
had
to
push
the
button
today,
I
would
say:
let's
go
the
release,
notes
draft
needs
to
be
PR,
tinda
sake,
release
and
I
should
have
taken
a
look
at
it.
B
A
Then
it
says,
after
that,
you
do
a
no
mock
release
build
and
then
the
next
step
is
starting
sometime
in
the
afternoon.
So
at
this
point,
basically
all
of
the
bits
have
been
cut.
It
is
now
time
for
us
to
like
announce
and
publish
things
so
in
Monday's
case
we're
aiming
to
do
this
at
3:00
p.m.
Pacific.
A
B
A
H
A
So,
assuming,
like
all
of
the
bits,
have
been
cut
and
we've
gotten
all
of
that
necessary
and
the
draft
for
the
blog
post
looks
good.
Then
we
say
cool.
We
announce
everything
we
publish
the
blog
post,
so
I
feel
like
I'm
gonna,
take
what
I
have
in
the
playbook
here
and
kind
of
put
it
into
the
agenda
for
Monday's
meeting
and
make
sure
that
we
all
agree
and
understand
those
are
the
steps
to
be
taken
home.
A
The
other
thing
about
Monday's
meeting
is
I
suggested
this
yesterday,
in
slack
in
person
and
on
the
mailing
list.
I'm
gonna
move
Monday's
meeting
to
8:00
a.m.
Pacific
time
so
same
time
is
the
Tuesday
Thursday
meetings.
It's
gonna
be
the
same
zoom
URI
you
used
for
Monday
Wednesday
Friday,
we're
just
going
to
start
two
hours
earlier
to
give
us
two
extra
hours
in
case
something
goes
wrong,
so
the
idea
here
is,
we've
told
told
media
to
wait
for
our
signal
and
we
plan
to
send
out
that
bat
signal
at
3:00
p.m.
A
Think,
that's
all
that
I
have,
let
me
see.
I
I
took
I,
took
all
of
the
responses
you
all
put
in
the
contact
info,
spreadsheet
and
I'm
doing
the
needful
with
those,
and
it
will
take
me
some
time
to
show
you
the
results
of
all
that.
But
I
appreciate
everybody
who
filled
that
out
and
I
took
my
best
guess
based
on
that
for
everybody
who
didn't
fill
it
out
and
I
think
that's
it.