►
From YouTube: WG LTS Bi Weekly Meeting 20200804
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).
B
A
So
the
the
last
thing
that
was
spearheaded
by
this
working
group
was
trying
to
go
from
a
two
years
worth
of
you
know,
releases
right.
So
what
do
we
want
to
do?
Next?
What
can
we
shoot
for
next?
Basically,
basic
question
and
the
thing
that
helped
us
there
was
the
release
team,
switching
from
like
individual
release,
managers
responsible
for
a
specific
release
to
a
group
of
managers
that
can
like
attack
them
to
push
a
release
out.
That
kind
of
like
helped
out
right.
A
So
I
was
trying
to
see
what
would
be
the
next
thing
that
we
can
shoot
for
here,
and
you
know
what
would
be
the
obstacles
for
that
and
I
think,
over
the
weekend
or
was
it
friday?
Somebody
asked
a
question
on
twitter
and
my
answer
to
that
was
like
okay,
we
have
to
get
a
bunch
of
features
from
beta
to
ga.
A
Only
then
we
can
think
about
an
lds
at
that
point.
What
was
like
this
is
all
stuff
from
older
discussions,
and
I
don't
know
if
there's
any
new
things
that
you
all
came
up
with
or
thought
about.
I
was
repeating
what
we
had
talked
before.
B
Yeah
yeah
yeah,
so
I
think
the
last
time
we
talked
about
the
last
time
we
talked
about
stuff
was
the
I'm
sorry,
I'm
just
gonna
post
to
the
channel
that
we
are
actually
having
a.
B
See
me
pop
in
and
pop
out,
so
you
asked
me
the
question.
Yes,
that's
right,
yeah
yeah!
I
got
that
because,
because
yeah
I
got
the
email
from
zoom
being
like
your
meeting.
Attendees
are
waiting
because
I
mean
I
say
because
I
gotta
get
up
at
like
1
30
in
the
morning
to
do
this
call.
So
that's
why
I'm
like
well.
I'd
rather
have
the
call
and
who
got
up
cause,
I'm
bigger,
I'm
fighting.
B
No,
no!
That's
fine,
like
I
said
I'd
rather
have
caught
up
with
it.
I've
got
the
club
for
something.
So
yes,
I
think
the
the
last
time
we
talked
about
other
stuff
we
got
to
do
so
I
mean
now
now
the
kept
is
implementable.
B
The
I
mean
that's
sort
of
a
large
part
of
what
we
wanted
to.
That
was
the
initial
goal,
but
yeah.
We
definitely
talked
about
that
in
order
for
things
to
be
supportable.
B
For
for
a
year
like
and
to
be
more
supportable,
we
need
to
make
sure
that
you
know
we
clear
all
those
clear
all
the
beta
apis
out
and
make
and
be
better
and
have
everyone
better
about
the
the
yeah
getting
apis
to
ga.
So
I
think
just
trying
to
remember
jordan
did
a
lot
of
work
on
this.
I
think
the
last
thing
I
remember
yeah.
The
last
thing
I
remember
was
that
that
was
sort
of
insane.
You
know,
I
think
the
only
one
left
is
ingress
now
yeah.
B
I
think
we
need
to
ask
me
to
check
with
him,
but,
yes,
I
think
a
lot
of
a
lot
of
that
work
is
also
done.
So
the
stuff
that
tim
had
mentioned
was
was
here
talking
about.
B
How
people
some
people,
you
know
people
have
some
people
have
asked
for
slower
releases
and
other
people
have
asked
for
faster
releases,
and
you
know
is
that
something
that
this
one
group
needs
to
talk
about,
because
it
came
up
a
lot
in
the
discussions
of
increasing
the
support
period
was
well.
If
we're
messing
with
the
support
period,
do
we
change
the
release
cadence
as
well,
and
that's
why
that's
why
the
support
period
kept
says
one
year
rather
than
three
releases,
so
we
could
be
like
hey
we're
not
talking
about.
B
We
don't
want
to
open
this
can
of
worms.
We've
got
enough
worms
already
thanks.
A
It's
if
we
have
to
slow
people
down
and
make
them
think
and
ask
ask
them
for
like
to
put
their
foot
down
on
something
right.
We
have
to
set
their
expectation
like.
Let
me
put
it
in
another
way.
For
example,
we've
talked
several
times
about
having
the
last
release
in
the
year.
Basically
they're
short
of
time.
There
is
kubecon.
A
There
is
christmas,
you
know
lots
of
holidays,
so
we
all
and
it's
always
a
short
release,
and
so
it
it
almost
feels
like
if
we
can
designate
the
last
release
of
the
year
as
a
stabilization,
stabilization
release
and
basically
say
no
features
allowed
yeah.
B
You
know
and
the
thing
that
this
whole
exercise
I'm
trying
to
change
the
support
window
has
taught
me
is
that
when
you
want
to
get
such
a
big
project
to
change,
things
like
you've
got
to
be
incremental
about
it
like
otherwise.
You
know
you
end
up
with.
A
B
We've
got
to
find
small,
relatively
easily
implemented
things
that
people
will
probably
agree
to
through
the
minimum
hassle.
If
we
want
to
and
the
more
we
do,
those
things
the
more
we
will
prove
that
you
can
change
things
and
then
it
will
be
easier
to
make
bigger
and
bigger
bigger
changes.
B
Yeah,
I
think,
like
I,
I
think
I
think,
having
the
last
release
of
the
uv
sterilization
is
a
great
idea
personally,
but
you
know
we'll
probably
need
to
that
feels
like
a
yeah.
We'll
definitely
need
to
talk
a
secret
release
about
that
one
I'd
rather
not
make
them
panic
again,
like
I
did
when
I
put
put
the
wrong
piece
on
the
camera.
Initially,
I
feel
like
I've
used
up
my.
A
B
For
my
lifetime
yeah
so
that
one
that
one
is
fair.
A
There
is
some
momentum
behind
it
that
we
can
gather,
because
sick
testing
is
trying
to
clamp
down
on
stuff
and
sig
release.
You
know
is
kind
of,
like
has
its
hand,
hands
full
because
of
the
long
release
that
we've
had.
For
you
know,
119,
and
you
know
the
ci
is
still
in
a
mess
when
we
are
trying
to
stabilize
it
in
many
ways,
so
there
they
would
be
definitely
be
amenable
to
it.
A
What
we're
going
to
face
thinking
aloud,
as
you
know,
the
teams
that
really
that
rely
on
features
like
node
or
yeah
yeah,
not
even
api
machinery
to
that
extent,
but
there
are,
you
know,
teams
that
rely
on
getting
things
in
and
those
are
the
ones
that
are
not
going
to
be
happy.
A
B
Yeah
yeah,
I
mean
yeah
yeah,
everybody
who's,
who
still
has
a
big
all
the
things
who
still
have
a
relatively
large.
You
know,
change
set.
Every
release
are
going
to
be,
like
you
know,
missing
at
least
a
year
kind
of
sucks
yeah.
So
I
mean
I
I
would
probably
put
maybe
I
mean
I
think
oh
yeah,
I
think
signon
is
really
the
only
one
where
a
lot
of
it
is
still
in
the
corner.
Right
like,
and
it's
still
coupled
with
the
most
of
the
network
stuff
is.
A
A
If
you
tell
them,
don't
do
features
they
they're
gonna
ball.
So
we
have
to
say:
do
these
things
first
and
if
you
still
have
room
then
do
features,
or
you
know
that
doing
features
should
be
the
like.
The
last
thing
on
the
list
or
list
of
items
like
you
have
to
front
load
them
with
a
bunch
of
things
saying
push
for
conformance.
Make
sure
that
you
add
more
tests
for
conformance,
promote
things
that
are
not
in
conformance
conformance
right.
A
Make
sure
that
there
are
no
flakes
make
sure
you
add
ca
jobs
for
the
things
that
you
you
needed
chr's,
but
you
put
them
off
right
like
come
up
with
this
kind
of
a
checklist
where
we
give
them
a
bunch
of
tasks
to
do,
and
so
they'll
have
their
hands
full.
Basically,.
B
Basically,
basically,
basically
having
it
having
that
last
release
of
the
year
be
the
one
where
c
testing
gets
to
be.
Like
you
know,
hey
you've
got
to
do
your
chores
before
you
get
your
ice
cream.
A
Oh,
this
is
not
my
phrase,
it's
it.
It
came
from
for
sure,
but
yeah
yeah.
We
had
a
similar
talk
in
a
different
in
this
sick
testing
stuff
and
then
I'm
like
reflecting
on
what
was
that
there.
B
Yeah,
okay,
so
that
makes
sense.
Yeah
so,
and
I
mean
I
think
thank
you
for
coming
to
the
call
by
the
way
like
it's,
you
know,
with
the
captain
of
all
like
and
we
haven't
had
many
people
showing
up
and
since
we're
mouthful
as
well,
it's
been
harder
to
get
people
to
shop
because
no
one's
coming,
yeah
yeah,
so
yeah.
That
makes
sense
to
me.
B
B
B
You
know
some
sort
of
relatively
broad
group
focused
on
you
know
on
just
poking
making
sure
that
the
support
of
the
overall
support
ability
of
the
project
is
being
poked
forward.
B
Where
there's
these
cross-cutting
things
like
you
know
like
that
sort
of
thing,
because
you've
got
testing,
no
release
all
needed
to
be
involved
in
that,
and
without
a
without
sort
of
some
sort
of
coordination
function
to
to
have
a
place
to
raise
this
sort
of
thing.
Then
it's
on
a
single
person
like
you
to
to
head
to
all
of
those
things
and
and
actually
make
the
change
happen,
rather
than
having
a
place
where
we
can
come
and
be
like
hey.
I
think
that
we
could
increase
the
supportability
by
doing
this.
A
Okay,
so
take
a
peek
at
this
dock
and
I'll
point
you
to
the
thread.
Also,
where
is
this
thread
this
is
on?
This
is
spilled
over
many
different
email.
A
I
am
trying
to
get
you
a
link
here.
Yeah.
A
Yeah
and
the
doc
is
the
one
that
was
pasted
by
you
know
that
was
pasted
by
whitetail
yeah.
Let
me
give
you
the
email
where
it
came
from
as
well.
So
you
know
the
context.
A
This
kind
of
goes
with
the
flow
of
what
you
were
talking
about
like
increased
stability
of
kubernetes,
so
you
are
vmware
right
yeah
and
where
are
you
located
sydney,
sydney.
A
A
So
maybe,
if
we
are
done,
we
can
switch
a
little
bit.
I
wanted
to
ask
you
a
few
questions.
C
B
C
Okay
sounds
good,
give
me
five
minutes
and
then
I'll
I'll
shoot.
You
a
link,
sorry
to
everyone
who
might.
B
Be
watching
the
recording
that
this
is
a
bit
of
a
weird
call
but
yeah,
hopefully
we'll
see
we'll
see
more
people
on
a
future
seek
on
a
future
lte
wg
lts
meeting.