►
From YouTube: UX scorecard: Upgrading GitLab Omnibus
A
Hi
I'm
Sanjay
I'm
a
product
designer
for
the
Geo
and
the
distribution
team.
Today,
I
would
like
to
walk
you
through
the
user
experience
of
upgrading
design
omniverse
to
specify
this
task
when
system
administrator
noticed
adds
that
your
lab
instance
is
updated.
They
want
to
update
to
the
latest
version
so
that
they
can
enjoy
the
new
features
and
also
enjoy
a
very
stable
gillip
experience.
A
So
this
is
the
overview
of
fitness
journey.
So,
if
I
can
just
move
to
this
mural
board,
there
were
two
different
steps
in
general,
the
first
that
was
to
check
the
version
and
the
general
flow
after
checking,
the
version
was
to
come
back
to
the
update,
landing,
page
and
figure
out
like
which
is
the
right
package
to
choose,
and
then
they
are
working
on
the
comment
line
in
their
face,
and
there
were
two
different
ways
of
doing
this.
A
A
So
just
for
curiosity,
I
try
to
Google
online,
like
you
lab,
upgrade
or
Gil
I'm
up
the
and
I
found
a
very
popular
post
in
Stack
Overflow,
which
was
asked
like
six
years
ago
and
still
active
like
a
month
ago,
and
there
were
a
lot
of
piece
and
seems
like
they
kind
of
want
to
check
this
version
on
this
page.
It
is
under
the
top
navigation
and
first
level
menu
is
like
health,
so
I
think
maybe
it's
easier
to
show
you
this.
A
So
this
is
my
test
instance
and
there
you'd
like
to
check
the
version
here
in
the
help
and
I
think
for
okay.
So
this
is
the
latest
version,
so
there
is
no
label
at
the
moment.
But
if
this
is
like
outdated
version,
then
I
can
see
some
label
like
yellow,
like
update,
available
or
I
need
to
update,
like
ASAP.
A
So
if
I
come
back
to
the
tack,
so
we're
way
to
check
the
version
so
I
couldn't
capture
the
major
upgrading
journey,
but
I
could
capture
the
minor
version
update
and
it
was
on
my
GC
ppm
and
it
was
just
really
minor.
I
think
it
was
a
patch
update
and
it
took
me
like
around
4
minutes,
but
I
think
around
1
minute.
It's
just
like
exploring
the
UI
and
check
the
update
landing
page
and
starting
from
the
back
up
and
then
I
moved
to
updating
Gila.
A
A
Upgrading
and
I
found
a
couple
of
questions
from
the
left
forum,
also
because
it
seems
like
user
was
a
bit
confused,
actually
more
than
50
results,
and
then
they
didn't
understand
like
because
we
don't
show
this
information
on
the
UI
and
also
on
the
CLI,
so
they
might
be
confused.
It
was
understandable
and
another
sneak
peek
was
I,
think
we're
using
two
different
terminology,
sometimes
because
on
our
landing
page.
A
So,
for
example,
here
it's
about
update,
Gil
lab
every
information
could
be
found
here
and
we're
using
upstate
get
lab
for
version
update,
but
what
I
could
notice?
It's
like.
We
are
using
the
terminology,
upgrading
things
on
the
c
ii
ii
ii
ii
changes,
so
it
might
be
a
bit
confusing
for
user,
because
if
they
successfully
run
the
comment
and
then
update
it
or
upgraded
it
and
then
they'll
see
like
upgrade
completes
is
a
bit
problematic
when
they
need
to
check
the
documentation
or
they
need
to
explore
this
about
gillip
comm.
A
A
So,
in
conclusion,
based
upon
our
grading
rubric
system,
I
consider
this
experience
as
the
plus,
which
includes
some
unnecessary
steps
with
average
complexity.
I
think
this
was
because
of
the
major
upgrades
not
about
the
minor
version
update
the
approximate
upgrading
time,
for
only
us
was
around
four
minutes,
which
was
quite
nice,
but
I
think
it's
still
difficult
to
understand
like
how
many
version
I'm
actually
behind
from
the
latest
version,
and
maybe
it's
better
to
keep
some
more
guidance
for
okay.