►
From YouTube: GitLab 16.4 Kickoff - Enablement:Tenant Scale
Description
16.4 milestone kickoff for the Tenant Scale group. 16.3 planning issue: https://gitlab.com/gitlab-org/tenant-scale-group/group-tasks/-/issues/107
A
We
are
currently
at
slightly
reduced
capacity
in
the
team
due
to
some
PTO
and
paternity
leave
of
one
of
our
team
members,
there's
also
a
little
bit
of
Fallout
from
previous
Milestones,
which
is
why
I
tried
to
keep
the
planned
issues
for
16.4
below
the
estimate
capacity,
and
you
can
see
here
what
the
goals
are
for
this
particular
Milestone.
They
align
with
the
okrs
we
have
set
for
the
team.
We
do
have
four
for
the
upcoming
quarter.
A
We
are
looking
into
several
issues.
First
of
all,
we're
going
to
continue
working
on
a
couple
of
front-end
issues,
one
that
we
will
start
taking
up
in
this
particular
Milestone
is
the
work
on
the
organization
front
page,
in
particular
the
header.
This
is
kind
of
what
we're
working
towards,
and
we
have
split
this
up
into
several
issues.
So
we
will
tackle
this
piece
by
piece.
A
Those
have
been
completed
already
from
the
front-end
side,
but
they're
currently
only
fed
with
mock
data,
and
we
need
these
apis
to
start
feeding
them
with
real
data,
which
is
why
we're
taking
up
this
work.
Now
from
the
design
angle,
we
are
starting
to
look
into
what
the
transition
will
look
like
in
the
admin
area
once
the
organization
is
introduced
and
how
we
will
handle
the
different
layers
of
administrative
capabilities
moving
forward,
there's
also
a
poc
in
the
making
that
is
looking
into
how
forking
is
going
to
be
handled
in
the
context
of
the
organization.
A
A
We
aim
to
conclude
the
Milestone
with
a
demo
of
this
functionality
and
we
are
focusing
on
migrating
foreign
keys
to
loose
foreign
keys,
to
unblock
this
particular
goal.
There's
a
whole
there's
a
bunch
of
issues
that
we're
working
towards
to
do
that.
They're
listed
here.
This
is
the
main
focus
around
cells
for
this
milestone.
A
We
are
also
working
with
other
teams
on
fixing
cross
joints
for
our
team.
We
will
look
into
cross
Trends
relating
to
groups,
but
there
are
many
other
stages
involved
in
this
effort.
You
can
see
this
outlined
here,
there's
also
code
review,
planning,
source
code
and
so
on.
So
we
have
reached
out
to
these
teams
to
help
us
with
these
efforts.
Most
of
them
have
scheduled
the
work
as
well
for
16.4
and
last
but
not
least,
we
also
want
to
look
into
taking
the
decomposition
work
from
experiment
to
better.
A
So
there
are
a
few
issues
we
have
listed
here.
We
are
targeting
the
16.6
release
at
the
moment
to
bring
the
self-managed
decomposition
to
better.
So
the
issues
here
are
dealing
with
tackling
some
errors
that
we
observe
frequently
ensuring
that
newly
created
table
partitions
are
locked
and
that
shared
models
can
be
migrated
safely.