►
From YouTube: 2021-06-17 Crossplane Community Meeting
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
the
recording
has
started-
and
this
is
the
june
17th
2021
crossland
community
meeting.
We
are
on
our
way
towards
the
v
1.3
release
of
cross
plane,
so
we
will
jump
into
some
of
the
patch
releases
we've
been
doing
on
previous
releases
and
then
also
the
details
about
1.3
coming
up.
So
let's
just
talk
real
quick
about
the
patch
releases
that
came
out.
I
think
that
was
just
yesterday.
A
Dan
did
you
did
you
ran
these
releases?
Do
you
want
to
talk
about
the
the
impact
or
change
in
these
patches.
B
Yeah
for
sure
this,
this
isn't
affecting
too
many
folks
right
now,
but
there
was
a
a
bug
in
the
rbac
manager
which
I
always
am
hesitant
to
say,
there's
a
bug
in
the
arbeit
manager,
because
I
feel
like
that.
Just
inherently
sounds
severe,
but
it
really
wasn't
too
big
of
a
deal.
B
In
fact,
it
was
giving
less
permission
than
we
want,
and
so
what
was
happening
was
when
providers
are
installed
before
their
controllers
are
started
in
a
deployment,
a
service
account
is
created
and
a
a
role
is
bound
to
that
service.
A
cluster
role-
and
you
know
when
a
provider
is
installed,
it
brings
along
a
number
of
crds
with
them.
B
The
our
bank
manager
is
responsible
for
creating
the
cluster
role
that
has
permissions
on
all
of
those
types
that
are
introduced
by
the
crds,
and
then
it
also
gives
some
access
to
some
common
data
types,
namely
secrets,
config
maps
leases
and
I'm
missing
one
there.
I
believe
there's
four
of
them,
but
basically
common
common
data
sources
or
common
objects
that
a
provider
would
need
to
interact
with,
and
the
reasoning
for
the
config
map
and
the
leases
or
the
lease
object
is
for
leader
election
right.
B
So,
if
you're
running
multiple
replicas,
which
you
can
enable
by
when
you
install
provider,
you
reference
a
controller,
config
object
that
says
you
know
replicas
three
or
sets
the
environment
variable
which
all
cross
plane
main
crosslink
community
maintain
provider,
support
of
leader
election.
True,
it
starts
three
replicas
and
it
would
put
into
leader
election.
Basically,
one
of
them
is
running
and
reconciling
the
resources,
but
if
it
goes
down,
another
can
take
over
in
controller
runtime.
B
You
can
elect
to
choose
between
using
config
maps
for
leader
election.
You
can
kind
of
think
about
this
as
as
a
lock
right,
you
take
control
of
a
resource
and
that
signals
that
you're,
the
leader
or
you
can
move
to
the
newer
leader
election
api
or
the
coordination
api,
which
offers
a
lease
type.
So
essentially,
the
the
issue
here
is
that
the
rbac
manager
used
the
wrong
group
on
the
cluster
role
for
the
lease
object.
B
So
if
a
provider
was
running
was
running
with
multiple
replicas
with
leader
election
enabled
and
had
opted
into
or
was
using
a
modern
version
of
controller
runtime
that
used
the
lease
api
by
default,
it
would
fail
to
start
because
it
would
say
I'm
I'm
unable
to
determine
if
I
even
can
become
the
leader,
because
I
don't
have
access
to
leases
so
essentially
that
just
this
just
corrected
that
pretty
small
bug.
That
was
impacting
a
few
folks
and
we
wanted
to
get
some
patch
choices
out
there.
B
I
know
you'll
notice
that
1.0
is
still
an
active
branch
until
1.3
which
we'll
talk
about
today.
We
did
not
make
a
patch
release
there,
because
1.0
does
not
currently
give
access
to
leases
at
all
when
it
was
introduced.
Control
runtime
did
not
support
leases
and
we
haven't.
You
know
added
that
because
that's
seen
as
a
feature,
rather
than
a
bug
fix
so
anyway,
1.0
will
see
end
of
life
here
in
about
a
week
and
a
half,
and
so
we
elected
not
to
do
a
patch
there.
A
Cool
dan
thanks
for
getting
us
updated
on
those
patch
releases
that
went
out
just
yesterday
and
what
the
cause
for
the
fix
was
there.
Other
news
for
releasing
yesterday
was
for
provider
aws.
A
We
did
a
0.19
release
for
the
aws
provider,
with
a
lot
of
new
support
for
new
for
services
within
aws,
most
notably
like
lambda
and
cloudfront
are
some
of
the
services
that
are
in
there.
I
think
they're
they're,
all
listed
in
or
most
of
them
are
listed
in
this
release-
notes
right
here,
but
so
that's
available
now
and
you
can
start
taking
a
look
at
you
know
using
crossplay
and
supervision
to
manage
some
of
these
additional
services.
Now
as
well
too.
A
I
believe
with
this.
I
guess
that's
right
here
in
the
release
notes
with
this.
This
makes
aws
a
performance,
cross-branding
provider
as
well
too,
which
we've
been
talking
about
in
some
of
the
previous
meetings,
but
we'll
go
into
an
agenda
item
further
down
as
well
too
so
a
few
releases
going
on
in
the
past
couple
days
and
then
we
are
working
towards,
as
we
said,
the
1.3
released
it
is
coming
up
in
just
over
a
week.
A
I
guess
no
sorry
a
week
and
a
half
or
so
so
the
release
date
is
intended
to
be
june
29th.
We
are
in
a
feature
freeze
now
we're
telling
this
is
that
sort
of
monday
the
future
freeze
dan
or
is
that
already
started?
I'm
sorry.
B
We
are
currently
in
feature
freeze,
although,
as
a
note,
we
have
been
somewhat
flexible
with
feature
freeze
in
the
last
couple
of
releases
in
terms
of
we've
we've.
Let
some
things
in
that
have
been
in
progress
leading
up
to
it,
but
monday
will
be
code
freeze.
So
we
really
let
anything
after.
A
That
yep
good,
I
guess
I
got
that
right
in
the
notes
here
I
got
thrown
off
a
second
when
I
was
trying
to
do
the
math
on
today's
thursday.
The
17th
29th
is
more
than
so.
It's
like
tuesday
of
the
following
following
week,
but
yeah
so
next
week
would
be
the
posterior
code
for
this
week
and
we
are
currently
in
future
fees.
A
Yes,
so
let's
talk
about
what's
in
that,
you
know.
I
think
that
the
community
meeting
is
always
an
opportunity
to
talk
about
what
we
want
to
see
in
releases
as
we're
wrapping
up
the
current
1.3
release
and
getting
it
out
the
door
and
not
doing
any
more
features
for
it.
It
becomes
more
of
a
conversation
of
hey.
A
What's
in
1.3,
what
you
know,
what
maybe
some
edge
cases
or
bugs
or
things
that
we
want
to
continue
to
fix
in
1.3,
but
then
also
the
floor
would
always
be
open
to
what
our
bigger
features
and
things
of
interest
in
the
next
milestone
in
1.4
is
fall
2..
We
do
not
yet
have
a
1.4
board
project
planning
board
up
yet,
but
you
know
we
kind
of
keep
that
discussion
going
here
and
probably
probably
the
next
community
meeting
will
have
the
early
1.4.
A
You
know
initial
planning
and
and
kind
of
design
stuff
going
on
early
on
there.
So
let's
jump
into
the
1.3
board
is
not
able
to
make
it
today
so
I'll
go
ahead
and
speak
for
him.
Some
some
big
updates
there
there
that
there
is
so
cross
resource
references.
There
is
a
design
dock
that
is
out
and
open
from
wafik
that
he
opened
a
few
days
ago,
maybe
late
last
week
that
I'm
not
sure
but
pretty
recently.
So
I
think
this
is
pretty
interesting,
because
this
is
a
high
demand.
A
High
impact
feature
that
kind
of
updates
the
shape
of
crossman's
apis
to
be
able
to
in
a
generic
common,
consistent
way,
be
able
to
refer
from
you
know,
one
resource
be
able
to
point
at
fields
or
references
on
other
resources,
so
you
can
start
pulling
things
in.
You
know
waiting
for
fields
to
get
updated,
etc
across
multiple
resources
now,
which
is
really
nice
for
a
eventually
consistent,
actively
reconciling
type
of
control,
plane
approach,
so
I
think
the
pr
is
linked
within
this
issue
here.
A
I
don't
know
it
off
the
top
of
my
head,
but
it
is
23.85.
So
that's
a
you
know.
A
big
effort
went
into
this
to
kind
of
start,
shaping
this
api
and
get
this
design
updated,
which
actually
ends
up
fixing
multiple
issues.
So
you
know
this
the
the
feature
work
behind
this
will
not
be
in
1.3.
A
Let's
be,
let's
be
clear
about
that,
but
the
design
work
is
here
in
1.3
and
ready
for
folks
to
comment
on
and
kind
of
be
able
to
share
their
opinion
on
what
the
api
looks
like
the
ergonomics
and
usability
around
it
and
what
may
be
missing
from
it.
A
B
Sure
so
there
are
a
couple
things
and
one
of
them
I've
added
here,
but
before
I
cover
that
one,
a
fairly
large
one
that
I'm
trying
to
see
if
I
can
find
the
issue
for
it,
but
it's
basically
around
when
a
when
we
were
using
a
patch
that
was
from
one
resource
to
another
in
a
composition.
B
So
if
you
have
two
objects
in
a
composition,
you
couldn't
have
you
couldn't
patch
from
one
to
the
other,
if
you
tried
to
patch
back
to
the
composite
resource
and
then
forward,
if
you
will
to
the
other
composed
resource.
So
let
me
let
me
grab
the
issue
here,
real
quick,
because
I
think
ben
created
the
issue,
and
it
is
pretty
descriptive
one
moment
here
all
right,
yeah
required
patch
policy.
So
this
is
21.75.
B
Let
me
drop
it
in
here
and
if,
if
you
wouldn't
mind
pulling
that
up,
jared
ben
has
a
good
example
here
of
of
what
it
looks
like
when
you're
trying
to
do
something
like
create
an
s3
bucket
and
then
create
an
im
roll
based
on
that
that
references,
the
arn
of
the
s3
bucket
and
the
issue
there
is
that
we
are
all
we
were
all
or
nothing
with
composition.
B
So
what
I
mean
by
that
is,
if
you
were
unable
to
render
all
the
resources
right,
a
field
was
missing
or
patch
was
missing.
We
wouldn't
create
any
of
the
managed
resources
in
the
pr
that
fix
this,
which
is
or
change.
This,
I
think,
might
be
more
appropriate
is
2180.
B
We
instead
say
if
we
can
provision
any
of
the
resources,
we
will
provision
them,
and
so,
in
this
case
we'll
go
ahead
and
create
that
bucket.
Even
though
we
can't
create
the
iam
role,
that
is
missing
a
required
patch,
what
that
allows
you
to
do
is
have
objects
that
are
dependent
on
each
other
right.
B
So
in
ben's
case
he
had
the
bucky
getting
created
and
then
he
had
a
from
composed
or
two
composite
field
patch
that
took
a
status
field
of
the
s3
bucket,
patched
it
back
to
the
composite
and
then
a
from
composite
filled
patch
on
the
im
roll
that
took
that
field
had
been
patched
back
and
patched
it
forward
to
the
im
roll,
so
lots
of
back
and
forth
here,
but
essentially
what
this
allows
you
to
do
is
have
resources
that
are
dependent
on
each
other
and
wait
for
one
to
come
available
before
the
other
one
gets
provisioned.
B
So
that
will
be
enabled
here-
and
I
know
a
lot
of
folks
who
are
doing
things
like
setting
up
eks
clusters
with
irsa
enabled
we're
doing
something
like
ben
is
doing
here.
Creating
you
know
permissions
on
something
after
it
gets
provisioned
this
unblocks
a
lot
of
folks.
So
that's
definitely
a
big
one
that
will
be
in
1.3.
B
The
other
one
that
I
mentioned
here
is
just
looks
like
a
cross-plane
runtime
update,
but
essentially
the
the
package
parsing
has
been
adjusted
slightly
and
why
this
is
important
is
because
it
will
be
possible
with
the
1.3
cli,
to
produce
a
a
valid
package
so
produce
a
an
oci
image,
tarball
and
x
package
file.
That
is
not
valid
with
older
versions
of
crossplane.
B
If
you
use
the
same
source
that
you're
using
right
now,
that
will
not
happen,
so
it
would
have
to
be
a
net
news
source
where
you're
building
with
the
new
cli
and
installing
in
an
older
version
of
crossplan.
So
this
is
a
fairly
unlikely
scenario,
but
essentially
there
were
valid
yaml
streams
that
we
were
not
allowing,
and
so
we
adjusted
the
parsing
a
little
bit
so
that
we
use
yaml
document
terminators,
which
basically
say
this
is
the
end
of
a
document.
B
It
allows
you
to
concatenate
yaml
streams,
so
this
makes
it
possible
for
if
you've
ever
worked
with,
like
cube
builder
and
seen
that
you
know
it'll
have
a
a
return
and
then
a
document
separator
at
the
top
of
crds
generated
you'll,
see
in
our
providers.
We
strip
those
off
because
the
the
package
parser
had
issues
with
that
things
like
that
and
little
little
intricacies
of
the
animal
documents
that
were
that
would
cause
the
parser
to
fail.
Those
are
now
if
they're,
valid
yaml
streams
will
be
accepted.
B
A
Awesome
and
another
another
big
thing
to
mention
for
upcoming
1.3
is
around.
You
know
the
ability
to
patch
from
multiple
multiple
sources
as
well
too,
that
had
been
a
long-standing
pr
that
is
now
in
and
will
be
included
in
1.3
as
well
too.
I
think
it's
highly
highly
requested
feature,
so
the
you
know
being
able
to
take
in
a
single
patch
to
be
able
to
take
multiple
values
and
then
concatenate
them
or
aggregate
them
into
a
single
field
is,
is
now
totally
possible
and
there's
documentation
for
it
as
well
too.
A
That
will
be
part
of
the
1.3
release,
so
that
is
going
out
the
door
and
we'll
be
in
this
in
this
release,
and
I
think
that'll
make
a
lot
of
folks,
happy
and
hassan.
I
know
you're
on
the
call
and
you
had
written
a
composition,
that's
sort
of
using
that
functionality,
so
that
will
be
part
of
1.3.
Now
that
you
will
be
happy
to
have
that,
I
think
yeah
right.
A
B
The
the
other
one
that
unblocks
a
few
folks
is
the
change,
and
I
think
this
might
have
come
up
at
the
last
community
meeting,
but
it
is
in
the
done
column
and
it
is
old
and
active
revisions
can
create
deleted
resource
before
new
active
one.
B
This
was
blocking
some
folks
when
they
updated
a
provider
to
a
new
revision,
and
let's
say
there
was
a
crd
that
and
the
previous
one
was
v1
alpha
one,
and
then
it
drops
v1l1
support
and
introduces
v1
beta1
support,
so
basically
there's
no
translation
layer.
B
An
update
of
a
crd
like
that
does
does
not
work,
and
so
the
solution
would
be
we'll
just
go
ahead
and
delete
the
crd
and
let
the
new
revision
create
it.
However,
because
we
have
old
inactive
revisions
still
creating
their
crds,
if
they
don't
exist
and
just
adding
an
owner
reference
on
them,
rather
than
a
controller
reference,
there
could
be
a
case
where
you
delete
the
crds.
You
could
upgrade
to
the
new
revision,
but
the
older
vision
would
recreate
the
crd
with
the
old
schema
before
the
new
one
could
replace
it.
B
So
essentially,
this
change
just
says:
if
you
are
in
inactive
revision,
if
your
crds
still
exist,
you'll
put
your
owner
references
on
them
and
and
they'll
stick
around,
but
if
they
don't
exist,
you
won't
actually
try
to
recreate
them,
which
means
that
the
only
way
that
you
can
lose
a
crd
for
an
inactive
revision
would
be.
You
have
to
actually
explicitly
delete
it
and,
and
so
you're
you're
kind
of
opting
into
that,
and
you
could
always
bring
it
back
by
rolling
back
to
the
previous
revision.
B
So
that's
kind
of
a
small
change,
but
there
were
some
folks
that
had
kind
of
a
bad
time
updating
some
providers
that
dropped
alpha
support.
You'll.
Note
that
probably
in
the
next
release,
we'll
have
some
more
machinery
around
handling
alpha
apis,
potentially
even
opting
to
mandate
that
users
specify
they
want
alpha
crds
installed
because
they
can
be
dropped
without
notice
between
releases
based
on
our
versioning
scheme.
A
That
sounds
good
dan
cool,
so
I
think
you
know.
I
think
that
through
this
group
here
you
know,
if
folks
already
have
ideas
about
things
they
want
to
see
included
in
the
next
release
for
1.4-
that's
great,
we
can.
You
know
talk
about
that.
But
probably
you
know
something
to
start
thinking
about.
For
you
know
big
items
or
you
know,
items
of
value
for
the
community
high
demand
features.
You
know
we
will
have
a
full.
You
know
eight
week
cycle
for
1.4.
A
That
starts
at
the
end
of
june,
beginning
of
july
here.
So,
if
you
people
want
to
start
thinking
about
you
know
what
are
those
high
impact?
High
impact
high
demand
features
that
would
benefit
the
community
the
most
then
we
can
kind
of
take
that
into
our
next
planning
discussions
in
the
next
community
meeting
two
weeks
from
now
and
kind
of
put
a
plan
together
for
what
we
want
to
be
accomplishing.
A
Does
anybody
have
any
any
items
or
comments
that
they
want
to
add
right
now
on
milestones,
103,
104,
anything
related
to
releases
and
upcoming
stuff.
A
All
right,
okay,
okay:
if
not,
then
we
can
go
ahead
and
move
on
to
the
community
topics
section
dan.
I
did
not
get
a
chance
to
to
look
up
and
see
if
there
had
been
any
recent
live
streams,
podcasts
or
anything
like
that
recently.
Do
you
want
to
comment
on
that
real
quick?
Can
we
just
update
the
doc
here.
B
There's
none
on
my
end.
There
might
be
a
few
community
ones.
Just
folks.
I
think
I've
seen
on
twitter
that
I
could
drop
in
here.
A
Had
done
had
done
one
recently
as
well
too
yeah
like
any
of
those?
That's
a
good
reminder
too,
because
we
see
a
lot
of
those
on
twitter
come
up
and
you
can
kind
of
collect
those
and
add
them
here
into
the
community
meeting
agenda.
So
we
can,
you
know,
be
talking
and
getting
some
non-twitter
reach
feeds
related
visibility
for
them
as
well,
too
cool
yeah.
If
you
can
update
the
doctor,
we
can
do
that
async,
so
the
so
we
can
talk
to
the
cncf
incubation.
You
know
the.
A
As
of
last
time
we
had
the
last
end
user
interviews
with
the
technical
oversight
committee
scheduled
those
were
completed
and
the
technical
oversight
committee
is
should
be
discussing
now
going
to
open
the
public
comment
period
for
the
incubation
proposal.
So
all
the
links
here
are
still
here
for
the
due
diligence,
the
proposal
itself,
etc.
The
slide
deck
all
that
stuff.
A
If
anybody
wants
to
take
a
look
at
those
they're
right
there
and
then
a
request
to
the
community
is
that
when
the
public
comment
period
does
open
up,
we
will,
you
know,
put
us
put
a
message
on
slack,
we'll
put
it
on
twitter,
etc
all
those
communication
channels
to
get
folks
to
add
their
support
for
it
there.
I
think
a
lot
of
folks
have
done
that
on
the
pull
request
itself
here,
but
part
of
the
process
is,
you
know
when
you
have
a
public
comment
period.
A
Is
that
gives
another
specific
opportunity
on
the
cncf
mailing
lists
for
the
technical
oversight
committee
to
see
some
of
that
community
support
there?
So
that
will
definitely
be
something
that
comes
up
and
would
love
the
community
to
jump
in
there,
and
you
know,
add
some
plus
ones
and
some
some
you
know
some
support
for
right
there,
so
we'll
send
that
out
when
that
is
open,
I'm
hoping
for
that
pretty
much
any
day
so
be
on
the
lookout.
For
that.
A
So
conformance
in
certification,
there's
been
a
you
know,
a
lot
of
great
progress,
a
of
getting
that
program
off
the
ground
we've
talked
about
that
before,
but
now
we've
got
more
and
more
pull
requests
that
are
being
opened.
That
are
the
results
of
running
the
conformance
suite
for
various
providers.
So
we've
got,
you
know
the
the
provider.
Marcus
did
a
great
job
with
the
equinix
metal
provider.
There's
a
performance
results
for
that.
We've
got
ibm
cloud
apollo.
A
Thank
you
so
much
for
your
help
on
that
one
as
well
too,
and
driving
that
in
getting
ibm
cloud
results
for
the
being
a
certified
performance
provider
up
there.
Gcp
is
up
there
as
well,
too
provider
helm
and
more
coming
as
well
too.
There's
a
big
push
on
aws
to,
as
I
mentioned,
the
0.18
release
had
some
fixes
and
improvements
to
get
aws
to
be
a
certified
provider,
so
those
results
performance
results
should
be
landing
in
the
pr
here
on
the
cncs
conformance
repo
as
well
too.
A
So
a
lot
of
great
work
and
effort
from
all
the
providers
to
you
know,
get
their
writers
to
performance
stage
and
then
running
the
suites
and
following
up
and
getting
all
the
results
in.
So
thank
you
very
much
for
all
the
efforts
on
that
one
to
kind
of
put
together
this
performance
program
and
start
showing
some.
You
know
some
some
demand
for
it
and
some
value
in
it
and
getting
the
governing
board
of
the
cncf
to
to
vote
for
it
with
all
that
body
of
work
there
to
show.
A
The
so
lfx
mentorship,
so
that
program
has
come
to
an
end
for
the
spring
term,
for
rahul
rahul
did
successfully
graduate
the
lfx
mentorship
program.
I
made
a
lot
of
great
contributions
over
the
12
weeks
that
he
was
part
of
the
program
there
and
you
know
he
gave
did
the
final
assessment
violation.
Final
evaluation
got
all
the
pull
requests
merged
in
that
we
wanted
to
as
well
too.
So
all
the
planned
work
was
included
into
the
cosplain
repos,
the
crossband
test,
repos,
the
provider,
no
op
repos,
etc.
A
So
it
was
across
a
number
of
different
code
bases
and
it's
all
in
and
rahul
successfully
graduated.
So
I
think
romeo
you're
on
the
call-
and
I
just
wanted
to
call
out
your
your
work
and
your
efforts.
There
was
definitely
really
appreciated
and
it
was
great
to
see
you
grow
and
get
more
involved
in
the
community
throughout
the
the
spring
term,
though,
and
it
definitely
shows
the
value
of
being
able
to
connect
to
the
community,
grow
the
community
and
get
more
people
involved
in
open
source
stuff.
A
So
thank
you
very
much
for
your
efforts
on
that
reward.
It
was
great
to
have
you
as
part
of
the
program.
A
All
right
and
we
will
be
in
the
future,
doing
more
programs
like
that,
like
google,
summer
code
or
lfx
mentorship
for
other
terms
as
well
too.
We
are
not
part
of
the
summer
term
for
lfx
mentorship,
but
I
would
expect
that
we'll
get
back
on
it
for
the
the
fall
term.
Sometime,
like
the
september
time
frame
after
the
summer
is
over
here
any
other
community
related
topics
or
news
that
folks
want
to
bring
up.
A
All
right,
then,
we
can
keep
going
on
to
the
prs
section
here.
I
think
muaf
had
one
for
the
generic
resource
references
which
we
kind
of
touched
on
earlier
dan.
Is
there
more
context
on
that
that
morph
wanted
you
to
give.
B
No,
no,
I
just
added
that,
and
I
think
I
think
you
did
a
a
good
job
of
covering
at
the
beginning.
Okay,.
A
Cool,
so
the
link
is
in
the
agenda
documents
for
folks
to
go
ahead
and
weigh
in
on
how
the
api
is
looking
and
the
design
of
this
here.
I
think
it's
look.
I
read
it
through
and
it
looks
pretty
solid
to
me,
but
it
would
definitely
be
great
to
have
more
eyes
on
it
and
kind
of
see
what
people
are
thinking
about.
You
know
how
useful
it
is
and
if
it
solves
problems
for
them.
A
Okay,
so
there
wasn't
any
other
prs
or
things
that
were
written
on
the
agenda
doc
or
deeper
technical
discussions
for
this
time.
So
anybody
have
other
agenda
items
that
were
not
in
the.
A
A
Okay,
all
right,
although
there
aren't
any
other
agenda
items
that
folks
want
to
bring
up,
then
we
could
go
ahead
and
move.
You
know
go
ahead
and
adjourn
the
meeting
here
and
we'll
be
on
slack
and
and
twitter
and
all
sorts
of
other
ways
to
connect
with
us
and
then
be.
I
think
yes,
so
by
the
next
time
we
meet
the
1.3
release,
will
be
out
and
we'll
be
discussing
1.4
plans
to
what
we
want
to
build
and
what
we
want
to
focus
on
there
as
a
community.
A
So
hopefully
folks
can
think
about
that
and
come
to
the
community
meeting
in
two
weeks
from
now
to
start
thinking
about
what
we
want
to
be
accomplishing
in
the
1.4
time
frame.
So
thank
you.
Everybody
for
joining
good,
to
see
everybody
and
take
care.