►
From YouTube: GitLab 15.4 Kickoff - Package
Description
Any thoughts or feedback, feel free to leave them in the planning issue! https://gitlab.com/gitlab-org/gitlab/-/issues/364438
A
Hi
team,
my
name
is
katie
and
I'm
the
product
designer
for
the
package
stage,
and
today
I'm
going
to
talk
a
little
bit
about
what
the
team
is
working
on
mazda
in
15.4,
and
so
as
with
the
last
couple
of
milestones,
our
number
one
goal
is
to
continue
the
really
amazing
work,
the
team's
doing
on
the
container
registry
migration,
and
so
the
migration
is
nearly
done.
This
milestone
will
be
focusing
on
scalability
performance
and
data
instrumentation.
A
So
why
is
this
work
on
the
container
industry?
Important?
Well,
the
migration
and
all
of
the
work
that
the
team's
doing
will
unblock
a
lot
of
features
and
functionalities
and
improvements
that
we
want
to
make
to
the
container
registry.
So
that's
super
exciting
and
in
terms
of
ui
changes,
we
also
are
moving
the
container
registry
cleanup
policies
to
a
single
page,
I'll,
just
show
what
that
looks
like
so,
basically
going
forward
when
you're
editing
or
setting
up
your
clean
up
policies
for
the
container
registry,
it
will
be
on
its
own
page.
A
A
So
this
issue
is
to
resolve
that
bug
from
the
back
end
perspective,
so
that
would
be
super
great
to
get
that
resolved
and
on
the
package
registry
side
again,
where
we're
kind
of
tidying
up
our
settings.
So
we're
also
tidying
up
the
package
duplicate
settings.
So
basically,
this
is
again
kind
of
like
a
foundational
issue.
We're
tidying
up
the
ui,
because
we
have
a
lot
of
exciting
improvements
coming
to
the
package
settings
and
we're
kind
of
keeping
things
tidy
before
we
add
to
them
so
yeah,
that's
pretty
exciting.
A
This
is
kind
of
continuing
work
that
has
been
happening
in
milestone,
15.3
and
other
things
of
note.
Another
thing
that
we
hear
a
lot
from
from
customers
is
they
want
if
a
package,
if
a
maven
package
doesn't
exist
within
gitlab,
it
would
be
great
if
gitlab
could
go
and
fetch
that
from
from
mainland
central,
we
have
this
feature
already
for
npm
and
pipe
packages,
so
we're
starting
implementation
for
this
maven
feature
as
well,
and
the
first
step
of
that
will
be
happening
this
milestone.
A
So
basically,
if
you
set
something
in
the
admin
area
of
gitlab
and
that
setting
is
able
to
be
shown
in
in
groups
and
projects,
for
example,
so
this
will
be
the
the
first
step
towards
that
maven
feature
and
we'll
be
working
on
that
maven
feature
for
all
of
this
quarter.
But
it's
super
exciting
to
get
started
on
that
and
make
the
first
step
towards
that.
A
Maven
package
forwarding
feature
another
thing
that
the
team's
working
on
is
we
hear
often
from
customers
that
they
might
have
their
packages
on,
for
example,
competitor
products,
but
they're
moving
into
gitlab.
They
want
to
consolidate
as
much
as
possible
in
in
gitlab,
because
that's
really
the
value
of
gitlab,
and
so
how
can
they
kind
of
automate
that
process
if
they
have
all
their
packages
on
a
competitive
product?
How
can
they
move
them
seamlessly
into
git
labs?
A
First
step
towards
a
feature
is
to
add
a
last
downloaded,
add
field
in
the
package
model.
So
what
does
that
mean
and
we're
going
to
track
when
a
package
was
last
downloaded
and
the
reason
is
as
we're
extending
our
package
cleanup
policies,
we
often
hear
that
people
want
to
be
able
to
set
cleanup
policies
on
whether
or
not
the
package
is
in
use.
A
So,
with
this
last
downloaded
app
field,
we'll
it
will
be
the
first
step
towards
allowing
people
to
set
package
cleanup
policies
based
off
of
the
package
usage,
which
I
think
would
be
a
super
exciting
feature
and,
and
we
have
a
couple
of
stretch
goals.
One
of
them
is
related
to
what
I
was
just
speaking
about.
So
we
also
may
be
able
to
surface
when
the
package
was
last
downloaded
in
the
ui.
A
That
just
depends
on
capacity,
that's
a
bit
of
a
stretch,
goal
and
and
in
terms
of
other
things
that
are
kind
of
worth,
highlighting.
We
also
continue
package
touchpoint
research.
So
what
that
means
is
myself
or
tim
the
pm
we're
always
looking
for
customers
who
are
using
either
the
package
registry
container
registry
or
dependency
proxy
and
we'd
love
to
just
have
a
one
hour
conversation
with
you.
A
It
would
be
very
informal
and
we
tried
to
do
three
of
these-
a
milestone
where
we
kind
of
just
learn
about
how
you're,
using
these
features
and
any
problems
that
you're,
having
any
things
that
you
wish
work
differently
and
understanding
your
workflows
and
the
purposes,
basically
to
kind
of
understand.
You
know
where
we
should
put
our
focus
and
if
there's
any
blind
spots
in
our
futures
that
we
need
to
know
about
so
yeah
there's
a
lot
of
things
going
on
as
usual,
it's
a
pretty
exciting
milestone
yeah.