►
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
Hey
everyone
welcome
to
our
release,
kickoff
for
milestone
15.4.
My
name
is
david
disanto.
I
lead
product
here
at
gitlab.
I
will
be
your
mc
today
for
the
live
stream
last
month,
justin
ferris
filled
in
for
me
and
a
big
thank
you
to
him
for
doing
so.
Unfortunately,
he
set
the
bar
a
lot
higher.
So
hopefully
I
can
live
up
to
his
example.
A
Today,
I'm
joined
by
some
of
the
members
of
our
awesome
product
team.
They
are
in
the
order
they
will
be
presenting
kenny
johnston,
senior
director
of
product
for
our
ops
and
analytics
sections
and
he'll,
be
providing
our
ops
section,
update,
josh
lambert,
director
of
product
for
our
enablement
and
sas
platform
sections,
and
he
will
be
providing
updates
for
our
enablement.
Section,
melissa,
oshkerkov
group,
product
manager
for
our
plan
and
ecosystem
stages
will
be
providing
our
updates
for
the
dev
section.
A
Derek
ferguson,
senior
product
manager
for
secure
dynamic
analysis
we'll
be
providing
our
updates
for
the
sec
section,
and
then
taylor,
mccaslin
group,
product
manager,
for
our
model,
ops
and
anti-view
stages
will
bring
us
home.
With
updates
from
the
model
ops
section,
we
are
focused
on
delivering
value.
Iteratively,
with
a
focus
on
our
fy23
product
investment
themes,
those
are
get
live,
hosted
first,
which
does
not
mean
gitlab
hosted.
Only
gitlab.com
is
the
largest
self-known,
our
largest
known
self-managed
deployment.
It's
a
little
bit
clearer
for
you
and
we
know
that
we
can
meet
the
needs
of
gitlab.com.
A
A
We
can
drive
multi-stage
adoption,
which
provides
more
value
to
the
user,
and
our
final
theme
is
extend
our
lead
in
ci,
cd
devops
doesn't
end
until
applications
are
deployed
in
production,
and
we
want
to
make
sure
that
as
seamless
and
frictionless
as
possible,
before
I
hand
it
over
to
kenny,
I
do
want
to
go
over
our
short
public
service
announcement
on
this
live
stream.
We
will
be
discussing
our
product
roadmap,
which
does
include
upcoming
features
and
functionality.
A
It's
important
to
note
that
the
information
presented
is
for
informational
purposes.
Only.
Please
don't
rely
on
it
to
make
purchasing
or
planning
decisions.
We
plan
very
ambitiously
here
at
gitlab
and
all
details
discussed
on
this
live
stream
today
are
subject
to
change
the
timing
of
any
products,
features
and
functionalities
at
the
sole
description
gitlab.
B
Awesome
thanks
david.
Let
me
go
ahead
and
share
my
screen:
real,
quick
okay,
so
my
name
is
kenny.
I'm
the
product
leader
covering
the
ops
section,
the
off
section,
is
comprised
of
verify
package
release,
configure
and
monitor
stages
at
gitlab.
We
seek
to
enable
rapid
adoption
of
ops
best
practices
by
providing
an
amazing
developer
experience,
while
providing
enterprises
with
the
tools
they
need
to
ensure
that
that
happens
efficiently
and
safely.
B
I
was
I'm
going
to
highlight
one
really
exciting
initiative,
that
is
about
extending
our
lead
in
ops
and
then
four
upcoming
features
for
improving
key
workflows
in
the
ops
section.
So
the
first
one
I'm
super
excited
to
showcase
this.
Many
of
you
know
that
gitlab
has
a
very
robust
incident
management
capability
that
includes
both
escalations,
instant
timelines,
which
we
recently
added
the
ability
to
manage
instances
themselves
and
alerting
based
on
you
know,
ingesting
of
performance
alerts,
all
really
exciting
stuff.
B
There's
a
key
part
of
that
workflow
that
we
have
not
yet
invested
heavily
in
that
we're
going
to
over
the
next
couple
of
releases,
and
that
is
an
instant
workflow
via
slack.
So
most
organizations
who
are
responding
to
instance
are
doing
so
in
slack
and
so
we're
going
to
build
a
really
great
experience
where
we
connect
your
single
source
of
truth
for
the
incident
from
git
lab,
with
the
ability
to
collaborate
directly
in
slack.
So
that
is
starting
with
technical
investigation
in
the
15-4
release.
B
But
we're
going
to
be
adding
capabilities
like
the
ability
to
use
a
slash
command
to
declare
an
incident
directly
within
slack.
That
will
create
an
incident
and
populate
it
with
the
important
links
that
you
reference,
including
the
incident
slack
channel
right
in
your
gitlab
single
source
of
truth
and
then
the
ability
to
have
kind
of
bidirectional
communication
where
in
gitlab
you
can
add
a
comment
and
add
a
specific
slash
command
like
this
slack
incident
example
here,
and
that
comment
will
post
to
slack
and
vice
versa.
B
B
The
first
is
making
it
easier
to
understand
and
differentiate
the
types
of
pipelines
you're
using,
so
gitlab
has
standard
pipelines
that
are
triggered
from
commits
and
then
what
we've
called
detached
pipelines
that
are
often
triggered
from
changes
in
merge
requests
and
are
especially
common
when
you
use
merged
trains.
So
those
can
be
both
the
merge
train
pipeline
that
is
pre-merging.
Your
merge
request
into
master
and
the
one
that
actually
performs
the
merge
after
you
hit
merge
on
a
merge
request.
B
Those
have
all
kind
of
universally
been
labeled
as
detached
when
viewing
your
pipelines
in
the
pipeline
view.
We're
going
to
start
differentiating
them
between
merge,
request,
merge,
result
and
merge,
train
pipelines
so
that
users
can
easily
find
the
pipeline
associated
most
associated
with
an
exact
merge
request
that
they're
interested
in
super
excited
and
a
highly
requested
feature
that
will
provide
clarity
when
reviewing
various
pipelines
in
your
projects.
B
Next
we're
going
to
be
surfacing
the
custom
variables
that
you
add
to
manual
jobs
when
you
run
them
manually,
so
in
gitlab,
for
for
a
long
time,
you
have
been
able
to
trigger
manual
jobs
from
specific
pipeline
definitions
and
also
supply
custom
variables
into
those
jobs,
so
that
you
can
manually
say
these
are
the
variables
that
I
want
to
inject
into
this
job
definition
and
execute
it.
B
What
you
haven't
been
able
to
do
necessarily
is
then
go
back
and
change
the
variables
that
you
have
submitted
or
understand
which
variables
you
did
submit
when
reviewing
the
job
itself,
as
it
processes
we're
going
to
be
adding
in
15.4
the
ability
to
use
this
drop
down
in
retrying
the
job
to
not
just
retry
it,
but
also
update
the
variables,
and
when
you
update
the
variables,
you
also
get
a
view
of
what
variables
were
used
when
you
transacted
the
job
in
the
first
place.
B
In
the
release
section
we're
going
to
be
adding
the
ability
to
search
for
environment
names,
our
environments
page
are
becoming
heavily
utilized
with
organizations
creating
an
increasingly
number
an
increasing
number
of
environments,
and
so
we'll
be
adding
the
ability
to
easily
search
for
a
specific
name
within
that
environment
view.
So,
for
example,
if
you're
looking,
you
only
want
to
look
at
the
review.
B
Apps,
you
can
drill
down
to
just
filtering
your
view
of
environments
to
just
those
environments
that
are
created
for
review,
apps
and
then
the
last
two
are
last
one
is
about
improving
our
artifacts
table.
So
today
your
pipeline
can
generate
pipeline
artifacts,
but
it's
difficult
sometimes
to
triage
those
pipelines
to
understand
if
they
should
be
deleted
or
to
understand
what
actually
triggered
the
specific
pipeline
artifact,
what
pipeline
commit
user,
and
so
it
we're
going
to
be
improving
that
experience
by
adding
a
lot
more
information
to
our
pipeline
artifacts
view
in
this
tab.
B
So
you
can
see
things
like
the
number
of
artifacts
generated
by
a
specific
pipeline,
the
branch
that
it
was
created
from
that
the
pipeline
was
created
from
the
commit
and
the
creator
and
the
user
of
of
that,
the
creator
being
the
specific
user
who
triggered
that
pipeline.
So
this
will
really
improve
your
ability
to
triage
artifact
pipelines,
find
specific
ones
from
specific
pipelines
and
make
decisions
about
which
ones
might
need
to
be
saved
or
reviewed
or
deleted.
B
C
Thanks
kenny,
those
are
really
exciting.
Looking
forward
to
those
arriving
on
our
product
later
this
month
or
next
month,
I
should
say
so.
I'm
josh
lambert
again
going
to
take
us
through
the
enablement
highlights
and
we
will
start
off
with
github
hosted
first
for
this
year,
real
quick
off
the
top
we'll
be
working
on
a
fair
bit
of
compliance
related
work.
C
This
release
as
well,
but
with
that
said,
we
can
jump
into
additional
first
work
as
well,
and
the
big
one
for
geo
is
that
we
will
be
continuing
continuing
to
shift
more
of
our
existing
kind
of
bespoke
replication
code
for
projects
wikis
and
also
container
registry
over
into
the
cell
service
framework.
This
is
to
get
rid
of
the
kind
of
bespoke
one-off
code
that
replicates
them
and
moving
more
towards
the
framework
where
we
can
get
a
lot
more
velocity
and
maintenance
benefits
as
part
of
our
investments
there.
C
So,
looking
forward
to
that
and
being
able
to
again
consolidate
our
code
base
here
and
we're
also
on
the
database
group
side
looking
to
support
our
partners
over
in
ops
and
supporting
our
ci
partitioning
effort
and
in
particular
we
are
working
on
focusing
on
making
our
tools
that
we
offer
to
teams
within
get
lab
and
our
broader
community
to
better
be
able
to
partition
the
tables
that
they
are
responsible
for.
And
so
you
can
see
a
bit
of
work
here.
C
We
have
in
flight
for
helping
to
make
sure
we
improve
those
petitioning
tools
and
we're
working
very
closely
with
the
ci
team
to
make
sure
if
we
identify
gaps.
We
also
address
them
in
real
time,
as
we
need
them
to
make
sure
the
effort
moves
forward.
So
I'm
looking
forward
to
that-
and
that
is
our
main
philosophy.
First
work
and
we
are
moving
on
into
key
workflow
usability
and
the
big
one
for
us
is
we'll
be
continuing
to
work
towards
moving
towards
vertical
navigation
for
our
global
search
experience.
C
So
right
now
you
have
a
horizontal
kind
of
tabbed
bar,
which
is
not
very
flexible,
and
we
are
moving
towards
a
more
dynamic
left
rail
side,
navigation
which
a
lot
of
you
are
probably
familiar
with
in
many
other
products.
So
really
excited
about
this
and
we'll
be
doing
this
again
to
kind
of
spread
the
foundation,
but
also
then
be
able
to
build
on
it
by
offering,
for
example,
the
ability
to
filter
by
language
on
code,
search
and
so
you'll
be
able
to
see,
for
example,
how
many
different
language
files
you
have
and
results.
C
You
have
and
live
process
more
effectively
when
you're
looking
for
a
particular
type
of
result
here.
So
looking
forward
to
those
and
really
improving
that
search
experience
as
well.
C
In
doing
so,
we
are
working
on
the
memory
team,
which
is
now
called
the
application
performance
team
to
continuing
to
improve
how
we
can
investigate
puma
memory
usage,
and
so
in
particular
here
we
will
be
finishing
off
the
work
to
get
running
information
and
keep
dumps
off
of
our
kind
of
running
code
base
in
production.
So
we
can
actually
understand
how
things
are
behaving
under
various
workloads
and
production
use
cases,
and
then
they
can
better
tune,
our
optimizations
and
memory
utilization
over
time.
C
For
for
these
use
cases,
I
will
also
be
doing
adding
support
for
ubuntu
2204,
which
is
important,
because
the
current
release
of
lts
is
kind
of
you
know,
kind
of
trending
towards
duplication,
and
then
we
also
have
kind
of
wrapping
things
up
here,
improving
how
we
handle
secret
management
and
omnibus.
C
Now
this
isn't
a
problem
in
our
kubernetes
and
hybrid
offerings,
but
for
omnibus
oftentimes
there
can
be
some
secrets
that
are
in
the
configuration
files
and
we
are
working
towards
removing
those
and
so
we'll
be
going
through
and
making
sure
all
of
our
rails.
Passwords
are
migrated
over
into
our
secret
base
solution,
which
is
encrypted
and
then
we'll
also
be
working
towards
having
a
system
for
all
the
other
non-rails
passwords
like
postgres,
and
things
like
that
that
we
provision
and
configure,
but
necessarily
have
in
rails
as
well,
and
so
we're
looking
to
make
that
plug-able.
C
So
we
can
plug
into
your
own
secret
management
solution
for
those
who
self-manage
git
lab
for
something
like
vault,
so
looking
forward
to
making
this
an
overall,
better
experience
for
our
users
and
better
handling.
How
we
deal
with
secrets
on
that
particular
kind
of
vm
on
the
website
and
with
that
I'll
pass
it
over
to
melissa,
to
talk
about
dev.
D
Thank
you,
hi,
I'm
melissa,
I'm
representing
the
dev
section,
the
dev
section
is
made
up
of
manage
plan,
create
an
ecosystem,
and
I've
got
a
lot
of
exciting
stuff
to
share
with
you
for
15.4,
the
first
one
being
around
improving
the
onboarding
experience
for
skim
or
sso
provision
users.
This
is
a
line
to
our
git
lab,
hosted
first
theme
so
for
users
that
are
provisioned
by
a
group
and
the
group
has
a
verified
domain
associated
with
it.
D
D
I'm
also
excited
to
share
our
rollout
of
the
auto
disabled
webhooks
alert
features.
So
what
this
is
to
do
is
that
for
400
errors,
users
will
need
to
reconfigure
and
re-enable
web
hooks.
If
you
encounter
a
certain
number
of
errors
and
for
500
errors,
web
hooks
will
enter
a
cooldown
period
to
allow
the
system
to
come
back.
So
this
is
what
an
alert
will
look
like.
D
This
will
be
shown
to
project
owners
and
maintainers,
letting
them
know
that
there's
something
they
need
to
look
at
we're
going
to
improve
system
stability
with
this
feature
and
we're
also
going
to
be
giving
customers
confidence
that
their
web
hooks
are
functioning
as
expected,
and
then
this
theme
first
also
we're
going
to
be
improving
gitlab
pages
performance
by
rolling
out
internal
api.
Caching,
now
moving
on
to
our
theme
of
key
workflow
usability,
you
will
now
be
able
to
prevent
mrs
with
failed
status
checks
from
being
merged.
D
Previously,
mr
authors
could
see
the
result
of
status
checks,
but
they
could
merge
at
the
mrs,
regardless
of
the
results
now,
projects
can
be
set
up
to
optionally
block
on
this.
So
this
is
what
this
will
look
like.
It's
another
configuration
check
and
what
this
does.
It
allows
users
to
rely
entirely
on
external
status,
checks
to
approve
or
reject
the
mars,
based
on
their
custom
logic
or
results
from
third
party
tools.
D
This
milestone
will
also
be
introducing
the
option
to
manage
configuration
for
the
pipelines
must
succeed.
Settings
at
the
group
level
previously
this
was
only
available
at
the
project
level.
Doing
this
at
the
group
level
will
basically
allow
it
to
propagate
to
all
child
projects
and
is
aligned
with
our
story
of
giving
compliance
team
a
single
place
to
set
properties,
and
it
would
look
like
this
you'll
have
an
option
to
enforce
for
all
subgroups
and
projects
last
milestone.
We
introduce
tasks
and
for
issues.
D
D
D
D
E
All
right,
thank
you,
melissa
that
is
extremely
exciting.
There's
several
things
in
there
that
I
am
particularly
excited
for
all
right,
so
I'm
going
to
go
over
the
what
sec
has
coming
up
in
1504,
just
as
a
reminder
set
contains
the
protected,
secure
stages.
E
So,
looking
at
what
we've
got
in
15
4,
all
of
the
features
that
I'll
be
talking
about
fall
into
the
fy
23
product
theme
of
improving
key
workflow
usability,
so
first
off
in
the
protect
stage,
we'll
be
enabling
group
and
subgroup
level
scan
result
policies.
This
is
a
feature
that
I
know
a
lot
of
people
have
asked
for,
so
it
will
allow
you
to
set
a
policy
based
on
scan
result
at
the
group
level
and
have
that
applied
to
projects
in
that
group
rather
than
setting
the
policies
in
each
individual
project.
E
E
E
All
right
for
dynamic
analysis,
we'll
be
working
on
adding
graphql
schema
support
for
dust
api
and
api
fuzzing.
This
will
enable
incredibly
easy
configuration
when
testing
graphql
apis
by
automatically
using
the
schema
that's
already
available
in
the
repo,
also
for
on-demand
dash
api,
we'll
be
switching
our
analyzer
over
to
the
api
security
engine.
This
will
immediately
enable
a
lot
of
functionality
that
was
previously
missing
on
on-demand
desk
api
scans,
such
as
graph
scanning
graphql
apis
and
using
postman
collections
to
configure
the
test.
E
Switching
that
analyzer
over
will
also
pave
the
way
for
us
to
release
our
api
security.
Analyzers
ga
been
a
lot
of
improvements
in
this
analyzer
and
we're
excited
to
use
it
by
default
for
all
of
the
api
scans
and
then
finally,
we'll
be
continuing
work
on
the
browser-based
das,
active
vulnerability
checks
and
now
that
we've
released
all
of
the
existing
passive
checks,
we're
moving
on
to
the
active
checks
and
plan
to
release
those
throughout
the
next
few
milestones,
all
right.
That
is
all
for
sec
in
154.
So
now
on
to
taylor
for
model
ops,.
F
Hi
everyone,
my
name
is
taylor.
Mccaslin,
I'm
representing
our
model,
ops
section.
I
want
to
cover
a
couple
of
different
areas:
the
first
one
being
applied
mml
for
that
we're
approaching
our
release
of
suggested
reviewers.
So
we're
going
to
release
this
in
14
or
in
15.4.
F
This
will
be
a
beta
feature,
but
this
is
our
first
machine
learning
powered
feature
at
gitlab.
This
creates
a
model
to
recommend
reviewers
based
on
the
code.
Changes
in
your
merge
requests
so
look
forward
for
this
for
ultimate
customers,
and
this
will
help
improve
key
usability
workflows
for
for
choosing
reviewers
for
a
merge
request.
F
F
If
you're
not
familiar
with
what
the
package
registry
is
capable
of
today,
it
has
a
capability
called
generic
packages
which
we're
exploring
extending
to
support
machine
learning,
capabilities,
azure
version
models-
you
can
push
them
into
a
generic
package
and
push
them
to
gitlab
and
use
the
package
api
to
push
and
pull
like
you
would
a
package
we're
excited
about
this.
We'll
also
add
support
for
managing
metadata
and
experiment.
F
F
The
incubation
team
is
looking
at
creating
a
hosted
version
of
the
open
source
project
ml
flow
and
making
that
available
to
gate
lab
registered
users.
So
look
forward
to
this
experimental
feature
if
you
use
mlflow,
definitely
participate
in
this
epic
and
help
give
our
incubation
engineers
some
direction
and
then,
finally,
I
want
to
talk
about
a
new
section
that
we
haven't
previously
talked
about,
which
is
our
anti-abuse
section.
F
This
is
really
about
protecting
gitlab
instances
from
user
behavior.
That's
this
that
disrupts
productivity
and
an
organization's
ability
to
build
and
deploy
code.
One
thing
I'll
say
here
is
that
we
don't
talk
about
a
lot
of
the
details
here,
because
we
don't
want
to
tip
off
any
abusers
of
what
specifically
we're
doing
to
thwart
their
nefarious
activities,
but
we
are
introducing
a
new
capability
to
ban
users
at
the
group
level.
F
This
is
new
for
gitlab.com
you'll.
Be
able
to
ban
and
unban
users
if
you're
an
admin,
this
will
also
tie
into
some
new
functionality
that
we'll
be
releasing
in
15.4.
That
will
allow
organizations
to
automatically
block
users
who
take
certain
actions
on
the
platform
that
they
have
deemed
inappropriate
or
nefarious.
A
A
First,
there's
really
a
lot
of
great
work
being
done
by
the
geo
team
looking
to
continue
to
make
progress
on
moving
projects
and
wikis
the
self-service
framework,
as
well
as
registries
on
key
improved
key
workflow
usability,
make
it
easier
to
distinguish
merge,
request,
pipelines,
surface
use
variables
when
retrying
jobs,
the
options
and
the
updates
that
josh
gave
around
global
search
is
really
cool,
as
well
suggested
reviewers
getting
fully
integrated
into
the
ui
das.
A
Api
and
api
plus
testing
supporting
graphql,
also
really
cool
ci
on
the
ca
team,
the
composition
analysis
working
on
building
out
the
needs,
the
needed
infrastructure
to
support
continuous
vulnerability
scanning
switching
over
having
group
and
subgroup
scanned
result
policies,
I'm
making
it
easier
and
making
progress
to
introduce
things
like
iterations
and
milestones
for
work
items.
Also,
really
cool
tasks
is
amazing
if
you've
not
seen
it,
please
go
play
with
it.
A
It's
really
cool
being
able
to
block
merging
if
a
failed,
stash
check
happens
and
then
finally,
things
like
support
autocomplete
suggestions
in
the
content,
editor
and
then,
finally,
with
the
externally
nci
cd,
introducing
the
incident
workflow
to
the
gitlab
slack,
app
very
cool
being
able
to
have
comparative
reports
on
the
dora
metrics,
as
well
as
improvements
to
how
you
can
run
reports
with
a
date
range
picker
again.
Just
a
couple
of
the
highlights.
A
Please
check
out
the
release,
kickoff
page
for
the
full
list
of
items
that
we
discussed
today
and
please
like
and
comment
on
the
issues
the
team
highlighted
today.
It's
the
best
way
we
can
engage
with
you.
This
is
going
to
be
our
best
release.
Yet
I
know
I
say
that
every
time,
but
I
feel
like
this
one's
going
to
be
the
best
one.
So
thank
you,
everyone
for
watching
and
join
the
release
kickoff
and
have
a
great
day.