►
From YouTube: GitLab 14.5 Kickoff - Enablement:Distribution
Description
Kickoff for the Distribution group for the GitLab 14.5 release.
Planning issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/923
A
So
for
14.5,
we've
got
any
rollover
from
14.4,
obviously,
and
then
moving
into
supporting
s390
architecture,
fips
compliance,
our
operator
next
release
and
then
finally,
any
tech
debt.
So
talking
about
our
path
forward
for
s390
is
going
to
lead
through
grpc.
This
is
something
we're
going
to
work
on.
Basically,
this
is
a
value
add
to
our
users
by
by
giving
us
a
more
robust
offering
for
linux
on
z
support.
A
A
We
also
might
end
up
working
on
this
one,
but
basically
pretty
heavy
lift
to
be
fixed
compliance
on
our
omnibus
package
for
14.5.
A
We're
also
going
to
do
our
investigation
issue
for
cloud
native
tips,
compliance,
and
this
will
probably
spawn
a
couple
more
issues,
but
you
know
once
we're
going
to
tackle
this
work
and
then
probably
tackle
any
issues
that
come
out
of
this
in
14.6.
A
Basically,
this
fips
compliance
will
support
any
customers
that
are
interested
in
a
higher
level
of
compliance
or
requirements
from
their
customers,
and
this
is
going
to
be
a
great
value
ad
get
lab
and
then,
finally,
you
probably
have
noticed
the
operator
has
dipped
in
priority
compared
to
previous
releases.
A
This
is
not
to
say
it's
not
important,
but
after
we
have
g8
it,
which
was
officially
announced
on
october
12th,
we
had
a
great
launch,
but
the
work
doesn't
stop.
So
we
want
to
keep
moving
forward
with
iterating
on
our
gitlab
operator
and
with
that
comes
a
couple.
Great
value
adds
in
14.5,
hopefully
so,
enabling
true
zero
downtime
upgrades
is
probably
the
biggest
one,
and
also
our
official
red
hat
certification.
A
With
that
comes
working
on
the
operator
lifecycle,
one
operator,
lifecycle
manager,
excuse
me,
and
basically
this
will
allow
us
to
list
the
operator
and
operator
hub
and
in
the
openshift
operator
hub.
So
all
these
are
great
next
iterations
for
operator,
as
we
continue
to
improve
and
work
towards
its
higher
level
maturity.
A
Finally,
we
have
some
tech
debt.
So
now
that
things
have,
you
know,
we've
gotten
past
our
ja
release
of
our
operator.
We
want
to
tackle
some
of
the
tech
debt
that
we've
been
putting
off
work
on
some
docs
improvements,
to
give
a
little
more
clarity
to
some
of
our
tutorials
and
and
installation
guides.
That
sort
of
thing
so
overall
we're
very
excited
about
14.5
and
hope.
You
have
a
great
rest.
Your
day.