►
From YouTube: Q2 FY21 GitLab Product Release Update for Sales
Description
Brian Glanz with Product Marketing discusses the latest on key, sales-relevant highlights of GitLab 12.9–13.0 and related resources. Slides: https://tinyurl.com/y9vrdrot
A
Welcome
everyone,
I
am
just
sharing
my
screen
here.
We
are
looking
in
true
gitlab
fashion
at
the
gate,
lab
handbook,
in
fact,
even
truer
to
get
lab.
This
is
not
in
the
handbook.
Yet
it's
in
the
review
app
of
a
work-in-progress,
mr
that
will
be
merged
later
today,
adding
a
page
to
the
handbook
for
product
release
updates.
A
This
will
collect
not
only
today's
session
and
the
media
related
to
it,
but
things
like
the
13.0
launch,
the
version
12,
that's
12.0
through
12.10
year-in-review,
that's
a
blog
post
and
video
and
slide
deck,
and
things
that
you
could
consider
a
product
release.
Update
will
be
on
this
page.
I
will
actually
use
it
also
to
launch
the
deck
for
today.
A
Some
of
this
content
will
also
be
hand
booked,
but
you
know
not
all
of
it
fits
exactly
in
a
handbook
page
so
bear
with
us,
as
we
get
to
be
more
and
more
handbook
first
and
website.
First
we're
looking
at
three
releases:
12
9
through
13,
o
we'll
also
look
back
in
time
and
a
little
bit
ahead
and
there
will
be
a
lot
of
links.
A
We
did
this
three
months
ago,
looking
at
six
months,
and
this
particular
slide
was
really
popular,
so
I
actually
brought
it
back
and
updated
it.
So
we
were
looking
at
12
3
through
12
8
and
the
rapid
innovation
differentiator,
and
how
much
we
had
added
per
version
over
those
6
months
in
terms
of
significant
features
and
per
tier,
and
then
we
zoomed
out
just
a
little
bit
to
look
at
significant
new
features
and
improvements.
A
So
that
includes
things
that
are
really
important
like
performance
improvements,
but
that
are
not
technically
considered
features,
and
so
they
don't
get
framed
that
way
in
the
release,
blog
post,
they
are
in
the
post
they're
mentioned,
and
then
you
get
links
to
documentation.
So
it's
only
stuff,
that's
significant
enough
to
be
in
the
release
blog
post
that
feeds
the
visualizations
you're.
Looking
at
here
and
over
six
months
yeah
we
saw
well
that's
a
nice
lift.
We
were
actually
not
just
innovating
rapid,
but
we're
innovating
more
and
more
rapidly,
that's
cool.
A
But
what
if
you
zoomed
out
I
did
that
version
12
year
in
review
just
a
couple
weeks
ago,
and
when
you
look
at
12
months,
it's
like
wow,
it's
even
more
obvious.
We've
increased
the
speed
of
our
innovation
by
a
hundred
percent
over
the
12
months,
so
folks,
like
Mike
in
in
Tech
Talks
there.
They
feel
the
disturbance
in
the
forest
and
like
wow
this
it's
going
so
much
faster
than
it
used
to
even
a
couple
of
months
ago.
A
It
wasn't
this
fast
and
he
checks
the
data
and
sees
essentially
the
same
thing
slightly
very
slightly
different
numbers.
I
love
it.
When
people
look
at
things
in
multiple
ways
and
and
basically
get
the
same
result,
the
exact
number
like
860
over
a
year
that
doesn't
matter
as
much
but
the
ballpark
matters
in
the
trajectory
of
course
matters.
A
A
lot
there's
a
little
bit
of
pushback
I
got
from
last
quarters
a
product
release,
update
that
the
rapid
innovation,
differentiator
or
even
the
open-source
differentiator
are
a
little
bit
like
old
news
and
a
little
bit
like
they're,
just
holistic
right.
So
they're
they're
attributes
that
make
people
feel
good
about
doing
business
with
us
as
opposed
to
being
really
values
based
and
I
want
to
push
back
on
the
push
back
and
say
no
actually
I
think
those
two
things
are
hugely
important
in
addition
to
the
collaborative
customer
experience
because,
of
course
they
are
also
contributors.
A
A
lot
of
the
value
being
added
to
the
product
is
being
driven
from
those
community
contributions
for
the
version
12
year
in
review.
I
zoomed
out
over
three
years,
and
you
can
see
a
couple
years
ago.
As
version
10
closed,
we
were
getting
something
like
a
hundred
community
contributions,
merged
per
monthly
version
of
get
lab,
and
that's
now
up
a
hundred
percent
as
well,
what's
better
than
100
how
about
200
right.
A
So
we
have
an
incredible
amount
of
contributions
from
the
community
and
it's
not
old
news
in
the
sense
that
those
contributions
keep
going
up
and
to
the
right
while
our
own
generally
rapid
innovation
keeps
getting
more
and
more
rapid
as
well,
and
even
to
extrapolate
from
that.
That
number
860
occurs
to
me.
You
know
in
the
next
year,
if
I'm,
thinking
about
buying
gitlab
I'm,
not
just
buying,
what's
in
13.0,
right,
I'm
buying
the
opportunity
to
enjoy
a
thousand
significant
new
features
and
improvements
in
the
product
over
the
over
the
year
ahead.
A
So
it's
important
that
we're
not
only
selling
what's
in
the
product
right
now,
but
also
selling
this.
This
trajectory
that
we're
on
our
roadmap,
how
open
it
is
in
our
awesome
track
record
of
delivering
on
that
roadmap
heard
a
lot
of
people
make
that
point
in
QPR's
and
just
thought.
I'd
say
that
out
loud
in
this
update,
because
I
thought
it
was
really
valuable
point
as
well.
All
right,
I
have
some
slides
here
that
I'm
not
going
to
talk
a
lot
about,
including
the
double
flywheel
model
of
how
community
contributions
matter.
A
I
just
wanted
to
make
sure
that
they
were
in
the
deck.
So
if
you
wanted
to
look
at
the
speaker
notes
under
this
one
or
any
of
the
others,
you'll
find
lots
of
links
to
sort
of
give
some
more
background
for
some
of
what
I'm
saying
in
the
session
the
significant
features
added
again
over
six
months
and
then
zoomed
out
over
twelve
months,
even
just
in
terms
of
those
significant
new
features.
You
can
see
us
with
like
a
hundred
percent
more
rapid
innovation
than
even
a
year
ago.
A
Now
so
really
powerful,
stuff
I
think
all
pulled
by
the
way
from
publicly
available
data
sources
like
our
public
dashboards
for
community
contributions.
Things
like
that,
so
anybody
else
could
go
out
there
and
produce
the
same
visualization
or
an
equivalent
a
lot
of
what
I
pointed
to
a
quarter
ago
and
that
release
update
was
the
release
posts
and
I
was
a
little
bit
of
pushback
on
this
one.
From
just
a
couple
of
folks
who
said
those
are
super
long.
A
You
really
want
everybody
on
this
call
to
read
that
whole
release,
post
and
I
said
no
I,
don't
really
mean
read
the
whole
thing,
but
everybody
on
this
call
should
definitely
read
the
top
part,
and
so
I
actually
I
tried
to
screen
cap.
Even
the
twelve
nine
release
post,
it's
ridiculously
long
in
terms
of
trying
to
make
a
screen
cap
for
a
slide.
You
had
to
snake
it
around
right
to
get
it
all
on
there
and
yeah
there,
but
the
top
cart
is
just
500
words.
A
Take
you
five
minutes
to
read
product
marketing,
ghost
writes
it.
It's
very
values
based
the
you
know,
differentiators
the
use
cases
we're
working
on
the
buyer
personas
all
that
stuff
is
dancing
around
in
our
heads.
While
we
carefully
choose
those
words
that
are
useful
for
all
of
you
in
telling
the
story
not
only
of
this
release,
but
if
given
up
in
general,
so
definitely
read
that
and
I
also
said
you
should
all
read
the
key
features.
Three
months
ago
there
were
only
five
of
them
per
each
release.
A
That
is
now
like
a
dozen
or
even
a
little
bit
more
for
each
release.
We've
had
forty
I
think
over
the
past
three
months.
I
still
think
you
should
all
read
that
and
part
of
it
is
just
we're
releasing
so
much
more
every
month,
but
we're
also
double
clicking
on
that
and
trying
to
decide
whether
we
should
keep
a
lid
on
how
many
features
are
called
key
in
the
given
month.
A
Just
so,
you
know
that
is
a
little
longer,
but
all
that
content
is
written
by
folks
who
have
in
mind
this
basic
question,
not
just
in
terms
of
documentation.
How
does
this
work,
or
you
know
how
do
I
use
it,
but
what's
it
good
for
like
like
why?
Why
should
people
care
this
has
been
added
to
the
product,
and
so
that
should
shine
through
the
content
there
and
that's
what
this
is
all
about.
A
Of
course,
we're
here
to
talk
products,
but
in
terms
of
value,
so
I
say
that
not
just
because
it's
kind
of
fun
to
use
these
graphics
and
stuff,
but
because
we're
not
going
to
talk
about
a
lot
of
the
details
and
certainly
not
the
more
technical
aspects
of
what's
new
in
the
product.
There
is
a
lot
of
material
out
there
and
the
rest
of
my
slides
give
you
some
more
links
to
that
material.
Some
of
it's
gotten
really
really
good.
A
I
would
say
from
all
quarters
we're
actually
improving
on
the
material
we're
producing
about
our
product.
Since
three
months
ago,
the
field
flash
newsletter
was
launched,
and
it
does
exactly
what
I
just
said.
It
tells
you
what's
new
in
gitlab.
What's
in
that
release
blogpost,
but
per
value
driver
and
Monica
brilliant
job
with
this
in
the
whole
newsletter
read
the
whole
thing,
but
especially
to
this
part
of
it.
What's
get
labs
she's,
writing
it
with
the
PMM.
Who
is
the
messaging
lead
in
that
month?
A
A
So
you
get
an
email
version
and
a
slightly
scrubbed
version
is
then
up
there
in
the
handbook.
So
you
can
just
go
to
the
handbook.
Click
on
the
link
in
this
slide-
and
you
will
find
the
last
three
months
of
this-
and
this
is
what
it
looks
like
and
again
couldn't
advocate
for
it
enough.
It's
just
exactly
sort
of
what
we're
here
to
do.
A
A
You
know
entire
DevOps
lifecycle
delivered
in
a
single
application,
yep
it's
it's
it's
a
platform
for
everything
and
so
I
I
think
that's
actually
great
and
then
any
three
months.
We
should
have
at
least
a
few
significant
things
for
each
of
our
differentiators
for
each
of
our
value
drivers,
certainly
there
being
only
three
of
them,
and
that
was
just
kind
of
a
nice
validation
of
it.
It
wasn't
something
where
I
came
away.
Saying
boy
in
these
three
months
we
really
op
during
I
optimized
for
kubernetes.
You
know
not
so
much
so
that
doesn't
mean
nothing.
A
It
means
good
things,
I
think
in
twelve,
nine,
in
addition
to
just
linking
you
to
the
post,
which
which
again
is
the
the
real
authority
on
this
I
pulled
out
some
things
like
new
in.
Let
me
it's
one
of
my
UI
out
of
the
way
here:
new
and
ultimates:
more
efficient
vulnerability
management
on
security,
dashboards,
Auto
remediation
of
vulnerabilities
found
per
container
scanning
super
cool
to
have
Auto
remediation,
expect
more
of
that
kind
of
thing
and
get
lab
in
the
future.
A
So
I
pulled
some
things
out
under
these
slides,
but
really
you're
going
to
get
most
of
it
and
and
the
the
best
way
to
tell
the
story
from
the
post
itself.
That
stuff
gets
worked
on
not
only
by
really
great
folks
but
reviewed
by
everyone
up
through
the
leadership
of
the
company,
so
very
carefully
vetted
material
and
yeah
I've
pulled
it
out
here,
but
I'm
not
actually
going
to
talk
a
lot
about.
What's
on
these
slides,
we
all
can
read,
and
now
all
of
us
should
read
it's
in-house
posts.
A
The
version
twelve
year
in
review
is
something
I
also
would
point
to
I
put
it
together
myself
a
couple
weeks
ago.
This
would
take
you
straight
to
the
blog
post
version.
It's
an
easy.
Breezy
read
I
point
to
it,
partly
because
again
there
isn't
a
really
strong
narrative
if
you're
just
like
what
did
we
do
twelve
nine
to
13.0
write.
Those
three
versions
are
not
engineered
in
such
a
way
as
to
mean
something
as
a
as
a
group
of
three
and
I.
A
A
It
has
been
awesome
even
some
of
the
industry
news
posts
about
it
like
a
DevOps
comm
are
doing
better
than
most
of
the
posts
that
they've
ever
had
that's
great
news
that
it's
it's
so
popular,
not
even
just
on
our
own
website,
but
the
news
about
it.
I
pulled
a
couple
of
comments
out
of
hacker
news,
customers
and
users
celebrating
our
transparency.
They
love
that
that
roadmap
is
there.
A
They
love
that
they
can
see
us
all
having
debates
about
what
should
be
in
the
next
version
or
what
this
means
and
how
valuable
it
is,
and
they
love
participating
in
that.
So
that's
all
being
celebrated
I
think
properly.
If
you
want
more
product
detail
outside
of
just
what's
in
the
posts,
which
is
a
lot
of
detail
by
itself,
but
you
want
it
in
video
form
by
all
means
check
out,
learn
at
get
lab.
Dan
Gordon
is
TMM
team.
A
Doing
some
amazing
work
there
a
lot
coming
out
soon,
but
it
but
a
lot,
that's
already
really
great
for
13.0
being
as
celebrated
as
it
is
the
Tam's
and
essays
and
folks
in
customer
success.
Just
generally,
actually
did
a
showcase
I
think
this
was
just
yesterday,
but
here's
a
link
to
the
playlist
of
all
of
their
customer
success
skills
exchange
sessions-
the
one
yesterday
was
really
nice
in
terms
of
demonstrating
and
shortly
but
with
with
some
technical
depth.
A
Each
of
the
most
important
things,
in
my
opinion
in
13.0
I,
agree
with
what
they
chose
to
to
demo
and
to
discuss,
and
they
talked
a
lot
about
why
those
things
are
valuable,
so
I
would
go
ahead
and
consume
that
video
content
to
if
you
want
to
double
click
into
13.0
and
then
the
future.
Everyone
knows
how
loss
in
the
future
is
going
to
be
I
just
love
it.
My
computer
is
accidentally
full
of
pictures
like
this,
of
course,
in
13.0
we
do
a
fair
amount
of
looking
ahead.
A
That's
what
we
do
with
a
major
release,
but
there
are
also
some
other
good
examples
in
recent
get
lab
history.
Looking
ahead,
this
is
a
copy-paste
out
of
that
blog
post,
but
Scott
Williamson,
EVP
and
products
also
recorded
a
video.
It's
five
minutes,
long
to
celebrate
in
mark
13
arrow
and
to
talk
about
the
future.
Given
five
minutes
of
your
time,
that
is
a
great
video
right
there
with
some
apologies
to
anyone
watching
this
later
who's,
not
a
get
lab
team
member.
A
We
have
some
give
internal
videos
that
I
want
to
make
sure
everyone
here
has
seen
and
that
are
extremely
relevant
to
product
release.
Updates
the
worldwide
go
to
market
failed
update.
We
do
it
once
a
quarter.
This
quarter.
It
was
canceled
as
a
live
meeting,
so
it
disappeared
from
everyone's
calendar
and
I
I.
Think
just
asking
around
I
think
people
misinterpreted
that
it
didn't
happen
and
what
happened
is
we
did
it
a
synchronously?
So
please,
if
you're
on
this
call-
and
you
haven't
yet
watched
the
video
from
that
quarterly
update,
go
back
and
watch
it.
A
I
link
you
directly
to
the
product
update
part,
but
of
course,
McBee
leads
it
off
and
it's
the
whole
regular
quarterly
update
very
well
worth
watching.
There's
some
detail
on
what
Scott
talks
about
in
terms
of
product
updates
and
he
also
led
a
product
group
conversation
again
get
lab
internal
content
here,
I'm,
not
listing
all
of
the
important
things,
because
some
of
them
I,
don't
even
want
to
say
out
loud
and
a
public
call,
but
there's
some
really
important
stuff
and
some
really
exciting
stuff
in
those
in
those
videos.
A
A
I
pointed
a
few
months
ago
to
these
Direction
pages.
They
have
actually
continued
to
improve,
there's
really
good
stuff
here
in
terms
of
storytelling
about
gitlab
and
what
we're
planning
to
do
in
the
rest
of
this
fiscal
year,
but
also
in
the
next
three
years,
and
why?
What
we're
not
going
to
do
all
that
stuff?
Is
there
one
change
worth
noting
the
CI
CD
Direction
page
has
been
rolled
up
into
the
ops
page,
so
verify
package
release
are
now
on
the
obstetrician
page.
A
You
know,
update
your
bookmarks
I'm
sure
you
all
bookmarked
that
when
I
shared
it
a
quarter
ago,
he
looked
ahead
also
includes
a
monthly
kickoff
call.
There
are
lots
of
kickoff
calls
when
you
go
looking
you'll
find
you
know
like
dozens
of
them
in
every
month.
Don't
watch
them
all
watch
the
ones
you're
really
interested
in
sure,
but
definitely
watch
the
one
general
kickoff
call
I,
think
everyone
here
can
confine
those
20
minutes.
A
It's
really
well
worth
it
it's
high-level
stuff,
and
so
here's
a
link
to
that
tells
you
what's
coming
up
in
just
a
few
weeks
and
actually
goes
out
four
days
before
the
previous
version
is
released.
So
there's
a
little
bit
of
a
dose
IDO
there
13.1,
because
it's
next
there's
a
lot
of
material
out
there.
You
can
see
the
way
we
list
it
on
the
pages
I'm
linking
to
includes
call-outs,
for
what
tier
that
feature
is
coming
in
at
and
also
includes.
This
is
a
sort
that
I
ran
for
just
the
highlights.
A
So
just
things
in
13.1
that
we're
anticipating
will
be
considered
highlights
no
guarantees
when
we
actually
sit
down
and
I
think
the
writing
has
actually
already
started,
but
when
we
really
sit
down
to
write
it
and
rank
things
and
haggle.
But
at
the
moment
these
are
the
things
we
already
think
should
be
highlighted
in
13.1.
A
So
all
of
that
is
there
for
the
taking
that
gets
me
to
my
thank
you
slide
and
before
Q&A
I
actually
have
a
question
for
the
crowd
on
the
call
here,
which
is,
you
know,
considering
the
field
flash
newsletter,
considering,
learn,
etiquette
lab
and
a
lot
of
these
things
that
are
the
direction
pages.
All
these
things
actually,
and
there
are
more
of
them
that
are
better
than
they
ever
were
in
terms
of
product
release.
A
Updates
I
came
to
creating
this
sessions
content
and
felt
a
little
bit
like
it
was
done
and
I
should
just
make
sure
I
curate
all
that
stuff,
because
we
all
have
tens
of
thousands
of
words
flying
by
our
eyeballs
every
day
inside
the
jet
lab
bubble
and
make
sure
you
knew
where
the
good
stuff
was
and
what
I
thought
was
worth
your
time,
in
addition
to
a
little
data
and
analysis.
But
what
I'm
asking
is?
Was
this
worth
it
to
you
as
an
enablement
session?
Should
we
do
another
one?
A
Every
quarter,
it
may
be
pinched
a
little
just
by
the
fact
that
we
just
turned
the
page
on
a
major
version.
So
there's
a
lot
of
release,
update
material
out
there
right
now,
but
I'm
feeling
a
little
bit
like
this
could
be
considered
redundant
and
I
want
to
make
sure
it's
not
that
it
is
valuable.
So
that's
a
question
for
you,
but
please
anybody
else,
chiming
chime
in
with
a
question,
and
if
you
would
just
want
to
answer
that
in
text
you're
more
than
welcome
to.
B
A
Good
to
hear
and
I
do
think
some
of
these
resources
are
wickedly
hard
to
find
like
weird
hard
to
find.
You
know,
you're
using
Google
to
search
their
own
stuff
and
Docs
and
I
was
joking
with
somebody
yesterday.
You
know
that
Google
they
should
start
a
search
engine
because
he,
even
when
you
use
it
to
point
it
at
their
own
stuff,
it's
surprisingly
hard
to
find
some
of
these
files
out
there.
So
maybe
there's
a
usefulness
in
terms
the
curation
function
to.
A
B
I'll
continue
since
I
wrote
down
the
question.
First
off,
look
I
just
wanted
to
say
thanks
for
rolling
these
metrics
up
it's,
it
is
encouraging
to
see
that
what
we're
doing
things
well
and
just
to
show
that
the
proof
of
us
growing
as
an
organization
in
terms
of
numbers
is,
is
paying
off,
and
you
know
some
regards.
Do
we
have
resources
that
outline
who
and
get
lab
is
the
the
DRI
for
different
about
get
lab
comm
pages
and
resources
like
like
the
vision
pages,
so
is
that
a
product
or
an
engineering
or
marketing?
A
In
this
regard,
I
have
seen
some
pages
pop
up
things
like
a
last
updated
date
and
yeah
dris.
If
anything,
those
are
usually
referenced
in
the
handbook,
which
is
not
always
immediately
connected
to
that
webpage.
You
ended
up
on
on
our
website,
so
part
of
its
that
does
it's
like
you,
could
search
the
handbook
and
find
out,
but
I
think
it
would
be
better
if
it
was
right
there,
at
least
for
the
types
of
pages
you're
talking
about
I'm,
going
to
take
that
feedback
back
in
the
marketing.
A
We've
got
some
good
pow
wows,
coming
up
with
product
marketing
and
with
the
content
team
and
with
folks
who
are
the
dris
for
some
of
what
you're
talking
about.
Can
we
just
manually
add
who
you
should
paying
or
when
it
was
last
updated
like
to
the
bottom
of
the
page
in
cases
where
we
want
to
make
sure
that's
as
easy
as
possible,
I
think
we
can.