►
From YouTube: Geo Scheduling Call
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
B
A
B
The
minutes
count
today,
okay,
closed
column,
the
first
one
is
an
easy
one
determine
if
we
needed
to
include
deployment
in
canary
and
the
answer
was
no,
so
we
can
close
that
one
out
creating
a
Vincent
design
creation.
That
was
the
one
with
a
really
wonderful
proposal.
That's
also
done,
and
let
me
just
remove
the.
B
D
A
This
this
issue
was
opened
before
we
invested
a
lot
more
time
in
understanding
the
upgrade
procedure
for
zero
downtime
upgrades
and
once
we
finished
actually
revamping
that
tone
revisited
this
and
it
feels
like
it's
no
longer
worth
doing,
which
is
actually
a
big
win
if
you
think
about
it.
But
if
we
can
come
to
the
conclusion
that
you
know
we
looked
at
it
carefully
and
we
are
not
willing
to
do
it
anymore.
I
think
that's
actually
really
good.
Yeah.
D
B
B
B
B
B
B
D
I
finally
managed
to
we
could
use
it
and
the
fix
was
merged.
Eventually,
it
was
just
the
same
fix
because
it
was
a
spec
failure
on
the
secondary
worker
and
the
spec
already.
The
change
already
happened
on
the
primary
worker
spec.
So
it's
it's
weird.
We
didn't
do
that.
In
the
same
time,
it
should
be
gone
now.
Well,.
B
Thanks
for
taking
a
look
at
that,
it's
it's
been
hanging
around
for
a
while,
so
I'm
glad
that
you
were
finally
able
to
recreate
it.
B
A
B
A
B
A
I
think
the
remaining
question
here
is
if
it
can
be
back
ported
and
what
versions
I
think
at
the
moment
the
discussion
stands
at
back,
porting
it
to
12.2
m
12.3,
where
twelve
point
three
is
within
the
usual
SMA
hit.
12
point
two
is
not
but
potentially
not
twelve
point
one,
but
I
think
this
discussion
is
ongoing.
In
any
case,
we
should
like
there's
also
some
debate
on.
If
this
is
something
that
we
should
have
a
little
blog
post,
just
saying
hey,
this
is
something
that
you
know
will
will
hit
you
in
the
really.
A
B
That
some
I
do
think
that
the
scope
of
this
conversation
falls
out
of
this
meeting,
but
I
think
that
it's
worth
having
as
part
of
a
separate
call
or
something
just
how
we
handle
things
when
we
find
our
own
p
ones.
So,
let's
let
me
just
take
a
note
that
we
need
to
talk
about
this
separately
and
and
do
that.
B
C
A
So
I
think
the
last
state
and
I
am
about
to
the
last
state
here.
Is
that
I
think
the
the
merge
request
closing
this
has
no
open
issues
anymore,
no
open
discussions.
So
this
is
the
multi
node
yeah,
but
they
are
merge
conflict.
So
I
have
to
look
at
that.
The
last
thing
that
I
think
we
need
to
do
before
we
can
close
this
is
I
have
to
go
through
that.
The
last
thing
I
think
after
that
is
to
ensure
that
somebody
actually
uses
those
instructions
for
the
next.
A
great
demo
and
final.
B
A
B
A
B
B
B
E
B
There
doesn't
answer
the
question
of
where
this
work
is,
though,
so
this
is
still
open.
I
have
a
chat
with
him
later
on,
so
I'll
get
another
update
of
where
this
is
be.
Okay,
I'm
just
going
to
leave
that
rather
than
trying
to
find
out
the
estate
from
the
issue
itself,
because
I
also
want
to
find
out
about
what's
happening
with
the
follow-up
issues,
because
there
seem
to
be
a
lot
of
them
and
we're
going
to
need
to
think
about
what
to
do
with
the
ones
he
finds
but
I.
B
C
A
I
think
I
made
a
mistake
earlier,
so
there's
some
questions
yada-yada
that
we
moved
as
blocked.
This
is
actually
so
this
this
this
issue
here
is
the
one
that
actually
demands
to
create
the
documentation
for
an
aged,
a
Geo
setup,
and
that
is
that
is
that
is
blocked
on
the
upgrade
I
think
there's
some
questions.
I
think
I
have
to
actually
look
at
and
see
if
there
are
any
things
in
those
questions
that
are
yet
unanswered
and
if
that's
no
longer
the
case,
then
we
can
actually
close
it.
A
B
I
think
they're
big
they're,
both
they
were
both
stood
there
in
the
block
column.
We
need
to
have
a
look
at
so.
Okay,
the
one
in
the
block
column
that
we
didn't
deal
with
yet
was
about
the
rake
task,
which
is
the
way
to
Monash
and
Devon
ash
is
away
so
I
know
that
nothing
has
changed
okay,
so
we
can
leave
that
and
then
we
round,
the
in
dev
column,
is
only
for
past
mine,
hey,
okay,
the.
B
B
C
C
A
B
E
B
Repos
are
hurt
with
the
recent
commit.
A
flag
is
enveloped.
If
this
is
the
one
where
they
were,
if
they're
two
years
old,
then
they
weren't
invalid
not
able
to
reproduce
this
locally.
With
the
repository
provided
asking,
so
we
need
to
chase
up
this
because
there's
been
a
week
and
Kevin
hasn't
come
back.
B
B
Great
so,
interestingly,
there
seems
to
be
a
lot
of
stuff
that
was
closed
and
finished
out,
and
it
seems
that
some
people
haven't
picked
up
new
stuff.
Yet
so
there
must
be
either
this
things
in
here
that
are
in
the
wrong
state,
or
people
were
great
at
finishing
things
off
on
Friday,
so
that
they're
really
plating
on
Monday
all.
E
A
A
A
A
I
think
this
is
sort
of
the
in
in
a
way.
We
don't
have
to
wait
for
this
one
to
complete.
Before
doing
this,
we
could
just
upgrade
here
without
upgrading
the
Postgres
database,
because
we're
not
doing
this
automatically
anyways
at
the
moment,
because
we
know
there
are
issues
with
this,
so
I
think
it's
fine
to
to
do
it
now,
but
I
also
I
would
probably
argue
that
the
other
things
are
a
little
bit
more
imminent.
So
I'll
move
this
down
just
because
people
will
pick
up
other
things.
First,.
B
A
Yeah,
the
upgrade
the
object,
storage,
work,
I
think
that's
actually
I
mean
we
are
working
on
the
object,
storage
replication.
So
we
should
also
think
about
the
documentation,
pretty
small
just
so
that
we're
not
really
behind
so
I'm
happy
to
leave
it
here,
but
this
is
probably
something
that
needs
to
be
picked
up
by
Gabriel
as
well.
Yeah.
A
A
This
is
related,
so
this
belongs
to
this
sort
of
nice
package
of
of
small
bugs
to
make
the
foreign
data
record
more
robust.
So
actually,
what
I'm
going
to
do
is
I'll.
Do
this
because
CCR
relatively
small
small
tasks
that
I
think
are
good
to
do
and
I'm
happy
with
this
year.
I
want
to
check
something
quickly,
which
is
the
design
registry
work,
because
that
belongs
to
an
epoch
and
I.
C
A
A
A
Yeah,
so
here
is
the
handling
design.
Uploads
show
what
the
sync
information.
So
these
are
all
the
the
last
bits
that
are
needed
to
actually
complete
the
design
repository
work.
I
think
that's!
That's
good
document.
Every
step
needed
to
replicate
in
your
data
type
I
personally
like
having
this
after
those
two
items,
because
this
is
a
new
data
type,
all
right
that
we
are
adding,
and
these
are
the
last
two
tickets
that
actually
have
to
do
with
it.
A
B
A
And
then,
after
that,
we
have
the
verification
for
uploads,
which
is
another
thing
that
we
we
wanted
to
look
into.
So
those
are
the
first
steps
of
upload
verification.
We
wanted
to
touch
them
in
12.3,
but
didn't
get
to
them
so
I'm,
starting
to
like
put
things
in
here,
so
that
that
work
also
kicks
off
yeah.
B
A
Because
we
have
this
very
nicely
broken
down,
but
it's
a
it's
a
it's
a
long
list
of
tickets
and
I
do
I
do
think
we
should
do
this
right.
I
think
it's
like
honor
from
from
my
perspective
as
a
as
a
customer,
you
know
I
expect
that
the
data
that
is
synced
to
my
secondary
is
also
verified,
and
we
could
argue
you
know
if
uploads
is
the
the
most
urgent
of
items
that
we
need
to
do,
but
I
I
think
it
is.
A
B
The
reason
that
why
I
want
to
check,
if
it's
still
the
case
is
because,
after
the
design
repositories,
work
and
creating
a
list
that
says
this
is
how
we
would
add
a
new
data
type
if
we
just
pretended
for
a
moment
that
we
didn't
do
uploads
how?
What
would
we
need
to
do
to
be
able
to
do
uploads,
and
not
all
those
things
correctly
included
on
this
list?
Okay
and.
A
B
B
A
B
A
And
it
has
been
lying
dormant,
a
different
while
okay
and
then
there
is
the
usual
amount
of
a
long
list
of
items
that
I
haven't
sorted
properly,
because
I
think
this
is
good
enough
in
terms
of
for
for
the
next
week.
As
you
know,
like
items
and
I
do
have
another
thing.
That
I
would
like
to
quickly
discuss
that
we
may
need
to
accelerate
yeah.
D
A
C
C
B
D
C
A
Ideally
I'd
like
to
have
it
happen
here,
but
it
still
may
require
some
work
because
it's
I
mean
it
depends
on
how
we
want
to
play
it.
I
think
we've
invested
quite
a
bit
of
work
on
some
items,
breaking
them
down
that
we're
not
on
the
Billboard,
but
I
think
it
may
need
to
somebody
actually
picking
this
up
spending
some
brain
energy
and
saying
these
are
the
options
that
we
actually
have.
A
C
B
B
At
the
moment
that
the
performance
is
not
great,
but
what
happens
when
we've
got
thousands
or
tens
of
thousands
more
records
than
what
we
currently
have
or
even
I'm,
not
sure
what
I'm
not
sure
how
this
table
grows,
but
I
can
only
imagine
that
it's
going
to
get
bigger
over
time
and
we
need
to
think
about
what
happens
if
we
could
project
forward
like
six
months
from
now.
What's
gonna,
what
is
it
going
to
look
like
yeah.
D
B
A
A
A
That's
that
I've
also
fixed
fix
the
road
map,
looks
a
little
bit
better
now
and
before
I.
Think
in
terms
of
what
we
need
to
start
thinking
about
very
soon
what
we
are
going
to
do
with
promotion,
demotion
and
failover.
That's
definitely
an
area
that
I
think
we
should
plan
on
tackling
a
little
bit
more
more
actively
yeah.