►
From YouTube: GitLab Group Kickoffs - Package:Package Registry
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
Welcome
to
the
15.11
kickoff
for
the
package
registry
group,
my
name
is
Jackie
Porter
acting
PM
for
the
package
stage,
while
Tim
Rizzi
is
out
on
PTO.
The
package
registry
group
has
some
exciting
Investments
planned
in
15.11,
with
a
focus
on
supporting
artifactory
compete,
exciting
work
related
to
customer
bugs
for
our
highest
used
areas
like
npm,
Maven
and
terraform,
while
also
focusing
on
improving
the
package
metadata
generation
experience.
A
First
up,
we
have
the
work
to
help
your
journey
from
artifactory
to
gitlab,
we're
building
out
an
importer
to
support
nuget
package
migration.
This
feature
will
allow
you
to
easily
use
pipelines
to
migrate
nuget
packages
to
gitlab
efficiently.
Second,
we'll
start
a
handful
of
Maven
bugs
to
help
make
it
easier
for
you
to
use
Maven
packages.
First,
we'll
support
error,
handling
related
to
a
replication
lag
when
uploading.
The
shaw
second
will
improve
another
error
related
to
a
maven
race,
condition
related
to
a
different
action.
A
When
a
file
is
uploaded,
the
shot
is
rejected,
making
it
fairly
confusing
for
users.
The
third
Maven
Improvement,
we're
looking
at
making
is
to
improve
the
package
creation
race
condition.
So
hopefully,
this
will
help
make
Maven
package
experience
a
little
bit
easier
for
users.
Another
usability
Improvement
will
be
tackling
in
15.1.
11
is
to
improve
the
discoverability
of
settings
by
adding
a
link
from
the
package
registry
page
to
the
settings.
A
This
will
help
address
some
feedback
that
we
received
from
from
users,
making
it
even
easier
for
people
to
navigate
to
group
settings
from
the
package
registry
View.
Finally,
in
support
of
world-class
devsec
Ops,
we
are
working
on
making
the
package
registry
at
Best
in
Class
product
by
improving
the
reliability
of
the
package
registry
with
metadata
generation.
A
We
have
a
handful
of
steps
and
issues
scheduled
for
15
or
11
to
support
this,
which
include
creating
a
service
to
support
metadata
storage
and
optic
and
object.
Storage,
we'll
also
work
on
creating
a
background
worker
which
will
help
trigger
the
npm
metageneration
so
that
it's
happening
unbeknownst
to
users
and
then,
finally,
the
Regeneration
of
the
npm
metadata
when
certain
packages
occur,
like
package
creation
or
deletion
or
a
tag
is
created
or
deleted
or
updated.
For
example,
we
are
so
excited
for
this
Milestone.