►
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
First
thing
to
note
is
that
my
new
microphone
has
arrived,
so
hopefully
the
crackling
that
was
on
some
of
the
recordings
will
be
gone
and
the
recordings
will
be
a
bit
clearer.
Okay.
So
it's
all
about
the
release.
Montes
1.1.
We
spent
the
last
week
continuing
to
test
we've
done
all
of
our
we've
done
pretty
much
all
of
our
tests.
At
this
stage
we've
done.
We've
walked
through
all
of
the
the
UI
use
cases
transferring
stuff
we've
installed
on
Windows
and
Mac.
A
We
did
have
an
issue
on
Windows
10,
which
was
related
not
really
to
the
core
of
the
software,
but
related
to
how
we
build
the
Installer
there's
a
problem
with
with
one
of
the
windows
J
decays
when
it
builds
a
self,
an
installer
that
includes
the
jdk
itself,
there's
a
bug
in
one
of
the
versions,
so
that
was
something
we
discovered
and
fixed
this
week.
So
we
have
release
candidate
for
the
binary
is
together
and
there's
some
ongoing
I
guess
longevity
tests,
but
it
were
pretty
much
there
at
this
stage.
B
Focused
on
testing
people's
testing,
her
synchronization
installation
setting
up
the
private
network
between
Monte's
and
other
clients
when
it's
yeah
I
think
we're
almost
there.
Also,
as
I
said,
there
is
one
of
them
going
his
investigation,
some
Claude
Margo
as
machine
and
I'm,
not
sure
what
will
be
result
of
it.
But
I
think
that
this
one
was
sending
Fink.
A
Yeah
yeah
I
think
that
kind
of
ties
into
some
of
the
experiments
that
Jeremy
was
doing
on
on
the
ec2
instances.
In
that
weave,
we
tried
to
we
cranked
up
a
compute
optimized
instance
versus
some
of
the
other
instances
that
are
available
and
really
the
amount
of
I
guess.
Network
traffic
that
we
were
able
to
handle
was
going
up
as
the
number
of
of
CP
or
the
the
processing
power
increased.
So
it's
kind
of
despite
you
know,
despite
everything,
there
is
a
lot
of
CPU
activity
going
on
in
the
node
it
needs
to
do.
A
It
needs
to
do
what
it
needs
to
do
in
terms
of
encryption
and
decrypting
and
validation,
and
so
on
so
I
suppose,
to
some
extent
there's
it's
always
going
to
be
a
little
bit
CPU
bound.
But
that
was
an
interesting
experiment.
I'll,
try
to
add
the
the
results
of
that
into
the
into
the
blog
for
for
the
release.
B
You
are
right,
the
first
thing
can
be
CPU
bound
tests.
We
are
not
reading
any
things.
We
are
only
writing
things
from
the
network,
so
yeah,
one
regu
in
regular,
think
we
are
more
I/o
banthas.
There
are
a
lot
of
reach
there
and
level.
Db
isn't
good
and
healthy
crits,
so
yeah
it's
to
two
modes
of
operation
and
each
one
has
different
bounds.
B
A
A
And
so
that's
I
mean
that's,
that's
gonna
roll
around
sometime
early
next
month.
So
obviously
we
need
to
get
our
hourly
set
before
that
and
we
will
so
there's
a
few
more
things
to
finish
up
so
it'll
probably
be
the
Monday
of
of
Monday
or
Tuesday
of
next
week.
Just
while
we
continue
a
bit
of
longevity
testing
and
make
sure
that
there's
there's
nothing
else,
gonna
go
wrong.
A
A
There
are
some
sort
of
rough
sketches
of
the
outline
of
what's
going
to
be
in
it
and
there
will
be
some
meetings
taking
place,
I
think
amongst
the
community,
starting
probably
I,
think
tomorrow,
to
figure
out
what
the
what
the
next
some
of
the
next
stages
in
evolution
of
the
VTC
are.
So
that's
gonna
be
cranking
up
starting
this
week
and
continuing
next
week
and
you
guys
Conrad,
Whiggish
and
Radek
I'm
thinking
towards
the
end
of
the
beginning
of
next
month.
That
will
become
more
relevant
to
you
so
more
on
that
as
we
get
it.