►
From YouTube: Configure Roadmap 2021.02
Description
Provide feedback in: https://gitlab.com/gitlab-org/configure/general/-/issues/115
A
Hi,
my
name
is
victor,
I'm
the
product
manager
of
configure
and
this
video
is
to
discuss
a
little
bit
our
milestone,
our
roadmap.
Sorry,
it
was
the
idea
of
nicolas
that,
even
if
it's
hard
for
us
to
organize
sync
meetings
to
discuss
roadmap,
it
might
be
valuable
for
all
of
us.
If
there's
video,
at
least
that
fosters
the
discussion,
so
I'm
going
to
open
an
issue
we'll
link
this
video
in
that
issue
as
well
and
just
feel
free
to
provide
feedback.
A
But
let's
see
how
our
load
roadmap
looks
like
today,
we
didn't
had
such
a
discussion
for
quite
some
time.
I
think
the
last
one
we
had
in
was
in
december,
so
I
left
the
previous
table
and
created
a
new
one
as
well
to
be
able
to
compare
the
differences
so
clearly
we
are
moving
much
slower
than
we
wanted
to,
and
this
is
a
fact,
so
I
tried
to
adjust
our
plans
accordingly.
There
were
many
many
changes
in
the
past
months,
like
the
trial
from
state
management
ui.
A
A
A
That's
amazing,
but
I've
scheduled
it
for
1311
even
to
be
to
have
it
finished,
because
we
might
not
have
the
designs
ready
there
and
we
might
want
to
have
a
bit
of
a
discussion
around
it.
So
what
I
really
would
like
to
have
on
the
agent
size
actually
this
issue,
but
what
we
have
already
prepared
is
the
basic
insights
into
the
agent.
So
the
easing
details
page
and
that's
that
what
we
are
working,
what
we're
going
to
work
on?
That's
why
they're
in
single
column
here
then
the
work
continues
on
the
ci
tunnel.
A
A
A
I
presume
that
we
might
be
able
to
ship
the
module
registry
in
three
milestones.
This
is
pretty
long
time
frame.
I
think
for
such
a
feature
and
there's
an
ongoing
research
discussion
now,
with
marshall
and
mikhail,
mostly
about
the
auto
labeling
feature
of
the
agent,
and
that
would
be
the
next
topic.
I
would
like
to
work
us
on
and
again
we
are
just
continuing
with
the
high
value
secrets,
management
features
and
starting
on
the
improved
traffic
merge
request
experience.
A
A
A
A
A
We
can
run
even
internal
cause
with
orit
who
manages
the
releases,
because
this
is
strongly
related
to
releases,
but
this
is
what
I
would
like
us
to
focus
on.
First,
the
only
difference
between
releases
and
deployments
might
be
that
releases
more
from
the
manager
point
of
view,
while
deployment
is
from
the
developer's
point
of
view,
and
we
want
to
focus
on
the
developer
first.
A
How
do
you
know
who
uses
your
module
and
whether
you
are
whether
they
are
on
the
latest
version,
where
you
can
deprecate
an
old
version?
If
there's
a
security
problem
with
one
of
your
versions?
How
can
you
think
about
that?
This
came
up
at
a
few
customer
calls
and
seems
to
be
a
premium
or
ultimate
feature
around
the
module
registry,
so
once
we
are
done
with
the
basic
module
registry,
I
would
like
us
to
add
this
premium
feature
on
top
of
it.
This
will
require
design
work
as
well.