►
From YouTube: GitLab 12.9 Kickoff - Plan:Certify
Description
The Plan:Certify kickoff for GitLab release 12.9.
The 12.9 Planning issue for the Plan stage can be found here: https://gitlab.com/gitlab-org/plan/issues/62
A
A
So,
throughout
the
12.8
release
cycle,
we
worked
really
hard
to
work
on
understanding
our
metrics
much
better.
We
wanted
to
understand
our
velocity.
We
wanted
to
understand
how
much
capacity
we
had
in
each
release
and
what
we
found
was.
While
our
velocity
is
continuing
to
increase
release
over
release,
we
were
still
over
planning
our
releases
and
what
that's
done
is
it's
created
a
backlog
of
items
through
in
dev
or
in
work,
which
is
not
ideal
for
our
stage,
so
we're
working
very
hard.
A
A
I
need
to
be
broken
out
into
their
own
sort
of
settings
area
for
Service
Desk,
so
we're
starting
to
start
a
problem,
validation
cycle
on
that,
in
addition-
and
that's
captured
actually
right
here,
where
we're
talking
about
how
we
could
potentially
break
this
section
out,
as
we
add
further
items
into
something
like
the
service
desk
section
on
our
next
issue
for
solution
validation.
Is
this
whole
adding
issues
adding
participants
to
HTV
email
address?
A
Currently,
when
you
email
the
service
desk,
you
are
a
participant
on
an
issue
in
any
responses
to
that
issue
that
are
done
within
get
lab,
gets
sent,
email
back
to
you
as
a
participant.
However,
in
a
situation
where
you
may
call
a
company
support
line
and
they
want
to
create
an
issue
in
your
behalf,
there's
currently
no
way
to
add
you,
the
customers,
email
address
to
that
issue,
to
allow
you
to
get
the
updates
out
of
that
issue.
A
A
That's
one
of
the
main
things
we're
gonna
validate
from
a
design
perspective,
we're
marching
forward
with
our
requirements,
management,
and
there
are
a
lot
of
follow-on
issues
that
were
writing
currently,
where
we
want
to
provide
further
features
to
that
new
stage
or
new
section
for
requirements.
Management
now
that
we're,
including
the
MVC
there's
a
lot
of
follow-on
work
that
we
want
to
get
designed
and
the
designer
and
I
are
gonna
work
closely
to
try
to
get
ahead
of
some
of
that
work
to
enable
the
developers
to
have
a
good
amount
of
backlog
ready
for
implementation.
A
So
we're
very
excited
to
do
that.
As
I
mentioned
at
the
beginning
of
this
video,
we
did
spend
a
lot
of
time
throughout
12-8
understanding
our
current
velocity
and
we
were
definitely
over
scheduled
in
twelve
eight,
so
twelve,
nine
we're
gonna
step
back.
We're
gonna,
complete
all
the
work,
that's
in
the
pipeline's
right
now
and
hopefully
queue
up
a
lot
more
exciting
work.
So
we're
very
excited
to
see
where
this
goes
there
any
questions,
as
always,
please
feel
free
to
reach
out
via
the
YouTube
comments
or
within
get
lab
itself.
Thank
you
very
much.