►
From YouTube: Kubernetes 1.12 Release Burndown Meeting 20180925
A
C
D
E
A
So
technically
there's
it
looks
like
there's
a
lot
on
the
agenda,
I
suppose,
but
there's
there's
actually
a
pretty
small
amount
to
talk
about
today.
So
I
expect
a
fairly
long
meeting,
but
the
the
minutes
are
just
long
or
the
agenda
is
just
long,
be
thorough,
make
sure
we're
able
to
track
everything
day
to
day
right
now,
I've
dropped
a
link
into
the
zoom
chat.
There.
A
A
This
meeting
is
being
recorded,
I'll
be
uploading
it
to
YouTube
so
as
always
behave
accordingly,
so
to
start
out
overall
agenda
where
we
are
in
things
yesterday,
we
did
our
left
last
branch
fast
forward,
pulling
in
master
content
into
the
release,
112
branch,
and
then
we
initiated
the
master
branch
saw
so
master
branch
at
this
point
is
113
content
and
it
is
off
and
away
I.
Think
tied
has
got
about
a
hundred
commits
pending
that
it's
working
on
merging,
so
113
is
often
running
for
us
on
112.
A
What
this
means,
as
that
is
we're
letting
things
sit
with,
not
changes,
we're
expecting
to
see.
Ci
tests
continue
to
pass
successfully
and
that
will
no
longer
be
on
the
master
branch.
Obviously,
all
those
commits
merging
for
1.13
are
going
to
cause
it
to
diverge
there,
but
the
release
112
CI
signal
obviously
still
remains
relevant
to
us
and
as
the
ones
we're
looking
at.
A
There's
I
think
three
things
there
that
happen,
though,
in
that
branch
one
we
continue
to
have
test
flakes,
so
there
are
things
that
do
appear
to
to
fail
there,
but
the
the
expectation
that
is
looking
at
them
debugging
through
the
logs,
is
that
it's
just
a
one-off
sort
of
thing
something
hosting
and
then
that
the
subsequent
want
run
would
be
green
again.
So
far
that
has
been
the
case.
A
A
A
A
If
we
have
something
we
need
for
the
112
release
branch,
our
process
traditionally
is
to
merge
it
to
master
and
cherry-pick
it
to
the
release
branch,
but
right
now
sort
of
extrapolating
I'm,
not
sure
if
by
tomorrow,
we'll
actually
have
that
backlog
merged
and
there's
already
one
commit
in
there
that
we
want
to
get
and
then
Yong,
Li
I
think
you
may
be
proposing
a
patch
that
might
need
to
go
in
there.
A
So
I
guess
we're
gonna
talk
about
that
more
in
a
little
bit,
but
just
something
that
we'll
need
to
figure
out
is
how
we,
if
we
can
preferentially
hurry
a
commit
into
the
release
branch
without
just
force,
merging
it
directly
there.
If
we
can
do
a
cherry
pick
properly
still
so
our
one
remaining
issue,
then,
in
terms
of
where
we
stand
on
technical
content
versus
CI
signal
and
testing,
we've
been
dealing
with
some
some
final
issues
around
upgrades
and
as
of
Friday
into
the
weekend.
A
Everything
there
was
looking
good
on
the
cube
ATM
front,
but
we
still
had
one
issue
and
the
sort
of
cluster
subdirectory
of
of
cluster
bring
up
an
upgrade,
and
it
turns
out
that
that
was
the
problem
that
we've
been
having
on
and
off
with
various
aspects
of
the
node
taints,
by
condition.
So
there's
a
PR
one
final
PR
6/8
9/8.
For
that
we
need
to
get
into
the
release
and
is
all
approved
and
into
tied
for
merge
right
now,
but
we're
just
waiting
on
tide.
A
E
A
A
C
A
I
think
is
somewhat
expected.
Last
week
we
were
having
a
number
of
issues
around
CI
failures
in
these
particular
tests
as
well.
So
I
I
think
that
we
so
one
of
two
things.
Either
we
have
something
going
on
on
the
hosting
side,
which
I'm
I'm
still
a
little
bit
worried
about
that
that
that's
unstable,
but
it
may
also
be
that
we
have
some
problems
with
those
particular
pre
submit
tests.
So.
A
C
A
B
A
B
A
Down
some
people
today
to
figure
out
how
to
get
that
published
and
then
I
want
to
see
so
I
guess
this
is
more
sig
note:
gonna
try
to
chase
down.
A
E
A
A
This
has
historically
been
a
weakness.
We
have
had
a
number
of
other
ones
going
through
over
the
past
week
or
three
where
things
were
being
staged
and
already
in
advance,
so
it
may
be,
because
this
is
a
little
bit
newer
tool
that
they
haven't
quite
gotten
the
flow
of
when
they
should
be
doing
that,
and
we
haven't
quite
identified
it
as
one
of
the
things
that
we
need
to
be
watching
for
on
our
side
as
well.
D
D
High,
so
the
one
1204
CRI
tools
was
just
released
two
hours
ago:
I,
don't
know
if
that
yeah
the
CRI
CTL
is
in
that
as
well.
So
I
think
it's
just
something
that
popped
in
this
morning,
so
I
I,
guess
if
I
scare
is
not
a
Googler,
so
he
won't
have
permissions.
So
we'll
have
to
wait
for
some
West
Coast
folks
to
wake
up
yeah.
B
A
Well,
I
will
push
aggressively
today
to
see
what
we
can
do.
We
obviously
got
to
get
the
file
and
place
see
how
we
can
get
it
pushed
through
the
tests,
because
I
I
also
think
we're
gonna
have
some
test
flakiness
here,
get
it
merge,
approved,
get
it
into
tied
and,
and
then
I'll
add
it
to
my
list
of
things
to
see.
If
we
can,
if
it's
possible
to
jump
the
tide
queue
it
all
to
get
it
in
faster
yeah.
D
D
D
B
A
A
Okay,
thank
you
for
bringing
that
to
us
of
the
other
open,
PRS
and
issues
that
are
112
labeled
and
also
having
glanced
through
just
a
little
bit.
The
recent
open,
PRS
and
the
last
day
and
issues
I'm
not
seeing
anything
else.
That's
jumping
out
immediately
as
an
issue,
so
I've
got
our
issue,
counts
and
PRS
listed
in
that
the
agenda.
If
anybody
wants
to
glance
at
them,
but
it's
aside
from
this
this
new
PR
69
o33
for
the
cry,
control,
image
or
yeah.
A
C
A
A
A
Okay,
so
one
piece
of
good
news
that
came
in
overnight
last
week,
we
had
merged
the
update
to
go
Lang
110
for
in
the
release
tool
chain,
and
we
had
been
waiting
to
see
if
anything
changed
on
the
scalability
front.
That's
always
just
a
worry
there
with
those
being
very
long
running
tests
and
I
got
a
slack
overnight
that
that
was
looking.
Okay
and
good.
Just
wanted
double
check.
A
A
Is
that
I'm
not
seeing
it?
A
notification
came
up
on
my
phone
and
I
just
read
it
there
and
I'm,
not
sure
which
slack
channel
that
came
through,
and
so
at
any
rate,
that's
good.
We
murdered
that
emerge
that
changed
into
CNN
a
destabilization
anywhere
else.
A
master
branch
or
release
112
blocking,
so
everything
looked
good
and
confirmation
from
scalability,
so
I
think
we're
completely
good
to
go
there.
A
The
the
only
other
things
on
the
agenda
that
are
just
sort
of
like
an
FYI,
no
change,
just
a
copy-paste
from
yesterday's
minutes
on
the
documentation
front,
everything
is
done
and
good
and
pending
and
we
wait
until
the
release
is
going
live
and
at
that
point
we
make
the
new
documentation
live.
So
there's
not
skew
there
from
a
user's
perspective,
so
everything's
staged
and
ready
they're
just
ready
to
press
the
button.
There
should
be
happening
on
Wednesday
some
final
prep
and
Thursday
publication
release
notes.
Similarly,
things
are
practically
done.
A
Glancing
through
them
yesterday,
I
would
say
they're
pretty
much
done
might
be
some
other
late,
known
issue
or
PR
information
that
gets
pulled
in
r1
PR
for
the
the
upgrade
issue.
That
one
will
have
a
release
note
as
well,
that
comes
in
I,
haven't
looked
to
see
if
it's
actually
there
yet,
but
that
stuff
should
finalize
and
merge,
possibly
today
otherwise
tomorrow
and
then
communications.
A
So
the
the
communications
team
lines
up
a
set
of
interviews
for
a
couple
of
us
on
the
release
team,
in
particular
the
lead
and
sometimes
the
the
shadow
and
features
lead
as
well,
so
Stephen
and
I
this
time
around
have
been
doing
a
number
of
interviews
with
the
press
talking
about
the
upcoming
release
and
sometime
on
Thursday
Friday
I,
guess
those
will
go
to
press
get
published
on
on
the
internet,
not
too
much
more
to
say
there.
Any
questions
from
folks.
C
A
C
A
D
Tim,
the
only
other
thing
I
had
was,
if
you
look
at
the
two
issues
in
the
milestone,
112
from
DG
Hubbell
I
am
NOT
able
to
figure
out.
If
it's
a
testing
hole,
why
we
didn't
catch
those
two
or
whether
it
should
be
I,
don't
know
it
seems
like
they're,
using
things
similar
to
how
cube
radium
sets
up
things,
but
he
still
found
two
error,
two
problems,
so
I
don't
know
if
we'll
probably
have
to
bring
it
up
with
SiC
testing,
I
think
to
review.
C
So
this
so
just
for
context,
Dalton
is
former
Aquarius
and
currently
builds
the
typhoon
distro.
So
if
you
have
used
that
for
I
mean
there
are
some
similarities
and
insofar
as
it
uses
blue
cube,
so
if
he's
discovering
things,
I
saw
I
watched
the
typhoon
repo
as
well
so
I
saw
a
few
things
like
he's,
been
working
on,
pushing
out
the
1:12
stuff
as
well.
So
if
he's
discovered
something,
it's
probably
worth
taking
a
look
at.
D
He
yeah
that
that's
why
I
mean
he
looked
important
and
he
was
actually
pointing
to
some
other
distro
trying
to
make
a
change
to
accommodate
what
we
are
doing
so
it.
You
know
kinds
of
flows
the
other
way
and
we
are
not
getting
to
know
it
early
enough.
Thankfully,
the
RCD
help
for
him
to
find
those
issues
so
yeah.
The
other
way
to
do
this
is
see
if
dalton
can
set
up
a
test
against
our
master
and
see
if
how
how
we
could
report
that
to
test
red
or
something
like
that.
A
You
got
to
be
a
big
enough,
distro,
probably
to
have
enough
resources
to
dedicate
to
tracking
upstream
aggressively
pre-release,
but
you'll
end
up
getting
bit
by
things
that
aren't
well
communicated
I,
guess
so.
I
totally
agree.
Somehow
I
missed
this
one
in
I
get
up
notifications.
Your
message
from
a
couple
days
ago
saying:
should
we
net?
This
is
a
known
issue
or
actually
I
did
reply.
Yeah
you
did
days
yeah.
E
A
Think
it's
totally
reasonable
to
and
I
I
see
it
as
something
that
the
distinct
should
be
thinking
about
a
noticing,
especially
when
a
distro
user
is
trying
to
consumer
stuff
with
the
RC
level.
That's
I,
ideally
we'd
be
getting
their
information
before
sort
of
today,
but
those
are
exactly
the
sort
of
things
that
I
think
are
really
ought
to
be
in
the
known
issues
so
that
others
don't
run
into
the
exact
same
thing.
Yeah.
A
A
D
D
The
main
thing
I
want
to
eyeball
is
the
fight.
Welsh
asks
whether
the
we
generate
the
fight
well
shot
in
the
code
as
well
as
in
the
scripts,
so
I
want
to
make
sure
that
they
match,
because
one
o,
the
one
that
we
generate
from
code
ends
up
in
the
release,
notes
and
the
ones
from
the
scripts
actually,
and
we
end
up
uploading.
A
So
if
you
have
a
suggestion
of
an
experiment
that
would
be
appropriate,
maybe
we
can
talk
about
it
on
the
cig
release
Channel
today,
yep
and
Doug's
definitely
around
and
able
to
do
some
things,
and
if
we
do
it
kind
of
middle
of
the
day,
as
we
also
have
the
testing
for
people
around
as
well
yep
someone
quick,
oh,
we
are
up
against
the
or
actually
this
isn't
a
half
hour.
This
is
scheduled
for
a
full
hour,
so
we
we
can.
A
A
Okay,
if
not
I'll
call
it
a
meeting,
we
will
have
a
meeting,
definitely
tomorrow
and
the
next
day
as
well,
and
ideally,
the
release
will
be
out
the
door
on
Thursday
and
that
will
be
it
and
the
the
other
calendar
invites
that
are
open
for
after
Thursday
along
I'll
be
cancelling
so
retrospective
thoughts
in
the
retro
dock.
Please,
if
you
have
any-
and
we
will
be
in
touch
over
the
next
couple
of
days
thanks
everybody
bye,
oh
dear.