►
From YouTube: GitLab 13.4 Kickoff - Package:Package
Description
13.4 Kickoff video for the Package stage
A
Hello
and
welcome
to
the
kickoff
video
for
the
package
stage
at
gitlab.
This
is
for
milestone,
13.4,
which
is
scheduled
for
release
on
september
22nd
2020.,
I'm
here
with
ian
who's,
our
senior
product
designer
for
the
stage,
and
today
we're
going
to
be
walking
through
what
we're
working
on
in
terms
of
the
validation
track,
design,
build
track
and
then
maybe
we'll
just
close
with
some
things
we're
excited
about
ian.
Do
you
want
to
talk
about
a
couple
of
things
that
we're
working
on
on
the
validation
track?.
B
B
B
Yes,
we
did
an
unmoderated
solution,
validation
test
for
the
cleanup
policies
for
image
tags.
This
was
something
that
was
really
special
to
me.
We
put
out
the
mvc.
We
got
some
feedback
from
our
users
that
the
forum
and
mechanics
wasn't
very
clear.
So
we
did
a
redesign
and
sent
it
back
out
to
our
customers.
Asking
does
this
now
make
sense?
Do
you
understand
what
information
is
being
displayed
and
how
it
will
impact
this
automatic
process?
B
A
Cool
yeah,
I
like
it
much
better.
Look
I
really
like
how
we
made
the
regex
into
a
single
line.
Instead
of
that
big
box,
I
think
that's
much
more
clear
and,
and
then
the
copy
is
all
super
tight.
It
looks
great,
okay,
another
design
issue.
We
were
talking
a
lot
this
kickoff,
but
do
you
want
to
talk
through
this
issue.
B
For
sure,
very
related
to
the
cleanup
policies
we
were
just
looking
at
we've
heard
a
lot
from
our
users
and
our
customers
that
this
really
helped
them
manage
their
storage
costs,
and
we
want
to
take
those
learnings
related
to
the
container
registry
and
move
them
over
to
the
package
registry.
Help
people
that
are
producing
a
lot
of
custom
packages
over
a
large
number
of
teams
and
organizations
manage
those
packages
that
aren't
getting
used
anymore
in
an
efficient
and
automatic
way.
A
B
This
one
is
a
really
little
ui
update.
What
we
did
is
we
have
another
versions:
tab
in
the
package
detail
view
that
lets
you
see
other
versions
of
a
package
you're
looking
at
we
copied
over
the
list
view
that
we
have
in
other
parts
of
the
product
and
there's
a
lot
of
duplicated
data.
Specifically,
we
use
the
name
every
single
line
and
that
doesn't
really
help
anyone.
A
Well,
I'm
looking
forward
to
that
one
too.
Okay,
I
could
take
the
next
issue,
so
this
one,
the
dependency
proxy
right
now
currently
works
with
the
container
registry.
It
allows
you
to
pull
to
proxy
and
cache
images
that
are
hosted
on
docker
hub.
So
if
docker
hub
goes
down,
the
image
is
already
in
the
cache.
A
You
don't
have
to
worry
about
your
pipeline,
not
running,
and
it
also
run
faster
because
it's
cached
the
issue
is
that
up
until
hopefully
the
end
of
this
milestone,
you
haven't
been
able
to
use
it
with
private
projects,
so
we're
adding
in
authentication
so
that
if
you
have
a
private
project
which
is
very
common
on
git
lab
you'd
be
able
to
use
the
dependency
proxy.
So
I'm
really.
B
A
The
other
thing-
and
maybe
you
can
see
a
theme
developing
here-
we're
really
trying
to
work
on
storage
management
across
the
stage.
So
I
mentioned
that
we're
doing
cleanup
policies
for
tags
and
packages,
we're
also
going
to
be
giving
you
more
options
to
just
delete
packages
from
the
package
registry
right
now.
You
cannot
delete
packages
from
the
group
level
view
so
we'll
be
just
adding
in
that
functionality
in
the
next
milestone.
B
A
Cool
yeah-
and
this
is
part
of
an
overall
ui
polish
epic,
that
we're
working
on
that
you
can
check
out
the
details.
If
you
click
into
this
issue,
I'm
just
going
to
move
you
over
to
the
left
side.
Here
you
can
see
if
you,
if
you
follow
into
this
epic,
there's
a
bunch
of
issues
there.
So,
if
you're
interested
in
contributing
it's
a
good
option,
there's
a
lot
of
work
in
there.
A
B
This
one
is
mostly
to
try
to
tackle
some
tech
that
we
have
on
the
front
end.
Moving
from
some
of
the
custom,
css
and
custom
components
that
we've
created
in
the
package
ui
and
move
it
over
into
more
standard
uis
and
get
it
to
be
more
reflective
of
pajamas,
so
that
the
code
on
the
front
end
and
how
it
feels
and
interacts
is
all
in
alignment
with
the
rest
of
gitlab.
So
we
feel
like
a
really
included
feature.