►
From YouTube: Kubernetes 1.12 Release Burndown Meeting 20180927
A
A
A
A
You
well
we're
two
minutes:
past
Nik
on
slack
I
am
going
to
go
ahead
and
get
started.
Welcome
to
the
Thursday
September
27th
release
team
meeting
for
our
communities
1.12.
This
is
our
last
meeting.
The
release
is
going
out.
I
see
no
reason
not
to
you
at
this
point,
so
probably
a
relatively
short
agenda
today.
I
will
paste
the
agenda
and
notes
in
the
zoom
there
for
reference.
This
is
a
public
meeting,
as
always,
it's
being
recorded,
it
will
go
up
to
YouTube
shortly
after
the
meeting.
So
please
behave
accordingly.
A
So
today,
Thursday
September
27th
release
day
the
couple
things
we
have
on
the
plate
today
committing
the
final
release,
notes,
pushing
the
docs,
live
on
the
website
and
pushing
the
release.
So
it's
basically
it
we'd
had
some
testing
for
issues
or
I'm
really
hesitating
calling
this
testing
for
I
really
think
we
should
start
talking
about
rel
infra,
but
publishing
about
was
having
issues
and
overnight
got
a
message
from
Nikita
on
slack
that
things
were
good
and
then
also
an
affirmation
from
sttt
Estefan
I
believe
it
is
in
slack
also
mentioned.
A
Things
were
looking
better
earlier
on
slack
so
that
all
looks
like
it
is
a
go
glancing
through
issues
and
PRS
this
morning.
Again,
no
changes
notable
there
on
three
PRS
four
issues.
These
are
things
lining
up
for
one
12.1,
no
apparent
blockers
there,
no
new
surprises
the
one
thing
that
I'm
aware
of
at
this
point
is
that
cry.
Cuddle
version
upgrade
that
we
had
come
to
our
attention
on
Tuesday
morning.
That's
still
not
merge
ready
as
it
stands,
so
that's
one
12.1
material.
A
If
you're
aware
of
anything
else
pending,
please
bring
it
up
because
we
want
to
make
sure
that
our
brand-new
patch
manager
has
eyes
on
it.
So
any
comments
or
questions
at
that
point.
B
So
I
agree
that
everything
is
looking
good,
but
I
did
want
to
give
a
heads
up
the
test
grade.
Various
test
period
dashboards
seem
to
be
out
of
date
relative
to
the
amount
of
data
that
is
being
dumped
into
GCS.
So
a
great
example
would
be
like
this
test.
Great
job
which
shows,
or
this
test
grade
dashboard
shows
the
last
occurrence
of
this
job
happening
on
926
at
10:28
a.m.
but
if
I,
then
click
through
to
uber
Nader's.
B
B
These
links
are
all
showing
up
in
chat
and
this
chen's
a
bunch
of
builds
on
9:27,
so
I'm,
currently
working
with
internal
team
members
to
figure
out
why
some
of
the
test
grade
dashboards
don't
seem
to
be
updating,
but
I
have
just
swept
through
all
of
the
things
in
the
release,
112
blocking
dashboard
manually
and
don't
see
any
continuously
failing
tests,
but
just
giving
you
a
heads
up
if
you're,
double-checking,
stuff
and
things
look
weird
I'm,
probably
gonna
file
an
issue
on
this
shortly.
Thank.
A
You
for
bringing
that
up,
because
I
didn't
actually
look
at
the
specific
times
on
those
so
I
where
I
looked
and
saw
green,
it
was
looking
like
it
made
sense,
but
yeah
that
is
troubling.
So
on
the
at
least
on
the
for
the
one
example
you
did,
it
does
look
like
more
recent
builds.
Do
you
continue
to
be
green
so
that
at
least
is
positive.
A
All
right
well
moving
along
then
do
we
have
Nick
Nick,
yes,
I
believe
we're
a
go
on
committing
the
final
release,
notes.
Looking
at
the
draft
things,
look
good.
A
A
C
A
A
A
D
A
Yep
looks
like
it
updated.
Okay,
so
once
that
merges,
I
will
give
the
Doug
go
ahead
on
final
build
yesterday
afternoon,
since
we
had
nothing,
we
were
anticipating
coming
in
for
changes
on
anything.
He
did
a
test
mock,
build
and
publish,
and
the
the
mock
changelog
looked
as
expected
as
well.
Having
pulled
in
the
that
point,
obviously,
stale
draft
as
well,
but
things
looked
good
and
correct
there.
So
we
will
get
the
official
build
turning
this
morning
and
then
roughly
around
four-ish
o'clock.
A
A
So
other
than
saying
thank
you
to
everybody,
I
don't
know
if
there's
anything
else
too
much
to
do
at
this
point.
Thank
you.
Thank
you.
Thank
you
to
everybody
for
all
of
your
hard
work.
It's
really
been
I
would
say
four
months
for
a
lot
of
folks,
given
when
things
started,
ramping
up
on
unselecting
the
team.
B
E
E
So
the
the
schedule
is
merged.
I
have
the
intro
the
release,
a
kickoff
me
all
kind
of
drafted
up
I
plan
to
send
it
on
Monday
I
want
we
used
to
go
out
today
and
not
send
it
on
Friday,
so
I'll
sign
it
Monday
morning.
So
yeah,
it's
pretty
much
just
touching
upon
the
fact
that
it's
such
a
short
release
and
you
have
to
be
mindful
of
the
future
load.
E
So
that's
the
main
process
point
that
I'm
insisting
the
release
in
addition
to
Docs
and
tests
also
being
completed
by
code
freeze
other
than
that
I
think
the
release
team
is
almost
set
with
all
the
initial
housekeeping.
If
not
just
ping
me
and
I'll
be
meeting
with
Kendrick
later
I
mean
make
tomorrow
to
go
over
the
fallouts
from
112
the
feature
for
lots,
so
that
both
of
us
are
planning
to
meet
the
six.
E
F
A
Press
is
good,
then,
like
people
want
to
want
to
know
about
it,
but
I
partly
hope
that
we've
done
a
good
job
of
making
this
a
boring
release
in
theirs.
Maybe
that
translates
into
less
dramatic
needs
there,
but
yeah
I,
think
part
of
us
doing.
Our
job
is
kind
of
keep.
It
thing
boring,
so
hopefully
we're
getting
more
into
that.
That
phase
of
this
maturing
project.
A
So
I
updated
the
the
theme.
I
don't
know.
If
anybody
has
any
questions
about
it,
does
everybody
get
it
slight
slight
nerdy
joke.
A
A
At
the
the
top
of
today's
agenda,
I've
got
it
noted
there
Thursday
October,
4,
there's
the
link
retrospective
is
the
retrospective
doc
any
thoughts
or
comments
you
have
in
there.
Please
glanced
through
it.
Look
at
what's.
There
supplement
it
and
then
also
a
link
to
the
community
meeting
where
we'll
be
on
the
agenda
for
next
week,
and
if
you
don't
have
the
zoom
already
for
that
meeting.
It's
also
in
that
Google
Talk.
A
A
So
press
the
button
which
button
have
we
cutter
release,
so
the
release
has
not
been
cut.
I
I,
don't
know
for
sure.
If
anything
in
the
cutting
or
just
in
the
publishing
pulls
in
the
the
release
notes.
So
I
wanted
to
make
sure
that
that
got
commit.
So
that
is
merging
right
now,
once
I
see
that
actually
it
is
merged,
so
I
will
give
Doug
the
go-ahead
to
start
the
build
right
now
awesome.
Thank
you.
A
Alright
well
a
day
I
do
have
I
said
this
was
the
last
meeting.
I
do
have
tomorrow's
meeting
still
on
the
calendar,
officially
I
think
just
in
case
any
craziness
shows
up,
but
as
long
as
things
are
looking
okay
tonight
I
will
go
ahead
and
cancel
that
meeting
and
we'll
follow
on
in
the
retro
and
that'll.
Be
that.
E
Just
one
quick
thing:
the
first
113
meeting
is
coming
Monday
at
11
a.m.
PST.
Then
I
should
have
gone
up
but
FYI
thanks.
So
we
don't
have
any
it's
back-to-back
week
off.