►
From YouTube: GitLab 14.1 Kickoff - Plan
Description
Planning Issue: https://gitlab.com/gitlab-org/plan/-/issues/340
A
All
right
welcome
to
the
plan
stage:
14.1
kickoff
we've
got
the
whole
team
here,
certified
product
planning
and
project
management.
A
We
are
going
to
take
you
through
just
high
level
what
we're
kicking
off
in
this
release,
and
I'm
going
to
start
out
just
by
talking
about
a
shared
venture
that
we
have
as
a
team
and
gabe
or
mark
can
jump
in
as
needed.
As
I
talk
through
these,
so
one
of
the
really
cool
things
that
we're
doing
for
the
next
four
to
six
months
is
we're
combining
our
teams
together
to
solve
planning
objects
which
is
essentially
currently
within
gitlab.
A
So
the
main
mvc
that
we
are
going
to
start
with
will
be
a
project
level
feature
object
which
will
behave
similarly
to
group
level
objects,
but
we're
essentially
going
to
be
proving
the
model
of
an
epic
at
product
project
level
and
how
it
relates
to
issues
or
other
objects
below
it.
Once
we
solve
that,
we
can.
A
We're
going
to
go
through
a
few
mvcs
where
we
look
at
multi-level
epics,
which
are
features
as
well
as
starting
to
render
these
on
different
views
so
like
rendering.
The
new
feature
object
on
two
road
maps,
rendering
it
in
list
views
board
views
and
all
of
that,
and
then
the
find
this
part
we
haven't.
Really
we
haven't
done
due
diligence
on,
but
we
need
to
do
a
migration
of
our
current
epics
onto
this
new
feature.
A
A
But
we're
putting
all
of
our
focus
right
now
on
getting
mvc1
weighted,
so
all
of
these
are
going
to
be
transferred
into
git
lab
and
the
team
is
going
to
go
through
and
wait
all
of
the
work
for
mvc1
so
that
in
14
2
we'll
be
able
to
kick
off
and
do
the
actual
work
so
high
level.
That's
where
we're
at
in
terms
of
this
shared
planning,
object,
initiative.
B
Switch
at
the
beginning
and
switch
to
my
usb
hub
instead
of
my
microphone
anyways
moving
on.
Let
me
share
my
screen.
Real,
quick
and
I'll
talk
through
just
a
few
of
the
things
in
plan.
As
person
mentioned,
we
are
focused
solely
on
this
effort
and
in
fact
my
team
has
kind
of
been
working
on
laying
some
groundwork
for
this
to
start
off.
B
Anyways
and
one
of
the
things
that
we'll
be
working
on
is
adding
support
for
issue
types
and
so
like
this
is
where
we
talked
about
the
feature
you
know,
that's
actually
usually
powered
by,
like
what
we've
been
working
on
already
same
as
mark
and
certify
have
been
moving
and
migrating
requirements
into
a
type
of
issue
as
well
we're
kind
of
formalizing
this,
where
issue
types
will
have
icons
and
we're
still
sorting
out
the
details
around
we
might
hold
off
on
one
of
the
default
feature
issue
types
that
we
were
gonna
launch
with
called
the
feature
and
use
that
for
this
work
that
we're
doing
to
consolidate
planning
objects,
but
we're
already
kind
of
have
some
mmrs
against
this.
B
That
we
had
scheduled
a
couple
for
the
last
few
releases.
So
we're
gonna
finish
that
up
in
support
of
the
kind
of
ongoing
effort
that
we
have
across
the
stage
and
then
playing
work
with
iterations.
B
We
got
really
close
to
being
finished
with
iteration,
cadences
and
14.0,
and
so
that's
going
to
carry
over
we're
going
to
we're
basically
going
to
get
the
last
few
merch
requests
that
already
open
in
and
then
default
to
feature
reflect
on,
so
that
will
be
launched
and
then
we're
going
to
continue
working
and
chipping
away
improving
the
availability
sla.
B
So
this
is
our
air
budgets
work.
It's
a
lot,
so
we're
kind
of
just
trying
to
chunk
up
a
little
bit
and
calculate
each
release
and
then
there's
ongoing
work
around
improving
performance
of
mr
issue,
discussions,
controller
and
reducing
memory,
consumption
for
issues
in
merge
requests.
This
is
part
of
the
ongoing
q2
okrs.
B
So
it's
still
a
little
bit
unclear
how
much
more
progress
we're
going
to
be
able
to
make
here
as
it's
a
fairly
complex
issue
and
there's
also
ongoing
rapid
actions
and
database
work
that
has
kind
of
bumped
this
down
and
so
for
the
capacity
we
have
allocated
towards
performance
refinement.
I'm
hopeful
that
we
can
make
progress
here,
but
we're
trying
to
get
as
much
of
this
stuff
cleaned
up
as
possible,
so
we
can
focus
solely
on
moving
the
planning
objects
shared
initiative
forward.
So
that's
what.
C
A
Nice,
okay
I'll
go
next
quickly,
just
to
go
through
mine.
So
similarly,
as
we
mentioned,
we
are
all
focused
on
the
planning
object
work,
so
that
is
the
majority
of
what
the
team
will
be
working
on.
They
also
will
be
helping
to
wait
for
14.2,
which
will
be
a
big
effort
to
get
all
of
that
work
weighted.
A
We
do
have
some
carryover
from
14.0
a
few
bugs
that
have
been
frustrating
for
me
as
well.
This
is
one
that
is
a
bug
with
adding
new
sub
epics
when
you're
at
the
group
level,
but
a
lot
of
our
time
also
is
going
to
be
on
fixing
some
performance
related
bugs
and
trying
to
contribute
to
our
uptime
values
as
well
as
app
decks
figuring
that
out.
The
back-end
team
has
a
lot
of
ongoing
work
there.
So
not
too
many
with
the
focus
on
planing
objects.
C
Excellent,
thank
you
so
yeah
for
the
certified
team.
Let
me
share
here
real
quick
and
it
looks
like
I
have
to
make
an
edit
here
after
this,
but
at
any
rate
yeah
for
the
certified
team.
We're
really
excited
to
build
our
requirements,
management,
we're
really
excited
to
bring
requirements
into
an
issue
type.
I
know
gabe
mentioned
briefly
about
how
we're
trying
to
consolidate
on
a
single,
primitive
issue
type
so
that
we
can
build
out
features
in
a
collaborative
and
efficient
way.
C
The
first
one
to
go
that
direction.
Right
now
is
the
requirements
so
we're
we're
kind
of
leading
the
charge
here,
and
hopefully,
we'll
learn
a
lot
from
that,
as
the
team
goes
through
this
migration.
So
this
initiative
is
going
to
bring
the
benefits
of
issues
to
requirements.
It
will
allow
a
lot
of
opportunity
for
linking
and
relating
different
requirements
together
with
other
objects
that
are
also
issue
types,
so
that's
very
exciting
work.
We
also
have
one
carryover
from
previous
release,
so
this
actually
is
a
requirements.
Last
state
reporting
consistency
that
we've
noted.
C
It
seems
to
only
occur
when
using
the
graphql
endpoints,
but
we're
trying
to
make
sure
that,
at
any
rate,
this
has
been
it
missed.
13
all
10
and
14
0
all
the
way
through
14..
So
this
is
going
to
be
prioritized
we're
going
to
make
sure
we
take
care
of
this
in
this
release.