►
From YouTube: GitLab 15.8 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
Manager
of
the
global
search
team
at
B
flat
today,
I'm
going
to
talk
about
our
15a
release
planning.
So,
first
of
all,
I
want
to
mention
that
we'll
have
reduced
capacity
in
the
next
release
cycle
because
of
holiday
season.
Our
main
focus
will
be
finished.
The
ongoing
work
that
we
started
from
previous
releases,
the
first
feature
I'm
going
to
talk,
is
about
improving
user
search.
A
We
have
created
the
user
index
and
also
added
to
the
data
migrations
to
like
fill
the
user
data
in
the
elastic
cluster
in
private
releases
in
15a,
we'll
focus
on
finishing
the
last
major
piece
of
the
work
and
that's
checked
by
this
Advanced
user
search
issue,
and
the
next
feature
that
I'm
going
to
talk
about
is
to
add
a
filter,
a
programming
languages
in
the
code
search
result
page
extract
by
this
I
think
we
have
finished
the
patent
work
in
private
release
and
now
it's
behind
the
feature
flag.
A
The
next
feature
I'm
going
to
talk
about,
is
to
provide
an
indicator
in
the
code
search
result
when
there
are
multiple
matches
within
the
file,
and
so
this
is
based
on
our
user
feedback.
So
we
have
a
issue:
that's
when
there
are
multiple
matches
in
the
search
results
within
a
file.
We
only
show
the
first
match,
so
this
is
two
people
indicators
that
we
tell
the
users.
Okay,
there
are
multiple
matches
in
one
file.
A
The
Phantom
work
may
have
to
wait
until
we
have
proper
ux
designs,
but
it
will
start
the
backend
work
first
in
58..
The
next
feature
is
to
support
group
level
V
key
search.
We
had
a
proposal
for
the
solution
in
1507
and
we
will
start
our
event
work
in
15a.
A
A
The
next
part
is
the
maintenance
work
that
we
plan
for
15a.
The
first
we'll
continue
addressing
the
other
budgets,
while
violation
related
issues.
We
believe
the
user
search
Improvement
will
help
on
this
overall
effort
and
also
we
also
do
some
improvement
for
our
code.
Wiki
indexing
SLI,
the
next
maintenance
work
we
are
going
to
do
is
to
get
one
gen,
Ruby
3
compatibility
if
we
resolved-
and
this
is
part
of
our
overall
2b3
upgrade
effort-
we'll
also
continue
our
code
search
or
advanced
search
and
code
react.
A
Texture
will
be
continue.
Working
on
this
issue,
which
is
moved
search,
controller
to
using
present
also
we'll
continue
optimizing
group
level,
searches
for
Wiki
and
code.
This
is
part
of
our
overall
optimizing
group
level
searches.
A
The
last
maintenance
work
is
to
draw
out
the
live
index,
lifecycle,
management,
work,
and
now
this
feature
is
behind
the
feature
flag,
we'll
plan
to
start
the
job
in
the
next
release.
For
the
pack
fixes
the
first
one
will
have
some
issue
to
address
in
our
new
and
test
execution.
I
will
also
address
a
few
security
issues
in
the
next
release,
because
our
direct
Defender
need
will
be
helping
with
other
teams
for
the
next
release.
So
we
have
to
see
what
we
can
do
for
ux
design.
A
A
Okay,
that's
all
I
have
today
for
our
50a
planning.
Thank
you
for
watching.