►
From YouTube: WG LTS biweekly 20200609
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
B
B
A
B
A
Wondered
how
many
people
were
gonna
actually
get
today
because
there's
so
many
different
things
going
on
at
the
moment,
and
we
don't
have
a
whole
lot
to
talk
about.
I've
got
a
couple
things
too
that
are
fairly
minor
to
make
sure
we
follow
up
on
yeah
coming
weeks,
but
we
talked
about
those
give
people
another
minute
or
two
I
guess
yeah.
B
A
Yeah,
that's
that's
basically,
that's
what's
on
my
list
for
to
talk
about,
for
they
all
I'll
type,
these
in
the
minutes
just
for
agenda
wise
and
then
we
can
get
into
it
in
a
few
minutes
if
anybody
else
tries
to
otherwise
just
to
sync
up
us.
A
B
A
I
know
what
I
did
so
I
was,
as
I
was
starting
to
write
things
for
the
agenda
today.
The
couple
things
that
we
probably
should
talk
about
I
noticed
that
we
didn't
have
the
recording
linked
from
last
time,
so
I
grabbed
it,
but
YouTube
then
started
to
autoplay,
but
with
like
a
minute
of
silence
at
the
beginning,
so
that
window
is
long,
bury
the
body
voices
and
like
what
well
in
a
partly
josh
has
had
issues
where
zoom
like
miss
identifies
him
and
I
was
like.
A
A
All
right,
we
may
as
well
get
goin
it's
eight
minutes.
Past
I
did
a
couple
things
in
the
agenda
and
should
have
done
that
last
week,
so
it
was
there
and
clear
for
anybody
who
wondered
if
we're
gonna
be
talking
about
anything.
So
the
the
two
meta
things
are
well
really,
though,
the
one
meta
topic
at
this
point
is
documentation
yeah
degree.
How
do
we
spread
the
word?
So
the
two
specific
things
there
then
blog
post,
the
release
team
has
reached
out
for
that
and
I
will
start
a
Google
Doc
for
that,
okay,.
B
A
Then
we
can
kind
of
collaborate
on
it.
I
think
this
should
be
fairly
lightweight
shouldn't,
be
too
big
of
a
deal.
The
only
question
I'd
wanted
to
start
this
like
last
month,
but
I
was
kind
of
waiting
to
see
what
happened
with
respect
to
two
one,
not
sixteen,
seventeen
and
eighteen
own
backup
for
anybody.
Who's.
Listening
to
this
on
the
recording
or
checking
in
everything
that
we've
been
talking
about
so
far
has
been
about
increasing
well
so
far,
so
far
kind
of
this
year.
A
After
all
the
discussions
last
year,
we've
been
discussing
increasing
the
patch
support
timeline
for
kubernetes
releases
to
one
year,
or
previously
it
had
been
nine
months
or
sort
of
three
active
releases.
At
a
time
the
we'd
proposed
to
cap.
It
went
into
the
enhancements
repo
as
provisional
earlier
this
spring
and
then
last
week
it
merged
as
implementable
as
it's
written.
A
It
covers
one
nineteen
and
newer
getting
the
the
one
year
of
patch
support
and
there's
been
discussion
that
kind
of
petered
out
around
it
for
how
we
do
that
for
maybe
1.18
1.17
1.16,
which
are
currently
in
support.
So
if,
as
we
make
a
blog
post,
we
just
have
to
those
things,
we
can
definitely
talk
about
the
basic
state
with
119
mentioned
that
there's
discussion
for
others
point
over
to
the
locations
where
those
discussions
are
see.
A
If
maybe
we
get
some
additional
useful
input
there
that
sways
the
conversation
one
way
or
the
other,
but
I
think
we
need
to
be
careful
not
to
sort
of
send
incorrect
message
on
those
earlier
releases
and
it's
hard
because
the
message
right
now
is
incomplete.
We
would
maybe
overstate
things
if
we
say
us,
it's
not
going
to
happen,
but
we
we
maybe
give
too
much
hope.
B
A
So
we
need
to
find
a
place
for
that
documentation
to
live
and
then,
ideally
as
where
we're
doing
our
scheduled
releases,
which
at
this
point
we're
making
patch
releases
on
a
monthly
cadence
as
we
keep
that
schedule
up
to
date,
we
need
a
way
of
doing
that
more
mechanically.
Instead
of
just
somebody
manually,
editing
a
markdown
document,
or
as
we
is,
we
have
things
in
multiple
repos
and
it
becomes
multiple
PRS
against
multiple
markdown
Docs
or
the
neckla
fire
related
things
on
the
official
website.
A
So
what
we've
been
talking
about
for
a
while
and
sig
release
is
moving
over
to
a
machine-readable
schedule
and
sig
Docs
was
interested
in
that
we've
got
the
early
starts
of
that
now.
There's
a
tool
linked
in
the
minutes
for
a
schedule,
creator
or
schedule
builder,
and
an
initial
draft
PR
of
the
first
implementation
of
that,
and
if
we
start
operationalizing
that
on
the
sig
release
side,
then
it
should
be
something
that
sig
Doc's
can
rely
on.
But
we
just
need
to
to
go.
Have
an
additional
conversation
with
sig
Docs
like
is
that?
A
A
So
those
are
the
main
things
really
that
I
wanted
to
just
mention
today
and
and
really
like
I
had
said
last
week,
come
with
the
stuff
coming
out
of
sig
release
that
I
would
chase
that
down
with
sig
Docs,
so
I'm
happy
and
able
to
do
that.
And
then
it's
especially
on
the
blog
post
I
would
like
to
have
lots
of
eyes
and
hands
on
drafting
that.
But
I'll
get
some
initial
something
started
for
conversation
and
share
out
a
Google
Doc.
B
I
think
I'm
currently
on
the
sig
releases
list
as
the
person
who
should
be
making
a
payoff
a
doctor
PR.
Do
you
want
me
to
like
over
a
placeholder
Pia.
B
A
And
oh,
and
so
one
other
thing
that
came
up
in
the
the
release
team
meeting
on
Monday.
That
should
be
getting
some
announcement.
They're
gonna
push
those
out
a
week
or
two
okay,
I'm
pretty
a
week,
so
the
the
twelfth
while
it
feels
like
it's
looming
isn't
actually
looming
against
us
good
placeholder
PR.
That
would
just
be
like
a
dummy
PR
against
a
random
file,
but
that's
like
useful,
so
I
think
in
the
issue.
A
Page
or
blurb
on
a
page
that
describes
what's
currently
in
support
right
now,
for
example,
so
like.
If
you
went
to
Kate's
dot,
IO
you're
running
kubernetes
1.13,
you
could
find
out
that
you're
not
gonna,
get
support
on
that
or,
if
you're,
if
you're
running
one
dot
18.1,
you
want
to
know.
What's
the
current
release,
if
you're
looking
at
the
118
docs,
for
example
like
maybe
this
is
per
Doc's
branch
cuz,
that
if
you're
looking
at
the
118
Doc's
you
might
want
to
see
like
one
at
18.3,
is
the
current
release.
E
A
And
it
they've
been
asked
to
have
that
to
get
more
detail
than
that.
So
that's
where
we're
looking
at
like.
Could
we
have?
In
addition,
just
like
that
thing
that
says
18
17
16
have
it
say
the
current
release
is
foo
and
next
release
is
expected
to
be
on
date
whatever
so
you
know
actually
said
this
page,
since
it
does
mention
the
old
release
cycle,
maybe
I
could
go
ahead
and
make
a
placeholder
PR
against
this
one.
E
A
E
E
D
E
E
A
Not
an
issue
as
long
as
we
get
this
change
in
for
119
it's
on
their
master
branch,
it
flows
into
the
119
branches
it's
created,
and
then
okay,
but
there
there
may
be
some
fuzziness.
The
I
I
still
worry
a
little
bit
about
the
119
release.
That's
shaping
up
to
be
at
least
a
five
month.
Release
we're
gonna,
maybe
get
three
releases
this
year.
But
what
the
how
the
cadence
looks
going
forward
like
we
may
need
to.
A
E
A
And
that's
kind
of
where
I
figure,
I
I'll
just
go
start
a
conversation
with
sig
Docs
folks
to
say
like
how.
How
should
we
do
this
and
there's
a
couple?
Issues
between
Docs
and
sig
relates
about
fixing
this
up,
because
we
had
broken
that
placeholder
previously
that
they
keyed
on
for
for
tracking
the
current
releases.
So
as
we
try
to
get
towards
something
better
so
that
it's
more
descriptive
for
the
readers
we
got
a.
We
got
to
figure
out
what
the
right
interlock
is
between
the
automation
on
the
two
sides
and.
A
The
release
team
in
the
any
issue
so
in
kubernetes,
enhancements
issue
1498
for
this,
but
there
was
the
one
associated
with
this
kept
it.
The
really
seems
docs
people
had
reminded
to
do
it
on
the
dev
119
branch
yeah.
B
Okay,
so
I
guess
you've
got
you've,
got
both
of
the
action
items
at
this
point.
What
a
what
else
do
you
need
us
to
do?
I,
don't.
A
Think
anything
I
figured
I,
know
Doc's
people
more
or
less
in
my
time
zone.
So
that's
sort
of
why
I
figured
like
I
would
yeah.
B
A
All
right
we'll
try
and
get
the
the
doc
stuff
rollin
and
like
I
mentioned,
we
I
I've
been
gonna
do
stuff
last
week,
but
then,
as
people
started
talking
about
pushing
the
dates
out,
it
hinted
pushed
lower
on
my
to-do
list.
It
didn't
happen,
but
it's
on
the
list
of
priority
things
to
get
lined
up
this
week,
especially
just
because
I
think
it
starts
with
conversation
with
sig
Docs
to
find
the
right
place.
Yeah.