►
From YouTube: 2019-12-17 Rook 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
A
We've
got
let's
see
just
on
Friday.
We
did
the
one
that
1.8
release
I,
don't
know
of
any
issues
coming
up.
Well,
there's
one
potentially
that
I
want
to
think
about
backporting
and
it's
not
in
this
board,
actually
I
think
otherwise.
1.1
is,
is
in
a
good
shape.
No
well!
No
further
release
is
planned
as
of
yet
and
these
three
issues
I'm,
not
sure
we
need
to
work
it
out
for
1.1.
A
The
high
CPU
usage
issue
and
I
think
that's
still
an
ongoing
investigation,
so
I'm
not
sure
of
an
update
on
that
one.
Yet,
and
then
this
add
support
for
suicide
driver
object
creation
that
one
I
thought
we
already
had
that
one
done.
Maybe
it
just
wasn't
back
ported
and
in
that
case
I
think
we
can
just
wait
for
1.2,
because
I
know
that
one's
already
hidden,
1.2.
A
A
A
If
it's
this
old
status
right
now
yeah,
this
is
an
issue
where
the
operator
thinks
that
it's
an
upgrade
every
time
it
restarts
and
it
will
do
the
upgrade
checks,
which
means
if
any
Mon
is
down
at
the
time.
It's
doing
those
upgrade
checks.
The
operator
will
wait
indefinitely
and
not
be
able
to
to
continue
its
reconcile
loop.
A
Okay,
let's
talk
about
1.2,
then
1.2
we
have
we'd
planned
for
today
was
the
original
goal
and
I
think
we're
in
a
really
good
shape,
but
there's
a
couple
things
to
wrap
up
and
a
blog
as
well
so
I'd
like
to
target
potentially
tomorrow
for
the
1.2
release.
So
let's
look
at
what
we've
got
left
in
the
board.
Any
thoughts?
A
A
A
A
Yeah,
let's
think
after
this
there's
one
more
I
may
just
need
to
hit,
merge
on
and
then
we'll
go
with
it
thanks
a
lot
and
then,
as
far
as
a
blog,
just
that
I'm
playing
on
working
on
that
this
afternoon
in
anticipation
of
their
release
tomorrow,
it's
not
there's
not
a
lot
in
this
release,
but
I
need
to
get
you
to
put
from
an
edge
of
fest.
Has
some
new
features
in
it
as
well?
There's
anybody
on
from
edge
of
s
on
the
call
well
I'm,
sharing
my
screen.
A
B
A
The
next
meeting
we
have
would
have
in
two
weeks
is
on
New,
Year's,
Eve,
so
I
think
it's
pretty
clear
that
we
will
cancel
that
one
people
will
be
out
myself
included
unless
anyone
really
wants
to
hold
it
any
votes
for
that
we're
good
and
then
next
time
a
note
on
the
security
audit.
So
the
security
audit
is
pretty
much
done.
We
just
have
a
final
meeting
with
trail.
That's
later
this
week
to
get
the
final
report,
they
haven't
found
any
really
blocking
issues
or
major
security
holes
that
they
reported.
A
There's
some
there's
some
cleanup
things
they
found
from
running
tools
and
some
code
analysis
that
we'll
know
if
we
want
to
follow
up
on
and
fix,
for
example,
there's
a
tool
called
ghost
sec,
which
we've
actually
had
an
issue
open
that
we
needed
to
fix
some
of
those
issues
just
hadn't.
Yet
so
that's.
A
That's
my
understanding
that
they
hadn't
done
any
real
field,
blocking
blurring
issues,
so
I
think
it's
just
part
of
that
report
is
yep
were
planning
to
fix
these
issues,
and
my
understanding
is
CN.
Cf
was
more
interested
in
the
plan
to
address
them,
not
necessarily
having
them
all
fixed
cool,
especially
since
there
weren't
any
blockers.
A
A
Right
so
I
think
what's
left
is
the
so
Jarrod
is
I,
am
gathering
testimonials
from
production,
new
users,
yeah
I
just
hold
that
and
I
think
after
the
new
year
we
were
planning
on
following
up
on
that
and
then
the
yes,
a
security
of
you
production
users,
I
think
the
only
one
in
my
mind
that
was
effective.
That
is,
to
follow
up
from
our
tubecon
discussion
on
the
steering
committee
update
after
the
governance
and
yeah
that
that's
all
I'm,
aware
of
I,
think
you
were
on
that
email
to
Chris
I.
Just
don't.