►
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
Okay,
welcome
to
the
Monday
April
20th
Pacific
Time,
meeting
of
the
azure
sub-project
of
sit
cloud
provider.
It's
Tuesday
we're
big
day
and
cidar.
This
is
a
meeting
of
in
the
urbanized
community
and
thus
will
abide
by
the
community's
code
of
conduct
so
be
good
to
each
other.
This
meeting
is
being
recorded
and
will
be
posted
to
YouTube.
I
have
dropped
the
link
to
the
agenda
documents
into
the
chat.
I
have
a
few
agenda
items
that
I'd
like
to
cover
and
either
you
should
feel
free
to
add
your
own
items
and
we'll
go
from
there.
A
We
had
been
alternating
between
this
time
slot
and
the
time
slot
that
was
early
in
the
morning
and
Pacific
time,
which
meant
the
middle
of
the
night
and
eastern
Asia
and
Australia,
and
in
the
afternoon
in
Europe,
hoping
that
we
might
attract
some
contribution
from
folks
in
Europe
that
did
not
pan
out.
We
got
no
additional
participation
there,
and
so
the
proposal
was
just
to
switch
back
to
this
time.
A
Slot
got
plus
ones
from
Stephan
augustus
and
Rita
Jiang
and
that
you
two
are
here:
I'm
guessing
you're
voting
with
your
but
I'd
like
to
hear
if
this
is
a
good
time
for
you
guys
or
if
we
should
adopt
a
different
time.
If
this
is
a
good
time,
then
I'm
prepared
to
make
the
PR
and
update
the
community
pages
this
time.
What
do
you
guys
think.
B
B
A
B
B
A
B
B
So
you
know
future
I'm,
not
sure
whether
whether
the
cloud
provider
would
like
to
make
them
were
in
the
API.
So
so
then
each
cloud
provider
could
match
the
teacher
couldn't
manager
the
version,
the
version
metrics
more
easily
by
the
paddle
from
today.
If
it
were
hard
to
do
then,
because
we
just
the
bender,
then
has
a
library
and
there's
no
way
to
ensure
the
the
library
contains
no
break
in
today.
A
A
A
Providing
LTS
in
kubernetes
and
the
proposal
is
to
support
so
I,
basically
add
one
more
minor
version:
support
of
kubernetes
would
be
we'd
need
to
support
three
versions
and
it
would
provide
14
months
of
patch
version.
Support
I
can
include
the
kept
PR
in
the
notes,
if
that's
helpful
to
folks,
but
what
I'm
wondering
is:
are
there
implications
for
us
in
the
cloud
provider.
B
Okay,
so
I
think
if,
if
the
LTS
is
approved
very
faster
and
so
forth,
the
other
cheek
referral
is
another
table
years
then
introduced
and
chose
for
us
I'm,
not
sure
the
the
chart
thicker
than
the
order
for
LTS
a
branch
budget
for
for
Agri.
So
some
80s
some
error
changes
names
may
require
some
new
features.
So,
for
example,
a
person
may
be
required
with
the
new
version
I'm,
not
sure
whether
it
is
allowed.
She
updated
those
dependencies
in
with
long-term
supporters
branch
I.
A
B
D
D
D
A
B
A
B
B
A
A
So
I
guess
what
this
means
is
that,
once
this
step
is
adopted,
let's
say
it's
adopted
around
the
timeframe
of
119.
It
means
that
that
18,
we're
not
17
and
when
that
16
will
still
remain,
maintain
patch
release
branches,
and
it
just
means
that
the
community
will
provide
patches
for
those
releases,
whereas
we've
been
on
our
own
to
do
that.
For
the
older
versions.
B
B
A
A
A
B
This
is
edited
by
me
so
actually
the
length
of
the
test
coverage
improvement
plans
so
so
for
last
release
cycle.
We
have
refracted
all
the
airlines
to
80
supporters,
the
richer
Africa
Haider
from
various
area,
clients,
and
also
she
supported
the
back
of
the
choice,
series
limits
and
so
on.
So
this
helps
a
lot.
She
resolves
or
something
easier
with
a
cross
different
client.
But
after
than
that,
our
client
has
here
using
the
fixed
client.
So
we
should
switch
then
into
our
new
way
and
improve
our
test
coverage.
B
B
B
So
for
unchain
test
we
should
also
cover
to
the
rich
condition:
scenarios
for
concurrent
request
from
deeper
engine
results.
So,
for
example,
the
Bayonetta
update
may
be
complicated
with
the
load
balancer
update.
So
we
didn't
know
that
before,
but
here
just
a
loaner
from
last
year
is
duty
cycle,
so
you
know
ng.
In
that
case
a
we
should
cover
those
rich
condition.
A
B
B
A
B
And
the
last
one
is
so
we
want
to
retract
what
has
been
meeting
you
know
occurring
the
energy
in
touch,
so
we
actually
already
have
some
sometimes
in
Nevada,
including
the
the
component,
has
the
locust.
So
the
scallion
has
the
Calipari
test
and
so
on,
but
they
are
actually
some
features
that
they
are
meeting
there.
So
we
should
check
out
check
whether
wealth
could
weigh
at
the
mall,
for
example,
the
keep
youth
hostel.
We
did
have
calendars
yet
and
also
for
the
bottle
diameter
that
I
figure
it
also
not
the
body
do
yet.