►
From YouTube: GitLab 15.10 Kickoff - Enablement:Distribution
Description
Scheduling Issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1176
A
A
Here
is
our
scheduling
issue
for
the
quarter,
so
Milestones
15,
9,
10
and
11..
In
this
case,
we'll
be
talking
about
1510,
and
you
can
see.
We
have
the
exact
same
core
ethics
that
we're
going
to
kind
of
be
working
on
for
this
Milestone
and
the
next
one.
So
I
just
included
it
here
and
if
we
scroll
down
here,
you
can
see
the
issues
that
I'll
be
talking
about
in
this
video
underneath
this
heading.
So
what
we're
going
to
be
working
on
is
the
same
work
that
we
were
doing
last.
A
A
We
do
have
a
long
comment
here
from
DJ
and
some
discussion
from
Hussein,
with
basically
a
breakdown
of
build
efficiency,
work
and
career
experience,
work
that
are
going
to
be
highly
impactful,
and
this
is
kind
of
the
pool
that
we're
pulling
from
when
we
move
forward
and
Hussein
is
basically
described.
Some
improvements
here
for
CNG.
A
Another
thing
that
I
want
to
mention
is:
there
are
two
specific
epics
for
q1,
so
we've
got
a
q1,
so
the
efficiency,
epic
and
the
computer
experience
ethic
are
very
long,
but
we've
broken
it
out
into
q1
efficiency,
work
and
q1
contributor
work,
so
I'll
pull
up
those
epics
in
a
second
but
diving
into
our
distribution.
Delivery
logos
board.
You
kind
of
see
how
it
breaks
out
by
epic
that
we
plan
to
work
on
this
quarter.
So
you
can
see
the
top.
A
We've
got
obviously
bug
burned
down,
but
then
we
get
to
our
efficiency
improvements,
which
you
can
see
we're
going
to
work
towards
four
issues.
There
we've
got
five
issues
in
consumer
experience
and
actually
another
epic
related
to
contributor
experience.
So
both
these
issues
would
fall
under
contributor
experience
as
well,
and
then
you
can
kind
of
see
some
of
our
dependencies
who
work
here
at
the
bottom,
which
I'll
get
into
so
that's
kind
of
a
nice
breakdown
visual
to
see
what
we're
going
to
be
working
on
so
moving
into
our
efficiency
work.
A
This
is
the
Epic
that
Dieter
created
for
specifically
items
from
the
efficiency,
epic
that
we're
going
to
work
on
or
plan
to
work
on
q1,
basically,
the
same
ones
that
DJ
had
proposed
in
that
comment
that
we
discussed
and
then
this
is
the
controller
experience
Improvement
one.
So
these
are
again
the
the
same
issues
that
were
proposed
there
that
we
hope
to
accomplish
in
q1.
So
moving
on
to
specific
contributor
experience
items,
I
I
did
want
to
call
out
the
work
on
this
Milestone.
One
here
is
ensure
changes
to
other
components.
A
Don't
or
doesn't
break
package
builds.
So
this
is
very
important.
So
if
someone
comes
in
and
wants
to
make
a
change
to
something
that
we're
doing
here
in
distribution,
we
could
break
what
we're
doing
in
our
package
builds
and
obviously
that's
not
a
great
experience
and
leads
to
questions
coming
to
our
team
when
someone
wants
to
contribute
to
our
packages.
So
we
want
to
improve
that
experience.
A
So
this
is
a
great
issue
to
be
working
towards
another
one
we
have
here
is
have
a
single
source
of
Truth
ssot
page
in
the
handbook,
describing
how
new
versions
are
released
for
all
install
types.
So
right
now,
I
think
a
lot
of
this
knowledge
is
hosted
in
the
distribution
team
and
it
would
be
great
for
everyone
to
have
this
knowledge
so
that
someone
wants
to
contribute
to
any
of
these
projects.
This
one
might
be
a
little
more
internal
or
external
pacing.
A
So,
if
someone
you
know
externally,
is
interested
in
this
work,
we
want
to
make
sure
that
what
is
in
our
Engineers
Minds
is
for
all
to
see.
So
anyone
can
contribute
moving
forward
here.
So
those
are
two
great
issues
that
was
specifically
call
out
from
a
true
experience
and
I
just
want
to
call
out
some
of
the
dependency
work
that
we're
working
on.
A
So
we
are
still
testing
against
4.8
and
411,
so
we
finished,
or
you
know,
we
wrapped
up
a
lot
of
the
work
for
4.8
and
now
moving
into
1510
we're
gonna
be
working
on
411
for
openshift
work
and
then
moving
forward
in
159
we
finished
up
supporting
kubernetes
1.22
and
now
we're
going
to
be
starting
on
supporting
kubernetes
1.25.
We
will
not
finish
everything
here
in
1510.
A
You
can
see
only
one
of
the
issues
right
now
is
marked
as
1510,
but
we're
going
to
continue
working
towards
it
and
making
progress
and
then
probably
wrap
it
up
in
1511
or
at
least
in
anticipation
for
16.
Now,
so
that's
about
everything
that
we're
going
to
be
working
on
again.
Keeping
the
themes
of
build
efficiency,
contribute
experience
and
just
you
know,
keeping
our
software
dependencies
up
to
date
and
with
with
the
most
recent
versions
that
are
available.