►
From YouTube: Kubernetes 1.18 Release Team Meeting 20200226
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
I'm
gonna
start
recording
him
right
now,
so
welcome
everyone,
a
happy,
Wednesday
or
Thursday,
probably
depending
for
say
someone.
Some
part
of
the
world,
welcome
to
yet
another
release
team
meeting.
This
is
the
first
burndown
meaning
for
the
118
cycle,
and
there
was
a
there
was
a
little
bit.
There
was
a
little
management
issue
on
my
part
that
I
I
didn't
properly
send
out
the
invitations
to
everyone
on
the
team.
A
So
if
people
a
so
so
the
generate
agenda
for
today
is
going
to
be
relatively
light,
which
is
a
random
meeting,
so
it
should
be
light
just
to
start
with.
So
it's
going
to
be
even
lighter,
so
modest,
okay,
so
actually
before
we
get
started
a
since,
we
are
at
distributed
team
and
we
I
really
think
that
it
is
good
to
make
an
effort.
Is
anything
important,
a
I'll
make
sure
to
link
to
include
a
everyone
from
the
release
team
in
any
discussion
they
in
an
important
discussion,
either
slack
or
github.
A
So
then,
a
that
should
all
they
should
always
be
the
ultimate
source
of
truth
for
an
a
for
anything
regarding
the
release
team
and
for
people
who
want
to
keep
up
with
the
meeting,
because
they
were
not
able
to
make
the
meeting
because
I
didn't
have
the
invite
or
just
where
I'm
able
to
make
the
meeting,
because
it's
7
p.m.
into
your
time
zone
or
3:00
a.m.
Sunday.
Something
of
the
sort
I
said
it.
I
said
this
before,
but
I
want
to
say
it
again.
A
I
will
make
sure
that
the
meeting
notes
for
the
release
team
have
all
day
all
day
up
to
the
information.
So
if
you
miss
something
yeah,
you
should
be
a.
You
should
be
able
to
just
go
to
the
minute
through
the
meeting
notes
and
get
any
information
and
information
that
you
need
to
create
the
your
job
properly
or
you
know,
if
you're,
if
you're
curious
about
what's
going
on
and
with
that
rent,
let's
get
started.
Is
there
anyone
from
enhancements.
B
Updating
the
meeting
notes
as
we
speak,
it's
pretty
much
the
same
as
yesterday
we
did
close
out
a
couple
of
issues
that
we
notice
we're
duplicates
or
had
already
been
resolved,
but
I'll
make
sure
to
continue
to
build
off
the
notes,
I
just
chopped
down
here
and
got
them
going.
So
if
there's
any
specific
questions
on
things
that
were
mentioned
yesterday,
I'd
be
happy
to
provide
updates.
A
D
Hi
so
I'm
jumping
a
little
bit
last
minute
and
so
I
just
filled
in
our
latest
numbers
on
the
on
agenda,
and
we
are
still
green
I
mean
we
can
see
that
the
numbers
in
open
issues
and
PRS
have
been
decreasing
pretty
steadily
so
I
think
we
are
doing
with
right
now
and
so
for
the
rest
of
this
week.
We're
gonna
be
double
checking
their
all
issues
and
PR
in
the
mouth.
D
D
C
Or
Muntz
yeah
I'm
here,
that's
here,
so
please
thank
you.
E
So
docks
looks
good.
We
are
starting
to
see
a
lot
of
the
placeholder
pr's
landing
and
we're
all
chasing
down
relevant
issues.
I'd
say
we're,
probably
yellow
at
this
point.
I
have
a
lot
of
in
enhancement
owners
getting
back
to
us
about
docks,
PR,
saying
that
issues
are
being
removed
from
the
milestone,
but
I
don't
see
that
updated
on
the
sheet,
so
I'm,
assuming
that
enhancements
we'll
get
to
that.
But
I
have
three
or
four
of
the
ones
that
I'm
wrangling
that
don't
show
removed
on
the
on
the
sheet.
E
A
F
A
G
A
A
A
Okay,
yeah,
just
to
finish
off
the
meeting
with
my
update
and
with
a
with
the
next
couple
updates
a
Hubble
update.
Amelia
will
update
the
meeting
as
well.
I
got
carried
away,
trying
to
figure
out
what
to
do
with
the
calendar.
Put
a
third,
no
huge
updates
from
my
end
again
conference
is
coming
and
we
need
place
hold
a.
A
We
need
the
placeholder
paprs
to
be
in
place
by
I
believe
this
Friday
a
but
send
her
an
email
to
these
cichlids
and
to
the
accompany
a
to
take
a
them,
a
mailing
list
to
again
give
a
heads-up
to
everyone
other
than
that.
There
isn't
anything
particularly
particularly
important
that
I
build
it.
That
I
feel
I
have
to
mention
at
this
moment
and
scalability
updates
a
usually
we
don't
get
any
scalability
updates
for
the
burndown
meanings.
A
Just
usually
the
way
it
works
is
a
scallop.
Eight-Six
scalability
is
gonna,
send
someone
in
to
do
the
updates,
but
only
every
Monday.
So
unless
we
get
all
this
weekend
a
message
we
meaning
a
see
a
signal
or
someone
from
the
release
team
lead
from
the
a
from
the
lid
a
from
the
leap
team.
We
get
some
specific
message
from
six
scalability.
We
always
assume
that
nothing
has
changed
and
again
just
to
recapitulate
things
are
looking
good
on
the
scalability
front.
A
A
Come
once
twice
so
so,
okay,
again,
let
me
finish
off
this
meeting.
Thinking
thinking
every
single
one
of
you
and
I
apologize
sincerely
apologize
for
a
you,
give
a
giving
a
heads
up
about
the
meeting
510
a
5-10
minutes
in
advance,
but
hopefully
this
is
going
to
from
now
on.
We're
gonna
have
this
kind
of
this
kind
of
kinds
of
issues.
If
anyone
in
the
meeting
did
not
get
an
invite
for
the
Friday
meeting
a
please
pick
me,
it's
like
a
DME
or
DME
or
something
hopefully
I
figure
out
how
to
do
a
calendar.
A
How
to
do
calendar
invites
okay,
also
I'm
gonna
mention
here
and
I'll
mention
here
again
in
some
of
a
some
other
places
the
times
for
day
for
this
meal.
For
this
meeting,
some
different
from
the
from
the
Monday
May
and
I
made
the
decision
based
on
the
on
the
availability
of
people
who
answer
a
total
at
the
beginning
near
the
beginning
of
the
release
cycle,
I'll
send
something
out
again
at
some
point
to
a
to
the
whole
checked
and
this
that
these
times
are
still
good
for
a
forum
for
people,
but
other
than
that
again.