►
From YouTube: Pipeline Execution 15.2 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.2 milestone that the Pipeline Execution team will be working towards.
The 15.2 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/101
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%20execution&label_name%5B%5D=needs%20weight
A
Hey
team:
this
is
the
15-2
refinement
kickoff,
as
we've
kicked
off
15-1
and
that
work
has
already
started.
I
wanted
to
talk
through
the
planning
issue
that
is
out
there
for
15-2
as
you're
starting
refinement
of
that
milestone
so
15-2
our
theme
around
that
is
really
focusing
on
work
for
the
new
oss
plans
and
supporting
gitlab.com
stability,
which
is
an
ongoing
theme
for
us.
So
our
first
goal
is
meeting
our
reliability.
Slos
and
those
are
all
verified,
p
ones.
So
we
have
six
of
those.
A
It
looks
like
it's
a
big
list
in
fifteen
two.
I
know
infra
dev
issues,
though
among
those
and
then
as
we
get
into
the
product
priorities
that
gets
us
into
our
second
goal.
I'm
completing
the
ci
minutes
work
that
we
need
to
transition
those
existing
oss
projects
over
to
that
new
plan,
type
that
we
created
with
the
fulfillment
team.
So
there's
a
couple
of
items
that
go
into
there:
reducing
that
using
sorry
a
reduced
cost
factor
for
public
forks,
so
for
public
projects.
A
If
there's
a
fork
to
it,
it
uses
a
reduced
cost
factor.
We
don't
want
contributors
to
open
source
or
to
the
gitlab
project
having
to
burn
through
a
bunch
of
their
ci
minutes
just
to
contribute
to
those
projects,
we'll
use
a
reduced
cost
factor
for
that,
and
then
fabio
is
going
to
kick
off
some
work
around
making
the
standard
and
the
oss
cost
factors
configurable.
A
So
that
instance
admins
can
handle
that
themselves.
That'll
help
our
open
source
contributors
or
open
source
projects
who
are
self-managing
handle
the
same
thing,
so
they
can
say,
contributors
don't
have
as
much
of
a
quota
necessarily
used
up
by
minutes
if
they're
enforcing
one.
So
those
are
the
two
big
ones
that
I
wanted
to
call
out
and
then
I've
inserted
a
stretch
goal
as
well.
A
I
feel
like
we're
making
some
good
progress
burning
down
the
items
that
are
in
our
milestones
so
right
now
early
on,
I'm
introducing
the
stretch
goal:
completing
the
work
for
merge
trains,
that's
blocking
several
of
our
other
high
priority
bugs
in
that
category.
So
it's
the
object
model
realignment.
A
So
looking
for
comments
and
their
contributions
in
that
issue
around
what
the
next
steps
are
to
get
that
moving
the
the
issue
itself.
Probably
needs
an
overhaul
in
the
proposal,
so
let's
start
taking
a
peek
at
that
and
seeing
what
we
can
poke
at
what
we
can
learn.
What
we
need
to
do
to
move
that
category
forward
and
resolve
some
of
those
bugs
because
we'd
love
to
start
dog
fooding
that
on
the
gitlab
project
itself.
Yet
this
quarter.
A
So
those
are
some
of
the
high
profile
things
that
I
wanted
to
call
out
as
you're.
Looking
at
the
needs
wait
board
it's
all
in
that
stack,
rank
order,
verify
p1,
p2s,
p3s
and
then
further
prioritize
that
mark
and
sam
and
I
have
put
together
so
jump
in.
There
start
grabbing
some
issues
and
if
you
have
questions
feel
free
to
tag
me
thanks.