►
From YouTube: 2022-01-05 workspace 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
B
Yeah
not
much
has
changed
since
last
time
we
talked
mainly
because
of
holidays.
I
think
I
tried
to
push
it
forward
during
the
holidays,
with
the
people
that
were
available
and
got
a
bit
of
a
pushback
on
people
not
really
wanting
to
dive
into
a
the
subject,
so
they
say:
there's
a
big
discussion
going
on
there,
so
I
was
advised
to
move
on
with
the
existing
reviewers.
B
So
yeah,
that's
what
I
basically
did.
I
sent
it
back
to
simon
on
the
database
team,
so
yeah,
I'm
not
sure
if
we
can
push
it
harder
or
any
along
those
lines,
but.
B
Currently
got
some
feedback
addressed
that
we'll
see
what
what
comes
next
and
the
other
two
migrations.
Basically,
first
one
which
is
in
review,
is
for
git
label
work,
group
backfilling
and
the
other
one
is
the
general
backfilling
for
the
entire
projects
table.
Basically,
and
my
understanding
is
that
we
can
do
it
in
a
single
migration,
because
it's
batched,
because
we
can
basically,
we
have
control
in
the
admin
area
for
their
own
premise,
for
instance,
to
pause
it
and
keep
it
running
later.
B
If
anything,
they
need
to
deposit
for
any
reason,
and
it
also
seems
that
these
batched
migrations
were
implemented
when
we
needed
to
migrate
the
integer
primary
keys
to
big
end,
and
we
migrated
quite
a
big
amount
of
data
at
that
time,
like
billions
of
yeah
billions
of
records
or
something
along
those
lines.
So
I
think
we
are
checking
like.
B
If
we
release
this
migration
say
in
147,
then
they
will
not
be
able
to
go
to
14
8
unless
the
migration
has
run
and
completed,
which
is
kind
of
a
great
thing
for
us
to
know
that
on
premise,
we'll
have
this
backfield
project
namespaces.
So
we
can.
We
can
have
the
phase
two
code
merged
basically
after
we
release
this
this
migration,
but
in
terms
of
the
progress
yeah,
that's
where
we
are
at
right
now
and
that
ties
into
your
next
question
about
the
not
blocking
phase.
B
Two
and
my
understanding
is
that,
like
the
bulk
of
the
phase,
two
is
actually
blocked
by
having
the
backlink
migration.
There
are
bits
and
pieces
that
we
can
pull
and
work
on
in
the
meantime
before
the
backfilling
actually
happens,
but
the
the
the
bulk
of
it
is
dependent
on
having
the
project
namespace
records
in
the
database.
B
Yeah-
and
there
are
still
some
mmrs
that
can
be
managed
like
like
we
need
to
backfill
this
project,
namespaces
data
for
the
for
other
tables
as
well
like
members
and
routes,
and
probably
some
other
one.
I
cannot
think
of
off
top
of
my
head,
but
we
can
add.
Like
those
migrations,
we
can
probably
partly
backfill
some
of
the
data
that
is
related
specifically
to
the
namespaces
themselves,
but
not
to
the
project.
Namespaces.
B
There
was
some
some
discussion
going
on
about
refactoring
the
code
around
memberships
and
members
and
an
owner
for
the
project
and
namespaces
that
again,
that
can
be
worked
in
the
meantime,
but,
like
I
said,
like
the
bulk
of
the
of
the
changes,
the
core
of
the
changes
will
need
to
happen
once
we
have.
The
records
migrated
basically
I've.
I
know
that
jan
has
been
working
on
some
stuff
he's
not
on
the
call
and
I've
got
penguin
and
review
regarding
adding
this
namespace
id
column
to
the
routes
table.
B
So
there
is
some
work
going
on.
That
also
can
be
managed
yeah.
I
don't
know
like
if
we
have
enough
work
for
say
to
release
it
like
it's
yeah.
It
very
much
depends.
If
we
can
get
this
migrations
merged
in
14
7,
then
then
we
can
start
merging
the
phase
two
code
in
in
14
8
or
I'm
not
sure
which
milestone
is
coming
after
14
7.
B
I
think
my
understanding
is
that
we
need
to
delay
the
core
of
the
phase
two
code
to
next
release
after
the
the
migration
basically
is
being
released,
because
there
is
no
other
mechanism
because,
like
the
the
the
backfield
migration
is
a
post
migration,
so
it
runs
after
the
code
is
being
merged,
which
means
we
need
to
first
run
the
migration
in
one
release
and
then
have
the
code
be
in
a
different
release.
A
B
A
B
Yeah,
by
the
way,
the
featured
flag
is
set
to
true
for
the
project,
namespace
creation,
when
the
project
is
created,
so
that's
kind
of
out
of
the
way,
I
think-
and
that's
for
us
to
describe
it.
I
think
we'd
want
to
leave
it.
We
would
not
want
to
clean
it
up
just
yet,
we'll
probably
do
the
cleanup
in
next
release,
just
in
case
right,
but
it's
been
enabled.
So
we
kind
of
don't
have
the
blocker
on
merging
the
image.
The
back
fill
migration
itself,
which
is
the
good
part
in
all
this
story.
B
B
A
Okay,
so
thanks
so
much
alexandra
for
the
update
on
background
migrations,
I
believe
that
I
maybe
after
five
days
we
can
first
push
this
work
forward
with
everyone
coming
back
from
you.