►
From YouTube: GitLab 16.2 Kickoff - Enablement:Distribution
Description
Scheduling issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1233
A
Here
is
our
scheduling
issue
for
the
last
quarter,
and
so
this
is
the
last
the
last
milestone
for
this
quarter.
16.2,
you
can
see
we're
gonna,
be
working
on
maintenance
and
essential
upgrades
and
working
towards
our
operative
production
Readiness.
So
if
we
go
to
our
board,
you
can
see
the
a
number
of
the
items
that
we're
going
to
work
on
all
relate
to
maintenance
or
dependency
updates.
So
we
have
six
issues
scheduled
right
now
for
our
regular
maintenance
work.
A
These
are
just
sort
of
normal
things
to
to
keep
packages
going
out
every
Milestone
and
keep
the
team
working
effectively,
and
you
can
see.
We've
got
about
three
issues
scheduled
for
essential
upgrade
work,
but
you
know
the
supporting
kubernetes
1.25
updating
to
node
at
18
across
our
code
base.
A
These
are
both
things
that
I
would
also
Loop
into
maintenance
or
Central
upgrade
work,
and
you
can
see
we
saw
the
tail
end
of
a
couple
items
so
Secrets
management,
which
we
mentioned
before
increasing
our
number
of
reviewers,
which
relates
to
our
contributor
experience,
our
kind
of
trickling
into
162
as
well,
but
yeah
mainly
focused
on
maintenance
work,
upgrade
dependencies
and
working
towards
our
operator,
product
Uranus.
So
diving
into
our
maintenance
work
you
can
see.
We
have
a
number
of
items
still
that
we
hope
to
accomplish.
A
You
know
there's
36
issues
still
open,
but
you
know
obviously
we're
not
going
to
finish
all
these
in
this
quarter,
but
it's
nice
to
have
them
categorized
here.
The
one
of
the
main
ones
I
do
want
to
call
out
is
updating
our
album
charts
to
work
with
Geo
unified
URL.
This
is
a
great
feature.
Edition,
unified
URL
is
a
great
feature
that
Geo
implemented,
and
we
all
we
want
to
make
sure
that
it
works
with
our
help
chart.
A
So
there
was
a
number
of
research
items
that
went
into
seeing
how
we
can
make
this
work
and
now
we're
finally
getting
into
implementing
it.
So
this
is
a
very
exciting
item
that
folks
interested
in
unified
URL
will
soon
be
able
to
utilize
working
on
moving
on
to
our
essential
other
essential
upgrade
items.
I
just
want
to
mention.
You
know,
upgrading
to
a
newer
going
version.
A
Obviously,
I
mentioned
the
kubernetes
1.25
update
and
then
we're
upgrading
redis
to
version
seven,
but
another
one
here,
that's
listed
is
changing
Al
2022
to
Al
2023,
so
this
is
Amazon
Linux
2022
to
Amazon
links
2023.
recently,
Amazon
changed
the
name
and
a
couple
of
underlying
items
related
to
Amazon
Linux
2022
to
an
updated
version
called
Amazon,
Linux
2023..
So
in
16.2
we
hope
to
change
our
builds
to
Amazon
links
2023
and
upgrade
to
allowing
Amazon
links
2023
for
our
packages.
A
So
we
hope
to
implement
this
in
16.2
and
yeah,
so
the
next
phase
of
Amazon
Linux
coming
soon
as
far
as
production
Manus
goes
for
the
operator.
So
this
is
production,
Readiness,
brainstorming
for
the
operator.
A
One
of
the
main
items
in
this
epic
is
moving
the
operator
in
our
internal
maturity
Matrix
from
minimal
to
viable.
This
essentially
has
some
metrics
related
to
customer
usage
and
internal
issues.
Things
like
that,
but
one
of
the
main
items
listed
under
you
know
this
epic
is
our
production,
Readiness
and
parity
with
our
Helm
chart.
So
obviously,
right
now
our
home
chart
is
how
folks
utilize
and
create
instances
that
will
run
cloud
natively
or
in
kubernetes,
and
so
we
want
to
offer
the
same
parity
to
the
helm
chart
as
the
operator.
A
So
there's
a
number
of
items
that
we
need
to
complete,
but
working
towards
production
anus
for
the
operator
definitely
encompasses
making
sure
it
has
a
similar,
install
upgrade
and
just
general
user
experience
related
to
our
Helm
chart.
You
know
we
see
that
as
sort
of
table
Stakes
so
yeah.
This
is
one
of
the
main
items
we're
working
towards
in
16-2
and
hoping
to
be
production
rate
with
the
operator
earlier
in
the
year.
A
But
you
can
see,
we've
got
three
issues
currently
open
for
production
or
excuse
me
parody
with
the
helm,
chart
and
more
issues
on
the
larger
epic
related
to
production
awareness
coming
soon.
So
those
are
the
main
things
sort
of
a
maintenance
and
upgrade
dependency
heavy
milestone.
A
We
sort
of
do
this
in
Cycles,
I
would
say,
as
as
work
comes
in
you
know,
we've
been
heavily
working
on
security,
work,
compliance
work,
you
know
improving
our
contribute
experience
and
trying
to
improve
the
number
of
reviewers
and
maintainers.
We
have
in
the
distribution
projects.
A
So
now
it's
sort
of
time
to
I
guess
you
could
say,
eat
our
vegetables
and
do
our
normal
maintenance
work.
We
do
a
lot
of
Maintenance
work,
sort
of
every
Milestone
anyways,
but
this
one
definitely
has
a
heavy
Focus.
So
those
are
the
items
that
we
plan
to
work
on
16-2.
Thank
you
so
much
and
have
a
good
rest
of
your
day.