►
From YouTube: Kubernetes 1.10 Release Meeting 20180122
Description
A
A
Nope,
okay,
so
yeah.
So
the
agenda
is
a
bitly
Kate's
110
burned
down,
and
you
can
see
that
us
follow
along
after
the
fact.
So
it
is
week
4
of
12
the
release,
so
we
are
starting
to
make
progress
into
the
release
this
week.
If
you
look
at
the
timeline,
it's
actually
there's
not
a
lot
necessarily
scheduled
for
this
week,
other
than
feature
freeze,
but
due
to
a
large
number
of
outstanding
features
that
need
to
be
documented
and
put
into
the
features
process.
A
We
are
going
to
kick
that
deadline
up
a
week,
so
basically
people
can
have
another
week
to
work
on
getting
the
feature
documentation
in
place
a
little
bit
of
explanation
for
those
not
necessarily
familiar
with
the
release
process
and
why
we
do
the
feature
is
tracking
separately.
Essentially,
it
allows
us
to
track
release
over
release
movement
of
major
deliverables,
so
we
can
not
only
track.
What
is
the
status
is
something
alpha-beta
GA.
A
We
can
create
descriptions
of
what
we're
delivering
in
a
way
that
can
be
used
for
marketing
purposes,
so
that
people
can
learn
what's
in
a
release,
and
so
it
gives
a
little
better
view
of.
What's
being
delivered
than,
if
you
really
read
the
release
notes,
which
can
be
a
little
bit
overwhelming,
so
the
tracking
process
around
those
is
a
bit
manual.
A
Your
devoted
ski
is
handling
that
this
release
again
and
he
has
a
spreadsheet
that
ties
back
to
the
information
that's
in
github,
so
there's
essentially,
the
source
of
truth
is
in
github,
but
it
gets
reflected
in
the
spreadsheet
that
is
linked
in
the
release
schedule
which,
if
you
click
on
the
timeline
link
in
the
divert
now
meeting
minutes,
you'll
see
a
link
to
that.
So
this
week
there
wasn't
a
lot
on
the
schedule,
but
we're
gonna
we're
gonna,
kick
that
extension
out
caleb
miles.
Who
is
a
google
and
who
is
our
branch
manager?
A
This
release
I
had
a
bit
of
a
bike
accident
he's
okay,
but
he
it
did
cause
him
to
have
a
delay
in
his
his
ability
to
get
up
to
speed
and
get
the
requisite
Eccles
to
do.
The
Alfa
cut
so
he's
working
on
that
and
he
I
believe
he's
in
on
boarding
this
week.
So
hopefully
we'll
be
able
to
hit
our
target
of
next
week
for
the
110
zero
dash.
A
A
So
one
of
the
things
we're
gonna
do
this
week,
even
though
the
feature
freeze
is
gonna,
get
pushed
off
a
week,
we're
gonna
look
at
what
we
can
do
to
collect
the
marketing
sort
of
information
that
we
can
get
from
what
we
have
right
now.
So
we,
your
and
I
talked
about
the
timeline
for
marketing
and
also
how
that
might
impact
our
overall
feature,
timeline
and
I
feel
confident
that
we
can.
We
can
continue
at
pace,
even
though
we
pushed
the
feature
freeze
up
a
week.
A
Okay,
other
things
we
need
to
do
this
week.
We
need
to
start
digging
into
the
CI
signal
and
also
into
the
issues
right
now,
we'll
see
this
in
a
moment,
but
there's
44
open
issues
in
the
milestone.
That's
in
this
phase
of
where
we're
at
in
the
release.
That's
not
unreasonable,
there's
a
lot
of
stuff
in
there.
That's
just
tracking,
and
we
don't
know
necessarily
that
those
are
true
release
blockers,
but
well,
we
should
probably
start
looking
into
those,
especially
on
Wednesday.
March
is
important
because
there's
12
of
those
yeah.
B
Was
that
Tim
Tim
another
meeting
up
today
and
we're
gonna
start
through
the
releases?
This
is
Josh.
Oh,
Tim
and
I
are
meeting
up
today
and
was
going
through
the
issues
and
trying,
particularly
with
the
goal
right
now,
just
simply
trying
to
kick
out
things
that
don't
belong
in
the
milestone
that
were
put
in
the
milestone,
because
nobody
was
because
they
were
any
previous
milestone,
get
kicked
forward,
but
nobody's
still
nobody's
working
on
what
will
be
probably
about
half
of
those.
A
Okay,
great,
thank
you
so
much
so
SIG's
are
responsible
at
this
point
to
identify
what
is
gonna
need.
Of
course,
my
internet
connection
goes
wonky,
SIG's
need
to
identify
what
needs
user-facing.
Docs
there's
been
some
talk
about
a
label,
that's
the
user
facing
label
and
I'm,
not
sure
where
that's
at,
but
we
should
probably
talk
about
that
in
the
regular
sig
release
meeting
just
to
touch
base
on
it.
A
I
haven't
necessarily
felt
super
thrilled
with
the
way
that's
gone,
and
it's
getting
to
the
point
where
there's
enough
moving
parts
and
enough
team
members
and
all
that
that
probably
we
should
look
at
some
sort
of
project
tracking,
specific
app,
there's
Trello,
there's
others
and
probably
we'll
have
a
discussion
about
that
in
the
zoo
release,
meeting
coming
up
or
maybe
sick
PM,
there's
there's
a
bit
of
overlap
there.
So
we'll
have
to
figure
out
what
is
the
best
solution.
But
I
would
like
to
solicit
opinions
on
that.
A
If
you
have
opinions
about
what
is
worked
well
for
you
in
the
past
for
managing
projects
like
this,
where
you
have
a
lot
of
moving
parts
and
a
lot
of
project
milestones
that
need
to
be
hit
and
tracked
I.
Welcome
that
I'd
like
to
do
it
in
as
agile
a
way
as
possible.
So
I
do
have
a
preference
for
doing
that
in
a
sort
of
Kanban
type
way.
But
again,
if
you
have
strong
opinions
or
preferences
set
me
up
on
slack
and
I'd
love
to
I'd
love
to
hear
those
well.
A
Lastly,
for
this
week
I
am
going
to
be
replacing
Phil
wit
rock.
As
the
co-lead
of
cig
release.
Phil
has
had
to
step
down
due
to
being
a
busy
dad
and
having
a
lot
of
responsibilities,
and
he
nominated
me
as
a
replacement.
There
wasn't
any
in
the
Lazy
consensus
model,
nobody
screaming
yelled
about
it,
so
it
seemed
like
that's
going
to
move
forward
so
happy
to
and
and
honored
actually
to
be
in
that
position
like.
A
I
feel
like
most
things
are
on
track,
with
the
exception
of
the
Alpha,
which
is
totally
doable
and
honestly,
the
first
alpha
I've
never
actually
seen
any
cogent
feedback
come
on
at
first
alpha
anyway.
So
I'm
not
really
worried
about
that
in
the
slightest
I
think
all
all
signs
are
pointing
to
a
delivery
for
next
week.
Do.
B
C
B
C
A
Right
now,
the
dominant
opinion
is
that
it's
it's
for
the
release
team
primarily,
but
the
thing
is
as
the
ecosystem
and
riches
and
more
and
more
dependent
projects
need
early
feedback
on
their
integrations.
These
alphas
are
gonna,
become
critical
and
I.
Keep
saying
that
every
release
sends
like
I,
don't
know
what,
but
I
keep
hoping
I
keep
hoping
for
that
eventuality,
that
people
are
testing
their
their
stuff
early,
like
I'd
love
to
see
some
more
feedback
for
them.
Yeah.
B
A
A
A
A
Love
is,
if
you
are
one
of
the
owners
of
things
below
below
the
actual
break
out
by
cig
things,
like
branch
updates,
build
failures,
test,
feelers,
etc.
If
you
could
update
this
sheet
this,
the
many
minutes
ahead
of
the
meeting
with
your
update
that
would
be
fantastic
and
also
if
you
could
select
red,
yellow
or
green
in
terms
of
your
confidence
and
where
things
are
at
that
would
be
great.
A
So,
for
example,
if
we're
getting
ready
to
release
in
a
week
and
there's
a
million
build
failures,
I
would
expect
to
see
the
status
on
that
as
red.
So
what
this
does
is
it
gives
future
civilizations
as
they
unearth
the
archaeology
of
kubernetes,
the
ability
to
sort
of
see
what
the
process
was
as
we
went
through
it
and
also
where
we
might
have
hid
risk
points
and
and
where
we
mitigated
those
risks
so
again
that
just
sort
of
first
blush
red,
yellow
green
status
helps
us
understand
where
things
are
at
going
by
the
numbers.
A
A
Nothing
has
been
identified
as
a
black
swan
sort
of
waiting
out
in
the
wings
that
that's
to
be
expected
at
this
point,
open
PRS
in
the
milestone,
there's
21
open
versus
fifty-one
closed
in
terms
of
prior
releases.
That's
actually
low
I'm
a
little
bit
surprised.
It's
that
low
I,
think
people
are
still
coming
back
from
the
holidays
or
something
but
we'll
probably
see
that
escalate.
Relatively
fast
I
went
through
the
the
release
blocking
critical
these
these
other
PRS
and
there
weren't
really
anything
in
there
that
specifically,
that
needed
addressing.
A
In
my
opinion,
if
there's
some
as
we
go
through
these
meetings,
if
you
click
on
those
links
and
see
something
that
you
want
to
talk
about,
or
that
has
particular
interest
to
your
area
of
the
release,
definitely
do
that
put
a
link
in
there
and
we'll
talk
about
it
and
the
links
to
the
test
grip
dashboards
can
review
those
last
check.
Nothing
looked
totally
out
of
whack,
but
I
haven't
actually
gone
through
that
in
the
level
of
detail
that
I
wanted
to
so
Josh
and
who's.
Your
who's,
your
shadow
Josh.
A
D
D
This
is
sand
just
introduce
some
new
feature
on
Tesco.
It's
if
you
open
one
up
those
dashboard.
It's
pretty
easy
to
see
the
fading
or
the
fading
tests
are
showing
up
as
red.
Now
on
the
extra
port
city
opens
degree.
These
master
blocking
can
see
both
of
them.
The
tabs
are
in
blue
color,
but
the
winds
are
currently
in.
A
high
theory
is,
is
in
red,
it's
pretty
identify
like
which
ones
are
passing,
which
would
starting
now.
A
Looking
pretty
good
I
mean
sig.
Node
is
the
sort
of
the
hub
of
activity
there
and
it
and
note
about
this
too.
Is
that
so
anybody
any
particular
issue
can
have
multiple
SIG's
attached
and
so
there's
gonna
be
there's
not
a
one-to-one
relationship
between
account
here.
So
when
you,
when
you
have
these
issues
a
lot
of
times,
sig
note
will
be
a
secondary
or
or
somebody
that's
seen
as
a
visibility
on
these
issues.
A
A
B
A
A
D
Yeah
not
rather
than
to
release
yet,
but
we
switched
over
our
80
days,
account
from
Google
sponsor
to
a
list
on
to
the
same
staff
account
so
that
account
currently
does
not
happy
enough
Kota.
Yet
so
you
might
see.
Are
they
addressed
as
well
like
randomly
failing
to
bring
up
clusters
such
things
and
sick,
80s
I
believe
is
working
with
focusing
with
focusing
Island
to
figure
out
other
color
issues.
Okay,.
C
D
A
E
A
Then
what
it
says
in
the
dr.,
great
yeah,
so
I
need
to
set
up
the
Winton
Doc's
branch
just
like
just
like.
We
have
in
the
past
and
start
bringing
CEG's
Jennifer
just
because
somebody,
some
people
here
might
not
know
the
process.
Do
you
mind
explaining
the
the
docs
branching
strategy?
Because
it's
different
than
the
release.
E
Right
we
publish
Docs
from
master,
so
I'm
PRS
against
Doc's,
for
a
release,
go
against
a
Doc's
release,
a
you
know,
numbered
by
the
release.
So
this
will
be
I.
Don't
remember
the
exact
syntax
I'm
not
looking
at
it
right
now,
but
basically
it
calls
out,
though
one
doc
ten
minutes.
This
has
created
a
little
pain
in
the
past,
but
one
of
my
responsibilities
is
to
make
sure
and
typically
other
SIG's
maintainer
is
also
help
can
sort
of
catch
PRS.
E
A
C
E
Know
that
is
not
completely
updated.
It
was
simply
in
my
first
attempt
to
get
content
that
we've
been
maintaining
in
a
Google
Doc
into
the
right
repo
with
everybody
else's
role
documentation.
So
it
needs
to
get
updated
and
it
also
needs
to
cross
references.
Sig
Docs
is
well
the
docs
release.
Lead
is
now
on
taking
charge
of
generating
the
generated
Doc's.
It
used
to
be
a
bit
of
communication,
muddled
and
we're
still
ironing
out
the
last
wrinkles
to
that,
but
we
have
that
documented
elsewhere.
E
A
A
C
C
Unfortunately,
not
all
the
feature
owners
have
updated
their
features,
because
I
found
a
few
that
may
target
one
to
ten
as
well.
So
that
was
the
primary
reason
why
we,
we
decided
to
extend
their
features
deadline
at
the
same
time,
the
key
features
and
the
key
messengers
can
be
identified
today
and
right
now
for
all
for
the
upcoming
release.
So
I
hope
that
session
from
today
we
can
start
working
and
I
will
make
again
strategy
from
one
to
ten
release.
Great
Natasha.
G
Say
we're
gonna
meet
later
today,
just
to
look
at
the
features
you
know
PMS
or
key
messaging
around
them
to
this
community.
The
blog
outline
just
kind
of
get
all
of
those
things
in
order
and
ready
to
go.
So
we
can
move
forward
and
get
some
solid
drafts
to
the
release
team
in
early
February,
probably
by
February
6
to
10.
So
they
were
a
little
ahead
of
the
game.
A
A
All
right
least
notes
update,
so,
thankfully,
that
the
the
draft
was
made
Thank
You
Nick
for
that
and
what
we'll
start
doing
is
working
on
populating
that
I
would
love
to
know
from
Jennifer
and
Nick.
If
you
guys
had
any
discussions
about
whether
you
wanted
to
do
this
in
a
Google
Doc
outside
of
the
github
file
or
what
what
served
you
thought
was
the
best
practice
there.
E
But
I
we
have
talked
Nick
would
really
like
to
see
us
moving
to
a
better
with
generated
Docs.
There's
Nick
I
just
today,
looking
at
a
horse
release
list
and
thing
about
the
issues.
Reviews
been
thinking
about
some
additional
possibilities,
but
we
have
not
actually
sat
down
and
talked
about
that.
This
is
the
first
thick
is
hearing
that
I
have
been
thinking
about
other
possibilities,
so
we'll
update
you
in
the
next
meeting
or
Nick
can
tell
y'all
what
he's
thinking
about.
Now,
because
he's
here
and
I
need.
A
A
Next
week,
then,
we
will
have
a
discussion
all
right.
Any
announcements,
I'm
gonna,
go
ahead
and
turn
the
microphone
over
to
the
assembled
team,
and
any
questions
are
you.
Does
this
meeting
feel
like
it
was
effective
and
useful
for
you
all
that
good
stuff,
so
I'm
gonna
turn
my
mic
off
and
feel
free
to
chime
in.