►
From YouTube: GitLab 15.3 Kickoff - Package:Package
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
I'm
tim
from
the
pm
for
the
package
stage
and
today
I
wanted
to
highlight
a
few
of
the
exciting
features
that
we
have
planned
for
milestone
15.3,
so
the
package
group
works
on
the
container
registry,
the
dependency
proxy
and
the
package
registry
and
for
milestone
153.
There
are
a
few
issues
in
each
that
I'd
like
to
highlight
to
start
I'd
like
to
highlight
a
performance
improvement
that
we're
making
to
the
container
registry
cleanup
policies.
A
This
takes
advantage
of
the
new
version
of
the
container
registry
that
has
been
released
on
gitlab.com
and
should
we
should
see
performance
improvements
of
200x
plus
once
this
epic
is
resolved,
we
are
hoping
for
fifteen
three,
but
it
might
spill
into
fifteen
four.
A
We
also
have
a
couple
of
settings
improvements
that
we're
making
both
to
the
project
level
and
the
group
level
for
the
package
stage.
So
to
start
with
the
project
level.
Here
we
see
right
now.
If
we
navigate
to
the
page,
we
can
see
cleanup
policies
for
the
container
registry,
but
since
we're
adding
in
cleanup
policies
for
the
package
registry
as
well,
we
wanted
to
make
this
page
a
little
bit
more
useful.
A
A
Also
for
the
for
the
group
settings
we'll
be
making
a
change
as
well,
so
for
the
package
registry
you
can
choose
whether
or
not
you
allow
or
disallow
duplicate
uploads
for
maven
and
generic
packages
right
now.
This
is
what
the
layout
looks
like.
It
takes
up
a
decent
amount
of
space.
So,
along
with
the
previous
issue,
we're
moving
to
a
side-by-side
layout,
we're
doing
something
similar
here
so
for
maven
you
can
say,
allow
or
disallow
duplicates
and
then
you
can
enter
any
exceptions
in.
A
A
One
exciting
thing
is
that,
with
the
performance
improvements
that
I
mentioned
earlier,
we
should
see
orders
of
magnitude
fewer
of
these
errors
for
the
dependency
proxy.
We
have
a
bug
that
we're
hoping
to
resolve
where
you
cannot
use
project
access
tokens
to
pull
images
through
the
dependency
proxy.
A
This
has
affected
a
fair
amount
of
users
who
are
also
using
a
bot
user.
For
this
I'd
also
like
to
highlight
in
15.3
that
will
investigate
automated
package
imports
from
artifactory.
We've
had
a
few.
Quite
a
few
customers
recently
migrate
from
artifactory
to
gitlab
and
they
were
looking
for
an
easier
way
to
do
it
than
writing
their
own
scripts.
So
the
goal
of
this
issue
will
be
to
investigate
how
to
make
this
as
easy
as
possible
for
our
customers.