►
From YouTube: GitLab 14.5 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
the
first
few
items
that
we
have
planned.
We
have
several
security
fixes
which
will
be
announced
in
the
net
in
the
next
release.
We
also
have
several
performance
improvements
that
we're
making,
as
we've
seen,
increased
scale
and
adoption
of
the
dependence
dependency
proxy
and
package
registry.
We've
had
to
make
more
schedule
time
for
more
performance
improvements,
and
you
could
check
out
this
milestone,
planning
issue
and
read
about
how
we're
planning
these
and
what
more
details
about
these
issues
as
needed.
A
But
we
do
also
have
a
few
exciting
features
and
some
upcoming
design
and
research
that
we're
working
on
as
well.
So
the
first
issue
that
I
wanted
to
highlight,
if
you've
been
using
the
package
registry
for
your
npm
packages,
you
may
have
noticed
in
the
past
that
we
don't
support
having
all
of
the
metadata
that
comes
along
in
the
package.json
file.
A
So
we
support
basic
metadata
like
the
package
name
and
some
other
fields,
but
there
are
a
lot
of
fields
in
here
that
are
specifically
missing
and
really
until
this
data
is
available
in
the
api
and
eventually
in
the
user
interface
as
well.
It's
hard
for
us
to
be
the
single
source
of
truth
for
your
package
registry.
B
Cool
hi,
I'm
katie
product
designer,
as
tim
mentioned,
new
hire
new
to
the
package
group.
So
I'm
gonna
talk
about
the
adding
a
user
interface
to
the
dependency
proxy.
B
The
customer
impact
here
is
to
have
the
ui
make
it
clear
that
the
feature
is
working
expected
as
expected
and
that
you
can
see
what's
cached
in
the
dependency
proxy
and
tim
is
going
to
show
me
the
figma
file,
so
basically
as
a
first
iteration
we're
going
to
display
a
list
of
tags
and
when
the
tag
was
last
cached-
and
this
is
a
first
step
and
if
you're
interested
in
this
feature
or
wanting
to
learn
more
about
it,
we
want
to
extend
it
past
this
in
future
milestones.
B
So
we
would
love
to
chat
to
you
if
this
is
a
feature
that
you
think
would
be
useful
to
you
so
yeah
in
the
future.
We
would
like
to
be
able
to
provide
a
lot
more
rich
information,
but
I
think
that
this
is
a
great
first
step
to
add
a
ui
on
top
of
something
that
previously,
you
could
not
see
in
the
interface.
A
That's
true:
I've
heard
this
from
several
customers
that
this
is
something
that
they
have
no
way
of
knowing
right
now,
so
this
will
be
a
big
step
forward
in
in
terms
of
providing
this
information
thanks
for
working
on
that
design-
and
we
have
one
more
request-
I
think
katie,
do
you
want
to
talk
through
this
one.
B
Yeah,
so
we've
heard
from
a
lot
of
customers
that
managing
the
amount
of
package
files
and
the
storage
that
packages
can
take
up
is
quite
arduous
and
currently
it's
a
manual
task.
So
in
the
previous
milestone,
we
had
the
ability
to
talk
to
some
customers
about
what
their
needs
were
and
have
a
little
bit
of
an
idea
of
what
a
cleanup
policy
might
look
like
for
the
package
registry,
and
some
of
you
might
be
aware
of
the
cleanup
policy
for
the
container
registry.
B
So
this
is
a
similar
kind
of
idea,
currently
a
task
that
is
a
lot
of
manual
work
to
kind
of
clean
up
unused
artifacts
from
the
package
registry
and
the
this
issue
is
to
create
a
design
and
where
we
have
a
solution
for
that
to
kind
of
automate.
Some
of
this
manual
workflow
and
the
intention
is
we'll,
create
a
design
and
do
some
useful
testing
to
make
sure
that
it
addresses
the
need
so
similar
to
the
dependency
proxy.
B
If
this
is
something
that's
interesting
to
you,
please
reach
out
to
us
either
on
the
issue
or
to
either
of
us
directly,
because
we'd
love
to
talk
to
you
and
learn
more
about
your
needs.
For
this.
A
Great
yeah,
thanks
for
sharing
and
yeah,
we
look
forward
to
hearing
from
from
people
about
that
issue
and
everything
else
so
yeah,
I'm
really
excited
about
this
milestone
and
some
of
not
only
the
issues
that
we
spoke
about,
but
the
performance
gains
too
that
we'll
continue
to
make
for
all
of
our
features.
So
if
you
have
any
questions
reach
out
to
us
and
if
not
we'll
talk
to
you
in
issues,
thank
you.