►
From YouTube: GitLab 13.0 Kickoff - Package:Package
A
Hello,
I'm
Tim
I'm,
the
p.m.
here
at
kid
lab
for
the
package
stage
and
today
I'd
like
to
talk
to
you
about
our
upcoming
milestone,
13.0,
which
is
scheduled
for
release
on
May
22nd
of
2020.
Okay.
So
we'll
talk
through
a
few
features
on
this
list
today
on
the
kickoff
page,
the
first
one
is
I'd
like
to
talk
to
give
you
the
ability
to
use,
deploy
tokens
to
read
and
write
to
the
package
registry.
This
builds
off
an
issue
that
we
launched
last
month's
month,
which
allowed
you
to
read
and
write
to
the
container
registry.
A
So
this
will
allow
you
to
use
deploy
tokens
to
write
to
any
of
our
existing
or
future
package
manager
formats
like
MPM
or
maven.
So
by
the
end
of
this
milestone,
deploy
tokens
will
have
the
following
scopes:
they'll
have
read:
repository,
read
registry
write
registry,
read
package
registry,
write
package
registry,
so
looking
forward
to
getting
that
feature
into
your
hands.
The
next
one
is
related
to
our
image,
expiration
policies.
A
So
this
will
allow
you
to
define
an
image
retention
policy
to
ensure
that
you
never
accidentally
delete
a
master
or
release
image
or
whatever
you're,
calling
those
really
important
images
that
you
want
to
make
sure
I
never
get
to
lead
it.
So
this
will
be
an
extension
of
the
existing
expiration
policies
which
you
can
access
using
the
github
API
or
you
can
find
it
in
your
settings
and
see
ICG.
A
Ok,
the
next
one
I'll
scroll
up
here,
looks
like
I'm
editing
this.
The
next
one
is
using
the
the
pack
of
registry
UI
to
understand
how
a
package
has
changed
from
version
to
version.
You
best
show
what
we're
trying
to
address
here
currently
in
the
user
interface.
If
I
have
all
of
these
packages
are
named
the
same
thing
and
they're
all
tied
to
different
versions.
It's
very
hard
I
have
you
know
something
like
40
versions
here,
it's
it's!
A
A
So
what
this
will
do
this
issue
will
take
care
of
is
basically
add
support
for
additional
metadata
for
NuGet
packages.
I'm
really
excited
to
get
this
feature
out.
We've
seen
a
few
issues
in
the
community
come
up
to
address
this.
Ok
and
finally,
we
have
an
investigation
issue
which
normally
I
wouldn't
bring
up
on
this
call,
but
I'm
really
excited
about
it.
A
So
we
announced
at
the
end
of
March
that
we
were
moving,
that
gabab
is
moving
18
different
features
from
the
Enterprise
Edition
to
the
core,
and
one
of
those
is
the
core
package
registry,
offering
so
being
able
to
authenticate
setup,
get
lab
as
a
remote
and
publish
and
share
packages.
That's
all
moving
to
core
so
but
before
we
do
that,
we
need
to
investigate
how
we
could
possibly
move
that
code.
Where
are
there
any
risks?
What
are
the
other
implications?
A
So
so
this
issue
is
an
investigation,
but
we
expect
to
be
prioritizing
the
work
of
actually
moving
it
to
core.
Probably
a
milestone:
13.1,
okay!
Well,
that's
it
for
all
the
issues
today,
looking
forward
to
another
great
milestone
and
in
the
meantime,
if
you
have
any
questions-
or
you
just
want
to
talk
through
some
use
cases
or
you're
wondering
how
you
can
best
contribute,
feel
free
to
reach
out
to
me
at
tier
Izzie
at
lab,
comm
and
I'd
be
happy
to
talk
to
you.
Thank
you
very
much.