►
From YouTube: GitLab 15.1 Kickoff - Enablement:Distribution
Description
Planning issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1021
A
Here
is
our
scheduling
issue
for
15.1,
and
actually
this
is
our
scheduling
issue
for
the
next
three
milestones:
15,
1,
2
and
3..
The
reason
for
this
change
is,
we
are
going
to
be
focusing
the
next
three
milestones,
mainly
on
efficiency
projects
and
long-term
tech
debt
items
that
we've
been
hoping
to
work
on
for
a
while.
Now
and
now
that
we
have
just
finished
our
major
release
or
15-0,
it
gives
us
a
good
time
to
do
sort
of
a
pseudo
reset
and
tackle
this.
A
You
know
some
of
this
work
that
we've
been
putting
off
for
features
so
and
not
to
say
that
this
won't
affect
future
release
in
the
future.
Basically,
the
idea
is
that
this
these
efficiency
projects
will
ultimately
improve
how
quickly
we
can
roll
out
features
in
the
future,
and
we
feel
it's
a
good
time
to
do
so.
There
will
be
a
few
feature
items
that
are
mixed
in,
as
you
can
see
at
the
top.
A
There
is
our
git
lab
operator,
which
is
a
long-standing
item
that
we've
been
hoping
to
complete,
but
the
main
focus
for
the
next
three
milestones
will
be
those
tech,
debt
and
sort
of
engineering
quality
of
life
items
that
we're
excited
to
complete
so
diving
into
the
issues
here.
A
As
I've
been
mentioning
this
one
for
a
while.
Now
is
the
red
hat
marketplace
listing.
We
want
to
be
included
in
the
red
hat
marketplace,
because
it
shows
that
red
hat
is
certified
and
stands
behind
an
operator
that
we
have
created,
and
so
we
want
to
hold
our
operator
to
the
same
standards
that
red
hat
does
to
be
listed
in
the
marketplace.
A
A
Mainly,
we
have
to
have
all
ubi
variants
for
all
the
images
that
we
deploy
and
basically
we
need
to
either
decide
to
replace,
nginx
or
fork
it,
and
so
this
issue
here
is
a
spike
to
investigate
what
the
best
best
path
forward
is
and
then
once
we
decide
on
that,
it
unlocks
a
lot
more
issues
that
we
have
scheduled
for
15-1
related
to
listing
the
operator
in
the
marketplace.
A
A
This
causes
longer
time
to
develop
for
all
of
our
features
because
we
have
to
you
know,
implement
it
in
two
spots
and
so
by
completing
this
work
and
moving
forward
with
this
vision.
It'll
essentially
give
us
more
velocity
for
every
single
feature
we
implement
in
the
future.
So
this
is
big
for
us
and
we're
excited
about
it.
A
A
Next
up
in
our
efficiency
work
is
improving
our
team
pipelines.
So
right
now
we
face
or
we
are
facing,
an
increase
in
unscheduled
work
and
the
cause
is
essentially
these
pipelines
that
are
very
complex.
A
Originally
these
pipelines
were
created
organically
and
they
grew
as
they
needed
to
and
were
you
know,
iterably
worked
on
based
on
problems
that
kind
of
popped
up,
and
so
we
haven't
necessarily
have
a
lot
of
time
to
dedicate
specifically
to
improving
these
pipelines
and
because
of
that,
it
kind
of
causes
unplanned
work
or
distractions,
and
so
once
we
can
improve
these
pipelines.
It'll
keep
us
focused
on
the
issues
that
we
want
to
focus
on
and
yeah.
A
Ultimately,
in
the
end,
allow
us
to
produce
more
more
features
more
quickly
for
the
end
user,
and
so,
as
I
mentioned,
we're
not
only
going
to
be
focusing
on
efficiency
work,
but
another
item
that
I've
been
mentioning
in
the
past
and
we
need
to
continue
moving
forward
as
we
progress
is
our
fips
148-2
compliance.
A
So
we
have
a
couple
issues
not
necessarily
related
to
distribute
the
distribution
team,
but
items
that
we
can
work
on
and
so
in
an
effort.
This
is
a
you
know
across
very
large
cross-portfolio
effort
for
us,
and
so
we
want
to
keep
this
moving
forward.
A
So
there's
a
fair
amount
of
issues,
at
least
in
1501,
that
we'll
be
working
on
related
to
fips
as
well,
so
that
about
sums
up
for
what
we're
going
to
be
working
on
in
15-1
and
gives
you
a
general
sense
of
what
to
expect
for
the
next
two
kick-offs
15-2
and
3
and
yeah.
I
hope
you
have
a
good
rest
your
day
and
thanks
for
listening.