►
From YouTube: Plan 13.12 Kickoff
Description
Planning Issue - https://gitlab.com/gitlab-org/plan/-/issues/301
A
Hey
everyone
gabe
here
senior
product
manager
for
the
project
management
group
in
the
plant
stage,
along
with
my
stable
counterparts
in
the
certify
and
product
planning
stages
that
would
be
more
increasing
respectively.
We
are
going
to
talk
about
13.12
and
the
amazing
things
we're
going
to
be
prioritizing
and
working
on
during
the
upcoming
release.
I'm
gonna
go
ahead
and
get
started
talking
through
my
stage,
a
little
bit
so
level
set
with
some
context.
13.11
was
a
bit
of
a
interesting
journey,
to
say
the
least.
A
We
had
a
couple
racket,
rapid
actions
that
engineering
initiated
around
performance
and
database
concerns.
So
most
of
what
I
had
scheduled
in
terms
of
road
map.
Items
for
13.11
are
going
to
get
bumped
to
13.12
or
beyond.
So
in
terms
of
what
I
want
to
preview
that
we're
going
to
be
working
on
in
13.12,
I'm
going
to
just
talk
through
some
of
our
kind
of
performance
priorities.
A
So
it's
not
super
exciting,
but
the
projects
controller
show
page
executes
more
than
100
sql
queries,
which
is
over
the
limits.
We're
going
to
figure
out
how
to
fix
that.
That's
one
area
where,
hopefully,
if
we
fix
this,
it
will
decrease
the
load
on
the
database.
It'll
also
increase
the
performance
of
loading,
the
page.
A
A
Similarly,
groups
issue
lists
under
the
api
is
not
performant
at
scale,
so
we're
going
to
work
on
making
that
more
performant,
along
with
the
high
level
sql
queries
the
create
note
action
which
is
commenting
on
the
issue,
merge,
request
or
snippet
or
epic
or
anywhere
that
you
can
comment
test
cases
now.
Maybe
you
should
mark.
Can
you
comment
test
cases?
Yet?
A
Yes,
you
can
we're
going
to
figure
out
how
to
decrease
the
number
of
escrow
queries
that
creating
a
note
requires
and
then,
lastly,
another
big
focus
is
going
to
be
on
the
bonsai
reference
filters.
They
execute
too
many
queries
and
there's
a
lot
of
impulse
ones
if
you're
not
familiar
the
bonsai
reference
filters
are
the
things
that
post-process
all
of
the
markdown
before
it's
shipped
to
the
client
and
rendered
in
descriptions
and
comments
so
because
it
executes
too
many
queries,
there's
a
bunch
of
impulse
ones.
A
Not
only
is
it
increasing
the
level
of
database,
but
it's
increasing
perceived
performance
when
loading
notes
loading
descriptions
all
across
the
board,
so
this
is
kind
of
a
globally
optimal
thing
for
us
to
focus
on.
I
know
it's
not
like
super
exciting
all
the
stuff,
but
it
should
help
both
the
scalability
of
gitlab.com.
A
B
Okay,
so
for
product
planning.
Similarly,
to
project
management,
we
basically
shifted
our
13.11
into
1312,
so
we
don't
have
any
new
direction
items
that
were
actually
kicking
off
for
this
release.
However,
we
do
have
a
very
big
feature
that
we're
working
on,
which
is
our
epic
and
program
boards
we've
already
shipped
mvc1
and
so
mvc2
is
well
underway.
A
lot
of
that
is
shifted
into
1311
and
1312..
B
I
did
highlight
a
few
performance
enhancements
as
well.
We
have
also
a
spike
into
getting
a
planning
stage,
dashboard
done
with
the
scalability
team.
This
will
help
us
see
more
into
how
some
of
the
underlying
performance
is
going,
including
the
fact
that
a
design
design
management
is
actually
a
git
repo,
so
we're
going
to
light
up
some
get
tracking
features
on
top
of
that
and
see
how
we're
doing
in
terms
of
performance.
B
We
also
have
two
security
issues
that
are
open,
but
we've
got
two
significant
bugs
that
are
carrying
over
that.
I
just
wanted
to
mention,
because
I
know
I
brought
it
up
before
one
is
that
you
should
have
any
activity
when
you're
commenting,
commenting,
opening
or
closing
an
epic
should
be
recorded
on
the
user's
profile
right
now.
That's
not
working
so
we're
going
to
have
that
bug,
stay
open
and
carry
over
in
1312
and
that
some
of
our
filters
are
not
working
with
the
graphql
board
lists.
B
B
C
C
So
yeah
we're
in
the
same
sort
of
situation
here
with
certify
a
lot
of
the
1311
effort
and
capacity
was
dedicated
to
diverting
toward
improving
the
performance.
That's
actually
gone
really
well,
there
are
gonna,
be
a
couple
features
released.
However,
the
main
initiatives
for
1312
are
those
that
were
also
present
1311.,
mainly
this
linking
test
cases
to
requirements.
This
is
a
very
large
epoch
and
you
can
see,
we've
moved
it
to
1312
and
we
should
be
completing
in
14-0
if
things
go
according
to
plan.
C
This
is
a
fantastic
situation
that
will
allow
us
to
link
requirements
and
test
cases
together,
and
it
will
build
on
top
of
the
issue
type
for
requirements
which
will
actually
benefit
other
areas
as
well,
and
it
goes
back
to
something
gabe
and
mentioned
about
how
we're
trying
to
more
generalize
the
issue,
type
and
sort
of
account
for
that
in
different
ways.
So
this
is
a
fantastic
step
toward
that.
We're
very
excited
for
that.
C
We
also
do
have
some
performance
refinements
we're
looking
at
similar
to
what
kristin
mentioned,
we're
looking
for
a
dashboard
to
help
us
with
some
of
the
slis
for
service
desk,
as
well
as
understand,
better
sort
of
how
the
performance
is
for
the
certified
stage
in
general.
So
these
are
both
very
important.
We're
hoping
this
will
help
mitigate
future
performance
issues,
we'll
be
able
to
catch
them
early
and
fix
them
quickly.