►
From YouTube: GitLab 15.1 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
So
the
first
one
that
I'd
like
to
mention
is
in
case
you
are
not
familiar.
We
are
in
the
process
of
migrating
the
getlap.com
container
registry
to
the
next
generation
registry,
which
will
have
improved
performance
in
the
future,
we'll
have
an
improved
ui
and
also
support
a
variety
of
new
features
like
signing
of
images
and
other
important
features.
A
A
A
So
we
have
seven
issues
open
for
this
milestone
to
ensure
that
gitlab
is
fips
compliant
on
the
package
stage
in
15.1
next
up,
I
wanted
to
highlight
two
bugs
so
this
one
here,
there's
an
there's:
a
new
version
of
pip
that's
been
released
and
the
get
lab
pipe
pi
repository
is
not
in
spec
with
the
new
version
of
pip,
which
will
as
of
june
it
we
will
be.
A
Basically
it
will
stop
working
unless
we
fix
this
bug,
so
there
should
be
no
disruption
for
you,
but
we
want
to
let
you
know
that
by
the
end
of
15
1,
we
will
be
compliant
with
the
new
version
of
pip
as
well,
and
I
was
mentioning
the
container
registry
rollout
well
as
part
of
that
there's
a
bug
where
we
are
only
showing
100
tags
per
image
in
the
ui.
It's
because
pagination
is
not
currently
supported
in
the
next
gen
container
registry.
So
this
bug
will
resolve
that.
A
Hopefully,
this
isn't
hitting
too
many
people
yet,
but
as
we
continue
to
migrate
to
the
the
new
registry,
this
bug
will
become
more
prevalent,
so
we're
making
sure
we
address
it
before
it
becomes
a
growing
problem
and
I
think
katie
do
you
want
to
talk
through
the
next
issue.
B
B
So
this
issue
allows
the
user
to
be
able
to
say
how
many
duplicate
assets
that
they
want
to
keep
and
rather
than
keeping
all
which
is
the
default,
they
can
choose
a
lower
number
and
hopefully
that
helps
manage
the
storage
cost
used
by
snapshots
and
pre-releases
in
gitlab.
B
Sure
so
this
issue
is
a
stretch
goal
for
15.1.
So
at
the
moment,
when
you're
looking
at
your
container
registry
list,
actually
only
if
you
search
the
name
of
the
image
repository,
do
you
return
any
results,
so
the
certain
parts
of
the
path
don't
work
with
the
filter.
We've
also
seen
in
customer
interviews
that
this
very
long
path
in
the
in
the
ui
can
be
sometimes
a
little
bit
hard
to
read.
B
B
So
in
order
to
determine
what
the
best
solution
to
this
problem
is
we're
actually
conducting
a
survey
at
the
moment,
and
this
survey
is
to
understand
how
customers
would
like
the
data
presented
on
the
front
end.
For
example,
should
we
trim
the
front
of
the
path
to
make
it
more
usable,
so
this
survey
is
out
now
and
when
we
get
the
responses
in
we'll
make
a
decision
about
how
to
improve
this
behavior.
B
Yeah,
so
we
are
starting
an
initiative
which
we're
calling
touchpoint
interviews
and
generally
when
we
do
user
research,
we
have
a
very
set
script
and
we
have
a
specific
thing
that
we
want
to
learn
about.
The
purpose
of
this
research
is
actually
to
have
a
slightly
over
like
a
slightly
more
informal
format,
where
we
just
love
to
talk
to
customers
and
understand
how
they're,
using
any
of
the
package
features
at
the
moment
to
understand.
For
example,
what
are
your
workflows?
What
are
your
pain
points?
B
What
are
the
questions
that
we
might
not
have
been
asking
in
research
to
this
point,
so,
if
you're
interested
in
participating,
please
please
reach
out,
because
we'd
love
to
talk
to
you.
A
I
agree
and
I'm
I'm
really
interested
in
learning
some
of
those
cross-stage
workflows
too
in
particular
how
people
are
using
package
with
a
secure
features
as
well
as
release.
I
see
a
lot
of
crossover
and
customer
calls
so
be
great
to
see
how
we
could
help
fill
in
the
gaps
to
improve
cross-state
usage
cool
well.
It
seems
like
a
very
exciting
milestone
for
us,
thanks
katie,
for
reviewing
that,
and
if
you
have
any
questions,
please
feel
free
to
reach
out
in
the
issues
and
thank
you
very
much.