►
From YouTube: 2020 02 03 Database 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
All
right,
laundry's,
you
get
the
first
topic
there.
Oh
yeah.
B
Upgrading
to
puskás
11
with
12:10,
which
is
about
to
come
in
in
April,
I,
think
and
I
was
all
just
wondering
if
there's
something
left
that
we
have
to
address
until
that
point
in
time,
particularly
for
development
I
know,
there's
a
lot
of
things
in
progress.
I
just
wanted
to
ask
and
make
it
more
visible.
A
Yeah,
not
that
I'm,
aware
of
I
still
have
a
question
out
there
and
I
should
have
linked
the
issue
here.
But
you
know
what
happened
to
fruit
in
the
last
upgrade,
because
none
of
us
were
here
for
the
last
upgrade
because
it's
been
at
least
two
years
since
they
did
the
upgrade
uncom
for
Postgres
sequel,
so
I'm
not
sure
if
there's
a
testing
or
certification
process
that
they
did.
You
know
like
Jerry
aster
in
that
meeting.
A
What's
the
certification,
we
need
to
get
the
thumbs-up
to
go
forward
with
this,
so
I
have
a
test
out
to
Tania
and
the
QA
folks
to
see.
If
maybe
there's
a
way,
they
can
start
testing
on
some
of
the
our
reference
architecture.
So
the
two
to
250k
reference
architectures
that
we
have
to
see
if
they
can
test
against
that
on
Postgres
11,
but
other
than
that
I'm
still
gathering
feedback,
I,
don't
know
what
is
required.
A
B
A
Even
getting
specific
I'm
assuming
we're
going
with
latest
on
11,
which
is
11:6
but
Postgres,
does
quarterly
releases
and
there's
one
scheduled
this
February
to
this
month.
So
are
we
going
to
take
that
minor
version,
or
are
we
gonna
stick
with
eleven
six
until
seven
has
been
out
long
enough
that
we
trust
it.
You
know:
what's
the
process
there,
so
I.
B
Think,
typically,
the
minor
versions
are
not
a
problem
with
post
goes
to
think.
Typically,
you'd
say
that
the
not
upgrading
is
more
is
riskier
than
actually
going
with
the
latest
minor
release,
because
they
have
a
lot
of
fixes
in
that
yeah
and
it's
it's
a
good,
really
good
question.
It's
also
a
question.
How
we
deal
with
this
one
good
left
would
come,
for
example,
and
also
what
we
package
in
Tony
was
I
mean
I'm,
not
even
sure,
if
we
did
any
minor
upgrades
on
come
in
the
recent
year
or
so
for
nine.
A
B
A
B
So
we
prepared
the
change
for
a
structure,
sequel,
and
this
is
mostly
done,
I
think
just
missing
one.
One
more
respect
I
would
like
to
add,
but
other
than
that
it's
only
waiting
for
an
omnibus
and
charged
issue
that
we
discovered
question
is
of
we.
We
should
put
it
push
our
ratio
to
12-mile,
because
it's
dependent
on
the
nominee
was
issue
and
it
sounded
like
they
were.
The
distribution
team
was
picking
that
up
only
in
the
next
milestone.
A
A
A
B
A
If
there's
a
budget,
if
we're
you
know
if
it's
maybe
just
like
a
hack
day
where
we
just
sit
down
and
do
things
or
in
this
case
you
sit
down
and
do
something
because
that's
not
coming,
and
since
only
half
the
memory
team
is
coming,
probably
just
combined,
so
they'll
be
like
or
five
of
us
total
we
can
move.
We
can
figure
out
something.
Well,
we
will
figure
out
something.
I
just
have
no
idea
what
it
is
at
this
point
in
time,
so
I.
B
A
Yep
it's
this
issue
here.
Yeah
I
mean
if
we
have
time
during
the
team
day
and
we
can't
fill
it
up
with
other
things.
That
might
be
a
good
candidate
yeah,
but
it's
going
to
depend
on
what
all
their
team's
are
doing
to
know
more
to
come,
and
hopefully
that
coronavirus
doesn't
outbreak
in
Europe
and
shut
all
of
this
down.
A
And
then
done
much
I
know,
Andreas
is
added
to
the
12.9
planning
issue.
I
haven't
spent
any
time
on
it.
The
memory
team
meeting
was
just
before
this.
We're
gonna
follow
up
on
this
model,
what
we
did
in
the
past.
So
we
take
the
planning
issue
and
we
identify
the
issues
that
we
are
targeting
for
the
milestone
and
then
everybody
jumps
in
reads
the
issues
talks
about
what
they
feel
the
impact
of
the
issue
is,
and
then
they
will
upload
them.
A
This
one
will
have
a
good
impact
for
customers,
or
you
know,
provide
this
level
of
value
and
then
vote
on
the
weights
as
well
and
then
from
there
we'll
prioritize
the
milestone
accordingly.
So
that's
the
path,
we're
gonna
continue
forward
with
on
memory,
team
and
I
just
want
to
see
if
that
made
sense
for
us
or
if
that's
a
little
too
heavy-handed.
Considering
only
two
of
you
right
now.
B
A
So
now
I
will
continue.
We
all.
Can
you
continue
to
add
issues
to
the
milestone
planning
issue
and
sounds
like
we'll
go
more
lightly
for
now.
Just
talk
about
what
makes
the
most
sense
to
approach.
I
think
we
have
a
pretty
good
idea
of
the
things
we
need
to
try
to
accomplish
in
the
next
couple
milestones
memory
teams
a
little
different
and
we
have
a
lot
of
competing
priorities.
So
that's
why
we
came
up
with
that
process.
A
A
Prior
to
the
next
start,
okay,
not
urgent
I,
don't
know.
Is
there
a
cut-off
that
we
want
or
again
just
continue
to
work
on
it,
and
then
we'll
figure
out
our
cadence,
because
you
know
like
scrum
and
other
processes
I've
been
in
there
fairly
prescriptive.
You
know
you
need
to
have
like
two
or
three
Sprint's
planned
out
in
advance
that
are
pretty
well
understood.
A
We
did
prioritize
and
all
those
things
and
we're
we're
not
there
I,
don't
think
we
need
to
be
there
for
a
while
I
think
we
have
a
lot
of
dependencies
that,
even
if
we
tried
to
plan
our
milestones,
even
one
ahead
would
probably
get
interrupted.
Just
like
this
omnibus
issue,
you
brought
up
right
for
dependent
on
another
team.
So
if
we
had
planned
to
complete
this
in
twelve
eight,
the
rest
of
our
planning,
if
it's
dependent
would
be
thrown
out,
so
we
can
continue
with
a
Kanban
style
approach.
A
A
A
A
A
C
C
It's
not
really
clear
what
ones
are
the
most
problematic
I'm,
just
sort
of
like
oh
they're,
failing
randomly
across
a
variety
of
places,
so
we
kind
of
wanted
to
have
a
conversation,
maybe
with
product
and
try
to
get
a
better
feel
for
what
actually
is
the
priority
here
and
you
know
making
it
more
of
a
something
that
can
be
worked
on
and
kind
of
doing
it
the
right
way,
instead
of
just
trying
to
patch
one
query
that
then
next
week,
it'll
just
be
a
different
query.
That's
broken.
B
A
B
Think
it's
really
tricky
if
you
look
at
it
on
the
on
the
code
side,
so
we
discussed
as
early
as
whether
there
are
very
flexible
finders
and
play
that
we
use,
and
it's
I
think
we
shouldn't
try
to
patch
them
for
certain
cases,
because
that
really
adds
to
the
complexity.
We're
already
doing
that
on
some
some
cases
and
it's
more
not
great,
but
if,
instead,
we
were
saying
like.
Oh
we
want
to.
This
is
Project
SEARCH
right,
you
have
we
research
with
them,
get
lab
the
project
and
we're
looking
for
a
text.