►
From YouTube: Manage::workspace project weekly 2021-10-27
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).
B
I
have
one
one
point:
it's
from
sanat
who
we
cooperate
with
to
in
terms
of
creating
the
testing
environment
for
migration
testing,
the
migration
more
real,
and
he
he
wrote
to
me
this
morning
that
they
are
like
they're
working
on
this
and
they
are
going
to
help
out,
but
they
need
to
reach
out
to
the
other
teams
too,
to
make
it
possible.
B
B
A
Yes,
that
the
the
filtering
of
project
namespaces
from
queries,
there
is
at
least
a
couple
of
things
left,
I
think,
and
that
will
bring
us
to
being
able
to
move
the
in
order
to
to
match
the
creation
of
the
project
namespace
when
the
project
is
being
created,
because
that's
going
to
go
in
first
before
the
migration
itself
and
before
the
creation.
I
think
we
have
a
feature
flight
enablement
issue
that
they
create
is
blocked
by
kind
of,
because
we
need
to
enable,
I
don't
know,
do
we
have
the
feature
flag
enabled?
Yet
I
don't.
D
D
A
D
I
mean
the
point
is
that
we
know
that
we
don't
want
to
disable
it
then
later
yeah,
but
it's
yeah.
I
agree
that
yeah.
A
C
D
That's
for
that
point
yeah,
so
the
the
problem
is
that
I
will
be.
I
will
be
away
for
the
rest
of
this
week,
so
I
can
proceed
with
feature
flag,
remove,
enablement
and
remove
next
week
soonest.
So
if
this
is
a
blocker,
then
it
might
be
better
if
someone
else
takes
the
enablement
and
removal
of
the
feature
flag.
A
B
A
Proceed
with
enabling
the
feature
flag
should
not
affect
anything
right
now,
because
we
don't
have
any
project
namespaces
yet
in
the
database,
so
enabling
the
future
flag
should
just
help
us
see.
If
there
are
any.
I
don't
know
outstanding
issues
with
the
fact
that
we
will
now
introduce
filtering
by
type
within
the
within
the
queries,
but
that
should
not
like
break
anything
basically.
B
D
B
A
Yeah
I
do
have
the
migration
in
works.
I've
tried
it
locally,
it
works.
I
think
I
think
we
can
be
like
I
don't
know.
I
don't
know
much
about
how
we
build
these
qa
environments
and
how
easy
it
is
to
pull
in
some
branches
and
and
and
run
the
codes
from
those
glaciers.
But
if
that's
something
easy
for
them
to
do,
I
think
we
can
try
and
build
one
of
those
1k
or
2k
environments
and
and
try
and
run
some
tests
get
the
feedback
from
qa.
A
A
So
we'll
we'll
save
some
time
instead
of
waiting
for
me
to
make
it
production
ready
and
run
it
through
all
the
reviews
before
we
start
qa.
If
that
makes
sense,.
B
So,
but
my
main
main
concern
right
now
is
like
we
need
to
make
sure
that
the
testing
environment
is
close
in
terms
of
namespace
table
size
to
production,
because
what
I
am
afraid
of
the
most
right
now
is
the
fact
that
even
growing
this
table
over
two
times
will
create,
will
surface
some
problems
with
queries
somewhere
in
a
place
that
we
did
not
even
touch
because
of
the
just
the
pure
size
of
the
table.
B
A
A
A
If
everything
again,
it
depends
on
how
much
work
it
is
to
to
build
up
these
environments
to
to
run
these
migrations
and
so
on.
If
that's
a
lot
of
work,
maybe
it's
worth
waiting,
but
it
is
not
a
lot
of
work.
It's
it's
worth
just
investigating
and
seeing
what
feedback
we
get,
and
it
will
be
like
relieving
for
us
to
know
that
on
this
test
build
environments,
everything
is
just
as
smooth
as
before
the
migration
and
so
on.
A
B
D
Yeah
me
too,
because
I
suspect
that
the
biggest
question
or
the
biggest
concern
is
that
problems
will
turn
out
only
with
big
dataset,
because
I
suspect
that
if
you
use
only
the
basic
1k
setup,
which
creates,
for
example,
only
thousands
of
groups,
then
the
difference
might
be
too
small.
I
mean
in
performance
measurements
because
for
thousands
of
records,
even
an
index
might
not
take
any
effect,
because
the
index
will
not
be
used
by
database
planner
in
some
cases
for
small
amount
of
records.
D
A
D
If
it
would,
if
it
wouldn't
be
possible,
we
would
still
need
to
figure
out
or
get
in
touch
with
database
to
use,
for
example,
lab
environment
or
something.
I
think
that
andreas
mentioned
something
like
that
and
we
would
have
to
test
queries
manually,
but
it
wouldn't
be
a
complete
test,
because
we
cannot
cover
everything.
Then.
B
B
A
Performance
testing,
I
think
from
qa
would
give
us
is.
They
are
poking
a
lot
of
the
end
points
on
the
web
and
on
the
api.
So
even
if
we
missed
something,
for
instance
with
the
filtering
of
the
project,
namespaces
we'll
catch
it
at
that,
like
even
on
a
thousand,
probably
instance,
will
catch
some
of
those
misses.
I
think
so.
That's
where
I'm
mostly
kind
of
interested
in
getting
that
up
running.
Everyone
will
get
this
experience
of
getting
the
reminder
and
running
the
tests
and
so
on.