►
From YouTube: GitLab 15.11 Kickoff - Enablement:Distribution
Description
Scheduling issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1176
A
A
Here
is
our
scheduling
issue
familiar
as
always
we'll
be
creating
a
new
scheduling
issue
for
the
next
quarter,
which
will
be
16?
Oh,
our
first
major
release,
minor
minor
release
at
16,
1
and
16-2,
so
rounding
out
the
end
of
15.
A
We've
got
a
couple,
big
core
items
that
we
would
like
to
accomplish.
So
you
know,
speaking
of
the
major
release,
the
distribution
team
is
a
heavy
stakeholder
in
major
releases
and
we
are
a
large
producer
of
artifacts
that
allow
the
major
release
to
go
out
to
self-managed
customers.
So
it
is
important
that
we
prep
for
the
major
release
as
best
we
can
to
allow
a
Smooth
release.
So
this
is
probably
one
of
the
main
things
that
we'll
we'll
focus
on.
A
A
A
So
this
video
is
also
going
to
be
a
little
bit
different
sort
of
because
of
the
the
specific
Parts
aren't
necessarily
as
important
as
the
sort
of
some
of
those
parts
for
the
computer
experience
and
long-term
Bill
efficiency.
A
So
I
just
want
to
kind
of
pull
up
and
show
the
that
attention
that
we're
putting
on
those
efficiency
projects
as
well
as
the
you
know,
we're
a
major
release
prep.
So
if
I
kind
of
scroll
down
here
you
can
see
you
know
we
have
one
specific
specific
project
for
contributor
experience
listed
here,
but
we
have
many
projects
listed
that
all
relate
to
our
efficiency
work.
So
many
of
these
projects
down
at
the
end
so
modernizing
our
Omnibus
pipelines.
A
You
know
our
CI
configuration
for
Omnibus
and
then
going
down.
You
know
container
definition
so
related
to
our
you
know:
Cloud
native,
get
lab
the
build,
continuous
integration
for
actually
Cloud
native
so
including
improving
our
Cloud
native
builds
in
general
and
then
as
a
whole.
You
know
our
Omnibus
package
size
and
design
strategy,
so
you
can
see
the
attention
that
we're
we're
putting
here
on
efficiency,
work
and
contributor
experience.
It's
you
know.
A
It's
roughly
a
third
of
the
issues
that
we
hope
to
tackle,
and
then
you
know
going
back
up
here
as
I
mentioned
you're
working
on
our
support
for
our
dependency
updates,
so
supporting
kubernetes
1.25
for
deployment.
A
We've
got
testing
our
operator
on
openshift.
So
another
item
that
we
were
talking
about
for
dependency
updates
and
the
rest
here
you
know
much
of
this
is
prepped,
so
support
for
postgres,
14,
updating
going.
You
know
deprecation
for
open
source
15.3
and
changing
our
default
packages
to
postgres
13..
So
it's
kind
of
a
third,
a
third,
a
third
as
far
as
breakdown
goes.
A
If
there
are
the
items
here
are
related
to
True
experience
and
build
efficiency,
a
third
related
to
the
major
release
and
I
guess
not
quite
a
third,
but
you
know
a
handful
devoted
to
dependency
updates
and
you
can
see.
We've
got
bug
bird
down
that
which
will
always
prioritize,
and
then
one
I
want
to
specifically
talk
about
is
hopefully
rounding
our
our
enablement
of
contributions
to
arm
64
support.
So
we're
going
to
be
finishing
up
this.
You
know
these
build
scripts
to
run.
A
Multi-Architecture
Docker
builds,
which
is
going
to
kind
of
unlock
the
next
phase
of
work
for
contributors
to
this
project
and
folks
that
want
to
see
arms,
60,
core
support,
which
we
do
as
well
so
being
able
to
keep
this
progressing
and
kind
of
unlock.
A
That
next
phase
of
the
work
is
incredibly
important,
and
you
can
see
that
this
issue
currently
blocks
the
overarching
kind
of
Epic
here
for
supporting
multi-architecture
builds
for
CNG
images,
so
yeah,
that's
kind
of
a
quick
summary,
maybe
a
little
more
of
a
quick
video.
If
you,
if
you
want
to
take
more
attention
or
look
more
closely
at
any
of
these
issues,
you
know
feel
free
to
take
a
look
at
our
deliverable
board
here
and
then
you
can
view
exactly
what
I'm
talking
about
other
than
that
you
know.
A
I
hope
you
have
a
really
great
rest
your
day
and
yeah.
We
look
forward
to
our
1511
release
in
prep
for
16.0.
Thank
you
so
much.