►
From YouTube: GitLab 12.7 Kickoff - Plan: Project Management
Description
12.7 Release planning issue - https://gitlab.com/gitlab-org/plan/issues/35
Issue Tracking Category Direction - https://about.gitlab.com/direction/plan/issue_tracking/
Issue Boards Category Direction - https://about.gitlab.com/direction/plan/kanban_boards/
A
A
Alright,
if
you
want
to
follow
along
home,
this
issue
for
12.7
release
planning
within
the
plan
stage,
is
at
gate.
Lab
ward
/
play
/
issues,
/
number
35
within
the
project
management
group
in
12.7,
we're
in
a
kind
of
continue
on
where
we
left
off
to
12.6,
improving
milestones
and
defining
the
types
of
milestones
and
we'll
get
through
that
before
we
get
started.
Let's
look
through
the
issue
tracking
category
strategy
page.
A
This
has
not
changed
much
other
than
some
minor
typos
here
and
there
and
we'll
scroll
down
to
where
were
what's
next
and
why
we
still
need
to
solve
for
the
problem
of
managing
sprint
and
release
cadence.
You
can't
have
an
issue
that
belongs
to
multiple
time
boxes.
We
think
it
live
right
now
which
makes
it
difficult
to
calculate
velocity
over
time
and
also
practice
normal
agile
planning
methodologies,
like
scrum
mentoring
program.
A
Another
thing:
that's
holding
folks
back
from
adopting
get
labs
for
planning
and
project
management
is
the
ability
to
track
scope,
change
it's
in
a
mouse
in
and
you
see
down
here.
We
also
have
a
team
velocity
volatility
where
we're
splitting
out
the
calculation
of
that.
For
a
mouse
on
mouse
and
mouse
down
into
its
own
epic
running
through
this
first
epoch
right
here
of
managing
sprint
and
release
cadence,
you
can
tempt
if
you
want
just
a
little
nice
diagram
of
safe,
which
lot
of
organizations
are
using
specially
large
ones.
A
Core
problem
is
kind
of
talked
about.
You
can't
have
an
issue
label
tool
time
boxes,
there's
no
way,
therefore,
to
understand
capacity
from
one
milestone
to
another
that
are
the
same
kind
so
like
from
sprint
sprint
and
there's
no
way
to
report
progress
against
more
than
one
time
box.
So
it's
kind
of
a
problem
and
how
we're
going
about
solving
that
is.
We
are
going
to
add
the
ability
to
have
an
issue.
They
can
decide
multiple
milestones
and
12.6.
A
We
laid
the
from
grant
groundwork
for
this
by
enabling
a
data
migration
that
set
the
kind
of
the
data
format
up,
so
the
issues
Campbell
milestones
and
then
12.7
we're
going
to
actually
implement
it
in
the
interface
itself.
Along
with
that,
you
should
be
able
to
do
behind
multiple
milestone
types
within
a
top-level
group,
so
these
two
are
in
flight
right
now.
The
design
is
just
about
done.
If
you
want
to
check
it
out,
you
can
go.
Look
at
the
issues
themselves,
not
a
whole
lot
to
talk
about
other
than
this.
A
Having
these
two
things
will
enable
formal
practicing
of
scrum
would
think
at
lab,
which
would
be
cool,
and
once
these
are
in
place,
we're
going
to
do
some
further
Ottoman
automations
like
be
able
to
move
issues
from
one
mile
so
into
the
next
automatically
once
it
inspires.
We
can
also
then
calculate
things
like
velocity
up.
We
ran
in
number
for
nice
milestones,
pretty
cool
stuff.
There
see
what
else
yeah
we're
also
adding
furniture
so,
along
with
the
problem,
would
not
be
able
to
track
scope,
change
from
milestone
a
milestone.
A
The
simplest
approach
here
is
going
to
be
adding
burn
up
charts
and
you
can
kind
of
see
what
that
will
end
up
looking
up
down
here
next
in
the
burn
down
chart
we're
going
to
have
this
new
kind
of
contract
called
the
burn
up
chart
which
will
have
a
fixed
number
of
scope
items
so
as
it
involves
or
changes
over
the
course
of
a
milestone.
This
line
will
either
go
up
or
it
will
stay
the
same
and
then
the
green
line
reflects
what
issues
have
actually
been
completed
as
you're
tracking
against
that
milestone
itself.
A
We
haven't
updated
the
Asian
boards
much
either
other
than
we're
still
pressing
forward
with
real-time
boards
for
12.7,
the
team
has
a
goal
of
being
able
to
get
one
field
any
field
updating
in
real
time.
This
has
a
lot
of
dependencies.
We
have
to
implement
WebSockets.
We
have
to
coordinate
with
the
memory
group
to
make
sure
that
it's
performant
and
then
we
also
have
to
recalculate
running
to
support
subscriptions.
A
So
there's
a
lot
of
work
there
and
then
the
first
smallest
little
slice
we
can
do
is
getting
one
single
field
updating
with
this
new
kind
of
model,
so
that's
kind
of
to
go
for
12.7
there,
and
that
also
kind
of
correlates
well
with
issue
board.
Refactoring
we're
doing
a
lot
to
get
that
set
up
for
real
time
before
we
add
a
bunch
of
more
features
to
the
issue.
Words
like
swimlanes.
We
need
make
sure
that
it
is
structured
in
a
way
that
it
can
be
real
time.
A
This
is
WebSockets
already
and
we
can't
iterate
on
feature
set
with
a
code
base.
That's
up
to
spec
power
building
things
now.
So
that's
our
goal
for
12.7
a
lot
of
kind
of
framework
groundwork,
but
also
adding
some
nice
features
on
top
of
the
Matheson's
and
mouse
subtypes,
and
more
formally
supporting
scrum
and
stream
program.
That's
it
hope
you
enjoyed
you.