►
From YouTube: GitLab 13.5 Kickoff - Enablement:Global Search
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
A
13.5,
so
we
have
recently
been
working
through
in
the
last
three
releases,
a
lot
of
performance
related
items,
just
trying
to
you
know,
get
our
page
load
times
down,
and
we
and
since
13-0
we've
made
an
80
improvement
to
what
the
average
time
is
to
load
the
search
result
page
and
so
with
that
we're
at
least
satisfied
for
now.
A
We'll
probably
continue
to
iterate
on
that,
but
our
focus
is
now
shifting
to
primarily
be
updating
the
ui
for
the
result
page
as
well
as
getting
into
some
of
the
rank
areas
that
we
can
do
to
actually
help
relevancy
for
search
improve.
A
So
looking
at
some
of
those
details,
the
this
is
the
overall
outlook
of
what
we're
trying
to
get
to.
This
is
very
different
from
the
search
result
page
that
we
have
today,
you'll
notice
that
there's
a
lot
of
facets
that
are
filters
that
are
located
here.
On
the
left
hand,
side,
there's
a
narrow
list
for
our
results,
and
this
allows
us
to
put
more
results
in
a
closer
amount
of
space,
we've
added,
more
content
to
them
as
well.
A
There
will
be
some
sort
options,
we're
going
to
start
looking
at
how
we
can
bring
together
a
lot
of
these
different
areas
into
an
all
result
and
then
allow
the
allow
your
user
to
actually
like
filter
down
from
that
and
the
key
intent
to
that
is
that
if
you,
if
you
do
a
search
today
and
you
default
to
a
tab-
that's
like
code,
but
what
you're
really
looking
for
is
an
issue
or
the
best
result
might
be
at
issues.
You
may
not
see
it.
You
may
not
actually
know
that.
A
That's
the
best
result,
so
it's
kind
of
hidden
and
so
in
this.
In
this
view,
you
would
actually
get
everything
back
with
the
highest
rank
things
at
the
top,
and
then
we
could
actually
allow
you
to
filter
down.
You
can
choose
what
you
want
to
kind
of
go
view.
If
you
want
to
see
something,
that's
code
related
issues,
merge
requests,
you
can
start
filtering
down
through
those
things
and
really
customize
the
experience
to
what
you're
actually
looking
for.
A
So
the
we're
going
to
be
iterating
through
this
approach
doing
small
pieces
of
this
at
a
time
each
release.
So
that
way
we
can
get
these
functionality
pieces
out
there
like
as
quickly
as
possible.
You
don't
have
to
like
wait
several
months
to
get.
You
know
the
whole
completed
final
picture.
A
A
Allow
you
to
choose
between
merged
or
open
and
then
underneath
confidentiality,
you'll,
be
able
to
sort
or
not
swap
you'll,
be
able
to
select
things
that
only
view
that
are
confidential
or
not
confidential,
and
then
the
next
item
that
we're
actually
looking
at
is
the
sort
so
sort
will
at
least
be
available
in
this
is
the
finished
product
version
of
that,
but
sort
will
be
available
in
merge
request
issues.
A
We
are
now
actually
trying
to
add
a
new
scope
as
well,
that
will
be
epics
and
we
want
to
add
sort
to
that
as
well,
but
we
will
eventually
be
adding
sword
across
all
of
the
scopes
and
then
we'll
have
it
brought
back
into
this
total
page
design.
Once
we
have
those
capabilities
built
out
so
going
into
the
next
piece
is
ranking,
so
we
we
actually
do
look
at
trying
to
improve
rank
every
iteration.
A
But
this
is
a
big
milestone.
Change.
We
are
looking
to
change
our
default
operator
from
and
to
or
and
what
this
means
is,
that
you're
going
to
get
a
lot
more
results
to
come
back
on
any
given
search
and
that's
ultimately,
we
we
think
that's
going
to
be
a
good
thing,
but
we're
going
to
test
this.
We
think
it's
a
good
thing,
because,
if
you're
trying
to
look
for
something
you're
never
going
to
find
it
if
it
doesn't
come
back
as
a
result.
A
So
if
we
can
give
you
your
operator,
it
should
have
a
better
chance
of
coming
back
and
then
to
accommodate
that
we're.
Also,
looking
at
some
changes
to
one
of
the
levers
that
exists
inside
of
elasticsearch,
that's
called
minimum
should
match
so
minimum
shift
match
looks
at
all
the
terms
that
you
have
in
your
query
and
especially
for
longer
queries.
A
This
is
the
kind
of
core
component
elasticsearch
allows
you
to
make
that
type
of
change,
and
so
we're
going
to
essentially
start
with
tomorrow,
saying,
let's
make
our
rank
better
than
what
it
is
today
and
let's
come
back
and
find
better
ways
to
iterate
on
that
as
we
go
forward,
these
changes
are
not
very
difficult
to
go
in
and
actually
make
it's
just
about
the
testing
to
make
sure
they're
actually
making
an
overall
improvement,
and
with
that
there's
one
more
piece
that
we
have
that's
that's
coming.