►
From YouTube: GitLab 13.0 Kickoff - Plan:Certify
Description
Kickoff for the Plan:Certify Group.
Planning Issue located here - https://gitlab.com/gitlab-org/plan/-/issues/85
A
Hello,
everyone
and
welcome
to
the
certified
group
kickoff
for
13.0
here,
get
lamb,
that's
a
very
exciting
release.
Here.
We've
talked
a
lot
about
how
we
want
to
move
forward
with
planning
for
the
certified
team
and
given
that
we
are
a
shared
engineering
team
before
between
portfolio
management
and
certify,
we're
proposing
a
concept,
this
kickoff
of
doing
a
primary
focus
for
each
release,
as
well
as
a
set
of
secondary
topics
which
can
be
worked
in
the
background
and
they're
sort
of
ongoing
or
continued
themes.
A
We're
gonna
try
that
for
this
release
and
see
how
it
works
or
excited
about
that
our
primary
focus,
this
release
will
be
requirements,
management.
The
MVC
was
released
in
12.10
and
that's
very
exciting.
For
us,
a
whole
new
realm
of
opportunity
has
opened
up
within
your
DevOps
platform.
Now,
with
requirements
being
native
inbuilt
in
one
of
the
things
we're
looking
to
do
is:
there's
the
islands
two
outstanding
epic
to
improve
the
requirements
management
experience.
This
epic
has
numerous
fixes
or
just
updates
to
it.
A
Some
of
them
are
to
increase
the
length
of
requirements
how
long
they
can
be.
Also,
there's
some
options
here
for
filtering
support
for
the
requirements
list
right
now.
You
have
a
large
list.
We
like
to
have
some
filtering
support
there,
so
those
are
all
exciting
features
that
are
gonna,
be
great
additions
to
our
current
requirements.
A
Management
offering
there
are
also
a
couple
other
areas
that
we
look
to
want
to
look
at,
and
one
of
them
is
to
ensure
that
we're
not
incurring
technical
debt
early
on
in
this
feature
release
there's
actually
an
open
issue
right
now
for
front-end
technical
debt,
which
was
a
fantastic
addition
to
our
issues.
I
lists
a
series
of
things
that
we
want
to
fix
in
the
front-end
development,
to
sort
of
reduce
any
technical
debt
moving
forward,
and
that
enables
us
to
be
more
agile
as
we
move
forward.
So
that's
a
priority.
A
This
released
as
well
for
some
of
our
secondary
topics,
and
there
are
some
outstanding
issues
that
I've
talked
about
before,
such
as
configurable
email
addresses
for
Service
Desk
and
allowing
private
comments
and
comment
about
resources.
These
have
been
ongoing
for
two
or
three
releases
and
we'd
like
to
finish
them
up
this
release,
so
that
we
can
move
with
the
clean
slate
and
not
have
a
series
of
tasks
out
there
from
previous
releases,
so
that's
sort
of
on
the
agenda.
A
A
The
other
idea
in
this
release
is
some
planning
and
design
topics.
One
thing
that
we're
really
struggling
with
for
certify
is
understanding
how
people
are
using
our
product
and
how
many
people
are
actually
taking
advantage
of
the
features
we're
offering.
So
there
are
some
plans
in
the
works
to
get
more
specific
user
data
now
personal
data,
but
just
usage
data,
so
we
can
start
tracking
the
interactions
with
requirements
and
tracking
these
are
blocking
or
blocked
issues
just
that
we
can
better
understand
if
the
fixes
and
changes
we're
making
are
showing
that
improvement.
A
For
our
customer
experience,
the
other
notable
thing
to
mention
is
that
Service
Desk
is
moving
to
the
core
functionality
which
we're
very
excited
to
provide
that
to
more
users.
There's
a
current
issue
out
there
right
here,
I'll
bring
up,
and
basically
we're
planning
that
right
now
and
we're
planning
on
implementing
that
over
the
next
couple
releases
in
this
release,
we're
hoping
to
sort
of
start
getting
the
groundwork
laid.
So
this
will
be
coming
out
to
everybody
as
open
source.
This
is
very
exciting
and
I'm
really
glad
to
get
more
feedback
and
more
users
using
it.