►
From YouTube: GitLab 13.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
Hello,
I'm
tim,
I'm
the
pm
for
the
package
stage
at
gitlab
and
today,
I'm
with
ian
our
ux
designer
hello
and
today
we're
going
to
be
talking
about
some
features.
We're
really
excited
about
for
the
upcoming
milestone,
13.5.
A
So
thinking
about
themes,
we're
really
focusing
on
the
cleanup
policy
for
tags,
resolving
some
critical
bugs
with
the
package
industry
and
we're
also
preparing
for
to
break
ground
and
really
improve
the
dependency
policy
so
on
the
validation
track.
One
thing
that
we're
in
terms
of
problem
validation,
we're
going
to
be
interviewing
folks
in
the
community
about
how
can
we
help
you
find
troubleshoot
and
remove
packages
quickly?
A
B
This
is
something
that
will
help
our
users
and
our
admins,
who
again
are
managing
a
lot
of
packages
to
be
able
to
decide
whether
their
organization
can
have
duplicate
packages
inside
of
their
registry,
that
fit
some
user
user
stories
and
also
allowing
them
the
ability
to
reject
them
so
that
each
package
either
has
to
be
a
new
version
or
given
a
unique
name,
etc.
I
think
this
is
going
to
be
really
exciting
to
help
those
users.
It's
also
a
chance
for
us
to
review
those
kind
of
admin,
level,
settings
ui
and
refine
it.
B
B
This
one
I'm
really
excited
about.
We
did
the
solution.
Validation
recently
about
the
dependency
proxy
and
one
of
the
first
things
I
want
to
get
going
is
creating
the
ui
to
help
users
understand
what
is
happening
with
their
dependency
proxy.
Specifically,
what
packages
have
been
cached
and
been
pulled?
This
will
help
business,
we're
developing
a
new
feature
for
both
customers
and
ourselves
internally
to
understand
what's
being
cached
and
whenever
there's
a
bug
or
some
unknown
or
unsure
experience
happens,
we
can
go
and
look
and
see
what's
been
happening.
A
That's
cool,
so
this
will
really
expand
the
package
registry
from
being
just
hosted,
packages
to
things
that
are
hosted
outside
of
gitlab
like
mpmjs
or
maven
central,
or
something
like
that.
B
A
Well,
thanks,
I
think
I
can
move
on
to
the
build
tracks.
We
have
a
few
issues
here,
I'll
try
to
cover
them
quickly
if
you're
familiar
with
the
cleanup
policy
for
tags.
This
allows
you
to
programmatically
delete
your
image
tags
from
the
container
registry,
but
right
now
it's
limited
to
projects
created
after
milestone,
12.8,
that's
a
problem
for
a
lot
of
our
legacy,
customers
that
have
projects
that
go
back
several
years.
A
So
what
we're
going
to
be
doing
is
a
rolling
a
phase
rollout
of
the
policy,
we'll
start
internally
with
some
large
lab
projects
and
then
we'll
work
with
some
beta
customers,
and
our
goal
will
be
probably
in
13
6
to
have
the
feature
broadly
available
for
all
projects
we
just
need
to
because
we're
dealing
with
petabytes
of
scale
when
it
comes
to
the
container
registry.
A
We
need
to
roll
this
feature
out,
smartly,
to
make
sure
that
we
don't
cause
any
production
issues
for
dot
com
the
next,
but
the
next
bug
we're
talking
about
is
the
container
registry
policy,
not
removing
images,
so
some
users
have
reported
on.com
that
images
are
not
being
deleted,
as
stated
in
the
policy,
so
we'll
need
to
work
through
this
and
ensure
that
images
are
deleted.
As
expected,
we
really
want
to
make
sure
that
people
have
programmatic
tools
for
expiring,
old,
unused
images.
A
The
next
one
was
a
bug
that
was
recently
brought
to
our
attention
where
the
package
details
are
not
updating
when
the
same
version
is
deployed
from
a
different
branch.
So
this
is
kind
of
a
nasty
bug.
If
you're,
if
you're
using
the
package
registry
heavily,
we
want
to
show
we
want
to
ensure
that
your
pipeline
and
branch
details
are
correctly
displayed,
regardless
of
which
branch
it
was
displayed
from.
A
So
we
need
to
we'll
be
addressing
this
in
13.5
as
well,
two
more
and
they're
very
similar
we're
having
problems
with
nuget
packages
with
extended
versions
that
are
failing
to
upload.
So,
if
you
put
in
a
version
like
this
1.1.1.1,
it
will
fail.
We
need
to
make
sure
that
doesn't
happen
and
if
there
is
a
reason
that
it
should
fail
that
it
fails
gracefully
so
we'll
be
addressing
this
in
13.5
as
well,
and
then
a
a
similar
issue
we're
having
problems
with
python
packages.
A
If
the
package
has
a
period
in
its
name,
so
again,
we
need
to
make
sure
that
either
allow
the
behavior
or,
if
it
fails
to
make
sure
that
it
fails
gracefully.
So
that
was
great
thanks
ian.
For
that
anything
else,
you
want
to
add
to
that
before
we
close.
B
No,
I
am
really
excited
for
this
milestone
because
we're
going
to
take
a
moment
and
really
focus
on
refining
the
experience
and
make
sure
that
your
registries
are
stable
and
efficient
and
work
like
you
expected
them,
so
you
don't
have
to
think
about
them.
They
are
just
always
going
to
work.
I'm
really
excited
to
see
us
work
on
that.
A
B
A
Thanks
ian
thanks
everyone,
and
if
you
have
any
questions,
you
could
always
reach
out
to
me
at
t
rizzi
at
gitlab,
and
look
forward
to
talking
to
you
in
the
issues.