►
From YouTube: 2019 09 23 Memory Team Meeting
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
So
we'll
just
jump
in
to
the
agenda.
There's
a
lot
going
on
today.
So
there's
a
long.
The
agenda
anyway.
So
first
couple
notes
to
celebrate.
Congrats
to
Lexi
on
earning
a
discretionary
bonus
nominated
by
Camille.
I
will
read
more
about
it
in
the
company
agenda
today
feel
free
to
take
a
look
but
great
work
in
the
last
week
or
so
or.
A
A
A
Still,
it's
not
entirely
clear
to
me
when
the
cutoff
happens
for
any
kind
of
milestone,
release
I,
don't
think
there's
a
time
or
date
so
off
there's
a
date
but
I,
don't
think,
there's
a
time
of
day
setting
stone
for
the
final
cut
for
the
final
release
for
a
milestone
release
so
but
development
ends
on
the
17th.
Usually
they
cut
their
release
candidates
sometime
shortly
thereafter,
depending
on
which
day
it
lands
on.
A
Any
questions
on
that
so
well.
Andreas
joined
the
memory
team
last
week.
It
is
likely
he's
going
to
transition
to
the
newly
approved
database
team
whenever
we
can
get
the
hiring
figured
out
for
that,
so
the
database
team
was
actually
approved.
Last
week,
last
Monday
like
right
after
this
team
meeting
happened
when
we
announced
that
race
is
going
to
join
with
every
team.
A
So
regardless
we
got
andreas
over
here
working
with
us,
which
is
fantastic
and
once
we
actually
get
being
squared
away
for
the
memory
team
right
now,
we
don't
have
anything
until
q1
and
we're
trying
to
bring
a
couple
hires
forward
to
q4,
which
would
start
on
November
1st.
So
if
we
get
those,
then
Andres
will
shift
over
there
we'll
get
an
opening
on
every
team.
Again,
yeah
it
all
bounced
out
so
for
now
hundreds
they'll
continue
to
focus
on
database
work
and
but
he'll
participate
in
our
meetings.
A
Let
us
know,
what's
going
on
over
there
and
sometimes
recruit
some
help.
If
we
have
some
burning
issues
which
we
have
a
couple
right
now,
so
any
questions
on
that
all
right,
so
timeline,
12
3,
is
closed.
There's,
probably
a
couple
items
that
are
still
I
haven't
looked
at
the
mouse
down
board,
but
I'll
ping
folks
on
those
individually
make
sure
we
either
close
them
or
move
them
off
to
12,
for
if
they
are
truly
not
done
and
then
I
was
gonna
walk
through
all
the
issues
on
the
12
floor
board.
A
If
people
aren't
here
like
Jinyu
and
Camille
aren't
here,
then
those
haven't
watched
the
video
and
they
can
respond
and
update
accordingly.
So
first
issue
is
the
improve
improve
pipeline
process
service,
so
I
moved
it
to
in
dev,
because
I
know
that
Kamil
working
on
it
and
if
I
read
his
note
correctly,
I
think
once
this
once
the
em
are
related
to
this
is
close,
then
steps
one
through
three
will
be
complete
and
open.
It
up
to
everybody,
can
see
and
then
we'll
need
to
break
down.
A
A
In
dev
on
the
workload
board,
exam
I
was
asking
to
put
a
weight
on
there.
I
know
you're
kind
of
in
the
middle
of
it
now,
and
ideally,
we
put
the
weights
in
before
we
started
but
better
to
get
into
the
practice
of
it.
Then
let
it
slip.
So
if
you
could
put
away
down
there
and
just
ping
the
channel,
let
them
know
see
if
anybody
has
any
questions
about
the
work
being
done.
A
B
I
started
to
work
on
that,
but
I
was
switched
back
to
the
previous
one
because
it
was
closer
to
being
finished
and
on
this
one,
ie
I'm
current,
currently
looking
into
the
code
itself,
so
I
didn't
start
implementing
it
I
would
say,
but
the
description
is
pretty
great
I
mean
from
cameo.
So
there
is
some
plan
how
we
should
tackle
this
and
yeah
when
I
will
return
to
this
ticket
I
will
assign
weight
and
maybe
wrap
it
up.
If
I
will
have
any
additional
comments
on
that.
Okay.
A
A
A
A
The
next
one
defining
the
best
default
values
and
omnibus
for
Puma
I,
don't
have
an
owner
for
that.
But
I
think
once
we're
done
through
staging
I'm
configuring.
Some
of
the
values
in
there
and
I
know
that
Andre
house
was
working
on
some
of
the
DB
pool
values
and
staging
and
we're
ready
for
canary.
Then
we
should
work
on
updating
the
default
values
and
on
the
bus.
It
might
not
be
our
team
that
sets
those,
but
that's
down
the
road
and
we're
working
on
puma.
A
This
one:
can
you
spend
a
lot
of
time
with
the
community
contributor
on
this
and
we'll
continue
to
review
the
mrs
and
making
progress
on
it?
I,
don't
remember
who
was
on
this
one
Jen,
you
again
Jin
you
once
you
start
working
on
this
add
weight
to
it,
ping,
gentle
and
then
I
think
the
rest
of
them.
We
have
quite
a
bit
that
are
in
the
milestone
for
12:4
and
I.
Think
they're,
probably
quite
a
few,
that
we
need
to
push
over
twelve,
five
and
again
they're
in
priority
order.
A
A
C
A
C
So
I
think
they.
The
major
issue
for
12:4
is
the
first
one
to
reduce
the
lock
contention
on
one
of
those
tables,
I
added
a
bit
of
instrumentation,
so
that
goes
to
production
probably
this
week
and
there
is
a
fix
for
actually
removing
unnecessary
work
that
we're
doing
I
hope
that
sort
of
is
the
major
fix
that
we
need
to
do
and
if
there
is
more
work
that
needs
to
be
done
probably
need
some
feedback
from
from
the
CI
group,
where
maybe
we
can
actually
hand
that
over.
C
The
second
point
is
something
that
was
signal
boosted
over
the
weekend.
We
know
that
there
is
an
integer
overflow
coming
around
for
a
good
calm.
There
is
one
table
that
is
sort
of
the
major
offender
in
that
sense,
and
that's
short
from
overflowing,
so
in
the
next
few
months,
I'm
just
looking
into
how
to
fix
that.
C
A
C
The
upgrade
is
sort
of
more
involved
if
we
want
to
do
a
no
downtime
upgrade,
which
is
something
we
consider
for
a
gala
prom
that
there
is
a
lot
of
infrastructure
work
that
needs
to
be
done,
and
it's
not
necessarily
straightforward.
At
that
point
and
I'd,
we
had
that
as
an
OPR
for
infrastructure,
we
dropped
it
recently
and
I,
don't
know
what
the
way
forward
is
with
that
at
the
moment.
Okay,.