►
From YouTube: Geo Monthly Testing Update
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
I'm,
not
sure
if
the
format
is
the
right
thing,
but
I
thought
that,
let's
start
with
the
first
one
and
see
how
we
get
on
and
what
we
can
take
it
from
there
really
and
that
the
document
were
using
is
the
geo
discussions
document
that
I've
put
in
the
sec
channel
I'll.
Add
it
to
the
agenda
going
forward
so
yeah
that
sort
of
set
the
scene
to
start
with
I'm,
also
just
going
to
change
my
view
so
that
we're
recording
the
camera
view
there.
We
go
yes,
yeah
I
thought.
A
A
Well,
as
we
go
feel
free
to
add
change,
make
adjustments
like
I
said
because
it
says
the
first
one:
let's
just
see
how
we
get
on
okay,
okay,
so
the
first
one
on
the
agenda.
There
is
bug
triaging,
so
a
genuine
sent
a
message
asking
if
you
know
how
to
best
continuously,
you
notice
that
we
need
to
be
prioritizing
all
of
the
bugs.
A
We
will
just
have
to
deal
with
the
hopefully
few
that
pop
up
in
that
week,
or
hopefully,
none
that
pop
up
in
that
they're
just
taking
care
of
as
and
when,
rather
than
having
to
be
an
event
that
happens,
it
will
just
happen
on
a
weekly
basis.
So
I
wasn't
sure
if
there's
any
other
reporting
on
that
that
you
need
to
be
doing
putting
forward
today,
like
I,
don't
actually
know
what
how
quality
worked
with
us.
Oh
no.
B
The
main
ask
from
Tonya
was
just
to
make
sure
that
there
are
severity
and
priority
labels
on
all
the
books,
so
it
sounds
like
those
are
gonna,
be
getting
addressed.
Each
each
Friday
during
the
scheduling
calls.
So
that
was
basically
what
I
wanted
to
make
sure
what's
happening,
and
it
just
lines
me
I
was
just
checking
if
I
needed
to
be
sending
updates.
Oh,
it
sounds
like
this.
Isn't
the
most
efficient
way
of
doing
it?
Oh
well,.
B
A
A
B
Just
verifying
wiki
pushes
Fabian
I
had
made
a
spreadsheet
I
can
send
a
link
to
when
I
was
evaluating
coverage
and
there
were
some
other
areas
where
I
wanted
to
verify.
If
there
were
lower
level
tests.
I
just
haven't
I
haven't
gotten
to
that
point,
but
I
imagined
that
to
Rachel
that-
and
she
suggested
maybe
having
a
call
with
an
engineer-
might
be
the
most
efficient
way
of
going
over
what
already
exists
for
that
I'm.
Just
in
that
I
think.
B
Yeah
just
looking
at
it,
so
that's
what's
going
on
with
end-to-end
tests
and
then
I've
also
been
working
with
ash
on
automating
the
testing
of
the
no
downtime
upgrades
we
broke
that
down.
While
we
create
we
create
an
epidemic
and
broke
that
down
into
issues.
I've
been
working
on,
creating
a
rape
test
to
run
the
subset
of
the
smoke
tests
continuously
during
the
upgrade
process
and
I'm
gonna
I'll
be
checking
in
with
ash
on
that
I'm
a
little
bit
stuck.
But
that's
what
I've
been
working
on
right
now.
B
B
I
will
well
so
there
was
that
just
they're
reviewing
a
lower-level
test
coverage
with
an
engineer.
I
will
need
to
do
that.
It's
just
not
in
terms
of
a
priority,
it
hasn't
hasn't,
come
floated
up
to
the
top
yet,
but
is
something
that
should
cover
and
then
also
once
I
get
to
the
tests
for
like
the
antenna
tests
regarding
docker
registries,
oh
I'll
need
some
assistance
with
that.
A
B
Even
just
planning
in
general
the
best
way
they
do
be
checking
these
types
of
files
got
replicated.
I,
don't
know
if
I,
just
just
look
at
the
display
on
the
node
page
or
if
there's
enough
another
way
to
do
that.
So
in
general
it
sounds
like
yes,
I
can
have
some
time
with
an
engineer
to
go
over
those
things.
That's
gonna
be
my
next
step
for
those
tests.
Okay,.
A
B
A
Sure
a
favorite
masalas
call
he'd
have
a
thousand
questions,
but
we
are
recording
it
so
that
he
can.
He
can
watch
the
recording
later
all
so
that
everyone
can
option
recording
later.
Is
there
anything
else
from
anyone
on
the
call
that
you
want
to
ask
questions
about
to
go
over
or
any
conversations
that
we
need
to
have
since
we're
together.
B
A
A
A
That's
already
chewed
and
really
local
waiting
for
engineers
to
be
picked
up,
so
I
think
it's
still
some
time
until
Fabian
is
going
to
be
ready
to
start
like
investigating
brand
new
pieces
of
work
where
we
need
to
get
you
involved
right
from
the
beginning,
I
think
with
with
the
work
that's
coming
up
now,
we're
because
it
was
mostly
planned
by
the
time
we
arrived.
We
haven't
been
able
to.
A
You
know,
have
proper
discussions
around
how
the
testing
for
all
of
those
pieces
should
work,
but
I
think
that
the
entering
test
for
the
docker
River,
the
docker
registry
registry
replication
will
be
a
good
start
for
the
other
types
of
replication
that
we
need
to
be
adding
I
think
once
we
figure
out
how
to
perform
their
testing,
it
might
carry
through
to
the
other
types
as
well.
Yeah,
yeah,
okay,.
A
A
Okay,
well,
I,
don't
hear
many
things
so
I
think
we'll
we'll
wrap
off
the
call,
but
yeah
can
she
hear
thoughts
afterwards
them
if,
if
this
format
works,
if
we
need
to
do
this
on
a
monthly
basis,
so
if
there
should
be
rolled
actually,
we
may
as
well
talk
about
it
now.
Do
we
think
that
we
should
keep
doing
this
as
a
separate
call
on
a
monthly
basis,
or
do
you
think
this
is
something
that
we
can
roll
into?
The
g18
call
that
we
have
that's
also
on
a
monthly
basis.
B
A
Yeah
I
think
it's
also
fine
if
he,
if
you
want
to
dig
into
specific
issues
on
this
call
as
well,
I
think
this
might
be
a
way
to
jumpstart
some
of
the
conversations
that
you
need
to
have
separately.
But
it's
it's
already
time
that
people
have
set
aside
in
the
calendar
to
be
talking
about
testing
specific
things.
So
I
think
if
there
are
very
specific
questions
that
you
want
to
get
into
I
do
think
that
it
would
be
okay
to
do
that
here.