►
From YouTube: Test/Release Working Group Meeting 6/25/2018
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
A
A
A
So
we
are
expecting
to
cut
a
new
release.
Candidate
have
been
tested
manually
by
the
cherubic
requesters,
and
then
we
should
be
able
to
to
finalize
the
monthly
release
either
today
or
tomorrow.
So
that
is
simple.
If
you
are
aware
of
any
release
blocking
issues,
please
let
me
know
as
soon
as
possible.
So.
B
B
B
A
C
B
A
B
A
B
A
A
A
A
Just
a
snapshot
release
for
the
Phrygian
and
which
brings
us
to
the
third
topic,
which
is
0.8
one,
so
we
plan,
so
we
found
a
bunch
of
important
fixes
that
we
wanting
we
want
to
to
fix
in
point
eight
zero
and,
as
a
result,
we
are
going
to
cut
point
eight
one.
We
have
a
tracker
issue,
as
stated
in
this
meeting.
Note
please
take
a
look.
A
We
have
around
four
or
five
different
issues
that
we
want
to
fix
and
if
there
is
anything
else
that
should
be
fixed
in
point
eight,
please
add
it
to
the
tracker.
The
plan
is
to
cut
start
working
on
this
patch
release
after
we
ship
them
out
they
release
this
week.
So
it's
probably
around
two
word
end
of
this
week
or
early
next
week
we
are
looking
to
ship
on
it.
Work.
A
A
A
So
the
advantage
of
this
is
that,
if
you
remember,
we
used
to
have
a
big
end-to-end
test,
read,
impose
omit
that
ran
for
almost
an
hour.
Now
we
have
broken
it
down
into
individual
test
cases,
and
it
will
help
debugging
as
well.
Is
that
if
you
look
at
the
test
lab,
you
will
find
only
the
information
related
to
this
particular
test
read,
and
the
second
advantage
is
that
now
all
these
tests
take
around
less
than
25
minutes
to
run
instead
of
waiting
for
an
hour
now
it
and
they
all
run
in
parallel.
So.
B
A
That's
just
a
secondary
go
as
well.
We
will
be
trying
to
match
this
test
with
the
circle
test
as
well,
so
they
are
supposed
to
run
a
lot
faster
than
before
and
fed
offence
to
you
with
the
boscoe's
optimization.
That
said,
that
I
guess
he's
going
to
talk
about
that
a
little
bit
after
this,
and
eventually
since
we
are
dropping
the
we
want
alpha
1
and
we
won
support
rate.
We
will
be
removing
all
these
unnecessary
suffix
supposed
to
mr.
Costa
meet
the
hottest.
A
A
A
C
There
was
a
lot
of
issues
in
buskers
and
most
of
them
were
related
to
world
triggering.
So
we
didn't
see
those
quite
some
for
quite
some
time
before,
like
chris
has
been
running
since
January,
and
we
didn't
see
those
and
we
start
seeing
those
when
we
were
actually
failing
to
quit
cluster.
So
there
was,
there
was
environment
issues
in
in
DCP
in
UK
and
and
probably
some
some
bad.
C
We
have
great
investor,
so
I
fixed
most
of
those.
There
was
leaked,
we're
leaking
resources
where
Mason
would
actually
fail
to
create
a
cluster
but
still
hold
to
the
resource,
and
then
we
will
build
up.
The
other
issue
is
buskers
is
basically
as
a
lock
on
the
resources,
and
so
only
one
clan
can
access
resource
at
at
once
and
we're
doing
way
too
many
updates,
so
I
kind
of
bring
the
update
down
and
ending
and
during
the
investigation,
I
actually
set
up
a
dashboard.
C
C
The
were
definitely
helpful
in
in
understand.
What's
going
on,
so
we
have
multiple
components:
one
is
actually
resetting
the
DCP
project,
one
is
training,
DCP
project
into
Crestor,
and
so
each
has
its
own
actions
and,
like
the
dashboard,
helps
to
understand,
which
part
is
that
which
component
is
actually
not
but
fast
enough.
A
So
what
this
system
does
is
to
reposition
the
clusters
so
that
when
the
test
start,
it
doesn't
have
to
start
up
other
clusters
and
which
can
be
time-consuming
and
a
little
bit
unreliable
at
the
same
time
after
the
test
is
done,
this
system
will
just
return
the
cluster
back
to
the
pool
clean
up
and
recycle
the
project.
Next
time
we're
in
the
wind
and
a
new
test
pass
for
it.