►
From YouTube: Geo Scheduling Call 2020-08-04
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
No
problem:
okay,
so
billboard
closed
whoa,
okay,
there's
a
lot!
That's
good
and
wow.
A
Yeah
this
was
related
to
the
other
issue
that
we
had
closed
out
with
testing
moving
from
rep
manager
to
petroniana
geoprimary.
So
we
so,
I
wouldn't
say
it's
verified,
but
we've
we've
run
into
some
issues
and
have
created
the
follow-up
issues
necessary.
So
this
was
just
closing
closing
out
this
issue
as
well:
cool.
B
D
Yeah
well,
this
is
like
I
fixed
this
a
year
ago,
but
I
completely
forgot
about
relative
urls
so
for
for
one
year
it
was
a
bug
and
I
finally
fixed
it.
So
it
was
easy,
but
yeah.
B
Yeah
well,
thank
you
for
catching
it
and
fixing
it.
B
Oh
yep,
this
was
this
was
closed
by.
B
Value,
okay,
so
he
just
merged
pat's,
merge,
request.
E
I
just
I
yep
it
just
needed
the
select
in
there.
I
don't
know,
I
don't
know
how
that
happened,
how
that
got
lost.
A
Yeah
and
I
I
don't
think
we
normally
put
the
support
items
on
the
board,
but
this
one
felt
like
a
good
one
just
to
track
and
and
make
sure
that
it
got
a
little
attention
during
the
scheduling
call.
So
I
don't
know
if
it's
like
a
normal
habit
we'll
get
into,
but
I
think
for
anything
like
for
some
reason.
This
one
seemed
appropriate
since
it
was
a
follow-up
to
some
stuff
that
we
had
worked
on
before.
B
Yeah
that
makes
sense,
and
thank
you
to
kat
if
you
ever
watch
this.
This
is
a
another
I
mean
douglas.
You
can
talk
about
this
if
you
want
to
oh
he's,
not
there,
but
this
is
another
continuation
of
removing
feature
flags
making
registry
tables
the
single
source
of
truth
for
the
geo,
like
sync
state.
B
This
one
oh
yeah,
this
was
just
kind
of
like
there
was
a
warning
that
was
showing
up
for
everybody
in
gdk
and
in
the
end
we
decided
that
it
should
just
not
be
a
warning
should
be
silenced.
So
that's
how
we
resolved
that
one.
Thank
you
to
a
great
d.
A
Yeah
thanks
for
doing
that-
and
this
seems
like
one
of
those
stuff
that
should
just
work
types
of
label
issues
right.
I
don't
know
if
we're
still
using
that
yeah
but
yeah.
B
B
B
F
B
B
No
sorry,
I
can
only
see
six
people
and
I
didn't
know
you
were
here
or
not
sorry
about
that.
Go
ahead.
F
So
yeah,
so
after
one
vulnerability,
export
application
work
was
merged.
We
realized
that
actually,
these
exports
are
never
really
stored,
they're
only
around
for
an
hour
after
a
person
asks
for
it
and
since
they
are
updated
every
time
you
might
download
them,
it
doesn't
make
sense
to
store
them
at
all.
F
So
this
means
we
don't
need
to
replicate
it,
and
the
only
thing
replicated
in
in
this
feature
is
the
database
table
which
already
happens
with
postgas
replication.
Hence
so
many
closing
of
issues
and
I'm
currently
rewarding
the
work
there.
E
F
Had
talked
yeah,
I
think
we
had
discussed
this,
and
the
idea
was
that
anytime,
you
want
to
export
this.
There
would
be
a
record
created
in
the
vulnerability
export
table
which
you
cannot
do
on
secondary.
So
basically
you
cannot
export
these
on
secondary.
B
B
I
think
I'm
at
least
that
at
least
we
didn't
do
all
of
these
things
before
we
just
ended
up.
F
A
Definitely
a
very
legitimate
way
to
close
out
a
bunch
of
issues
is
just
determining
that
they
don't
need
to
be
done
so
yeah.
Thank
you
for
for
raising
for
yeah,
really
investigating
and
raising
those
questions,
and
then
also
just
quickly
adjusting
course
and
and
working
on
the
rollback.
Yeah
really
appreciate
that.
B
Oh,
I
thought
okay
yeah
yeah,
I
was
just
thinking
I
we
did
merge
removing
the
replication
code.
So
I
guess
that's
this
one
over
here,
but
there
are
other
pieces
to
yeah
to
do.
F
B
B
I
just
discovered
I
I'm
just
opening
some
issues
now
for
like
project
repo
design,
repo
and
stuff,
like
that.
Those
events
don't
skip
things
that
are
selective,
syncs
or
outside
of
selective
sync.
B
So
that's
that
was
causing
with
that
bug
on
staging
where
design
repositories
have
more
than
they're
supposed
to,
and
some
of
them
are
failed,
I'm
not
really
sure
either
how
we
didn't
catch
it
before,
or
maybe
it's
a
side
effect
of
switching
to
the
registries
as
single
source
of
truth
but
anyways.
B
B
Nothing
in
verification
things
in
review
accrety,
I
think
you're
working
on
this
one
now
alex
is
watching
this
all
right.
F
E
Yeah
this
is,
I
I
have
to
revisit
it
still.
I
I've
been
kind
of
focused
on
the
other
thing,
but
this
is
pretty
close.
Makriti
answered
some
questions
on
the
merge
request
for
me.
Thank
you
so
much
for
doing
that
yesterday.
That
was,
I
really
appreciated
that
and
otherwise
I
think
it's
just
got
some
failing
tests
and
hopefully
it
should
be
pretty
close,
then
actually.
B
E
Hard
for
me
to
tell
because
I've
had
lots
of
gdk
issues
since
joining
the
geo
team,
which
I've
only
been
on
for
like
three
four
months
now.
So.
A
I
don't
think
so.
She
said
that
she
has
a
conflict
yeah.
It
looks
like
there's
yeah,
there's
an
mr
out,
but
still
I'm
still
open
for
this
one.
B
C
D
Yeah,
it's
fix
it,
and
so
this
bug
existed
like
for
two
years
and
it's
yeah
it's
hard
to
test,
and
this
is
why
we
don't
have
good
test
coverage
for
this
feature,
and
so
it
allowed
it
to
be
broken
for
two
years
and
yeah.
I
finally
fixed
it.
D
I
didn't
improved
test
tests
because
well,
like
I
said
it's
hard
to
test
but
yeah,
but
I
added
one
test
to
do
not
forget
to
call
method
to
move
temporary
reaper
instead
of
main
one
so
like
it's
partially
like
improve
some
tests
test
coverage,
but
don't
fix
it
fully.
D
B
Yeah,
well,
that's
I
think
that
makes
sense.
I
was
kind
of
following
what
you're
saying
in
in
the
issue,
so
you
know
if
it's
fixed
and
test
conversion
is
improved
and
I
think
that's
a
good
thing.
E
Yeah,
this
is
pretty
close.
I'm
just
rerunning
some
tests
that
I
ran
before
making
sure
everything
still
works,
yep,
that's
it
and
then
I
think
otherwise.
B
Yeah
no,
I
was,
I
was
just
just
waiting
for
the
results
on
those
tests.
So,
and
I
know
you
said
that
gdk
was
giving
you
issues
so
after
that's
done,
then
I'm
ready
to
merge.
C
A
Yeah
jenny
provided
a
quick
update
in
geo
lounge
that
she's
planning
to
yeah
close
these
quad
planning
ones
out
this
week
and
get
started
on
the
getaway
cluster
testing
cool.
B
B
Oh
valerie,
this
is
like
adding
I
don't.
I
don't
know
I
I
wasn't.
I
don't
know
if
you
have
a
plan
already,
but.
D
I
think
I
implemented
like
60
percent
of
this
feature
already
locally
yeah,
so
I'm
not
really
agree
with
weight
but
wait.
B
Say
we
didn't?
We
didn't
really
plan
it
out.
Very
specifically,
it
was
kind
of
some
of
the
issues
were
just
copied
from
the
initial
implementation
for
blobs.
So
please,
I
think,
feel
free
to
change
the
weight.
I
didn't
have
a
lot
of
time
to
update
all
of
those
things.
D
Yeah
also,
I
think,
the
so
the
way
we
split
all
these
features.
Sorry
issues
like
it,
it's
acceptable
for
developing
this
feature
from
scratch,
but
with
self-service
framework.
I
think
it
should
be
split
a
little
bit
differently,
because
we
have
a
documentation
where
we
have
all
steps
needed.
So
it's
like
we
need
to
to
change
it
for
snippets
yeah,
but
I
mean
so
like.
I
think
we
need
to
split
it
a
bit
differently.
I
will,
I
think
I
will
erase
this
issue
a
little
bit
later,
like
tomorrow,.
B
Yeah,
I'm
sorry
about
that.
That
was
something
that
was
on
my
to-do
list
that
kept
getting
pushed
down.
So
I
yeah.
If
you
raise
an
issue
about
it
and
kind
of
like
with
what
you
would
like
to
see,
then
I
can
go
ahead
and,
like
you
know,
do
the
busy
work
of
rearranging
things
if
you
want
to
do
that
or
feel
free
to
edit
everything
yourself
in
the
epic
yeah,
okay
yeah.
Just
let
me
know
if
you
want
me
to
do
any
of
that.
B
A
Yeah,
I
can
talk
a
little
bit
about
this
one
yeah
before
gabriel
went
on
vacation
for
the
week.
He
provided
an
update
way
at
the
bottom
there.
A
I
think
he
went
through
a
lot
of
setup
on
a
lot
of
setup
and
that
while
he
didn't
get
the
cluster
actually
set
up
on
the
secondary,
I
think
he
did
quite
a
bit
of
investigation
and
where,
where
we're
at
now
is,
I
think
there
there
is
still
work
to
be
done
to
maybe
make
the
setup
more
efficient
and
and
so
he's
proposing
to
either
deep
prioritize
the
work
to
wait
for
petroni
to
be
less
experimental
or
investigate
some.
Some
improvements
on
omnibus
and
the
overall
documentation.
A
A
So
I
think
it's
on
my
it's
a
high
priority
for
me
this
week
to
kind
of
figure
out
what
what
exactly
needs
to
happen
next,
because
I
don't
necessarily
think
just
kind
of
just
waiting
for
waiting
for
patrony
to
be
less
experimental
without
some
action
from
us
is
the
best
way
to
go.
I
think
we
need
to
keep
moving
this
forward,
even
if
we
can't
say
that
in
13-3
we
support
this.
I
think
we,
I
think
it's
there.
I
think
people
are
going
to
want
to
try
it
out.
A
I
think
we
still
need
to
work
towards
trying
to
set
this
up,
even
if
it's
not
even
if
it's
really
hard
to
set
up
and
documenting
that
and
really
drilling
down
and
clarifying
what
what
needs
to
be
improved
in
order
to
make
make
the
setup
easier.
So
so,
that's
all
to
say,
yeah.
A
I
I
think
I'm
going
to
advocate
for
the
second
part
of
this,
which
is
investigating
the
improvements
on
omnibus
and
overall
documentation
and
just
trying
to
figure
out
what
what
what
we
need
to
do
there,
but
I
don't
think
we
can
just
kind
of
sit
back
and
say
like
all
right.
A
Let's
just
wait
wait
for
this
to
be
easier.
I
think
we
need
to
have
have
some
role
in
that
yeah.
Does
anyone
have
any
thoughts
or
opinions
on
that?
I'm
because
for
me
right
now,
it's
not
exactly
clear
what
needs
to
happen,
except
that
I
think
we
just
need
to
keep
kind
of
pushing
through
some
of
these.
A
E
I
I
guess,
how
is
there
a
point
at
which
we
don't
push
through
them
anymore
and
that's,
I
feel
like
that's
the
clarification
we
need
about.
This
is
like
how
how
much
work
do
we
put
into
this
before
we
say?
Oh
wow,
this
really
isn't
ready
because
it
look
based
on
what
gabriel
is
saying.
It
looks
like
he
already
wonders
if
we
need
to
wait,
and
so
I'm
not
saying
don't
push
through
that,
I'm
just
saying.
E
B
E
A
A
I
I
think
my
response
to
that
is.
Is
I'm
not
necessarily
saying
that
I
think
there
might
be
some
there's
like
different
levels
of
support
here
that
we're
talking
about
perhaps,
like,
I
think
you
know,
there's
the
ideal
that
has
lots
of
challenges
like
making
this
just
super
easy
to
set
up
and
like
failover
works,
without
a
lot
of
like
manual
intervention
and
and
that
sort
of
that
level
of
of
support,
and
I
think
there
are
potentially
levels
in
between
that
like
there's
a
lot
of
stuff
that
we
say
that
you
can
do.
A
But
we
don't
necessarily
it's
supported
in
the
sense
that
it's
really
easy
and
we
provide
lots
of
automation
around
it.
And
so
I
think
there
might
also
be
a
potentially
there
might
be
a
difference
in
understanding
of
what
we're
trying
to
achieve
here.
A
Like
you
know,
maybe
we're,
maybe
in
saying
that
we
support
this,
we're
trying
to
say
that
it's
really
easy
to
set
up
in
omnibus
and
there's
some
very
clear
steps
to
follow,
and-
and
I
think
that,
while
we
want
to
get
there,
I
think
it's
okay
to
to
be
making
more
incremental
progress.
And
maybe
say
like
hey,
we,
like,
I
think,
maybe
the
first
step
is.
We
try
to
set
this
up
at
all
costs
because
I
think
we
can
set
it
up
like
patron.
A
There
is
such
a
thing
as
a
patrony
standby
cluster
functionality
and
and
we
can
get
there,
but
and
and
but
maybe
it's
really
hard
and
we
can
say
that
yeah
this
is,
and
we
can
at
least
document
and
say
this
is
possible,
but
it's
really
hard,
and
we
can't
like
offer
official
support
for
this.
But
here
are
the
things
that
maybe
are
needed
beyond
that,
and
those
are
the
challenges
that
we
try
to
work
on.
Does
that
make
sense.
E
Yeah,
I
think
it
does
to
me.
Hopefully
it
does
to
other
people.
A
Yeah,
so
so
so
yeah,
so
maybe
we
won't
be
quite
at
the
place
where
we
can
say.
Yes,
this
totally
works,
but
I
think
a
good
place
to
be
a
good
place
to
aim
for
by
the
end
of
the
milestone
would
be.
We
have
petroni
people
are
gonna,
try
to
use
it,
here's
what
we've
found
so
far
with
geo
and
and
and
if
and
we
could
even
say
if
we
don't
totally
support.
A
If
we
we
can
even
say
we
don't
totally
recommend
this,
but
here
are
the
follow-ups
issues
that
we
have
and
and
what
we're
trying
to
work
on
next
to
to
make
to
support
it,
because
I
think
that,
like
we,
we
definitely
want.
This
is
something
that
we
definitely
want
to
support.
Even
if
there
are
challenges.
B
Yeah,
I
I
think
that
sounds
good
to
me.
You
know,
there's
always
there's
always
more
levels
of
support
than
we
realize
at
first.
I
think
yeah,
with
these
kind
of
things.
A
Yeah
yeah,
that's,
I
think.
That's
I've
covered
that
enough.
Thanks
for
letting
me
yeah
expound
on
my
my
thoughts
there.
C
Wait
is
douglas
here,
yeah
yeah-
I
am
here.
I
can
speak
about
this
one
since
last
week
we
don't
use
any
more
f.
Double
requires
choose
any
data
type.
C
B
B
Douglas
said,
that
makes
sense
seems
to
make
sense,
so
I'm
going
with
it.
I
have
an
mr
open
now
I
have
assigned
it
to
alex
for
database
review
and
I
I
split
out
even
further.
I
split
out
the
background
migration
part
I'm
going
to
do
that
in
an
another,
mr,
so
anyways.
This
work
has
begun.
E
E
Reviewed
for
you
in
like
an
hour
or
so
so
cool.
Thank
you.
It
looked
really
good.
I
just
started
it
before
the
meeting.
B
Cool
for
the
most
part,
I
was
taking
those
migrations
from
the
ones
that
we
did
for
uploads
and
stuff
like
that.
So
I
hope
you
that
that
it's
all
good
the
one.
That's
part
of
the
reason
why
I'm
splitting
out
the
background
migration
part,
because
I
don't
we
didn't
do
it
like
that.
Yet
so
that's
gonna
be
all
new.
B
I
think
we
can
reduce
the
weight.
I
don't
think
it's
10,
but
I
think
I
don't
know
do
we
need
to.
Is
it
worth
making
multiple
issues
because
I
feel
like
it
might
be
actually
easier
to
just
track
like
this?
I
don't
know
nick.
Do
you
have
any
thoughts
on
that.
A
B
B
Yeah
I
mean
I
don't.
I
still
don't
know
exactly
what
it
would
be.
But
there's
like
you
know
four
five,
mrs
here,
so
I
don't
know,
I'm
gonna
put
eight
still,
because
that
would
be
a
lot
of
issues
yeah,
okay,
so
if
that
makes
sense,
then
we're
done
with
in
depth.
A
Cool
yeah-
and
I
will
say
too
like
when
we're
talking
about
using
high
weights
and
whether
we
should
break
it
down.
I
think
it's!
It's!
Okay,
like
you
like
you're,
suggesting,
if
it's
easier
to
keep
it
all
in
an
issue,
but
as
long
as
we
if
it's
a
high
weight
as
long
as
we
know
that
we're
splitting
it
up
like
splitting
the
work
in
the
issue
up
into
multiple.
Mrs,
I
think
that's
just
fine.
G
I
think
we
sorry,
I
forgot
the
geoactive
for
some
reason
wasn't
on
the
issue
that
I'm
working
so
I
want
I
did.
B
G
So
sorry,
I
don't
know
why
that
wasn't
on
there
it's
my
favorite
yeah,
so
at
the
bottom
right
there
yeah.
So
this
one
we
recently
reintroduced
some
api
changes
that
were
originally
removed
and
deprecated,
and
so
that
took
some
time
for
me
to
get
that
figured
out
on
the
back
end
and
now
I'm
about
to
put
this
into
review.
So
hopefully
this
should
go
in
soon
and
this,
along
with
the
work
that
mike
and
I
did
on
the
details,
views
should
then
allow
like
everything
to
just
work.
G
So
hopefully
this
one
should
be
going
in
soon.
It's
a
pretty
big
change,
but
I
don't
really
see
a
way
to
like.
In
the
past,
I've
been
pretty
good
about
breaking
the
changes
down,
but
I
don't
really
see
much
more.
I
can
break
down
from
this
one,
so
it
might
take
a
couple
days
to
get
reviewed
but
yeah.
That's
it.
B
I
think
that's
okay,
if
it
if
it
makes
sense
in
one.
Mr
then
that's
fine,
so
alex's,
mr,
is
pretty
close
so
that
one's
gonna
be
in
like
very
soon.
So
we
can
test
that
cool.
G
B
G
B
Okay,
nick
I'm
gonna
stop
sharing.
A
All
right
so
yeah
ready
for
development
column,
so
I
moved
this
one
over
it's
now
available
in
it
will
be
available
with
13.3.
I
think
if
we
can
test
it
before
the
release
comes
out,
that
would
be
ideal.
I'm
I'm
not
super
familiar
with
the
process
of.
I
guess.
Testing
like
pre-release
builds
is
yeah
is,
are,
are
people
familiar
with
how
to
do
that?
Is
that
like
a
big
challenge,
or
would
it
be
better
just
to
like
wait
until
the
release.
B
A
Cool,
thank
you
yep.
So
that's
at
the
top
of
the
priority
list.
After
that,
a
lot
of
this
yeah
not
too
much
has
changed.
Runbook
style.
Documentation
is
still
a
high
priority.
I
think
akriti.
I
don't
know
if
you're
still
on
the
call
is
potentially
going
to
take
that
one
on
okay,
yeah.
B
A
So
let
me
just
assign
you
we
can
leave
it
in
ready
for
development,
but
I'll
just
assign
you
now
thank
you
for
taking
that
on
and
yeah
this
one's
still
here,
enabling
usage
ping
on
geosecondaries
to
help
us
make
some
progress
on
measuring
the
number
of
users
on
secondaries
and
then
below
that
I
can
follow
up
work
on
external,
mr
diffs,
and
I
guess
we
can
add
terraform
state
to
this,
and
I
don't
know
if
these
are
actually
the
correct
issues
to
have
here.
A
A
A
A
Yeah,
no,
no
problem,
I
think
it's
I
mean
it's
pretty
like
if
it's
pretty
straightforward
what
what
should
be
done
here
I
mean
you
know,
don't
worry
about
having
a
a
super.
Well
defined
description,
it's
if
you,
if
you
already
know
what
needs
to
be
done
and
and
you're
assigned
to
it,.
F
I
have
a
question:
what
about
external
merge
requestives?
Does
it
already
have
metrics?
I'm
not
sure
it
does
like
to
be.
Is
this
some
of
the
work
we
should
pick
up
because
tuna
is
not
here,
I
guess
alex
was
working
on
some
of
that.
E
Yeah,
mostly
I
so
tone
will
be
back
next
week.
Oh.
E
F
E
E
E
That
it's
not
already
part
of
the
the
first
step
because
he
may
have
included
metrics
in
there.
A
All
right
yeah,
thank
you
cool,
so
yeah
still
making
progress
on
that.
I
was
going
to
ask
about
snippet
replication,
but
we
addressed
that
already
valerie
and
mike
will
collaborate
on
refining
the
the
epic
there
re-examining
how
how
to
break
up
the
issue
so
yeah
once
once
both
of
you
have
worked
on
that,
I
think
yeah.
Please
add
the
next
the
next
in
line
issues
to
ready
for
development
yeah,
we
don't
yeah.
A
We
still
have
this
in
backup
investigation
issue,
and
I
did
there
was
interestingly
an
issue
in
the
distribution
team's
board.
Talking
about
handing
off
kind
of
doing
a
knowledge
hand
transfer
about
some
of
the
backup
restore
functionality.
A
We
haven't
had
to
put
a
lot
of
attention
to
this
yet,
but
we've
definitely
been
getting
pings
about
backup,
restore
bugs
here
and
there
and
generally
kept
them
off
the
board
unless
they're
really
severe.
But
I
do
think
that
that
work
will
pick
up
for
us
in
the
coming
months
and
so
distribution
has
it
scheduled
in
thirteen
five.
I
believe
to
do
some
work
around
documenting
backup,
restore
functionality
and
and
doing
more
of
a
knowledge
share
with
us.
A
So
just
a
heads
up
that
that
is
something
that
is
on
on
the
radar,
but
still
still
not
really
giving
it
too
much
attention
yet
and
then
still
have
this
follow-up
issue
to
the
to
the
promotion
script
that
can
just
be
yeah.
It's
not
super
high
priority,
but
don't
necessarily
want
to
lose
track
of
it
either
and
then
in
the
open
column.
I
guess
I'll
move
this
metrics
one
over
and,
let's
see,
follow
up
from
introducing
feature
flags
for
replicables.
A
I'm
not
super
familiar
with
what
that
is
looks
like
a
docs
update.
A
B
B
It
it
was
it's
kind
of
a
small
docs
update
you
might,
which
we
might
have
to
just
go
back
and
look
at
the
discussion
forum.
Yeah.
A
Okay,
yeah
I'll
go
ahead
and
move
this
over
into
ready
for
development.
It
would
would
be
good
to
yeah
just
to
follow
up
on
it.
Well,
while
it's
still
still
fresh
on
our
minds,
and
then
I
looked
at
this
one,
a
little
bit
is
this
something
that
we
seems
like
something
that
could
will
potentially
be
become
a
bug.
Is
this
something
that
we
also
want
to
prioritize
and
ready
for
development.
B
We
do
need
to
do
it,
I
mean
at
some
point
because
it
will
affect
every
you
know
all
of
the
blobs
and
we're
gonna
have
more
than
more
than
just
one,
but
I
have
like
I
just
opened
a
few
more
bug
issues
coming
out
of,
like
looking
at
staging
that
I
don't
know.
B
I
think
these
might
be
a
little
more
urgent.
Well
yeah.
They
are
a
little
more
urgent,
that's
the
investigation
issue,
and
then
I
opened
like
three
follow-up
bug
issues
out
of
that
which
they're
all
kind
of
very
related.
I
put
I'm
put
them
all
as
weight
one.
I
don't
think
they're
huge,
but
I
would
rather
put
those
in
cool.
B
Me
yeah,
so
I,
if
that's
okay,
I'll
adam,
is
geoactive
and
ready
for
development.
Is
that
okay.
A
Cool,
I
will
just
go
over
to
our
planning
issue
and
give
an
overview
yeah.
It
seems
like
we're
pretty
well
on
track
with
lining
up
with,
with
what
we've
planned,
I
mean:
we've
we're
still
working
on
the
blob
types,
but
still
very
much
on
track
to
to
wrap
those
up
for
the
milestone,
while
also
working
getting
started
on
snippet
replication.
A
This
is
right
at
the
top
of
ready
for
development.
We
are
making
progress
on
on
testing
petronium
italy,
so
so
that's
great
to
see
that
that's
also
in
progress.
I
think
the
upgrade
testing
was
sort
of
a
stretch
goal
for
this.
So
it's
it's
all
right
that
that's.
We
haven't
gotten
back
to
looking
at
that,
yet
documentation
improvements
for
a
planned
failover
also
soon
to
be
worked
on
and
progress
is
continuing
to
be
made
on
backfill
operations.
A
Epic
yeah
we've
closed
out
a
couple
of
these
ui
ux
administrator
improvements
as
well.
So
just
really
awesome
to
see
us
yeah
to
see
us
making
good
progress
on
what
we've
set
out
to
do
this
milestone
and
and
and
that
yeah
there's
there's
nothing
here.
That's
really
high
priority
that
hasn't
either
not
been
started
and
or
isn't
going
to
be
started
soon.
A
So
that's
that's
really
great
to
see
one
other
thing,
let
me
share
yeah
keep
sharing
my
screen
one
other
thing
I
just
wanted
to
highlight
and
I'll
stop
recording
now.