►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191204
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
hello,
good
morning,
everyone
it
is
week
11
of
the
kubernetes
117
released.
This
is
the
Wednesday
morning
burn
down,
I
am
going
to
be,
or
Sankar
and
I
will
be
your
host
today,
please
be
kind
to
each
other
and
adhere
to
the
kubernetes
code
of
conduct
and
I.
Think
that's
it
and
we
can
get
started
with
a
nominal
nod
to
enhancements
things.
C
Weary
as
well
I
think
the
master
master
loops.
Just
look
amazing.
It's
just
like
green
from
top
to
bottom,
which
is
pretty
much.
What
do
you
want
to
see?
So
that's
pretty
amazing.
The
informants
are
like
not
there
yet,
but
where
there's
like
couple
of
issues
that
we're
tracking
there's
actually
one
with
six
scheduling,
you
already
got
someone
to
like
address
that
so
there's
a
PR,
so
I
hope
that
that
will
go
to
green
soon
and
yeah.
A
Okay,
yeah,
we
should
probably
mention
those
windows
jobs
on
the
retrospective,
so
the
next
team
knows
what
to
follow
up
on,
but
that
that's
that's
what
I
want
to
hear
this
is.
This
is
too
good
we're
less
than
a
week
away
from
release
date
and
that's
been
pretty
much
the
case
where
every
release
said
I've
been
on.
It's
always
been
like
super
great
five
days
out
and
then
anyway,
I
really
really
hope.
It's
gonna
stay
great.
Thank
you.
So
much
for
your
hard
work
and
all
your
following
up
on
this.
D
E
Sorry
I
took
me
a
while
to
find
the
window
so
I'm
Marc.
This
is
green.
We
don't
have
any
critical,
urgent,
PRS
or
issues
or
important
issues.
There's
five
important
soon
PRS,
but
four
of
them
are
four
of
them.
Are
cherry
picks
like
automated
cherry
picks,
and
then
one
of
them
is
a
failing
test,
I
believe
so
that
is
still
in
progress.
E
So
I'm
not
sure.
What's
gonna
happen
with
that,
but
other
than
that,
I
marked
it
as
green,
because
we
really
haven't
had
any
critical,
urgent,
PRS
or
issues
come
in
in
the
past
24
hours.
Since
the
last
meeting,
which
is
really
nice
yeah.
A
A
A
Let's
see
cherry
pick,
cherry
pick,
those
were
all
opened
fairly
recent
and
they
are
literally
all
just
waiting
to
be
approved.
For
cherry
pick,
yeah
it's
for
me.
We
should
go
ahead
and
see
if
we
can
get
approval
on
those
because
they
might
have
an
effect
on
the
tests,
so
I'm
a
little
bit
concerned.
I
hope
not,
but
the
sooner
we
can
get
those
merged
abutters
we
should
follow
up
on
those
okay
is.
A
A
F
A
A
A
G
I
E
Was
just
that
that
one
test
PR
that
we
weren't
sure
about
the.
E
Let
me
just
pull
it
one.
Second,
because
I
am
slow,
it's
good
to
make
sure
good
enough
coffee.
Yet
it's
the
GC
GC
II
costs
beta
cereal
test.
That's
failing
it's
an
open
issue
right
now
and
then
I
think
there
will
eventually
be
a
PR
for
that,
but
I'm
not
really
sure
like
the
ETA
on
on
it.
But
people
are
talking
about
it
on
the
issue
today,
all.
G
Yeah,
we
might
need
to
do
something
about
this.
That.
G
E
A
A
J
I
C
C
A
H
Yeah
I
think
my
only
update
is
that
we
are
missing
about
two
rules
for
the
118
team:
the
lead,
roll
and
then
bug
triage
July
is
not
on
the
call.
So
I
will
ping
him
over
slack
just
to
see
if,
if
he
has
a
successor
in
mind,
you
can
nominate
additionally
for
any
shadows
and
leads
expect
a
117
experience
survey
coming
out
between
now
and
release
day-
hopefully,
hopefully
tomorrow,
if
I
have
enough
cycles
today
to
get
that
finished.
A
K
G
I
K
H
A
A
fallback
yeah
I'll
follow
up
on
that.
That
brings
me
to
my
updates.
The
retro
is
scheduled
for
December
12th,
that's
Thursday
at
the
time
of
the
kubernetes
community
meeting
the
other
thing.
What
was
the
other
thing,
I
was
gonna,
say:
I
will
have
the
retro
doc
up
sometime
today
or
tomorrow,
so
think
about
what
you
want
to
put
in
the
retrospective
things.
Think
about
things
that
went
well
for
you
and
your
team
think
about
things
that
can
be
improved.
That
doesn't
necessarily
mean
just
the
team.
A
One
of
the
things
I'm
gonna
put
on
there
is
I
need
bigger,
greater
faster
responsiveness
from
Sega
needs,
so
that
can
also
be
in
the
retrospective,
even
though
we
might
not
have
the
most
amount
of
control
over
it
should
still
be
in.
There
should
still
be
documented,
go
over
the
retrospective
action
list
from
last
release
and
see
what
we
worked
on,
what
we
improved
on,
what
we
followed
up
on
and
I.
G
I'm
gonna
try
my
best
to
drain
everything
in
that
list
by
the
time
that
we
hit
the
retro
I'm,
basically
I've
gotten
to
the
point
where
or
if,
like
shifted
milestones
for
the
things
that
are
assigned
to
me,
reassign
people
where
I
don't
need
to
be
assigned
anymore
and
a
lot
of
it
looks
like
documentation
and
p.m.
work
at
this
point,
so
I'm
gonna
try
to
drain
through
that
I
would
say
moving
forward.
G
What
we
should
probably
do
is
make
sure
that
the
the
new
emeritus
adviser
creates
the
retrospective
list
so
that
they
can
maintain
it
because
they
won't
necessarily
have
edit
access
to
the
repo
and
only
doing
a
is
for
a
single
release,
and
maybe
we
can
have
an
umbrella
for
all
of
the
retros
that
links
out
to
the
individual,
a
eyes,
a
eye
issues
right.
So,
like
one
match
high.
A
G
Yeah,
so
it's
it
yeah,
so
we
have
so
we
have
one.
We
would
have
one
massive
umbrella
that
would
track
the
eyes
are
tracked:
the
issues
for
a
eyes
across
multiple
release
cycles
and
then
individual
issues
that
are
assigned
to
each
of
the
emeritus
advisors
for
each
release,
cycle
that
have
the
release
cycle.
Specific,
yes,
I
feel,
like
I,
said
the
same
thing
three
times
in
three
different
ways:.
A
G
Would
say
that
that
responsibility
should
be
split
across
the
leads
and
the
emeritus
advisor
I
want
to
try
to
sweep
your
handbook
as
well.
By
the
time
the
release
is
out
or
well
are
just
a
little
bit
before
the
next
one
starts
to
fix
some
of
the
things
in
timelines
and
make
sure
some
of
the
links
are
correct,
yeah
and
have
that
as
well
as
the
emeritus
advisor
handbook,
so
that
we
can
try
to
squeeze
some
of
the
things
that
the
release
team
lead
doesn't
necessarily
need
to
do
out
to
the
emeritus
adviser,
sure
and.
A
A
G
Speaking
of
that,
there
was
an
issue
that
was
recently
opened.
I
know
Elena.
You
already
took
a
look
at
it,
but
talking
about
talking
about
async
tasks
that
we
can
do
on
the
release
team
right
and
how
we
get
that
done,
because
it's
kind
of
not
great
for
all
the
people
who
are
non-us
time
zones
to
to
try
to
work
and
be
synchronous
during
this
meeting,
especially
as
it
hits
burn
down
time.
So.
G
G
Maybe
we
can
make
that
part
of
the
feedback
survey
I,
think
that
I.
So
this
has
been
brought
up
multiple
times,
I
think
as
at
least
as
long
as
I've
been
on
the
release
team
or
around
the
release
team,
and
it's
something
that's
hard
to
do
period
like
we're
always
going
to
we're
always
going
to
buy
slightly
towards
the
people
who
are
in
the
time
zones
that
are
most
frequently.
H
G
Right
so
so
it's
hard
to
do
in
general,
I
told
David,
because
he
DM
to
me
and
I
said:
listen
you
run
with
it.
I
was
like
you
are
assigned
to
this.
You
go
run
with
it
because
we
need
someone
working
on
it.
That
is
not
in
a
US
time
zone.
So
we're
not
applying
our
bias
to
whatever
the
process
might
be
right
right.
A
A
So
if
we
collaborate
closely
inside
of
our
teams
and
and
I
think
some
some
of
the
teams
are
doing
that
more
closely
than
others,
but
that
way
we
can
keep
people
updated
and
keep
people
posted
without
waking
folks
up
at
3
o'clock
in
the
morning
or
having
them
stay
at
work
until
way.
Past
dinner
time,
yeah.
G
So
I
mean
it's
also
I
think
we're
going
to
see
I
think
it's
really
important
to
keep
the
synchronous
meeting
or
keep
some
synchronous
meetings.
I
know.
In
the
past
we've
tried
to
do
multiple
meetings
at
skew
time
zones
and
have
the
release
team
lead,
shadows
run
one
of
them.
If
they're
in,
like
amia
or
AIPAC.
G
G
A
G
Also
going
to
send
an
email
out
regarding
that
stuff,
it's
it'll
be
a
more
general
email
about,
like
hey
sigelei.
This
is
like
read
the
mail
that
you're
specifically
assigned
to
and
expected
to
read
as
part
of
your
role
as
a
sig,
chair
or
technical
lead.
So
if
there
are
things
that
you
want
me
to
drop
in
that
note,
let
me
know
because
I'll
send
it
before
the
end
of
the
day.