►
From YouTube: GitLab 16.2 Kickoff - Global Search
Description
Planning issue https://gitlab.com/gitlab-org/search-team/team-tasks/-/issues/146
A
B
Yes,
hi
I'm
Susie
I'm
the
engineering
manager
of
the
global
search
team.
Today
I'm
going
to
work
with
Josh
to
introduce
our
planning
for
defax
62
release.
A
We
have
been
working
to
switch
over
to
a
new
code
search
solution
based
on
the
open
source
project,
and
we
are
well
underway
on
building
out
that
integration
and
support
right
now
our
focus
is
on
moving
towards
our
opt-in,
Beta
And.
There
are
a
couple
key
items
that
we
wanted
to
support.
To
do
that
number
one
is
I'm
going
to
go
ahead
and
add
a
private
project
support.
A
A
There's
a
number
of
other
items
that
also
go
into
the
opt-in
Beta
around
just
making
sure
we
handle
certain
events
within
the
product
life
cycle,
things
like
handling
project
deletion,
so
that
content
is
also
deleted
off
of
the
index
servers,
but
also,
of
course,
triggering
indexing
on
import
of
projects,
handling,
projecting
moves
and
transfers,
and
things
like
that.
So
all
help
us
make
sure
that
our
opt-in
beta
goes
smoothly
and
we
can
handle
the
various
life
cycle.
A
Experience
will
really
help
out
our
users
and
finding
what
they're,
looking
for
and
narrowing
down
that
list
more
quickly,
so
looking
forward
to
that,
we're
also
having
support
for
both
group
little
wikis
and
for
epics.
A
So
these
are
now
content
types
that
you
can
actually
search
for
within
Global,
search
and
last,
but
certainly
not
least,
we
are
working
to
hide
archive
projects
by
by
default,
and
so,
if
you
have
a
lot
of
archived
projects
within
your
organization
or
your
instance,
sometimes
these
can
be
returned
as
one
of
the
top
hits,
which
is
oftentimes,
not
what
you're
looking
for
and
so
by
having
these
by
default,
we
can
turn
the
content
that
is
more
likely
to
be
relevant
for
the
user
to
them
more
easily.
A
As
far
as
one
of
those
top
hits,
and
of
course
you
can
turn
this
back
on.
If
you
really
are
looking
for
that
archive
project,
so
looking
forward
to
offering
that
to
our
users
as
well,
and
so
with
that,
that
is
the
main
features.
We're
working
on
is
16.2
and
I'll
hand
it
over
to
CZ
to
take
us
through
the
maintenance
and
the
bugs.
B
Hi
everyone
in
the
162
release
we'll
continue
our
efforts
to
make
performance
improvements
and
to
address
the
bugs
that
discovered
any
other
product
for
the
maintenance.
We'll
continue
the
work
of
moving
the
project
data
to
a
separate
Index.
This
is
part
of
our
over
overall
effort
of
splitting
our
gigantic
index
into
smaller
pieces
to
help
improve
the
searching
performance.
B
Also,
we
have
heard
the
feedback
from
our
customers
about
our
data
and
acquisition
framework
we'll
make
improvements
of
this
data
migration
framework
by
adding
more
documentations
and
also
will
also
to
ens
how
we
run
the
migrations,
for
example,
we'll
be
checking
the
cluster
health
status
to
decide
when
we
want
to
write
this
job.
B
Also
in
section
2
will
also
be
cleaning
up
a
couple
of
feature
Flags
for
the
bug
fixes
we
plan
to
work
on.
First,
we
have
the
customer
feedback
on
some
of
the
rig
tasks
which
are
used
to
report.
The
cluster
and
index
status
will
be
improving
the
the
two
rig
tasks,
to
make
the
clear
and
reduce
the
confusion,
and
also
I
will
address
the
issue
that
that
we
found
in
the
area
area
of
switching
between
the
default
branches.
B
So
we'll
make
sure
the
index
will
happen
correctly
when
the
default
Branch
switched
other
than
that,
I
will
also
address
a
couple
of
issues
that
we
found
in
the
areas
of
permission
and
access
level
checks.
Those
are
the
bug
fixes
we
plan
for
the
coming
release.
I
think
that's
all
from
that
side.
A
Great
thanks
easy
and
thanks
again
for
all
your
great
work
in
planning
and
organizing
for
this
release,
so
appreciate
it,
and
thank
you
all
for
watching
and
we
are
excited
to
bring
these
teachers
to
you
and
improvements
and
we'll
talk
to
you
next
month
for
our
16.3
release.
Thank
you.
Everyone
thanks
easy
thank.