►
From YouTube: Geo Scheduling Call 2020-07-07
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
C
D
So
this
one
was
just
a
small
little
bug
that
we
missed
that
there's
a
button
for
new
nodes
and
that
was
kind
of
dictating
the
spacing
on
the
top
right.
There
were
those
geo
nodes
and
something
I've
noticed
that
when
the
button
is
not
there
and
there's
no
spacing
so,
we
move
this
patient
to
be
on
the
element.
That
is
always
there,
which
is
a
title.
Pretty
easy
change.
Nice.
B
E
A
Nope
but
yeah
thanks
for
getting
this
in
I,
think
it's
yeah
I
think
it
was
unfortunate,
of
course,
to
for
package
files
that
barely
missed
last
milestone,
but
it'll,
be
it
feels
good
to
to
be
I
guess
releasing
it
to
this
milestone
with,
with
the
delete
event
replicated
so
yeah
very
exciting.
E
C
E
F
I
could
add
a
little
bit
to
that
if
you
look
at
the
status
on
staging
right
now,
the
package
files
progress
looks
crazy
and
that's
because
no
registry
records
are
getting
deleted
yet
because
this
is
not
yet
deployed,
but
actually
sounds
like
Douglass
just
fixed
what
was
going
on
in
staging.
So
what
I
hope
to
see
is
very
shortly
the
total
number
of
package
trials
the
secondary
go
to
go
way
down
to
the
memory
yeah,
oh,
so
this
this
was
like
yeah.
This
was
really
necessary.
F
A
I
just
want
to
say
thanks
for
I,
think
Fabia
has
comment
down
this
before,
and
all
the
iterated
I
think
it's
great
to
just
follow
up
quickly
with
these
on
these
sorts
of
things
with
with
small
em
ours
versus
maybe
like
opening
issues
for
them
and
kind
of
pushing
them
back
further.
So
thanks
for
following
up
on
those
right
away,.
E
G
B
A
B
C
C
B
Thanks
good
job
yeah.
A
Thank
you
so
much
for
yeah.
That
was
an
awesome
collaboration.
Thank
you
for
fixing
that
quickly,
I
think
it
it's
one
of
those
things
where
I'm
glad
there
it
would
look
like
it
was
only
going
to
be
back
ported
into
thirteen
one
and
I
think
luckily
it'll
also
get
in
thirty.
No,
since
we
have
some
customers
that
might
be
slow
to
upgrade
and
might
experience
this
down
the
line
and
and
maybe
not
be
able
to
get
to
13
one
right
away
with
their
upgrade
process,
so
yeah
Thank,
You
Douglas,
just.
C
Tried
something
more
yeah,
and
this
happened
basically
because
we
use
the
l.f.t.s
objects
project
table
as
a
single
source
of
truth,
when
we
enabled
selective
seek
my
projects
or
charts.
So
we
in
the
stable,
we
reuse,
the
same
l.f.t.s
objects
for
multiple
projects,
so
we
were
trying
to
sing
the
same
projects
over
and
over
again.
H
A
Yeah
looks
like
Gabriel
was
I,
think
that's
pretty
close
to
to
merging
I,
think
it
just
went
through
database
review
and
and
it's
back
to
Gabriel
now
and
yeah.
We
had
talked
last
week
about
I
think
we
had
assigned
it
to
you
Mike,
but
and
then
you
had
moved
it
forward
and
yeah,
so
it
seems
close
I
think
it's.
It's
still
good
to
get
this
done.
It's
the
whole
maintenance
mode.
A
G
B
A
A
A
I
B
F
A
I
wonder
if,
because
I
think
I
don't
know
if
there
were
any
action
items
from
your
review,
Alex
but
I
wonder
if
it
is
I
like
like.
Would
it
make
sense
to
try
to
assign
it
to
a
distribution,
reviewer
maintainer
right
to
look
at
well
while
equity
is,
is
out
or
do?
Is
it
better
just
to
wait
till
she
gets
back
in
case
there's
anything
left
on
it.
A
A
B
I'll
go
into
their
Channel
and
see
if
I
can
dig
someone
out,
Thanks
all
right
geo
settings
form
Zack.
D
Yep,
the
last
of
the
actual
feature
stuff
got
put
into
my
Tanner
review
and
the
maintainer
just
said
that
he'll
get
to
it
tomorrow
morning,
so
this
will
sit
for
a
minute
and
then,
after
that,
the
final,
mr,
is
open
to
just
remove
the
feature
flag
and
delete
a
legacy
code.
This
should
might
say
this
going
probably
into
the
week.
B
B
It
looks
like
this
is
just
waiting
on
the
preflight
checks
to
finish,
and
then
it
should
be
it's
a
top
of
that.
So
my
guess
is
once
the
pre-flight
checks
or
the
other
preflight
checks
tree
is
working
on
our
done.
She'll
probably
have
this.
It
looks
like
there's
already
a
Whitmer
drew
quest
too.
So
that's
cool
Jenny,
oh.
G
G
A
Yeah
I'll
speak
to
this
one
since
Gabriel
isn't
here
yeah.
This
is
just
a
bug
that
think
he
was
going
to
investigate
it's
you.
He
was
out
last
week,
so
so
I
think
there
and
there
there
wasn't
any
activity
before
that.
We
probably
want
to
just
comment
in
there
and
ask
him
for
an
update
if
you
wanna
yeah
just
mentioned
that
it's
coming
yeah
we're
discussing
it
during
the
call.
B
B
Oh
I
think
the
last
bit
we
were
working
on
is
adding
the
verification,
tables
and
figuring
out
how
we
could
add
the
verification
tables,
because
external,
mr,
the
the
mr
diff
table,
is
big
and
so
we're
trying
to
make
sure
that
we
can
trying
to
figure
out
a
way
to
add
the
verification
tables
without
adding
them
to
that
table
directly
or
the
verification
columns
without
adding
for
that
table,
which
I
think
we
managed
to
do
so.
This
should
be.
This
should
be
pretty
close.
A
Yeah,
no
thanks
for
the
update.
Yes,
it's
awesome
to
see
some
some
smaller,
mr
s,
broken
out
of
the
pot
on
this
yeah
I.
Think
just
the
main
concern
here
is
just
make.
We
have
I
think
the
17th
is
next
Friday,
so
that
feels
like
a
good
amount
of
time,
but
also
I.
Think
we
want
to
try
to
give
ourselves
a
comfortable
window
in
which
to
to
get
these
items
reviewed
and
merged
in.
A
Do
you
think
that
were
on
track?
I
was
thinking
that,
if,
if
we
could
have
these
additional
data
types
in
review
by
say
like
this
Friday
that
that
would
feel
like
giving
us
a
comfortable
window
to
to
get
the
to
get
it
into
the
released
youth.
Think
that
we're
on
track
for
that
or
or
do
you
think
that
might
be
a
little
a
little
too
soon.
You.
B
B
B
A
A
We
can
talk
about
all
of
these
at
the
end
and
and
maybe
just
have
a
check
in
on
it
later
on
in
the
week
yeah,
okay,
I
think
we
want
to
start
thinking
about
to
the
release,
but
but
we
don't
yeah
but
I
think
we
can
also
check
in
on
all
three
of
these
in
the
next
couple
of
days
as
well
so
yeah,
let's,
let's
move
on
to
to
the
next
one
thanks
Alex
sure
thing:
Mike.
D
So
Mike
and
I
are
kind
of
spearheading
a
new
strategy
as
far
as
how
the
front
end
can
consume
graphic,
UL,
and
so
we've
had
to
kind
of
loop
in
a
couple
subject
matter:
experts
of
grep,
2l
and
kind
of
get
them
on
board,
which
I
feel
like
we.
We
have
them
and
they're
they're
pretty
excited
for
it.
So
once
this
gets
kind
of
approved
by
them,
then
I'll
start
writing
the
tests
and
then
I'll
actually
see
this
down
the
review
path
and
there's
actually
not
that
much
changing.
B
B
C
B
A
C
E
A
Yeah,
thanks
for
sharing
that
looks
me
sure
my
screen,
alright,
so
yeah
ready
for
development
column
haven't
hasn't
changed
too
much
since
I
think
this
is
Fabien
kind
of
organized
it
a
little
bit
last
week
and
haven't
changed
it
too
much.
We
have
eight
items
and
I
think
that's
that's
still
a
pretty
solid
amount,
so
there
yeah
at
the
top.
There
is
the
adding
external
mr
disks
at
graph,
QL
API,
there's
getting
started
on
the
other
data
type,
vulnerability,
export,
replication,
I
yeah.
A
My
hope
is
that,
because
of
because
this,
this
is
kind
of
meant
to
show
how
quickly
we
can
move
with
the
self-service
framework
and
kind
of
with
with
the
findings
that
and
improvements.
That
tone
has
made
out
of
looking
into
external
mrduss
that
these
will
these
other
two
data
types
will
move
along
fairly
quickly,
but
yeah.
Definitely
what
let
me
know
if
those
are
if
there
are
any
more
roadblocks
that
we
run
into
there
and
I
think
that
that
will
be
something.
A
F
A
Cool
thanks
yeah,
and
then
we
have
a
couple
of
small
bugs
that
I
think
we
we
still
had
here
last
week,
so
so
yeah.
Those
are
also
here
to
be
picked
up.
I
think
I
think
other
than
that
going
to
start
adding
items
for
snippet
replication.
Next,
that's
kind
of
the
next
big
focus:
we've
deprioritized
package
file,
verification
and
and
some
of
the
maintenance
mode
stuff.
A
We've
also
pushed
back
the
POC
for
for
being
able
to
to
create
a
single
command
to
to
update
nodes
on
failover
and
and
we're
trying
to
put
more
of
a
focus
on
on
replicating
more
items
for
dr
viable
maturity.
So
those
will
be
some
of
the
next
items
to
to
make
it
onto
the
ready
for
development
column,
but
yeah
other
than
that
is
there
anything
else
that
we
that
I
guess
I'm
missing
there
or
that
we
should
be
bringing
into
ready
for
development.
A
Yeah
yeah
thanks
thanks
for
that
yeah
and
I'll
bring
it
into
ready
for
development
now,
I.
Think
yeah,
like
Jenny,
said.
The
main
thing
we're
looking
for
is
is
an
engineer
to
help
out
with
that
I
commented
in
the
issue
and
kind
of
ping,
the
entire
team
to
see
if
anyone
wanted
to
volunteer
I
think
in
reality
it's
gonna
have
to
be
someone
who
can
maybe
make
the
make
it
work
with
kind
of
the
timezone
difference,
but
I
I
did
want
to
open
it
up
for
for
everybody,
it
may
be
I.
A
Think
mike
has
been
helping
out
with
these
in
general,
and
so
thank
you
Mike
at
the
same
time,
I
want
to
make
sure
we
can
kind
of
like
the
staging
rotation.
You
kind
of
spread
things
out
a
bit
so
yeah,
please
everybody
take
a
look
at
that
and
see
if
see,
if
that's
something
that
you'd
be
interested
in
in
looking
at
and
I
commented
in,
there
too
I
think
would
be
good
for
it.
A
Yeah
see
and
then
yeah
just
kind
of
looking
at
the
open
column.
We
have
these
feature
flag,
removal
items,
I'm,
not
quite
sure.
What's
going
on
here,
I
think
we
had
I
think
it
had
been
in
dev
at
some
point.
I
think
I
will
move
it
move
it
to
the
bottom
of
ready
for
development.
As
a
small
bug
fix
that
someone
can
take
on
and
then
yeah
we
have.
A
We
have
a
couple
more
upgrade
demos,
but
we
are
yeah
going
to
try
to
figure
out
the
zero
downtime
issues
before
that
and
I
think
it
might
also
make
sense
to
we
have
a
couple
of
testing
verification
issues
for
for
get
OHA
and
for
Patroni
that
that
are
pretty
high
priority
kind
of
for
a
customer
opportunity.
So
so
it
may
make
sense
for
us
to
focus
on
those
before
upgrading
before
going
back
and
continuing
with
upgrade
demos.