►
Description
Brian Glanz with Product Marketing discusses the latest key, sales-relevant highlights of GitLab 13.0–13.3 and related resources. Slides: https://tinyurl.com/yxrnqmex
A
A
We
will
look
roughly
one
quarter
back
to
our
most
recent
major
release,
13.0
that
shipped
on
may
22nd
and,
of
course,
all
of
our
releases
ship
on
the
22nd
of
every
month,
as
gitlab
has
done.
For
now
more
than
100
consecutive
months,
I
am
brian
glanz
product
marketing
manager.
We
will
also
take
a
look
ahead
and
I
will
also
share
plenty
of
links
to
more
information.
A
Also
in
the
name
of
housekeeping.
This
presentation
is
public.
If
you
are
not
a
get
lab
team
member,
please
know
that
we
plan
ambitiously.
We
have
a
transparent
roadmap
and
wide
open
development
process
with
a
great
track
record.
I
should
add
of
delivering
on
our
plans,
but
do
note
the
distinction
between
plans
and
promises
in
previous
quarterly
updates.
We
looked
at
a
few
of
gitlab's
holistic
differentiators,
including
rapid
innovation
and
charted
the
growth
of
our
product.
A
In
terms
of
new
features,
per
monthly
release
and
releases
13.00
to
13.3,
we
added
55
new
features
in
the
premium
tier
and
33
new
features
in
the
ultimate
tier,
while
maintaining
our
roughly
60
40
split
between
what
we
add
for
free
users.
That's
the
60
percent
and
new
features
added
for
paid
users.
That's
the
40.
Of
course.
All
improvements
for
free
users
are
also
available
to
paid
users.
A
Now,
as
we
tend
to
do
with
major
versions,
we
hit
a
high
water
mark
with
13.0,
and
then
the
question
a
quarter
ago
was:
will
we
be
able
to
sustain
that
new
pace
with
13.0?
It
was
the
first
time
that
we
ever
released
more
than
100
significant
new
features
and
improvements.
In
one
version-
and
I
noted
a
quarter
ago,
I
was
doing
the
math
out
loud
that
if
someone
were
to
be
buying
git
lab
today
and
for
the
year
ahead,
they
would
not
just
be
buying
what's
in
the
proverbial
box.
A
At
the
moment,
they
would
also
based
on
this
trajectory
reasonably
expect
to
get
more
than
1
000
new
significant
features
and
improvements
over
that
year
ahead.
If
we
could
sustain
that
pace
so
based
on
these
data,
I'm
very
happy
to
report
a
quarter
later.
We
have
done
so,
and
these
are
really
nice
round
numbers.
Aren't
they
for
sharing.
We
now
release
regularly
more
than
100
significant
new
features
and
improvements
every
month
and
in
a
year.
Yes,
that's
over
a
thousand
a
quarter
ago,
I
had
a
little
bit
of
pushback
on
use
of
that
term.
A
A
A
Three
new
bug
fixes
that's
what
was
considered
significant
enough
to
mention,
but
if
you
check
the
change
log,
which
of
course
the
release
post
links
to
you'll
find
on
the
right,
seven
new
features
for
runner
in
13.2,
and
that
adds
up
to
more
than
70
improvements
to
get
lab
runner
in
that
version,
so
fewer
than
10
are
considered
significant
enough
to
be
in
the
release
post
and
just
to
double
down
on
that.
I
looked
also
a
few
other
places
brought
one
more
example:
bug
fixes
in
13.2
on
the
left.
A
You
see
in
the
release
post
a
couple.
Dozen
of
them
could
look
like
a
lot,
but
if
you
click
you
find
272
bugs
were
fixed
in
13.2,
so
again
we're
only
considering
fewer
than
10
of
those
improvements
to
be
significant
enough
to
be
in
the
release
post,
you
get
the
point,
we're
actually
fairly
conservative
on
what
we
consider
significant
and
on
what
we
put
into
those
release
posts.
Now,
how
do
you
keep
up?
Well,
my
stock
advice
is
read
every
release
post.
A
I
know
they're
long,
I'm
not
saying
read
every
word
focus
on
the
introduction,
that's
five
or
ten
minutes
of
reading.
It's
highly
values
based
it's
all
about
the
value
added,
it's
not
in
detail
how
things
work
or
the
technical
detail,
it's
written
by
a
product,
marketing
manager
like
myself
as
the
messaging
lead
and
then
also
read
the
key
features
section
it's
labeled
as
such.
There
are
about
a
dozen
of
them
and
pmms
also
weigh
in
in
terms
of
editing
things
there.
A
It's
all
about
why
customers
will
care
that
this
has
been
added
again
very
little
in
the
way
of
how
this
thing
works
and
there
are
links
to
docs
that
describe
all
of
those
things.
So
the
release
post
is
the
single
source
of
truth,
but
it's
also
really
good
reading
for
a
very
general
audience,
and
certainly
for
everybody.
Listening
to
this
presentation
today,
now
a
couple
new
tools
related
to
product
release
updates
have
been
really
popular
in
recent
qbr's
and
otherwise.
So
I
wanted
to
make
sure
I
brought
them
here
today.
A
A
A
Not
all
features
are
created
equal
right,
and
I,
by
that
I
mean
they-
take
different
amounts
of
time
to
develop
different
amounts
of
effort.
They
certainly
have
different
impacts
on
customers,
businesses
they
get
used
in
different
amounts,
all
of
those
things
and
more-
and
I
say
that,
because
you
might
leap
to
a
conclusion
based
on
like
how
many
features
are
there
per
category
in
this
release,
for
where
gitlab
has
invested
resources,
I
wouldn't
do
that.
A
I
would
just
use
this
tool
for
indicating
where
you
should
dig
in
where
it
would
be
interesting
to
look
now
in
terms
of
all
our
holistic
differentiators,
not
just
the
rapid
innovation,
but
also
our
open
core
product.
The
fact
that
everyone
can
contribute
our
collaborative
and
transparent
customer
experience.
A
We
noted
in
past
quarterly
updates
that
community
contributions
were
trending
steadily
upward
and
they
really
are
right
there
at
the
heart
of
where
these
three
holistic
differentiators
come
together
to
add
value
to
the
product.
Now
we
were
at
about
100
per
month
during
the
version
10
product
year
in
terms
of
community
contributions
merged
per
month
and
then
150
during
version
11
and
200
during
version
12
that
ended
just
a
few
months
ago
earlier
this
year.
That
begs
the
question:
should
we
expect
community
contributions
to
continue
growing?
A
A
A
I
should
also
mention,
because
I
know
in
one
case,
there's
public
information
is
totally
safe
to
do
so.
Roger
meyer,
one
of
these
mvps
works
for
a
customer
siemens
and
that's
not
rare
right.
Many
of
our
contributions
also
are
coming
in
from
customers,
so
you
can
see
the
convergence
of
those
holistic
differentiators
and
again
not
just
adding
value
to
the
product,
incidentally,
also
adding
value
to
our
customer
relationships
and
adding
value
to
our
community
into
our
relationship
with
them.
A
Now,
let's
talk
more
directly
about
product,
but
as
usual
in
these
updates,
let's
talk
product
in
terms
of
the
value
provided.
What
do
I
mean
by
that?
Exactly?
Let's
start
with
13.0.
We
all
know
it
relatively
well.
Of
course
it
was
a
major
release
and
we
had
appropriate
hoopla
associated
lots
of
videos,
lots
of
information,
press
releases,
the
whole
shebang.
I
share
a
look
at
the
release
post
header
for
each
version
in
these
quarterly
updates.
A
A
link
to
the
post,
of
course,
is
the
single
source
of
truth
and
then
under
the
header,
you
see
those
bold
purple
phrases.
Well,
those
are
about
the
value
added
by
the
top
features
per
each
release.
I
go
looking
for
those
phrases
in
the
post
copy
paste
them
out
here
or,
if
they're,
not
there,
I
write
them
myself
and
you
can
just
read
them
off:
improve
the
availability
of
get
repositories,
manage
more
complex
projects
and
streamline
your
existing
processes
with
gitlab
13.0.
A
It
makes
it
a
simple
little
punchy
phrase
there
in
terms
of
our
value
framework
for
get
lab
team
members
I
want
to
mention.
Sometimes
these
are
phrased
like
an
after
scenario
condition.
Other
times
their
their
positive
business
outcomes
or
or
other
times
required
capabilities,
you
know
deploy
them
as
you
will
in
your
process
and
then
a
per
each
top
feature.
I
also
mentioned
in
parentheses
there,
the
tier
it's
available
at
now,
13.1
improved
productivity
and
response
time
track
and
improve
code
quality
and
extend
compliance
and
security
with
gitlab
13.1.
A
It's
kind
of
fun
right
testing,
modifiers
for
modified
files.
First
excuse
me,
and
at
the
premium
tier
there,
I'm
very
excited
about
this
one.
It's
about
how
for
complex
projects,
sometimes
testing
or
some
testing
can
take
so
long
that
developers
may
be
tempted
not
to
wait.
They
effectively
lose
the
advantage
of
that
automation.
So
what's
changed
first
testing
that
lets
you
get
results
back
faster
for,
what's
most
likely
to
be
relevant
and
then
in
the
bottom.
That
ui
for
container
network
policies
is,
of
course,
compliance
related
also
in
the
ultimate
tier
for
13.1.
A
Some
of
them
have
to
hang
together
better
than
others,
but
okay,
the
iterations
feature
there
that
improves
agile
project
management
for
paid
users
and
it's
nice
to
see
load
performance
testing
coming
in
at
their
premium.
Tier,
that's
a
thing,
many
need
and
would
otherwise
have
been
doing
with
another
tool,
so
it
strengthens
our
single
application.
A
Differentiator
build
secure
software
more
easily
and
powerful
workflows
more
efficiently,
while
reducing
context.
Switching
and
ops
with
gitlab
13.3
eagerly
awaited
there
at
the
top.
Fuzz
testing
is
here
in
13.3,
first
with
coverage,
guided
fuzzing,
of
course,
in
the
ultimate
tier
and
also
an
ultimate
on-demand
dashed.
A
That's
for
times
when
say
you're,
not
making
a
change
but
still
need
to
run
those
scans,
maybe
for
compliance
for
example.
Now
as
I
do
each
quarter,
I
mapped
just
our
top
features.
Those
the
headline
features
plus
a
few
more
that
I
kind
of
pick
almost
made
it
into
the
headlines
per
functional,
differentiator
and
per
value
driver,
and
if
we
mapped
all
our
features
like
this,
it's
worth
saying
over
a
whole
quarter.
That's
you
know
several
hundred
features
every
box
would
have
something
in
it
right.
A
A
The
kickoff
video
for
gitlab's
next
release
is
already
available,
and
that's
always
the
case
at
this
point
in
the
cycle.
That
timing
is
the
same
each
month.
So
on
the
18th,
we
kick
off
the
next
next
version.
Before
releasing
the
next
version
on
the
22nd,
there
are
many
kickoff
videos
for
various
areas
of
the
product.
A
I
recommend
for
everyone
watching
this
to
watch.
Just
this
main
video.
That's
live
streamed
on
youtube,
so
it's
available
to
the
world
when
it's
live.
It's
your
best,
look
ahead
at
the
next
version.
In
this
case
13.4,
the
kickoff
handbook
page,
is
also
very
useful.
It
lists
everything
we
can
expect
at
that
time
to
be
in
the
next
version.
It
notes
which
features
are
coming
in
to
a
certain
tier.
If
we
know
that
and
then
some
of
what
we
expect
would
be.
The
highlights
are
also
known.
A
The
direction
page
also
entirely
public.
This.
The
strategic
section
here
has
another
really
important
and
recent
update
this
quarter.
If
you
have
not
already
do
check
out
the
new
three-year
strategy,
section
you'll
also
find
additional
detail
on
our
three
investment
themes
and
how
they
play
out
in
pride
in
terms
of
the
plans
for
this
particular
year.
A
A
I
loved
it
and
it's
a
really
nice
way
to
look
at
things,
including
that
different
features
which
didn't
look
as
important
inside
of
one
release
rise
to
the
top,
especially
when
you
look
over
more
time
and
per
value
drivers.
So
we're
going
to
do
that.
I'm
sharing
an
abbreviated
version
and
something
that's
a
little
bit
more
value
based
in
terms
of
value
added.
So
these
are
my
own
assessments
of
the
contents.
A
A
In
the
past
couple
versions,
there
have
been
more
than
a
dozen
improvements
to
merge
requests
and-
and
you
might
not
have
noticed
that
not
all
in
the
headlines
necessarily
mrs-
are
critical
to
a
day
in
the
life
with
git
lab.
So,
while
none
of
those
rose
to
being
in
the
headline
taken
together,
they
very
much
align
with
this
value
driver
as
do
the
performance
improvements
which
also,
unlike
features
generally,
don't
make
the
headlines.
A
But
over
the
past
quarter
we
have
improved
the
global
performance,
that's
the
total
performance
of
git
lab
by
about
10,
and
you
can
feel
it.
We
actually
also
have
a
lot
more
planned
here
and
you
can
see
that
behind
the
link,
I'm
sharing
I'll
move
similarly
quickly
through
the
following
slides,
I'm
not
going
to
read
all
of
their
contents,
I'm
providing
them
for
your
information
on
recent
and
upcoming
features
and
improvements,
reducing
security
and
compliance
risks.
A
A
And
container
host
monitoring
to
put
these
two
together,
both
add
to
our
differentiator
in
being
optimized
for
kubernetes
and
just
generally
for
supporting
cloud
native
transformation,
improving
operational
efficiency,
fair
to
say
this
is
more
important
than
ever
right
now,
as
in
any
challenging
times,
regardless
of
whether
it's
a
pandemic
or
just
a
general
challenge
to
one's
business.
Saving
time
and
money
is
not
just
about
optimization.
A
This
is
another
good
example
in
terms
of
being
able
to
aggregate
alerts
where
it's
not
just
one
feature,
it's
five
features
in
one
release:
five
in
the
next
and
then
over
time
it
emerges
as
this
a
really
big
value
pad
now.
Automation
of
this
nature
to
ensure
access
to
get
repos
essential,
not
just
for
pushing
code
also
for
deployments,
but
in
companies
like
get
lab,
it's
needed
to
support
all
the
work
that
we
do
and
that's
increasingly
becoming
the
case.
Inside
of
other
companies.
A
I
had
mentioned
iterations
in
13.2,
but
we
have
a
raft
of
related
improvements
coming
soon.
We
are
in
fact
working
with
red
hats
to
support
running
gitlab
on
openshift
awesome.
Many
recent
improvements
have
helped
to
simplify
complex
pipelines
for
users
and
more
help
is
on
the
way
in
that
regard,
lots
of
technical
details
on
these.
I
know
I'm
breezing
over
them,
but
that's
that's
part
of
the
point
for
this
presentation
get
more
detail
out
of
the
product
keynote
and
and
some
of
the
resources
I'll
point
to.
A
Incidentally,
at
the
end
of
this
presentation,
reducing
security
and
compliance
risks,
we
can
do
that
with
get
lab
because
of
our
single
app
differentiator.
That
is
being
a
single
application
for
the
entire
devops
lifecycle.
We
can
do
that
in
ways.
No
one
else
can
whole
new
capabilities
emerge
and
especially
in
security
and
compliance,
end-to-end,
insights
and
visibility.
We
just
can't
get
other
ones,
we'll
see
a
couple
of
examples
of
that
here.
A
We
can
enable
customers
to
identify
what
to
fix
first
and
thereby
reducing
security
risk.
We
talked
about
the
fuzz
testing.
In
addition
to
the
coverage
guided
test,
fuzz
testing
or
fuzzing.
We
will
soon
have
rest
api,
fuzz
testing.
Overall,
this
is
helping
to
find
vulnerabilities.
That
cannot
otherwise
be
found
very
well
worth
mentioning,
at
least
if
it
happened
today
and
it's
hard
to
predict
the
future,
but
likely
when
we
get
both
of
these
forms
of
fuzzing
integrated.
A
We
will
be
the
only
vendor
offering
both
types
of
fuzz
testing
and
they
find
different
things.
They
do
once
dynamic
when
static
and,
relatively
speaking,
they
do
different
things,
also
really
significant
other
than
that
functional
differentiator
is
the
more
general
functional
differentiator
of
we're,
making
fuzzy
fuzzing
easy
for
developers
to
do,
and
if
there's
a
reason,
it
isn't
typically
done
it's
because
it's
hard
not
because
it
isn't
valuable.
It's
highly
doubtable
auto
remediation
should
be
well
more
automated
trying
to
give
you
really
brief
summaries
here
and
we
will
soon
have
bots
handling.
A
More
of
that,
for
you,
I
mentioned
how
key
on-demand
dast
will
be,
and
you
can
expect
more
in
that
vein
and
then,
finally,
we
support
cloud
native
workflows
for
threat
monitoring,
as
as
we
do
generally
all
within
your
gitlab
experience
with
iteration
on
our
alerts,
dashboard
improving
operational
efficiency.
What
do
our
teams
have
in
store?
In
that
vein?
A
A
This
one,
I
read
as
get
labs,
quality
and
support
teams
sharing
more
of
what
they've
learned
in
terms
of
reference
architectures
for
scale
sharing
more
with
our
customers
and
finally,
gitlab's
upcoming
incident
management
system.
This
will
help
establish
on-call
schedules,
alert
routing
and
more
in
terms
of
the
details.
A
So
that's
our
look
ahead.
A
couple
of
more
add-ons
to
this
update
once
every
month
get
lab
team
members
in
field
receive
a
field
flash
newsletter
in
your
email.
I
cannot
encourage
you
highly
enough
to
read
that
entire
newsletter.
It
is
full
of
gold
well
produced
the
version
you
get
in
your
email
has
get
lab
internal
details
that
team
members
won't
want
to
miss
this
being
the
quarterly
product
release
update.
I
highlight
here
and
note
especially
the
what's
new
in
gitlab
section.
A
It
is
also
arranged
by
value
drivers,
so
it's
kind
of
like
an
appetizer
for
these
quarterly
updates
for
those
outside
of
get
lab
or
new
to
the
company.
There
are
also
slightly
scrubbed
versions
of
the
field.
Flash
newsletters
on
this
handbook
page
there's
also
an
archive
of
past
newsletters,
so
check
that
out
now,
if
you
were
looking
for
demos
or
more
technical
content,
I
mentioned
earlier
that
I
would
get
to
this
slide,
and
here
it
is
now
visit.
Learn
gitlab!
A
A
So
thank
you
for
joining
this
quarterly
product
release
update
and
you
can
find
much
more
about
what's
new
and
upcoming
in
our
product
and
from
across
the
whole,
get
lab
community
by
looking
online
for
our
first
all
virtual
24
hour.
This
time,
24
hour
long
user
conference,
it's
called
get
lab,
commit
previous
editions
have
been
held
in
major
cities
like
london,
new
york,
san
francisco,
the
theme
of
our
latest
and
greatest
gitlab
commit
is
you
belong
here?