►
From YouTube: GitLab 16.3 Kickoff - Enablement:Tenant Scale
Description
16.3 milestone kickoff for the Tenant Scale group. 16.3 planning issue: https://gitlab.com/gitlab-org/tenant-scale-group/group-tasks/-/issues/86
A
A
As
part
of
that,
which
means
we
do
have
some
carryover
to
handle,
and
that
is
why
we
have
tried
to
keep
capacity
to
not
go
all
the
way
to
full
capacity.
In
this
case,
I
would
like
to
walk
you
through
the
individual
goals
for
each
of
these
targets
that
we
have
set
so
there's
a
few
issues
regarding
the
self-managed
decomposition
that
we're
currently
tackling
mostly
this
is
to
ensure
that
data
can
be
migrated
safely.
A
We've
postponed
the
work
that
I
mentioned
in
the
previous
Milestone
planning
to
deliver
a
tool
to
help
customers
to
the
upcoming
Milestone
because
of
the
PTO
that's
outstanding,
and
we
will
just
focus
on
these
few
issues
regarding
safe
migrations
and
documentation.
Mostly
to
make
some
progress
on
this
particular
Target.
A
The
next
one
is
the
organization's
MVC
and
we
are
in
the
middle
of
building
the
Prototype.
At
the
moment,
we
have
nine
issues
relating
to
the
organization
in
this
milestone.
There's
some
front-end
work
that
is
ongoing
to
build
the
group
dashboard
overview
and
the
same
for
the
projects
and
users
overview.
However,
there's
some
API
calls
that
still
need
to
be
built,
so
these
pages
won't
be
fed
with
real
data
until
we
have
gotten
to
these
issues
and
that
can
take
another
Milestone
or
two
before
we
have
tackled
all
the
API
related
issues.
A
We
did
want
to
make
a
Headway
on
the
front-end
work.
This
is
why
we
have
already
prioritized
it
relating
to
sales.
We
are
still
working
towards
the
demo.
I
have
mentioned
in
the
last
Milestone
update,
there's
a
few
issues
that
we
recently
created
regarding
cross
joints,
that
we
need
help
from
other
teams
with
those
have
been
distributed
to
the
other
teams,
and
this
will
most
likely
become
an
okr
Target.
A
We
are
not
working
on
anything
relating
to
that
specific
initiative
in
this
milestone
and
are
just
focusing
on
the
issues
that
are
necessary
to
get
us
ready
to
demo
in
16.4,
and
the
target
for
the
specific
iteration
was
that
a
user
can
create
a
group
on
the
second
cell,
while
users
are
shared
between
cells.
So
this
is
what
we're
trying
to
demo
once
we
get
to
the
end
of
the
16.4
milestone,
there's
a
few
things.
I
would
like
to
mention
on
top
of
what
I
have
just
shown,
and
that
is
relating
to
the
organization.
A
There's
a
few
design
discussions
we're
tackling
at
the
moment
and
we
are
trying
to
develop
some
guidelines
to
check
with
other
teams
how
their
features
will
be
affected
by
the
introduction
of
the
organization.
So
we
took
three
examples
that
we're
working
through
the
first
one
is
the
user
profile
which
has
already
been
completed
in
16.2
and
we're
also
looking
into
Snippets
and
the
explore
functionality
and
how
those
will
be
affected
by
the
introduction
of
the
organization.
A
So
just
a
heads
up
on
that
and
there's
other
discussions
that
might
also
be
relevant
one
relating
to
what
the
release
coordination
will
look
like
for
the
organization,
MVC
I'm,
trying
to
build
a
plan
here
and
I
welcome
feedback
to
it.
We're
trying
to
roll
out
what
the
experimental
phase
is
off
the
organization
before
the
official,
MVC
or
organization.
A
General
availability
release
will
look
like
and
there's
also
a
discussion
on
how
we
can
mitigate
the
impact
of
one
of
the
steps
that
is
planned
for
the
rollout
after
the
MVC
release,
which
is
too
bad
off
gitlab
the
company
as
a
separate
organization,
and
that
would
have
significant
impact
on
especially
decontributor
experience,
and
this
is
why
we're
starting
this
discussion
early
to
come
up
with
Solutions
there's
a
few
of
them
suggested
here
already
and
the
contributor
success
team
has
already
engaged.
A
So
if
anyone
would
like
to
provide
feedback
on
those,
these
are
the
discussions
that
are
currently
happening
relating
to
that
and
with
that
I'm.
At
the
end
of
my
summary
for
16.3,
please
let
me
know
if
you
have
any
questions
and
I
see
you
in
16.4
miles
I'm
playing.