►
From YouTube: GitLab 15.7 Kickoff - Enablement:Distribution
Description
Scheduling Issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1131
A
A
If
you
want
to
take
a
look
back
at
what
we
worked
on
last
time,
you
can
view
the
couple
highlighted
items
here
and
the
specific
issues
that
I
called
out
in
the
last
kick-off
video
moving
forward
to
15
7.,
one
of
these
items
that
we
have
planned
out
from
a
while
back
and
now
it's
the
time
to
start
working
on
it
is
improving
distribution,
team
pipelines.
We
wanted
to
do
this
for
a
while.
This
could
be
viewed
as
a
tech.
A
Debt,
epic,
but
really
this
is
internally
facing
But,
ultimately,
will
help
you
all
in
the
future,
because
the
less
that
we
have
to
work
on
these
pipelines
or
the
less
complexity
introduced
by
the
pipelines
that
we
currently
have
means
the
more
time
that
we
can
work
on
new
feature,
work
and
deliverables
for
the
customer
so
and
the
users.
A
This
is
something
that
we're
very
excited
about,
and
we've
set
aside
a
fair
amount
of
our
15.7
miles
so
to
work
on
these
items
and
then
another
one
is
our
secure
solution
for
managing
Omnibus
Secrets.
This
is
a
one
that
we've
been
tracking
for
for
a
while
and
we're
slowly
chipping
away
at
it,
and
this
is
going
to
be
another
highlight
of
that
pick
that
we're
working
on
a
similar
theme
from
a
last
the
last
few
kickoff
videos
as
well.
A
We
do
have
some
compliance
work
that
we're
trying
to
wrap
up,
but
it
is
on
the
tail
end
of
the
compliance
work.
So,
as
I
mentioned
at
the
155
and
15
6
that
that
was
more,
the
focus
was
compliance
work
that
is
dwindling
now,
and
so
we
can
work
on
some
some
of
these
more
larger
epics
that
are
more
specific
to
the
level
rules
for
our
team.
So
moving
into
the
Team
pipeline,
epic
here
feel
free
to
you
know,
scroll
through
it
is
a
fairly
comprehensive
epic.
A
You
can
see
that
we've
got
262
issues
linked
here,
I
will
say
a
good
number
of
these
are
already
complete,
but
it
is
a
is
a
hefty
epic
that
will
will
be
a
while
before
we
complete,
but
we
sort
of
have
grouped
it
into
buckets
here,
of
mini
sub
epics
and
in
156
or
excuse
me,
57
58..
A
We
are
focusing
on
kind
of
closing
out
some
of
these
without
you
know,
dipping
our
toes
into
too
much
of
this
epic,
but
one
of
the
big
ones
that
I
want
to
call
out
here
is
improving
Cloud
native,
build
and
continuous
integration.
A
Sorry,
my
Mouse
is
having
a
little
trouble
here,
but
another
one
I
want
to
call
out
is
modern,
modernizing
our
pack
air
usage
in
Omnibus
pipelines
and
finally
support
certification
of
Amazon
Linux
2..
So
we
are
trying
to
close
out
a
few
of
those
in
15
7
and
then
the
15
8,
we'll
we'll
move
into
some
some
bigger
buckets.
But
overall
this
is
the
main
epic
that
we're
working
on
all
of
the
issues
that
are
tagged
or
you
know
related
to
this
epic-
we're
very
excited
about
because
it'll
improve.
A
You
know
the
way
we
work
so
moving
on
to
the
next
one
here.
This
one
is
certainly
more
customer
and
user
facing
this
is
our
secure
solution
for
managing
Omnibus
Secrets
I've
managed
to
mentioned
this
one
many
many
times,
but
I
will
re-mention
a
couple
of
the
the
main
items
that
we're
working
on
15
7..
A
So
we
want
to
encrypt
non-rails
password
stored
and
get
web
RB.
So
this
one
specifically
probably
warrants
a
little
bit
more
exploration.
We
still
aren't
sure
of
the
solution
that
we
want
to
introduce
here.
So
what
we've
done
is
we've
broken
this
out
into
a
spike.
A
So
this
used
to
be
just
you
know:
encrypt
non-rails
passwords,
but
now
we've
changed
this
over
to
an
investigation,
because
we
really
need
to
figure
out
the
proper
solution
before
diving
into
actually
completing
the
work
here
and
then
the
other
part
is
encrypting
all
rails,
passwords
stored
in
goab
RB,
and
you
can
see
here
that
we
have
2
and
15
6
that
are
probably
going
to
roll
over,
and
so
these
are
two
items
that
we
hope
to
complete
in
15
7.
A
and
then,
hopefully
closing
out
this
rails
password
sub
epic
here
in
157
or
15
8.,
so
between
those
two
items
and
then
wrapping
up
some
of
the
compliance
work,
not
a
whole
lot
to
mention,
as
I
said,
we
sort
of
specifically
called
out
trying
to
have
a
good
portion
of
this
15
7
Mile,
soon
to
be
this
pipeline
efficiency
work.
So
this
is
the
main
thing
that
we're
going
to
be
working
on.