►
From YouTube: GitLab 12.5 Kickoff - Manage
Description
Jeremy Watson previews what's ahead for the Manage stage in 12.5: https://about.gitlab.com/direction/kickoff/#manage
1. Preventing accidental group deletion: https://gitlab.com/gitlab-org/gitlab/issues/33257
2. Productivity Analytics, Type of Work: https://gitlab.com/gitlab-org/gitlab/issues/13010
3. Code Hotspots MVC: https://gitlab.com/gitlab-org/gitlab/issues/33177
4. Customizable Stages for Cycle Analytics: https://gitlab.com/gitlab-org/gitlab/issues/12196
5. Policies MVC: https://gitlab.com/gitlab-org/gitlab/issues/7626
A
Hey
there,
I'm
Jeremy
Watson
of
a
product
manager
here
at
ILM,
I'm,
really
excited
to
talk
a
little
bit
about.
What's
coming
up
to
twelve
point,
five
and
I'm
gonna
specifically
cover
the
manage
stage
of
the
death
of
lifecycle.
You
notice
the
word
on
a
different
page.
We
previously
had
our
kickoff
information
on
a
Google
Doc.
We
now
pulled
that
out.
We
have
a
dedicated
page
for
it
about
get
lab
comm.
A
So
whenever
you're
curious
about,
what's
coming
up
in
a
future,
release
feel
free
to
take
a
look
at
this
page
I'm,
going
to
talk
a
little
bit
about
these
five
issues
here,
I'm,
starting
with
preventing
accidental
deletions.
So
in
12.4
we
started
off
an
effort
to
introduce
the
concept
of
soft
solution
and
get
loud.
We're
gonna
extend
that
to
include
groups
as
well.
A
The
problem
that
want
to
solve
here
is
really
preventing
data
loss,
get
live
instances
and
allowing
you
to
kind
of
like
restore
projects
and
groups
for
a
limited
period
of
time
before
they
actually
become
hard
to
lead
and
challenging
to
recover,
so
we're
gonna
send
from
them
four
projects
into
groups.
Make
sure
that
you
have
a
comprehensive
coverage
and
some
protection
against
a
loss.
There
are
three
analytics
improvements
that
I'm
really
excited
about.
A
So
we're
curious
about
exploring
that
and
helping
engineering
managers
understand
the
cadence,
their
team's
productivity,
so
here
in
12.5
we're
going
to
introduce
that
concept
between
a
refactoring
shirin
and
new
works
that
you'll
be
able
to
track
that
on
a
group
and
project
level
have
over
time.
The
other
change
I'm,
really
interested
about
to
see
in
the
product
is
really
around
code
hotspots.
So
we
started
on
the
MVC
in
this
in
previous
releases.
We're
narrowing
down
on
a
MVC.
A
Iterations
were
interested
in
like
allowing
you
to
drill
down
at
the
group
level,
and
she
liked
particular
projects
and
particular
files
for
the
first
iteration
we're
gonna
just
start
at
the
file
level
and
allowing
you
to
color
code
and
understand,
based
off
of
the
heat
of
a
particular
file
like
how
often
you're
actually
committing
to
that.
So
I
think
this
is
going
to
be
the
first
iteration
on
a
really
interesting
feature.
A
It's
gonna
really
allow
you
to
understand,
but
their
high
level
what
files
what's
changing
in
a
rapid
basis
and
then
the
first
30
days
and
their
further
improvements
that
are
that
are
claimed
for
code
hotspots,
but
for
this
MVC
we're
really
interested
in
getting
market
and
getting
your
feedbacks.
This
is
something
you're
interested
in.
We
really
love
to
hear
from
you
once
you've
got
had
a
chance
to
use
it
and
I.
Think,
though,
the
last
analytics
feature
I'm
really
excited
about
is
around
customizable
statements.
So
cycle
analytics
is
a
really
interesting
feature
in
get
loud.
A
There's
a
number
of
events
that
you
can
kind
of
see
Vout
in
this
issue
that
are
numerous
and
allow
you
to
really
customize
the
stages
kind
of
tea
or
to
your
liking,
and
this
is
good.
The
first
NDC
that
we're
shipping
in
a
category
that
we're
calling
that
it's
known
in
their
on
the
industry
is
value
stream
management.
So
we're
excited
to
get
this
out
and
integrate
a
little
further
thanks
to
your
feedback.
A
The
way
that
we're
gonna
start
on
this
is
allowing
you
to
kind
of
define
a
policy
policy
base
force
that
you
can
apply
to
a
specific
project,
because
some
projects
might
be
no
critical,
app
like
applications
that
have
like
there's,
strict,
relatively
strict
rules
and
others
might
be
resourcing.
Projects
that
are
developer
focused
and
might
not
have
lists
the
same
types
of
attention
rules.
A
So
the
way
that
we're
starting
with
this
is
being
able
to
create
a
policy
that
a
double
deny
access
to
certain
parts
of
the
project,
whether
it
be
the
repository
or
the
operations
panel
based
off
of
like
a
user's
membership
in
a
particular
group
and
the
problem
that
we
want
to
solve
with.
This
is
really
around
separation
of
duties,
where
you
have
like
an
like
a
dev
team.
That
is
not
a
member
of
a
group
that
identifies
them
as
developers,
and
you
have
members
of
an
ops
team
that
is
also
the
group.
A
You
should
be
able
to
keep
those
two
worlds
separate
and
allow
like
an
Operations
team.
The
whole
media
with
ops
and
not
be
able
to
access
receive
the
repository
I
think
that's
a
really
exciting
request
that
we're
excited
to
explore
kind
of
in
12.5,
but
there's
I
think
there's
a
lot
of
other
great
things
in
store
if
across
12.5
that
we're
excited
to
ship.
So,
although,
if
I
was
going
to
be
shipping
in
November,
22nd
and
I'm
really
excited
to
get
it
to
the
market
and
to
get
your
feedback
on
it.