►
From YouTube: 14.8 Monthly Release Kickoff (Public Livestream)
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
Second,
we're
going
to
focus
on
improving
key
workflow
usability
recall
last
year,
we're
focusing
on
usability
as
a
whole,
and
we
did
a
lot
what
we
learned
from
there
is
now
we
have
some
really
complex
and
elaborate
workflows
that
we
need
to
focus
on
to
drive
improvement.
Some
of
them
are
listed
here,
including
enterprise
planning,
workflows,
settings
and
navigation
and
others
and
third
extend
our
lead
in
ci.
Cd
ci
is
one
of
the
first
use
cases
that
users
experience
with
git
lab
and
we
see
there's
a
lot
more.
A
We
can
do
to
help
our
customers
and
users
on
that.
So
that's
what
we're
going
to
focus
on
in
fiscal
in
the
fiscal
23.
I
want
to
remind
everybody
that
we
do
plan
ambitiously,
which
means
whatever
we
share
today
can
and
is
subject
to
change.
So
please
don't
make
any
material
assumptions
for
for
buying
purposes
and
things
like
that.
As
we
share
this
roadmap
as
usual,
you
can
follow
along
and
contribute
with
us
on
direction.
A
Slash
kickoff
page,
you
will
see
all
the
issues,
epics,
videos
you
can
click
into
any
of
them
and
really
directly
start
interacting
with
the
engineers
and
product
managers
and
also
choose
to
contribute.
If
you
want
to
with
that,
let
me
talk
about
the
lay
of
the
land
today,
we'll
start
off
with
david
talking
about
the
dev
section
and
all
the
stages
in
there
followed
by
hillary.
Who
will
talk
about
the
secure
and
protect
stages.
A
B
Thank
you
noob,
and
let
me
get
my
browser
shared
okay,
so
as
a
new
mention
we're
going
to
dive
into
the
dev
section
as
a
first
step
here.
Let's
talk
about
the
themes
for
the
depth
section,
so
in
q1,
they're
going
to
be
focused
primarily
on
get
lab
hosted
first,
as
well
as
the
improved
key
workflow
usability
and
you'll,
see
that
as
we
walk
through
the
items
for
14.8.
B
However,
the
editor
team
is
working
on
a
couple
of
research
tasks
that
I
wanted
to
highlight
for
that,
I
think,
are
pretty
interesting,
so
the
first
one
is
they're,
looking
at
potentially
replacing
the
web
ide
with
a
client-only
version
of
vs
code.
What
this
will
allow
gitlab
users
to
experience,
is
exactly
what
they
would
experience.
They're
running
the
vs
code
as
the
desktop
app.
B
However,
this
would
be
I'll
be
running
within
our
application.
The
other
benefit
of
this
is
this
will
allow
us
to
enable
gitlab,
specific
extensions
that
relate
to
our
product,
to
give
an
even
better
experience
for
developers
developing
within
the
gitlab
application,
they're,
also
working
on
reducing
the
bundle
size
of
the
new
content
editor.
Today,
it's
a
rather
large
transfer
when
you
first
access
it
and
we
want
to
be
able
to
improve
that
usability
experience
and
have
that
load
much
faster
for
you,
so
we'll
be
focused
on
that
as
well.
B
Within
the
plan
stage,
they're
primarily
focused
again
on
the
reliability
and
availability.
However,
I
do
want
to
highlight
usability
improvement.
The
product
planning
team
is
looking
at
adding
additional
components
to
the
roadmap
view.
That's
there
today.
This
will
be
focused
on
giving
you
the
ability
to
not
look
at
just
issue
weights,
which
is
how
it
works
today,
but
give
the
ability
to
look
at
open
and
closed
issues.
B
The
managed
stage
is
focused
again
on
those
same
two
themes:
how
are
there
some
really
great
usability
improvements?
I
wanted
to
highlight
the
compliance
team
is
continuing
their
work
on
improvements
to
the
compliance
report
or
compliance
dashboard,
depending
which
name
you
notify,
and
we
talked
a
little
bit
about
this
last
time,
but
to
kind
of
show
you
what
they're
working
on
today,
you
get
limited
information
on
the
report
and
you
don't
necessarily
get
everything
you
need
to
start
digging
into
it.
B
So
when
you
click
on
one
of
the
reported
items
again,
a
trail
will
slide
out
from
the
right
and
you'll
get.
Additional.
Information
includes
actual
next
steps
that
you
can
take.
This
includes
links
out
to
the
merge
request,
people
who
are
involved
in
the
review
and
so
forth.
This
is
the
beginning
of
providing
more
value
and
visibility
for
you
for
your
compliance
concerns.
B
B
The
other
area
they
are
working
on
is
giving
you
better
control
over
managing
groups
at
the
parent
group
level.
For
those
who
are
not
familiar,
there's
a
lot
of
options
again
in
the
admin
area
that
are
missing
at
that
top
level
name
space.
This
is
a
very
small
but
very
powerful
improvement.
Today,
if
you're
in
a
group
on
gitlab.com
or
gitlab,
hosted
environment
to
delete
a
project,
you
actually
or
group,
you
have
to
actually
go
into
the
group
settings
and
find
the
delete
button.
This
is
going
to
be
bringing
that
little
button.
B
Today,
if
you're
in
value
analytics,
you
get
things
such
as
deploys
and
deployment
frequency.
However,
that's
missing
from
the
cicd
analytics,
so
the
proposal
is
to
bring
that
same
data
to
this
report.
You
can
see
here,
they'll
be
including
that
at
the
top
of
the
chart
and
to
wrap
up
the
dev
section
with
ecosystem,
the
foundations
team
is
working
on
our
pajamas
migration.
If
you're
not
familiar
with
that,
there's
a
lot
of
really
great
detail
available
on
designdocketlab.com,
however,
for
this
milestone,
they're
focused
on
standardizing
the
dropdown
functionality
and
making
that
an
available
component.
C
All
right
awesome,
so
the
sex
section
has
a
lot
going
on
this.
Milestone
will
be
a
packed
milestone
for
us,
so
all
of
our
groups
will
be
working
on
projects
that
support
the
fiscal
23
theme
of
improving
key
workflow
usability.
First
here
you'll
see
that
the
dynamic
dynamic
analysis
team
has
for
das
they're
continuing
to
work
on
developing
passive
vulnerability
checks
for
browser-based
scanning.
So
as
a
reminder,
we've
built
a
proprietary
browser-based
scanner
that
will
eventually
fully
replace
zap.
C
C
Additionally,
corpus
management
for
coverage.
Guided
testing
will
go
live,
unfortunately,
so
for
the
uninitiated,
a
corpus
is
the
library
of
inputs
that
you
put,
that
you
give
to
your
fuzzing
tool
and
that
it
will
reference
in
order
to
test
an
application.
So
this
work
makes
it
easy
for
users
to
maintain
the
set
of
inputs
that
they
want
to
use
when
testing
their
applications
within
gitlab
and
then
the
last
couple
items
for
dynamic
analysis
are
around
advancing.
C
Our
recently
introduced
category
of
api
security,
so
first
of
all,
first
priority
for
the
team
is
focusing
on
improving
scan
speeds
and
then
also
on
switching
the
on-demand
api
scan
to
use
api
security
scanner
instead
of
instead
of
zap.
So
this
change
will
most
likely
ship
in
14.9,
but
it's
possible.
It
could
ship
in
this
milestone,
so
we're
bringing
it
up
now.
C
A
major,
immediate
benefit
of
this
change
is
that
it
will
allow
users
to
scan
apis
other
than
just
rest
apis,
so,
for
instance,
soap
and
graphql
apis,
as
well
with
the
on-demand
scan
and
then
we'll
we'll
also
allow
them
to
use
a
har
file
or
postband
collection
to
define
the
api,
rather
than
only
being
able
to
use
open
api
specs.
C
C
Oh
sorry,
apologies
there,
so,
basically
that'll
appear
in
the
ui,
so
users
won't
be
able
to
we'll
be
able
to
see
not
only
the
package
name
that
was
introduced
and
has
a
vulnerability,
but
also
the
exact
file
in
the
project
where
that
dependency
was
included.
So
that'll
make
it
easier
for
users
to
locate
the
vulnerable
package
in
order
to
fix
them.
C
C
Ultimately,
the
goal
here
is
to
be
able
to
bring
our
license
compliance
functionality
back
into
active
development
and
then
start
to
address
a
number
of
customer
requirements
that
have
surfaced
against
our
existing
offering
the
threat.
Insights
team
is
working
on
integrated
developer
security
training
so
to
truly
help
organizations
unlock
the
potential
of
a
shift-left
security
approach.
We
really
need
to
help
them
support,
elevating
overall
security
knowledge
within
the
development
organization.
C
So
there's
this
gap
that
exists
between
reporting,
a
security
finding
on
one
hand
and
then
having
a
developer,
really
fully
understand
that
vulnerability,
its
associated
risk
and
how
to
fix
it.
So
one
of
the
many
ways
that
we
want
to
help
close
this
gap
is
with
self-service
security
training
as
part
of
the
developer's
daily
workflow.
C
So
with
this
functionality,
we'll
provide
a
simple,
unobtrusive
way
to
access
highly
relevant
training
materials
from
security,
training
from
our
security,
training,
content
partners,
and
so
users
will
be
able
to
see
the
option
to
complete
a
specific
training
within
the
right
context.
C
So
that's
when
they're
actually
reviewing
security
findings
within
mrs
or
in
pipelines
or
on
a
vulnerability
report,
so
because
we
want
to
provide
access
to
content
from
multiple
training
providers.
This
feature
is
also
going
to
be
built
in
a
modular
way
and
the
experience
will
be
consistent,
regardless
of
who
is
providing.
Content
also
want
to
provide
a
heads
up
on
a
few
deprecations
that
are
coming
up.
These
won't
be
the
only
deprecations
that
you'll
see
in
secure
protect
functionality
but
they're,
some
of
the
more
notable
ones.
C
So,
first
four
thread
insights
as
of
15.0,
we'll
start
enforcing
validation
of
all
security
report.
Artifacts.
Additionally,
secure
report
formats
prior
to
schema
version,
14.0.0,
won't
pass
validation
and
will
therefore
no
longer
be
supported.
So
it's
important
for
any
security
tool
that
integrates
with
getlab
to
ensure
that
it's
adhering
to
proper
to
the
proper
schema
version
and
that
it
will
also
pass
validation.
So
there
will
be
more
details
on
that
available
in
our
release
post
and
then
in
relation
to
container
security.
So
we
will
be
deprecating.
C
The
existing
vulnerability
check
functionality
with
plans
to
actually
remove
it
in
15.0
and
then
simultaneously
we'll
be
releasing
security
approval
policies
which
you
see
here
in
the
14.8
release.
So
this
will
come
with
a
new.
A
number
of
improvements
for
security
teams,
including
including
the
ability
to
have
the
security
team,
manage
their
security
approval
policies
independently
from
the
development
team.
C
So
basically
maintainers
on
the
development
project
won't
automatically
have
access
to
edit
your
security
policies
so
sort
of
separation
of
duties
there,
the
ability,
you
also
have
the
ability
to
create
multiple
rules,
so
it'll
only
you'll
be
able
to
only
require
approval
on,
for
instance,
critical
vulnerabilities
for
sas,
but
then
for
container
scanning.
You
could
require
approval
for
criticals
and
highs.
So
basically,
the
flexibility
to
define
finer
grain
policies
is
coming
with
this.
With
this
feature,
and
then
you
also
have
the
ability
to
enforce
an
approval
process
for
changes
to
the
security
policies
themselves.
C
Finally,
for
static
analysis,
the
static
analysis
team
is
working
on
a
number
of
analyzer
updates
and
deprecations.
This
milestone
and
the
details
you'll
be
able
to
read
about
read
about
in
our
release
posts,
and
with
that
I
will
turn
it
over
to
kenny.
D
Awesome
exciting
about
the
security
policies.
That's
great
hillary
yeah!
Let
me
share
my
screen
all
right.
My
name
is
kenny.
I
am
the
product
leader
covering
the
ops
section.
The
op
section
includes
the
stages
of
verify
package,
release
configure
and
monitor
and
wow
what
a
doozy
14
8
is
going
to
be
an
awesome
release
for
the
ops
section.
When
I
was
preparing
my
highlights,
there
were
just
way
too
many
to
cover,
so
I'd
really
encourage
everyone
to
walk
through
the
videos
of
each
individual
group.
There's
a
lot
of
really
exciting
stuff
happening
in
14.8.
D
One
quick
note:
we
announced
in
the
last
kickoff
and
announced
publicly
in
blog
post
that
we
acquired
a
company
called
ops,
trace
and
we'll
be
integrating
them
wanted
to
call
it
that
we're
going
to
be
integrating
ops,
trace
and
calling
that
group.
The
monitor,
observability
group,
and
so
our
existing
monitor
group
is
renamed
to
the
monitor
respond
group.
So
you'll
hear
me
reference
them
in
this
conversation,
another
also
psa
will
be
deprecating
gitlab's
existing
metrics
logging
and
tracing
features.
Officially
in
the
15.00
release.
D
That
deprecation
has
already
been
announced
in
our
docs,
all
right,
all
as
the
rest
of
the
groups.
We
are
organized
and
heavily
focused
on
our
three
core
fy23
themes.
Those
are
gitlab,
hosted,
first,
improving
key
workflow
usability
and
extending
our
lead
in
cicd
in
gitlab
hosted.
First,
I
wanted
to
highlight
a
couple
of
investigations
and
issues
that
we're
working
on
that
are
the
result
of
high
usage
of
existing
parts
of
our
product.
D
So
if
you
use
gitlab,
ci,
you're,
probably
familiar
with
our
pipeline
authoring
experience
and
our
pipeline
editor,
we've
been
noticing,
as
more
users
have
been
using
the
pipeline
editor
that
we're
experiencing
increased
delays
and
aptx
scores
for
the
experience
that
users
are
having
when
when
editing
their
files.
So
we're
going
to
be
doing
a
deep
dive
to
make
sure
that
we
stay
within
that
group's
error
budget
in
14.8
and
then
the
second
one.
Where
again,
we've
been
seeing
a
lot
of
increased
usage
is
you've
been
following
along.
D
We've
announced
our
gitlab
agent
for
kubernetes
gitlab
agent
for
kubernetes
and
the
server
that
the
individual
agents
connect
to
and
to
in
order
to
connect
to
the
gitlab
instance.
As
we've
been
scaling
that,
particularly
on
gitlab.com
we've
been
noticing
some
scaling
challenges,
so
we're
going
to
be
doing
a
deep
dive
into
making
sure
that
that
service,
that
kubernetes
agent
server
on
your
instance
can
scale
as
your
usage
of
the
agent
scales
and
in
the
theme
of
improving
key
workflows.
There's
one
that
I
really
wanted
to
highlight.
D
This
is
a
really
popular
issue,
and
this
is
our
most
common
workflow.
It's
the
merge
request,
workflow
and,
if
you've
experienced
using
gitlab
across
multiple
projects,
you've
found
that
oftentimes
individual
projects
have
different
merge
strategies.
What's
the
process
by
which,
when
we
decide
that
we
want
to
merge
code,
it
gets
merged.
Some
of
those
can
be
things
like
merge
trains
or
other
merge
strategies
that
can
be
confusing
when
you're
jumping
between
projects
about
what
is
actually
going
to
happen
when
I
click
merge.
D
So
one
of
the
things
that
we're
going
to
be
working
on
in
14.8
is
improving.
That
user
experience
so
that
there's
a
kind
of
universal,
auto
merge
button
where
you
can
then
drill
down
and
find
out
the
exact
details
about
what
will
happen,
but
for
users
who
you
know,
are
more
used
to
jumping
between
projects.
They
can
just
quickly
hit
the
auto,
merge
button
and
be
satisfied
that
that
will
perform
the
merge
actions
that
are
set
up
for
that
project.
D
So
those
that
is
the
one
really
key
workflow
improvement,
we're
working
on
in
14.8
and
then
the
next
ones
are
about
extending
our
lead
in
ci
cd,
which
is
the
core
mission
of
the
ops
section.
So
the
first
issue
I
wanted
to
highlight
is
from
our
pipeline
execution
group
users
of
our
our
rules.
Syntax
will
know
that
it
can
sometimes
be
difficult
to
target
a
different
pipeline
experience
when
there
is
an
empty
branch
versus
a
branch
with
multiple
commits,
so
by
default.
D
If
you
were
to
create
a
new
branch,
the
pipeline
would
typically
run
on
that
empty
branch,
and
we
want
to
give
users
control
over
ensuring
that
they
can
maybe
have
a
different
experience
if
there
are
no
commits
on
a
branch.
So
we'll
be
adding
this
specific
variable
for
ci
branch
commit
count,
and
you
can
set
it
that
if
it's
equal
to
zero,
you
can
choose
not
to
run
a
pipeline
job.
This
is
a
highly
requested
issue
that
we're
really
excited
to
work
on
and
deliver
in
14.8.
D
The
next
is
in
our
runner
core
category.
We've
been
doing
a
spike
recently
about
how
to
ensure
that
we
can
both
have
a
standard
metadata
store
for
information
about
the
artifacts
that
are
built
by
your
runners
as
well
as
a
way
to
retrieve
attestation
about.
You
know
that
the
artifact
that
was
built
is
the
same.
That
might
be
the
artifact
being
deployed.
There's
a
common
open
source
project
called
grapheus.
That
does
this.
D
In
a
very
cloud-native
way
and
we're
going
to
be
working
on
a
poc
to
integrate
graphes
with
the
gitlab
runner
to
improve
your
ability
to
make
attestations
and
store
metadata
about
your
artifacts
is
a
really
critical
component
of
ensuring
that
you
have
a
secure
supply
chain
where
what
so,
you
can
track
that
you
know
what
was
built
is
the
same
thing
that
gets
deployed
to
production.
D
I'm
really
excited
about
this
issue,
and
the
next
two
are
about
our
deployment
process,
particularly
the
process
by
which
multiple
users
collaborate
on
a
kind
of
deployment
artifact
as
it
moves
through
environments.
We've
been
working
on
and
showcasing
to
you
future
for
the
environments,
page
redesign.
I'm
really
excited
about
this
edition
in
14.8
of
the
deployment
block,
so
that
will
allow
you
to
kind
of
expand
exist
or
most
recent
deployments
for
a
given
environment,
in
this
case
the
production
environment
and
see
various
things
like
the
trigger
the
pipeline
status.
D
D
Actually
in
14.7
we'll
be
releasing
the
ability
to
have
deployment
approvals
via
api,
we're
going
to
be
adding
that
to
the
ui
and
14.8,
and
that
will
start
with
directly
in
that
environments,
page
being
able
to
signal
and
approve,
if
you
are
an
approved
in
an
approved
group
for
performing
deployments
to
your
protected
environment,
your
approval
and
we
can
track
and
showcase
that
approval
throughout
the
application.
So,
as
I
mentioned
at
the
start,
really
exciting
stuff
coming
in
the
op
section
in
14.8,
definitely
going
to
be
the
best
release.
E
Thanks
kenny,
those
are
some
really
exciting
features.
Let
me
jump
over
into
the
enablement
section
now
so
similar
to
kenny.
We
have
way
too
many
awesome
features
coming
in
14.8
to
potentially
include
them
in
four
minutes,
so
I'm
going
to
just
cover
the
highlights
and
encourage
folks
to
please
take
a
look
at
the
kickoff
videos
on
our
kickoff
page
to
learn
in
more
detail
about
what
the
entirety
of
the
teams
are
working
on.
E
So
let's
get
started
with
a
course
with
gitlab
hosted
first
for
those
of
you
who
have
been
paying
attention
to
pickup
videos
for
the
past
couple
milestones,
we
have
been
working
to
essentially
decompose
gitlab's
database.
The
challenge
we
face
is
that
we
have
with
our
postgres
database.
Is
it
can
only
get
so
big
because
on
postgres,
you
can
only
write
to
one
node
at
a
time
and
that
node
can
only
get
so
many
cpus
and
so
much
ram?
E
And
so
at
some
point
you
have
to
do
something
different
and
what
we
are
doing
is
going
to
be
splitting
our
database
into
effectively
two
pieces,
which
gives
us
double
the
right
capacity,
and
so
we
are
underway
on
this,
and
this
is
largely
being
driven
by
the
sharding
and
the
database
teams.
And
you
can
see
we
have
a
bunch
of
work
here
in
progress.
E
In
particular,
we
are
working
in
this
release
to
help
to
make
sure
that
the
various
features
of
our
code
base
are
compatible
with
two
databases
so
effectively.
Our
code
needs
to
know
that
for
this
certain
data
type
to
go
to
this
database
and
for
this
other
database
data
type
to
go
here,
and
so
we
are
working
through
that
across
our
migration,
tooling,
our
backup
and
restore
and
other
functionality.
And
again
this
is
a
lot
of
what
our
starting
team
and
database
team
are
working
on.
E
In
addition,
we're
also
working
to
continue
to
improve
our
disaster
recovery
functionality.
The
goal
here
is
to
help
make
sure
that
we
can
innovate
more
quickly
and
have
a
more
reliable,
consistent
framework
underneath
our
replication
solution,
and
so
in
the
past
we
had
bespoke
kind
of
one-off
replication
code
for
each
data
type
and
we've
been
moving
those
into
our
self-service
framework.
E
And
so
what
we're
working
on
here
is
to
actually
move
that
metric
server
outside
of
the
web
server
process,
and
so
in
case
it
has
any
kind
of
problems.
It's
not
going
to
impact
our
ability
to
actually
serve
content
to
users.
So,
looking
forward
to
this
one
here
from
availability,
improvement
now
transitioning
over
from
gitlab
hosted
first
and
all
those
performance
and
scalability
and
reliability
efforts,
we
have
underway
over
to
key
workflows.
E
So,
for
example,
if
you
have
some
content
with
hyphens
in
between
today,
we
might
not
find
it,
but
with
this
improvement
we
will,
and
so
we're
looking
forward
here
to
really
have
a
much
higher
hit
rate
on
what
you're,
looking
for
across
different
kind
of
complex
punctuation
and
text
searches
to
ensure
that
we're
actually
giving
those
results.
You
need
so
looking
forward
to
this.
E
This
is
very
requested
to
overall
improve
our
code
search
quality,
we're
also
working
to
improve
the
performance
right
now,
when
you
perform
a
google
search
beneath
the
hood,
there
are
some
inefficiencies
we
found.
We
actually
passed
a
significant
number
of
project
ids
over
to
our
back
end,
which
can
cause
this
query
to
slow
down.
We
are
working
to
improve
this
and
hopefully
have
a
much
faster
groupable
search
in
the
product
than
we
do
today.
So
looking
forward
to
that
performance
and
ux
improvement.
E
E
We're
getting
again
very
close,
so
looking
forward
to
this
being
available
soon
and
last,
we're
also
working
to
work
through
pips
compliance,
and
so
we
are
working
to
achieve
this
for
our
self-managed
customers
as
well
as
potentially
other
use
cases,
and
the
goal
here
is
to
ensure
that
we
can
have
all
the
cryptography
within
the
gitlab
platform
meet
the
fips
one
for
just
two
compliance
standard
for
the
us
government,
and
this
will
help
unlock.
You
know
some
of
those
use
cases
and
customers
to
more
easily
adopt
gitlab
in
those
use
cases.
A
Thank
you
everyone.
I
heard
a
lot
of
amazing
pieces
of
improvements
coming
in,
I'm
really
interested
in
figuring
out
what
the
team
finds
with
respect
to
replacing
web
ide
with
client-side
vs
code.
It
looks
promising
improving
compliance
reports,
better
user
management
for
sas
through
the
workspace
initiative.
I
think
we
are
asked
we
have
heard
a
lot
of
our
sas
customers
ask
for
that.
So
that's
amazing
progress
changing
dashed
on
demand
api
scanning
engine,
so
we
can
scan
other
apis
beyond
rest.
A
Pretty
exciting
helps
expand
our
use
case
open
source
other
than
another
investigation
with
open
source
tech
to
replace
the
license.
Finder
would
love
to
get
community
also
chime
in
on
what
they've
seen
work
summarizing,
auto
merge
progress
in
the
merge
request,
again
very
complex
area
of
the
product,
making
it
easy.
That's
amazing,
different
ci
treatment
for
empty
branches
will
be
super
helpful
for
a
lot
of
our
customers
also
excited
about
another
plc,
which
is
integrating
graphs,
to
make
attestations
graphics
and
to
make
attestations
and
store
metadata
about
the
artifacts.
A
I
know
some
of
our
large
customers
have
tried
it
and
found
it
beneficial.
So
I'm
really
excited
to
see
how
the
plc
goes:
adding
approval
ui
in
protected
environments
again
an
amazing
amazing,
small,
but
very
impactful
usability
improvement
on
the
enablement
side.
All
the
work
we're
doing
for
scalability
and
availability,
including
database
decomposition
work.
Decoupling
things
like
the
metric
server
from
the
web
server
pretty
interesting
work
to
make
sure
we
we
continue
to
be
highly
available
and
resilient
and
scalable.
A
I
can't
wait
for
the
improved
code
search
quality.
I
personally
found
myself
doing
this
with.
You
know,
trying
to
look
for
files
with
hyphenated
things
and
not
being
able
to
find
them
and
then
phipps
compliance
progress
for
us
government.
I
think
this
is
amazing.
We
are
kicking
off
2022
with
a
super
amazing
roadmap.