►
From YouTube: Pipeline Execution 15.5 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.5 milestone that the Pipeline Execution team will be working towards.
The 15.5 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/112
The needs weight board can be found here: https://gitlab.com/groups/gitlab-org/-/boards/4178322?not%5Bmilestone_title%5D=Started&label_name%5B%5D=group%3A%3Apipeline+execution&label_name%5B%5D=needs+weight
A
Thank
you,
recording
the
15-5
refinement,
kickoff
and
kickoff
for
the
Milestone
I'm
sharing
the
planning
issue.
So
the
theme
for
this
Milestone
is
to
simplify
the
cost
Factor
calculation
for
public
projects,
so
our
goals
for
the
Milestone
is
always
meet
our
reliability
issue
slos.
So
our
verify
p1s.
In
this
case
we
only
have
a
couple
and
they're
not
actually
reliability
related,
not
security
or
anything
like
that.
We
do
have
one
confidential
issue
that
you
can
check
out.
All
of
those
are
linked
here,
but
we
do
only
have
three
for
this
Milestone.
A
So
we've
been
doing
a
great
job
burning
those
down
getting
those
addressed
as
they
come
in
excellent
work,
so
completing
the
CI
minutes
work
to
use
the
new
cost
Factor
UI
and
set
that
to
one
those
are
the
goals
really
for
the
issue
or
for
the
Milestone,
rather
so
completing
the
last
step
of
hardening
the
CI
limit
getting
that
cost
Factor
set
to
one.
So
all
public
projects
now
have
a
cross
factor
of
one
which
would
be
fantastic
for
those
free
or
for
all
users.
A
Really
so
it's
free
users
where
they
only
have
400
CM
ads
and
then
a
couple
of
other
follow-up
issues
here
that
we're
going
to
be
working
on
and
then
our
second
goal
or
the
third
goal
really
is
completing
three
quarters
75
of
our
scheduled
okr
issues.
There's
an
issue
search
here.
We
have
11
of
them
scheduled
during
the
Milestone,
and
this
wraps
up
Q3
as
far
as
okrscope
getting
us
into
October.
A
So
you
can
click
through
and
take
a
look
at
those
a
good
number
of
them
have
already
been
refined.
We
have
weights
on
them.
We
have
great
proposals,
so
we
should
be
able
to
just
pick
them
up
work
them,
get
them
closed
and
meet
our
okr
goals
for
the
quarter.
A
So
the
other
thing
I
wanted
to
do
today
was
kind
of
talk
about
the
issue,
breakdown
and
there's
a
thread
started
in
the
issue
itself.
So
you
can
take
a
look
and
think
of
look
at
how
we're
thinking
about
how
we're
going
to
break
that
down
at
this
milestone.
A
So
the
inputs
that
we're
looking
at
is
what
was
the
split
from
the
last
Milestone.
What
was
the
carryover
or
excluding
carryover
rather,
and
it
was
about
35
35
30,
feature
bug
maintenance.
The
reason
for
that
in
15
4
was
availability
is
in
a
good
spot,
we're
not
over
your
budget,
we're
99.97,
I,
think
as
of
this
morning
or
99.98.
A
It
looks
like
with
10
minutes
of
air
budget
remaining
and
so
we're
that
gets
us
the
ability
to
not
have
to
focus
on
those
maintenance
issues
not
have
to
focus
on
endpoints
that
we
need
to.
You
know,
get
more
performant
as
a
first
priority
for
us,
so
that
can
be
a
secondary
or
tertiary
priority.
The
other
thing
that
I'm
looking
at
is
how
many
missed
SLO
bugs
we
have
in.
As
we
were
planning
for
15-4
we
had
71.
Now
we
have
73
so
that
pile
continues
to
grow.
A
A
A
Basically,
eight
eight
and
eight
one
of
those
isn't
shown
here
just
because
it
is
a
confidential
issue,
but
you
can
scroll
through
and
take
a
look
at
those.
These
are
all
stack
ranked.
So
what
is
most
important,
usually
verify
P1
P2
or
severity,
S1,
S2
and
so
on
down.
So
if
we
have
to
make
trade-offs,
we
would
start
by
pulling
things
off
of
the
bottom
of
these
lists,
but
we'll
pull
from
them
equally,
basically
throughout
the
Milestone.
So
that's
the
kickoff
for
15.5
needs
weight
board.
A
You'll
start
to
get
things
on
that
next
week
or
the
week
after
I.
Think
as
September
starts.
Good
news
is
there's
not
too
much
in
15.5
that
still
needs
a
weight,
because
we've
gotten
a
lot
of
work
done
on
those
already.
A
lot
of
things
are
ready
to
go
and
if
you
want
to
go
ahead
and
start
as
you
finish,
15
4
and
you're
working
from
the
right,
everything
is
in
a
spot
where
it's
been
reviewed
or
is
you
know,
verified
in
production?