►
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
Hello,
everybody
and
welcome
to
the
team
growth
and
league
weekly
status
meeting
today
is
Tuesday.
The
27th
of
March
apologies
for
a
little
bit
of
the
late
start.
We
were
in
another
meeting
and
we
got
a
little
bit
delayed.
Okay,
so
Montes
1.1
were
we're
pretty
much
nearly
there.
From
last
week
we
had
I
think
there
was
one
or
two
P
or
z',
and
those
particulars
have
been
are
about
to
be
closed.
Is
that
right,
Conrad.
A
B
Currently
told
standing
peers
are
one
about
some
improvements
in
our
discovery
and
another
one
changing
cars
in
Calgary,
in
external
libraries,
verification
yeah
in
Discovery.
We
change
it.
We
prove
it
by
this
way
that
we
don't
longer
try
to
connect
for
some
time
for
peace
which
aren't
useful
for
us,
which,
for
example,
test
run
protocol.
For
now
it
was
we
are.
We
were
still
trying
to
connect
to
them,
even
that
they
were
returning
cow
to
us
that
they
are
not
compatible.
B
It
was
depleting
our
outgoing
connections,
so
it
was
pretty
bad.
Also,
one
thing
that
was
pretty
I,
don't
know
pretty
surprising
scientists
that
too,
of
doing
classic
clients
retro
different
things
in
honk
echo,
echo
is
used
to
validate
the
pink
for
which
it
responds
and
as
it
stands
correctly,
the
parity
return
different
value
than
gas.
So,
after
introducing
this
echo
validation,
we
weren't
able
to
connect
to
I,
don't
know
half
of
the
base
of
the
clients.
It
was
partly
as
I
remember,
because
there
is,
there
is
no
consensus
which
value
should
return.
A
B
A
C
A
B
B
A
Okay,
so
I
guess
that's
that's
it
in
terms
of
1.1
function.
We've
discovered
since
last
week,
I
thought
we're
out
of
the
woods
last
week,
but
we
have
discovered
one
or
two
little
things,
so
we
still
have
those
POS
but
works
they're,
very,
very
small
viewers,
so
I'm
expecting
them
to
close
pretty
much
imminently
and
then
we'll
start
our
our
test
cycle
and
some
of
our
our
soap
testing.
A
A
Okay,
so
then,
when
we
get
I
guess
just
as
an
overview
for
people
who
are
listening,
I
mean
we're
not
going
to
the
the
changes
that
we've
made
more
or
less
all
related
to
performance.
For
this.
For
this
point,
release
there's
no
changes
made
to
the
UI.
So
one
of
the
things
I
guess
that
we
will
see
is-
is
this
delay
that
we're
gonna
have
to
live
with
at
the
end
of
the
synchronization?
A
So
when
the
when
the
blockchain
is
synchronized
will
be
it
a
lot
quicker
now,
they're
still
gonna
be
a
long
delay
where
it
sits
there
at
100%
until
we
get
some
changes
to
the
UI,
so
we're
just
gonna
have
to
advertise
that
as
as
a
known
issue.
Unfortunately,
okay
beyond
that,
then
we'll
be
looking
at
at
the
next
release.
So
that's
gonna
start
cranking
up
very
soon
and
again
it's
assuming
that
we
don't
find
anything
serious
in
our
in
our
regression
testing.