►
From YouTube: 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
We
also
want
to
focus
on
improving
our
key
workflow
usability.
This
will
include
things
like
our
enterprise
planning
workflows,
including
our
workspace
initiative
and
work
items,
providing
an
intuitive
settings
and
navigation
experience
and,
of
course,
continuing
to
improve
and
provide
an
intuitive
and
pleasant.
Merge
request
experience.
A
A
A
B
Thanks
david,
my
name
is
sarah
wellner
and
I'm
the
group
manager
for
the
create
stage
here
at
gitlab,
I'm
going
to
cover
the
14.9
milestone.
Kickoff
highlights
for
the
dev
section,
starting
with
the
manage
stage
we're
going
to
see
api
support
added
for
two
final
of
the
door:
four
metrics
a
little
bit
of
background
door.
Four
metrics
are
key
metrics
that
have
become
industry
standard
for
some
companies
for
measuring
devops
success.
B
Adding
support
for
these
va
api
allows
external
tools
to
pull
gitlab
for
that
data
for
extraction
and
manipulation
analysis
elsewhere.
The
support
we're
adding
are
for
the
two
metrics
time
to
restore
service
and
change
failure.
Rate
time
to
restore
service
is
measured
in
median
time
needed
to
close
production
incidents
across
an
environment
and
the
second
change
failure
rate
is
represented
as
a
percentage
of
the
changes
released
to
production
that
resulted
in
a
degraded
experience
for
users.
B
B
Next
up
usability
improvements
for
the
github
importer,
so
tying
back
to
one
of
the
key
themes
for
the
year
when
importing
large
projects
from
github,
which
can
take
minutes
or
perhaps
hours
in
some
scenarios
to
complete
the
user
is
left
without
any
context
to
the
progress
of
the
import.
When
it's
completed
today,
the
user
simply
gets
a
message
that
says
this
is
complete
or
it
has
failed.
B
We
don't
provide
any
insight
into
whether
or
not
everything
was
successful,
or
what,
in
this
scenario,
failed
we're
adding
visual
indicators
to
give
you
a
sense
of
the
progress
of
the
import
over
time
and
then
the
elements
that
are
part
of
the
import
and
where
they
are
in
their
status.
This
gives
you
a
lot
more
helpful
information
in
terms
of
troubleshooting
when
things
are
taking
a
long
time
or
something
did
not
complete
and
finally,
from
the
compliance
group,
we
are
transforming
the
compliance
dashboard
into
an
interactive
whoops.
B
Pardon
me
into
an
interactive
report
to
help
compliance
managers
better
review,
triage
and
prioritize
which
violations
their
team
is
to
work
on.
Let's
take
a
look
at
the
changes
that
are
coming
up.
The
violations
are
going
to
be
displayed
in
an
organized
list.
You
can
sort
by
severity
with
the
addition
of
an
icon
that
gives
you
immediate
indication
of
what
you
should
spend
time
on.
B
B
B
B
B
B
The
source
code
team
is
going
to
be
working
to
bring
our
source
code
management
product
up
to
par
for
fips
compliance
in
line
with
the
ultimate
goal
of
making
all
of
get
lab,
fedramp
compliant
and
finally,
key
workflow
usability
element
coming
at
us
from
the
editor
group,
we'll
be
adding
a
new
setting
for
group
wikis
at
the
group
level
to
be
able
to
toggle
these
on
and
off
we're
familiar
with
the
settings.
Look
like
this
is
going
to
appear
under
permissions
and
group
features
and
you'll
be
able
to
disable
or
enable
it
at
your
leisure.
C
Thank
you
and
sarah.
That
sounds
like
some
great
stuff,
that's
coming
from
dev
in
14.9,
so
I'm
derek
ferguson
and
I'll
be
covering
the
sec
section,
and
we've
got
a
lot
going
on
in
14.9
and
you'll
see
that
the
main
theme
for
sec
in
this
milestone
is
improving.
Key
workflow
usability
you'll,
see
that
reflected
across
multiple
groups
in
our
section
so
getting
started
for
the
container
security
group.
C
We
plan
to
continue
working
on
scan
result
policies,
including
ux
and
ui
enhancements,
specifically
we're
working
so
that
security
approval
policies
can
be
viewed
together
in
the
same
location
as
the
merge
request.
Approval
rules
additionally
we'll
be
preparing
a
migration
script.
That'll
run
as
a
part
of
the
upgrade
to
get
lab
15.0
to
automatically
migrate
any
remaining
vulnerability
check,
rules
to
security
approval
policies.
C
In
addition
to
this,
we
plan
on
introducing
a
ui
to
easily
enable
container
scanning
via
merge
request.
This
is
going
to
follow
the
same
workflow
that
we
already
have
in
place
for
sas
and
dependency
scanning
all
right.
Moving
on
to
the
threat
insights
group
they're
going
to
continue
their
work
on
the
integrated
security
training.
This
feature
will
provide
a
simple
and
unobtrusive
way
to
access
highly
relevant
training
materials
from
our
partners.
This
is
going
to
improve
the
mr
experience
by
embedding
links
to
short,
interactive
security
training
exercises
directly
from
the
vulnerability
findings.
C
All
right
for
dynamic
analysis,
we'll
be
making
sure
that
all
of
the
das
specific
vulnerability
details
are
added
to
issues
created
from
vulnerabilities
found
by
das
scans.
So,
details
like
the
method,
url
request
and
response
are
going
to
be
shown
now
within
these
created
issues,
we've
talked
about
our
new
browser-based
das,
analyzer
in
multiple
releases
and
in
14.9,
in
addition
to
working
on
the
stability
and
performance
of
the
browser-based
spider,
we'll
continue
our
work
on
building
more
passive
browser-based
vulnerability
checks,
and
this
is
going
to
bring
us
much
closer
to
being
able
to
default.
C
Our
das
scans
to
the
browser-based
analyzer
in
a
future
release
all
right,
adding
on
to
what
we've
already
done
to
increase
the
speed
of
the
api
security
scanner,
we're
going
to
continue
to
add
speed
improvements
for
api
security,
to
provide
a
better
and
quicker
scanning
experience
and
finally,
for
coverage.
Guided
fuss
testing
will
start
working
to
support
coverage-guided
fuzzing
on
open
shift,
all
right.
C
Moving
on
to
composition,
analysis
within
composition,
analysis,
we'll
continue
working
on
the
mvc
for
showing
the
paths
to
dependencies,
and
in
this
milestone
we
will
continue
work
to
show
one
introduced
package
on
the
finding
details.
Page
we'll
be
continuing
working
on
this
mvc
to
build
out
this
feature
over
the
next
few
milestones
for
license
compliance
we'll
continue
work
in
14.9
to
find
a
replacement
for
our
current
analyzer
and
finally
for
static
analysis.
C
Streamlining
the
set
of
analyzers
will
also
enable
faster
iteration,
better
results
and
greater
efficiency.
In
addition
to
all
of
this,
we've
got
multiple
deprecations
and
removals
coming
up
across
the
board,
insect
and
15.0.
So
in
order
to
be
ready
for
this,
we'll
be
working
on
all
of
these
items
in
14.9,
and
with
that
I
will
hand
it
over
to
jackie
to
cover
the
ops
section.
D
D
The
op
section
contains
five
different
stages:
verify
package,
release,
configure
and
monitor
and
really
owns
all
the
experiences
to
effectively
leverage
configuration
and
operation
tasks
in
gitlab.
I
can't
cover
all
the
great
things
that
the
team
is
doing
in
14.9,
so
please
take
a
moment
to
check
out
the
direction
pages.
D
Just
like
david
said,
we'll
be
covering
three
main
themes
from
fiscal
year.
23
in
this
kickoff
first
up
will
be
an
issue
from
our
runner
team
in
the
verify
stage.
This
is
about
extending
our
lead
in
cicd
and
it's
a
spike
from
the
team
to
seamlessly
enable
generation
provenance,
as
required
by
the
salsa
framework.
This
issue
is
helping
us
enable
the
secure
supply
chain
direction
inside
of
git
lab
and
really
will
help
ensure
integrity
of
software
creation
from
beginning
to
end.
At
least
the
investigation
for
it.
D
The
team
will
be
looking
to
support
the
registration
of
agents
without
a
configuration
files
really
reducing
the
overhead
or
the
management
of
configuring.
Your
kubernetes
agent
transitioning
to
our
second
theme,
gitlab,
hosted
first,
we'll
be
focusing
on
driving
gitlab.com
now
and
accomplishing
our
99.95
availability
target.
First
up
is
an
issue
from
our
verify
pipeline
execution
team,
which
is
about
implementing
ci
cd
time
decay
in
14.9,
we'll
be
really
focused
on
thinking
about
how
to
partition,
ci
cd
data
to
improve
the
availability
and
performance
of
gitlab.com
sas
offering.
D
Additionally,
across
the
ops
section,
all
teams
are
prioritizing
several
optimizations
for
various
endpoints
that
have
errors
are
taking
a
long
time
to
respond
in
order
to
improve
our
air
budgets
and
ultimately
increase
the
availability
of
our
groups.
We're
really
excited
to
see
our
product
teams
continue
to
improve
toys.
The
improvements
to
scaling
last
step
is
a
theme
around
improving
usability
workflows.
D
Our
pipeline
authoring
team
has
been
hard
at
work
and
thinking
through
how
to
help
users
trigger
and
retry
jobs
across
multiple
projects
or
even
within
the
same
project,
and
today,
if
you
want
to
retry
a
specific
job
or
re-trigger
a
downstream
pipeline,
you
must
go
to
each
individual
pipeline
and
retry
it.
This
enhancement
14.9
will
enable
users
to
effectively
retry
their
trigger
jobs
and
downstream
pipelines
for
one
screen.
This
will
really
save
a
ton
of
time
for
those
who
have
a
bunch
of
downstream
pipelines.
D
Next
up
a
core
workflow
across
gitlab
is
the
verify
and
create
teams
working
together.
This
is
seen
in
merge,
request,
pipelines
and
merge
trains.
One
investment
that
the
verify
stage
is
going
to
be
working
on.
Will
be
improving
the
learnability
of
different
kinds
of
pipeline
types
today,
you'll
see
detached
pipeline
labels
in
git
lab.
This
can
be
really
confusing
because
there's
multiple
flavors
of
detached
pipelines,
including
merge
requests,
pipelines,
merge,
result
pipelines
and
merge
train
pipelines.
D
D
Is
this
test
summary
view,
as
well
as
the
metrics
view,
which
will
enable
you
to
seamlessly
interpret
and
view
these
different
inputs
inside
of
the
mr
widget
as
we're
updating
it
to
be
a
conform
pattern
across
all
all
those
experiences
that
wraps
up
the
op
section
kickoff
for
14.9
and,
as
I
noted
earlier,
there
was
so
much
to
cover
in
our
team's
release.
So
please
take
a
moment
to
jump
over
to
those
pages
I'll
pass
it
over
to
josh
lambert
to
cover
the
enablement
section.
E
Thanks,
jackie,
those
are
some
really
exciting
changes
in
the
op
section
and
looking
forward
to
those
being
available
in
14.9
for
enablement
as
similar
to
jackie
and
the
others.
This
is
not
everything
that
we're
working
on,
and
so
please
do
look
at
the
at
the
kickoff
videos
and
the
related
ethics
and
issues
for
more
information,
but
we're
going
to
hit
the
highlights
here
for
gitlab
posted
first
and
also
a
little
bit
on
new
markets
as
well.
E
E
Overall.
This
should
result
in
increased
performance
for
gitlab
and
increased
scalability
for
all
users,
but
in
particular
on
gitlab.com,
which
is
the
largest
instance
that
we're
aware
of
from
there,
also
focusing
on
the
database.
We
are
working
towards
having
our
batch
bank
run,
migration
service
become
ga
or
the
default
migration
service
for
gitlab.com
in
particular,
and
get
that
overall.
E
The
reason
is
is
because
this
migration
service
is
significantly
better
than
the
default
rails
migration
service,
because
it
can
automatically
tune
itself
on
how
fast
to
run
and
it
can
be
stopped
and
restarted
as
needed
without
restoring
all
over
again
and
so
provides
a
lot
more
control
and
a
lot
more
tuning
to
result
in
migrations
being
completed
faster,
but
also
more
safely
for
the
overall
stability
of
the
service
and
so
we're
working
towards
a
couple
items
here
to
get
to
version
1.0
and
make
it
the
default
for
everything.
E
So
looking
forward
to
that
to
improve
the
stability
of
gitlab.com,
also,
on
the
database
front,
we
are
working
towards
reactively
controlling
how
much
the
database
can
change.
In
a
short
period
of
time.
We
have
seen
some
patterns
where
maybe
a
user
runs
a
lot
of
api
queries
that
make
changes
and
those
can
maybe
downstream
make
additional
changes
which
can
impact
the
overall
index
scan
performance
or
just
general
database
performance.
E
You
can
see
some
of
these
things
in
some
of
the
recent,
not
recent,
but
historically
some
of
the
incidents
we've
had
where
our
database
performance
was
degraded
below
what
we'd
like
and
took
some
intervention
to
recover,
and
so
this
will
allow
us
to
automatically
respond
within
the
code
base
and
self-heal
much
more
quickly
to
prevent
these
types
of
degradations
in
our
services
and
so
looking
forward
to
this
to
improve
the
overall
performance
and
kind
of
consistent
feeling
of
gitlab.com
and
get
lot
of
sas
services.
E
Shifting
away
from
database
over
towards
application
performance.
Our
memory
group
is
working
on
consolidating
and
providing
guidance
on
our
various
profiling
tools.
As
you
can
see
here,
we
have
a
lot
of
them
that
we
use
across
gitlab
and
we
want
to
make
sure
it's
clear
which
one
should
be
used,
which
one
should
be
used
when
and
then
help
improve
the
kind
of
smaller
subset
from
there
to
help
developers
improve
the
performance
of
gitlab
more
easily.
E
We're
also
working
to
continue
to
shift
out
our
application
exporters,
or
these
are
the
things
that
generate
metrics
to
tell
grafana
and
other
tools
how
gitlab
is
doing
and
we're
moving
them
out
of
the
processes
that
kind
of
serve
websites,
our
web
service
and
other
things.
So
this
provides
isolation
so
that
we
can
separate
kind
of
the
application
code.
That's
doing
work
to
the
application
code
that
is
emitting
metrics.
E
That
way,
if
you
have
a
problem
in
the
metrics
code,
it
doesn't
impact
our
ability
to
continue
to
run
the
service,
and
so
this
will
allow
us
to
have
improved
reliability
of
our
of
our
application,
all
right
so
shifting
away
from
kind
of
the
overall
performance
and
scalability
and
moving
on
towards
advanced
search.
We
are
working
towards
supporting
open
search
and
our
advanced
search
services.
E
This
will
allow
customers
to
use
open
search
instead
of
elasticsearch
if
they
would
desire,
but
also
it
allows
us
to
have
at
least
on
aws,
for
customers
to
utilize
the
amazon
open
search
service,
which
is
a
nice
easy
way
of
running
advanced
search
when
you
have
gitlab
running
on
aws,
and
so
this
is
a
great
tool
for
folks
to
more
easily
run
these
over
time
and
reduce
kind
of
the
maintenance
effort
of
get
lab
on
aws.
E
Also,
we
are
moving
the
commits
out
of
the
general
elastic
search
index
for
advanced
search
over
into
its
own.
This
will
allow
us
to
have
a
more
improved
performance
for
advanced
search
service.
We've
done
this
with
previous
index
content
types
like
notes
and
merge
requests
and
we've
seen
great
results,
so
we're
continuing
to
go
through
the
rest
of
our
data
types
to
improve
advanced
search
performance
as
well,
and
that's
it
for
get
lab,
hosted
first
and
moving
on
to
new
markets.
E
So
our
distribution
team,
along
with
much
of
the
rest
of
the
company,
as
you
have
already
heard,
is
working
towards
fips.
Compliance.
Distribution
in
particular,
is
going
through
our
container
images
and
our
audios
packages
and
doing
things
like
making
sure
you
can
compile
all
of
our
dependencies
against
openssl,
as
well
as
a
few
other
work.
E
We're
doing
here
in
this
milestone
again
pushing
towards
a
compliant
fip
service,
which
would
be
helpful
for
certain
markets
in
the
public
sector,
but
also
build
towards
fedramp,
which
we
have
a
working
group
now
focusing
on
and
last
but
not
least,
we
are
hoping
to
finish
our
red
hat
certification.
I've
talked
about
this
in
the
past
and
we
are
quite
close.
E
We
have
one
more
image
left
to
go
to
move
on
to
a
ubi
base,
image
or
kind
of
like
a
rail
based
image,
and
once
we're
done
with
that,
all
the
requirements
should
be
addressed,
and
so
we
are
very
very
close
to
finishing
up
here
and
looking
forward
to
getting
that
red
hat
stamp
of
approval
on
our
operator.
So
our
customers
can
be
confident
that
the
gitlab
operator
can
run
well
in
the
red
hat
openshift
environments,
and
so
that's
it
for
the
enablement
section
and
I'll
pan
it
back
to
david
to
wrap
us
up.
A
Josh
and
thank
you
all
the
presenters
for
another
great
kickoff
call.
There
are
so
many
great
things
that
were
highlighted.
I
can
only
write
down
a
couple,
as
the
presenters
talked,
the
ones
that
stood
out
are
the
improved
detail
status
on
the
github
importer
process
linking
issues
together.
So
you
can
see
when
things
are
related
or
blocked
by
other
efforts.
A
Scanned
result
policies
continue
to
get
better.
That's
a
big
ask
of
our
enterprise.
Customers
continue
to
migration
to
our
new
das
engine,
adding
approval
and
reject
comments
when
improving
manual
deployments,
also
very
cool
fuzz
testing
support,
with
an
open
shift,
regis
being
able
to
re-trigger
downstream
pipelines
a
lot
easier
support
for
agent
registration
without
full
configuration
and,
of
course,
the
stuff
that
just
just
josh
just
touched
on
that
was
a
tongue
twister.
A
For
me,
there
support
for
open
search
within
our
advanced
search,
improved
search
performance
and,
of
course,
everyone
working
together
on
fix,
140-2
compliance
and
the
red
hat
owner
operator
certification
for
a
full
list
of
everything.
Please
check
out
the
release.
Kickoff
page
also
make
sure
to
click
through
like
comment
on
the
related
issues
and
engage
with
the
team.
Thank
you.
Everyone
for
watching
and
joining
this
release
kickoff
and
have
a
great
day.