►
From YouTube: GitLab 15.4 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
B
I
think
that's
easy,
so
we
expect
to
finish
the
back
end
work
for
this
feature
in
15-3.
In
15-4,
we
plan
to
roll
the
back-end
changes
out
through
a
feature
flag
and
we
will
start
the
front
end
development.
We're
really
excited
to
roll.
This
feature
out.
I
think
it's
going
to
add
a
lot
of
usefulness
to
the
code
search
we'll
have
the
ability
to
filter
by
language
and
also
show
how
many
results
are
matching
each
language
type.
So
this
will
be
a
really
fun
one.
Once
available.
A
The
next
feature
we
consider
to
work
on
is
add
labels
as
a
facet
on
the
search
result
page,
I
will
give
it
to
dimitri
who
is
going
to
share
more
information
about
this
exciting
feature.
C
A
A
So
so
far
we
covered
all
the
features
that
that
we
plan
for
154.
The
next
theme
is
about
maintenance.
Maintenance
is
about
to
improve
our
overall
stability
performance
of
the
feature,
so
in
154
the
first
part
is
to
continue
improving
the
global
search
error.
Budget
john
has
more
information
to
share
about
this.
This
work.
D
Thanks,
suzy,
yeah,
so
what
we
do
at
gitlab
is
we
keep
track
of
the
performance
of
search
across
the
board
with
this
work,
what
we
want
to
start
doing
is
have
fine
grained
insights
on
the
performance
of
different
types
of
searches.
So
if
it's
a
basic
search,
it's
going
to
go
down
a
different
technology
stack
than
advanced
search
and
what
we
hope
to
gain
by
this
by
having
fine,
grained
insights
on
search
performance
is,
we
can
identify
bottlenecks
and
make
search
more
efficient
and
faster.
A
B
Thanks
susie,
so
the
first
item
we're
going
to
work
on
is
to
continue
improving
the
elastic
search,
indexer
logging
and
traceability.
We've
begun
this
work
in
15-3,
which
started
with
documenting
how
errors
can
be
viewed
and
we've
created
some
additional
logging
improvement
issues
to
work
on
as
part
of
this.
So
that
will
be
what
we
work
on
for
15,
for
the
next
item
is
to
create
run
books
for
lost
updates.
There
is
not
currently
like
a
right
ahead.
Log
solution
implemented
yet,
but
we
need
to
prepare
like
alternative
disaster
recovery
strategies.
A
Yeah,
thank
you,
sir
other
than
the
features
and
the
maintenance
we
are
going
to
continue
address
and
the
higher
priority
backs.
In
154,
we
planned
to
work
on
addressing
one
content
issue
where
the
social
health
page
can
crash.
If
the
files
have
long
lines
in
a
search
result.
A
The
last
part
is
about
ux
design.
Our
ux
designer
nick's
up
here
today,
but
john,
is
quite
excited
about
this
work.
I
have
john
to
talk
about
it
on
nick
yeah.
D
Thanks
easy
yeah,
while
nick
can
go
through
a
lot
of
the
details
here,
I'll
keep
things
pretty
high
level.
These
are
items
that
we're
exploring
to
make
the
general
experience
of
searching
at
get
lab
better
for
users.
D
So
going
down
the
list
here,
one
of
the
things
is
making
the
navbar
search
be
a
little
bit
more
intuitive
by
providing
intuitive
hints
on
what
can
be
searched,
and
we're
excited
about
that
because
I
think
it'll
make
the
different
ways
of
search
a
little
bit
more
apparent
and
then,
secondly,
to
improve
looking
into
the
ways
that
we
can
change
the
contrast
of
the
search
box
just
to
make
it
more
pleasant
on
the
eyes
and
then,
lastly,
what
we're
exploring
is
indexing
users
in
elasticsearch
to
make
users
search
faster,
but
also
adding
the
ability
or
exploring
the
ability
to
search
users
by
different
attributes
instead
of
just
username.
D
So
all
these
things
were
researching
and
looking
into
and
we're
excited
to
see
what
type
of
insights
come
out
of
that.
Thank
you.
A
John,
thank
you,
everyone.
We
are
very
excited
for
our
milestone.