►
From YouTube: 15.6 Monthly Release Kickoff Call (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
All
right,
hey
everyone,
welcome
to
the
15.6
release
kickoff.
My
name
is
Justin
Ferris
I'm,
not
David,
DeSanto
I
have
a
little
bit
less
facial
hair
and
a
little
bit
more
hair
on
the
top
of
my
head
David's
out
today,
but
I'll
be
hosting
in
your
MC
for
today's
live
stream.
I'm
joined
by
some
of
the
most
awesome
members
of
the
gitlab
product
team,
I'll
list
them
off
in
order
of
which
they'll
be
presenting
first
off
is
Melissa
ushakov.
A
Our
group
manager
for
plan
we'll
be
providing
updates
on
our
Dev
section,
Hillary
Benson,
our
director
of
product
for
secure,
who
will
be
providing
updates
on
our
sex
session.
Sec
section
Taylor
McCaslin,
our
group
product
manager,
who
will
be
bringing
providing
us
updates
on
the
data
science,
section,
Kevin,
Chu
group
manager
for
the
monitor
stage,
providing
updates
on
Ops
and
then
Josh
Lambert,
who
will
bring
us
home
director
of
product
for
our
enablement
and
SAS
platform,
section
we'll
be
providing
updates.
A
There
I
get
a
lot
more
focused
on
delivering
value,
iteratively
aligned
with
our
fiscal
year.
23
product
investment
themes,
I'll
list
them
here.
First,
one
is
gitlab
hosted
first
gileb
hosted.
First,
does
not
mean
gitlab
hosted
only,
but
gitlab.com
is
the
largest
known,
self-managed
deployment,
and
we
know
if
we
can
meet
our
own
requirements,
we
can
meet
our
customers
requirements.
Our
second
theme
is
improving
key
workflow
usability.
We
know
improving.
A
Oh
sorry,
this
theme
will
be
focused
on
improving
our
key
workflows
and
we
know
if
we
improve
learnability,
we
can
drive
multi-stage
adoption,
making
gitlab
more
and
more
valuable
for
our
users
and
then.
Finally,
our
last
theme
is
extending
our
lead
in
CI,
CD
devops
doesn't
end
until
applications
are
deployed
to
production.
A
We
want
to
make
sure
that
is
a
seamless
and
frictionless
experience
as
possible
for
our
users
before
I
hand
it
over
to
Melissa
I,
have
one
short
public
service
announcement
on
this:
live
stream,
we'll
be
discussing
our
product
roadmap,
which
includes
upcoming
features
and
functionality.
It's
important
to
note
that
the
information
presented
is
for
informational
purposes.
Only
so
please
do
not
rely
on
this
information
for
purchasing
or
planning
purposes.
We
plan
ambitiously
here
at
gitlab
and
all
the
details
discussed
on
this
live
stream
are
subject
to
change.
B
Dev
is
comprised
of
manage
plan
and
create
so
I'm
going
to
be
covering
all
the
great
stuff
that
these
teams
are
working
on,
starting
with
web
hooks
cold
start,
so
we're
iterating
on
our
recently
implemented
web
hooks
disabling
feature
the
accounting
for
cold
starts.
This
is
a
common
scenario,
especially
in
more
complex
setups,
where
the
first
call
takes
just
a
little
bit
longer
to
execute,
so
we're
going
to
be
adding
some
logic
to
account
for
that.
B
We're
also
going
to
be
extending
our
feature
flag
to
allow
for
disabling
for
a
specific
actor.
So
if
there's
a
specific
web
hook,
that's
taking
longer
to
execute
that
one
can
be
allowed
to
basically
execute
a
bit
a
little
bit
longer
without
disabling
the
entire
feature
flag,
more
improvements
to
web
hooks
we're
going
to
be
encrypting
the
data
Associated
to
this.
B
So,
instead
of
it
displaying
clear
text
in
the
UI
it's
going
to
be
encrypted
and
we're
also
going
to
give
you
the
ability
to
mask
certain
portions
of
callback
URL
since
that
can
be
sensitive
data
as
well.
This
work
is
important
to
our
security
minded
customers
and
it's
actually
blocking
adoption
for
a
couple
of
people.
B
This
feature
will
make
it
much
easier
to
manage
users
since
skin
can
be
used
to
provision
and
deprovision
users
automatically
by
connecting
it
to
your
source
of
Truth,
for
user
management
and
on
the
theme
of
user
management,
we're
making
it
much
easier
for
group
administrators
to
have
control
over
their
users.
This
feature
is
particularly
valuable
to
SAS
admins,
so
we
recently
released
a
feature
where
you
can
claim
a
domain
at
the
group
level.
B
So
now
what
you
can
do
is
that
if
a
user
that
belongs
to
your
group
matches
that
email
domain,
you
can
essentially
Mark
that
user
as
owned
by
that
group
and
that
unlocks
some
really
interesting
features
like
controlling
that
user's
2fa.
So
group
owners
can
self-serve
disabling
2fa
for
those
users
and
not
have
to
reach
out
to
customer
support.
B
There's
more
coming
along
this
thread
of
user
management
at
the
group
level,
so
stay
tuned
for
that
now,
I'm
going
to
move
on
to
our
improved
key
workflow
usability
theme
we're
going
to
be
streamlining
the
issues
experienced
by
moving
some
of
the
least
commonly
used
items
on
the
menu
to
a
more
actions
menu.
So
I
can
show
you
what
that
would
look
like
you
see
here.
B
We
are
gonna,
be
exposing
a
to-do
whenever
there's
a
request
to
join
a
group.
This
brings
that
request.
It
bubbles
it
up
right
now.
The
only
place
where
that's
displayed
is
in
the
users
group
members
UI
there's
also
email
notification,
but
this
is
another
way
to
bubble
that
request
to
make
sure
it's
addressed
in
a
timely
fashion.
B
We
are
also
gonna
be
exposing
more
information
when
a
user
is
deleted,
and
this
will
just
give
administrators
a
broader
picture
of
exactly
what
will
happen
when
the
user
is
deleted,
along
with
their
contributions
to
make
sure
that's
the
intended
action
and
there's
no
accidents.
B
So
you
can
see
here
we're
going
to
display
the
groups,
projects,
issues
and
merge
requests
Associated
in
as
part
of
the
delete,
workflow.
B
And
last
but
not
least,
is
that
during
the
GitHub
migration
users
expect
that
all
relationships
between
objects
will
be
pertained
and
migrated.
B
So
we're
going
to
be
expanding
our
existing
functionality
to
also
bring
over
relationship
between
issues
and
Mrs
as
part
of
the
GitHub
migration
process.
And
it's
going
to
look
like
this
with
the
related
merge
requests
and
that
is
it
for
Dev
I'm,
going
to
be
now
handing
it
over
to
Hillary
who's
going
to
cover
sec.
C
So
there
is
just
a
massive
amount
of
work
actually
going
on
in
our
security
and
compliance
functionality
in
15.6.
So
to
kick
us
off
a
composition.
Analysis
is
kicking
off
a
multi-month
effort
to
replace
license
finder,
which
is
the
underlying
technology
for
our
license
compliance
functionality.
So
when
that
work
completes
likely
sometime
early
next
year,
users
will
see
a
number
of
benefits,
so
the
new
architecture
will
position
gitlab
to
be
able
to
provide
a
more
accurate
license
data
over
time.
C
The
static
analysis
team
is
beginning
work
to
move
scholar,
SAS
coverage
from
spot
bugs
to
sim
grip-based
scanning.
As
a
reminder,
some
grip-based
scanning
is
superior
to
the
other
various
language,
specific
open
source
analyzers,
because
it
provides
faster
scan
times,
better
results,
a
more
consistent
user
experience
and
also
more
flexibility
in
defining
custom
rule
sets,
regardless
of
what
the
language
is.
That's
being
scanned.
C
The
static
and
also
team
is
also
working
on
changes
to
the
vulnerability
report
that
will
eventually
allow
us
to
clean
up
the
report
and
do
some
some
record
record
keeping
for
traceability
if
users
decide
to
remove
rules,
whereas
today,
if
you
remove
a
rule
of
the
previous
findings
for
that
rule,
stay
on
the
vulnerability
report,
which
isn't
necessarily
what
users
want
or
expect
the
dynamic
analysis
team
has
a
couple
pretty
significant
headlines
in
15.6,
so
first
they're
taking
up
work
in
sort
of
a
net
new
area
for
us
which
is
API
Discovery
one
of
the
biggest
challenges
in
security
testing.
C
Your
apis
is
knowing
what
apis
you
have
to
begin
with.
So
the
idea
here
is
to
generate
an
open
API
schema
from
an
application
that
doesn't
already
produce
its
own
schema
without
actually
having
to
run
that
application.
So,
in
a
sense,
it's
a
sort
of
easy
button
for
setting
up
security
testing
of
your
apis.
This
is
a
major
project.
That'll
take
some
time
to
complete,
but
it's
kicking
off
in
15.6
and
the
team
is
starting,
as
you
can
see,
with
a
Java
spring
boot
rest
apis.
C
Second,
the
dynamic
analysis
team
is
also
working
to
move
our
browser-based
daf
scanner
to
General
availability.
This
is
super
exciting
we're
going
to
do
this
in
stages,
and
so
the
first
GA
delivery
will
include
the
crawler
itself,
the
authentication
Service
and
our
passive
vulnerability
checks.
C
Threat
in
science
has
some
significant
architectural
work
and
post-launch
inline
training
improvements
that
that
they
have
on
Deca
for
this
Milestone,
but
they're
also
continuing
work
on
a
multi-milestone
project
to
enable
continuous
vulnerability
scanning
with
a
specific
Focus
this
month
on
ingesting
software
billing
material
reports.
So
continuous
vulnerability
scanning
is
a
big
deal
for
users,
because
it'll
mean
that
they
can
maintain
visibility
into
the
security
footprint
of
their
dependencies
without
actually
having
to
take
any
action
in
order
to
do
that,
which
is
what
they
have
to
do
today.
C
So
the
idea
here
is
that
anytime,
The
Advisory
database
that
that
includes
you,
know,
vulnerability,
advisories
anytime,
that's
updated
with
new
vulnerability
information
or
anytime
the
user's
software
bill
of
material
changes.
Then
we
update
the
match
between
those
two
things.
So
users
will
always
know
in
sort
of
linear
real
time
what,
depending
what
dependencies
exist
in
their
software
and
then
what
vulnerability
is
those
dependencies
are
exposed
to
yeah
security
policies?
C
Team
is
working
to
add
support
for
role-based
approvers
that'll,
give
users
who
are
creating
scan
result,
policies,
more
flexibility
in
defining
who's
actually
eligible
to
approve
vulnerabilities
and
they're,
also
working
to
provide
support
for
dependency
scanning
in
scan
execution
policies,
which
is
very
heavily
requested,
feature
from
customers
and
then,
finally,
the
compliance
team
is
working.
This
Milestone
on
a
group
level
setting
that
will
allow
users
to
apply
a
default
compliance
framework
to
any
new
project.
That's
created
within
that
group.
C
That's
a
great
usability
Improvement,
because
today,
even
if
users
have
attached
a
compliance
framework
at
the
group
level,
they
still
have
to
manually
tag
subordinate
projects.
So
this
will
save
quite
a
bit
of
manual
work
and
that
is
it
for
the
SEC
section.
So
I'll
pass
it
off
to
Taylor
to
take
us
through.
What's
going
on
in
data
science,
awesome.
D
Thanks
Hillary
so
today,
I'm
going
to
focus
primarily
on
our
model
Ops
stage,
which
is
focused
on
supporting
and
enabling
machine
learning
workloads
across
gitlab,
so
to
get
started.
I'll
touch
briefly
on
our
applied
ml
group.
This
is
focused
on
applying
machine
learning
to
gitlab
features
to
make
them
smarter.
More
automated
we
released
suggested
reviewers
gitlab's
first
ml
powered
feature
last
release
this
release.
We
are
working
to
clean
up
a
variety
of
bugs
and
that
guy
and
back-end
UI
enhancements.
You
can
see
it's
a
long
laundry
list
of
things
to
improve.
D
So
that's
our
primary
focus
for
that
I.
Do
want
to
talk
real
briefly
about
a
single
Engineering
Group
here
at
gitlab
called
AI
assist.
This
is
a
machine
learning
recommendations,
Azure
typing
code,
to
do
line,
completions
and
suggestions.
Today.
This
is
a
single
Engineering
Group,
that's
working
through
a
POC,
that's
moving
into
an
NVC.
This
group
has
actually
just
added
support
to
the
gitlab
workflow
vs
code,
plugin
for
a
self-hosted
version
of
a
a
faux
pilot
open
source
project.
So
you
can
connect
to
a
self-hosted
instance
of
faux
pilot.
D
This
is
just
the
start
of
us
getting
into
this
area,
we're
actually
in
the
process
of
transitioning
this
from
a
single
Engineering
Group
to
a
product
group,
so
much
more
to
come
on
this,
but
we're
starting
to
fully
support
these
open
source
models
and
in
15.6
we'll
be
starting
to
develop
gitlab's
own
model
to
power.
A
version
of
this
as
well.
Moving
over
to
ml
Ops,
which
is
about
enabling
machine
learning
workflows
across
gitlab,
features
we're
looking
to
extend
the
package
registry
to
become
a
model
registry.
D
You
can
actually
host
your
machine
learning
models
with
the
package
registry
today,
using
the
generic
packages,
we're
going
to
be
creating
a
new
package
type
for
machine
learning
models
and
metadata
we're
actually
going
to
be
creating
an
open
source
standard
around
this.
Today,
models
are
packaged
in
many
many
different
ways:
there's
no
single
standard,
so
we're
proposing
a
standard
which
will
be
supported
in
the
package
registry.
This
will
allow
you
to
version
and
manage
your
different
versions
of
packages
or
of
ml
models
within
the
gitlab
package
registry
and
have
an
API
to
access
those.
D
This
also
sets
us
up
for
the
future
to
actually
do
auto
deployment
of
models
for
you
to
have
inference
of
those
via
kubernetes
much
more
to
come
on
that
in
the
future.
So
we're
started
with
this
extension
of
the
package
registry
and
then
finally,
I
want
to
talk
about
another
single
Engineering
Group
focused
on
a
machine
learning,
experiment
tracking
feature.
This
is
an
integration
with
mlflow.
This
is
nearing
NVC
availability
for
customers
to
try.
D
So
if
you
use
mlflow
today
check
out
this
epic
there's
a
work,
a
video
overview,
viewing
the
interactions
that
are
available
here.
This
will
eventually
tie
into
that
model
registry.
So,
if
you
use
ml
flow,
you'll
basically
update
your
url
to
point
at
gitlab
to
track
your
experiments
and
then
in
the
future,
we'll
allow
you
to
take
those
experiments
that
are
ready
to
go
to
packaged
models
and
transition
that
to
the
package
registry,
with
that
new
model
registry
that
we're
building.
So
that
is
a
quick
overview
of
our
model.
Ops
features.
E
Awesome
so
I'll
be
representing
op
section
for
this
kickoff
as
a
quick
refresher,
the
op
section
includes
a
verify
package,
release,
configure
and
monitor
stages.
Today,
I'm
going
to
be
highlighting
six
things
along
the
themes
of
improving
key
workflows
and
extending
our
lead
in
CI
CD,
and
there
is
a
lot
more
plans.
So
please
dig
into
the
individual
team's
plans
if
you're
interested
item
number
one
is
from
the
monitor
stage.
E
So
as
an
example,
here
is
an
instant
that
recently
happened
and
you'll
notice,
if
you
use
it
before
changing
the
Status
automatically
creates
an
event
in
the
incident,
but
not
the
severity.
Severity
is
obviously
a
really
important
detail
in
an
incident
so
in
this
iteration
we'll
be
adding
this
automation
to
the
incident
timeline
and
we'll
be
also
adding
a
bunch
of
other
features
along
to
the
instant
timelines,
such
as
incident
tags
and
so
forth.
So
if
you
haven't
checked
it
out
yet
take
a
look,
and
let
us
know
what
you
think.
E
The
second
item
is
from
the
package
group,
so
the
package
group
in
this
Milestones
focused
on
improving
storage
management
and
storage
calculation
for
the
package
and
container
Registries,
so
that
users
have
an
accurate
view
of
costs
and
have
a
chance
to
be
more
efficient.
So
along
the
theme
of
efficiency.
One
of
the
improvements
I
like
to
share
here
is
the
ability
to
bulk
delete
packages
directly
from
the
UI.
So
previously
you
had
to
click
delete
a
bunch
of
times.
This
makes
the
whole
interaction
quite
cumbersome.
E
We
were
adding
this
multi-select
feature,
so
you
can
get
to
you
can
get
rid
of
the
packages
you
don't
want
and
get
to
the
packages.
You
actually
move
quickly
and
easily
onto
the
theme
of
extending
our
leading
CI
CD.
The
runner
Fleet
group
is
working
to
bring
visibility
to
Hue
management
and
the
first
iteration
of
that
is
we're
going
to
be
showing
duration
and
queue
time
directly.
In
the
job
list
view.
E
This
will
give
users
more
insights
into
what
a
runner
is
doing,
and
this
is
particularly
useful
when
you
have
a
job
that
has
been
pending
for
a
long
time.
You
have
no
idea.
What's
going
on
having
this
information
right
there
on
a
job
list
view
will
give
you
the
information
you
need
to
make
the
appropriate
decisions.
E
The
next
item,
I
want
to
highlight
is
one
of
the
most
requested
features
for
CI
variables,
so
users
want
the
ability
to
Define
possible
values
for
CI
variables
and
let
users
set
them
when
actually
running
a
pipeline.
So
we
plan
to
let
users
Define
possible
values
for
any
CI
variables
via
yaml.
As
the
example
you
see
here
and
when
actually
running
a
pipeline
at
the
first
value,
that's
defined
will
become
the
default
value
and,
of
course,
users
can
select
other
possible
values.
E
This
will
enable
users
to
quickly
find
the
exact
artifact
that
you're
looking
for
and
last
but
not
least,
the
release
group
has
been
working
on
improving
the
deployment
approval
workflow
in
this
Milestone
we're
adding
a
bunch
of
things
to
this
particular
UI.
E
Lastly,
we're
adding
these
badges,
so
people
know
where
the
approvers,
what
which
group
they
belong
to
so
for
deployment
that
requires
multi-step
approvals.
This
is
easy
and
intuitive
to
use,
and
we
hope
that
makes
deployment
in
general
much
more
pleasant
at
your
lab.
That's
all
from
the
op
section.
I'll
turn
it
over
to
Josh.
Bore
enablement,
highlights.
F
Thanks
Kevin,
those
are
some
exciting
improvements
coming
to
our
deployment
section
in
particular,
I,
always
love
approval
rules,
workflows
and
making
those
easier
for
the
name
of
it
section.
We
also
have
a
number
of
exciting
improvements
like
everyone.
These
are
just
a
small
subset
of
what
we're
working
on.
F
So
please
do
check
out
Direction
pages
and
kickoff
videos
for
more
details
on
what
we're
working
on,
but
with
that,
let's
go
ahead
and
get
kicked
off
here
with
gitlab
hosted
first
and
our
first
item
we're
working
on,
which
is,
we
are
working
to
further
encrypt
at
the
how
we
handle
passwords
in
particular
for
rails,
as
well
as
also
non-rails,
passwords
and
secrets
in
our
configuration
files
for
our
self-managed
deployments.
F
We
have
already
provided
further
encryption
options
for
things
like
the
ldap
password
and
we're
now
going
through,
and
also
promoting
options
to
further
encrypt
other
things
like
incoming
email,
passwords
and
outgoing
email
passwords,
and
things
like
that
as
well.
So
with
that,
we
are
also
moving
on
towards
further
improvements
on
our
giddly
cluster
service.
F
So,
looking
forward
to
this
Improvement
to
significantly
improve
our
daily
cluster
service
for
everyone,
but
also
our
SAS
services-
and
this
is
also
another
item
there.
On
further
improvements
with
raft
and
moving
on
towards
our
database
group,
we
are
working
towards
improving
our
support
for
partitioning,
in
particular.
F
The
first
tables
we
are
up
here
on
purchasing
themselves
are
our
CI
cables,
as
you
can
see,
and
this
is
to
provide
the
CI
team
with
improved
tooling
to
help
them
go
ahead
and
actually
split
these
tables
out,
as
they
have
grown
quite
large
on
gitlab.com,
but
also
for
many
of
our
customers.
Utilize,
a
lot
of
pipelines
as
well
from
there.
F
We
can
move
on
to
our
improvements
to
our
ux
workflows
and
in
particular,
we
are
quite
close
on
adding
search
filtering
by
programming
language
to
improve
our
code
search
experience
and
help
you
narrow
down
potential
options.
We
are
quite
close.
The
back
end
portions
are
already
done
in
fact,
and
now
we're
going
through
and
adding
in
the
front
end
and
making
sure
it's
available
for
our
customers
to
utilize.
So
you
can
see
what
this
will
look
like
here
in
the
screenshot.
F
I
am
really
excited
for
this
Improvement
to
come
and
furthering
our
left
hand,
navigation
here
by
adding
additional
filtering
options,
which
is
quite
exciting
from
there.
We
also
are
working
on
indexing,
additional
content,
in
particular
the
all
users
list.
So
right
now,
when
you
at
mention
someone,
sometimes
it
can
be
kind
of
slow
and
we're
going
to
go
through
and
actually
add
this
to
the
essay
search
index.
F
So
it
can
be
much
much
quicker
and
provide
a
much
faster
experience
with
app
mentioning
people
or
otherwise
trying
to
find
users
within
the
platform
from
there
transitioning
over
to
more
of
the
maintenance
work.
Here
we
are
moving
projects
and
wikis
over
the
cell
service
framework.
These
are
the
last
two
we
have
to
go
through
and
do
we've
been
working
on
these
for
some
time
and
overall,
this
will
just
make
the
overall
Geo
service
much
more
maintainable
and
a
lot
of
the
crypto
go
more
quickly
in
the
future
and
Implement
further
improvements
faster
from
there.
F
We
are
also
working
to
have
upgrade
a
Ruby
version
to
3.0
Ruby
Richard
S7
will
no
longer
maintained
in
next
year,
and
so
we
want
to
go
ahead
and
actually
make
sure
we're
on
Ruby
3.0
before
that
happens,
and
so
our
performance
team
here
is
working
on
this
to
help
make
sure
we
can
coordinate
this
road
across
the
platform
and
have
it
go
smoothly
and
also
realize
the
benefits
of
Ruby
3.0
as
well
from
there.
F
We
are
also
continuing
our
work
on
investigating
the
in
general
memory
usage
of
Puma,
which,
as
you
can
see
here,
can
grow
over
time
and
what
we're
doing
here
is
improving
the
tooling
available
to
understand
how
Puma
operates
in
production,
and
we
have
most
of
this
done
and
now
we're
working
on
left
here
is
adding
the
option
to
upload
those
reports
out
to
storage.
So
they
can
be
read
later.
F
You
know
from
a
Production
Service
like
gitlab.com
here,
and
this
will
allow
us
to
get
a
better
idea
of
what's
Happening
Here
and
how
to
make
further
improvements
to
Puma
over
the
next
couple
of
months
and
years
and
from
there.
The
final
item
is
that
we
are
actually
wrapping
up
and
I'll
hand
it
over
here
to
David
to
take
us
home
on
the
rest
of
or
sorry
Justin,
on
the
wrap
up
our
kickoff
here
thanks.
A
Thanks
Josh,
we
can
hand
it
to
David
too
and
see
if
he
responds,
but
no
thanks
thanks.
Everyone
for
presenting.
A
We
are
running
out
of
time
on
the
call
today,
so
I'm
only
going
to
highlight
a
couple
features
but
I
do
encourage
you
to
check
out
our
release,
kickoff
page,
to
learn
more
about
all
the
great
things
the
team's
working
on
this
coming
Milestone,
but
on
a
couple
highlights
for
GitHub
gitlab
hosted
first
I'm
excited
about
the
rap
based
decentralized
architecture
of
daily
cluster
and
then
what
Melissa
articulated
around
all
of
the
web
hook
improvements
we're
making.
A
So
those
are
great
for
key
workflow
usability,
search
filtering
by
programming
language,
the
ml
model
exploration,
work
for
that
AI
assist
single
Engineering
Group.
That
Taylor
mentioned
all
the
license.
Finder
work
that
Hillary
went
over
is
super
exciting
in
addition
to
the
browser-based
dast
general
availability
to
do
is
for
Access
requests.
I've
heard
that
from
our
customers
many
times,
and
so
that's
a
great
quality
of
life
Improvement
for
anyone
who's
an
owner
of
a
group
and
gets
lots
of
requests
for
Access
user
search
index.
A
I
just
added
this
one,
but
I
run
into
that
all
the
time.
So
that's
going
to
be
a
great
Improvement
when
you
can
make
filtering
or
searching
for
for
users
and
mentions
much
much
faster
for
extender
lead
in
CI
CD,
the
Improvement
to
storage
management
and
storage
calculations
for
packaging
container
Registries
incident
tags.
Mvc
I
wanted
a
special
shout
out
to
observability
group
and
the
work
they're
doing
to
improve
error
tracking
on
top
of
the
open
Beta.
Those
first
foundational
features
for
the
next
Runner
token
architecture
is
a
bunch
of
great
work
there.
A
The
front-end
access
to
kubernetes
apis
through
casts
and
then
finally
improvements
to
environments,
page
and
deployment
approval,
so
lots
of
great
work.
This
coming
Milestone
again
special
thanks
to
all
the
presenters
today
walking
us
through
the
plans
for
for
this
Milestone,
and
thank
you
to
everyone
on
the
call
watching.
Like
I
said
you
can
check
out
their
release,
kickoff
page
to
learn
more
details.
Alright,
thanks.