►
From YouTube: Q1 FY21 Gitlab Release Update
Description
Product Marketing Manager Brian Glanz discusses key sales-relevant highlights of the 12.3–12.8 releases, new business value/selling opportunities in Ultimate/Gold, and Premium/Silver.
B
There
it
is
thanks
everyone,
while
I
get
my
permission,
sorted,
be
wary
who
update
your
max
right
before
you
do
a
thing
make
sure
my
desktop.
Why
don't
I
start
with
a
fun
fact
and
I'll
get
to
that?
A
lot
of
people
ask
when
I
sit
in
here
and
fun
facts
to
be
honest,
I,
don't
really
know,
I,
think
it's
just
a
fox,
but
it'd
be
cool,
but
yeah
kind
of
wish.
It
was
a
today
view
all
right,
we're
actually
covering
two
quarters
in
this
quarterly
release.
Update.
B
That's,
of
course,
six
major
releases
12.3
through
12.8,
so
we'll
get
right
to
it.
I
also,
you
may
notice
me
shuffling
a
little
bit
actually
have
some
notes,
because
covering
that
much
territory
and
get
lab
andia
is
a
little
crazy
for
20
minutes.
We're
still
going
to
do
it
because
that's
how
we
are
the
good
set
of
crazy
get
lab
has
released
a
new
version
of
our
software
Factory
in
a
box
on
the
22nd
of
every
month,
for
more
than
100
consecutive
months
now,
I've
been
in
software
for
more
than
20
years.
B
I
do
not
know
of
another
product
like
ours,
shipping
with
that
level
of
reliability
and
as
we
all
know,
reliability
is
everything
in
business
right.
So
you
can
mention
this
wherever
it's
useful
I
know
you
can,
because
Sid
did
so
get
by
a
commit
in
San
Francisco.
Let's
talk
product
and
not
in
terms
of
all
the
technical
details
as
much
as
let's
talk
product
in
terms
of
value
right
and
yes,
our
value
drivers,
also,
our
differentiators,
for
example,
12.2
was
the
last
time
we
had
a
release.
B
Update
like
this
with
a
headlining
feature,
there
directed
acyclic
graphs,
checking
my
notes
on
that.
One
be
the
first
kid
on
your
block
to
completely
understand,
directed
acyclic
graphs
seriously,
though,
you
should
read
at
least
the
tops
of
each
of
these
release
blog
posts,
they're
written
by
folks
in
product
marketing.
So
they
have
that
value,
centered
messaging,
that
you
need
and
then
read
this
section
below
that
it's
literally
called
key
features.
I'm
doing
this,
especially
for
anyone
who's
very
new.
B
That's
like
the
top
five
features
which,
in
any
recent
release,
is
less
than
10%
of
the
significant
features
so
you're,
just
gonna
get
a
5
or
10
minute,
read,
maybe
a
little
more
if
you
have
to
Google
something
like
DAGs,
but
with
that
also
a
demo
video
and
then
all
the
rest
of
the
release
post.
You
know
I,
hereby
absolve
you
of
the
sin
of
not
reading
all
of
it,
a
scam
it
you
know,
scan
it
for
that
stuff.
Your
customers
have
been
asking
for
scan
it,
for
just
whatever
is
new
in
premium.
B
Whatever
filter
is
useful
to
you,
but
do
actually
read
the
top
section.
It's
quick!
It's
useful
and
it'll
help.
You
learn
a
little
bit
about
stuff
like
DAGs
along
the
way
now
I
took
all
those
key
features.
That's
five
per
each
of
the
six
releases,
so
30
key
features
and
put
about
this
little
table
per
value.
Driver
per
differentiator.
Even
here
the
words
are
a
little
small,
so
I've
got
a
link
actually
to
might
work
there,
but
also
tease
out
a
couple
of
insights
in
terms
of
these
visualizations
I'm,
not
especially
surprised
by
this
one.
B
You
may
have
noticed
earlier:
I've
looked
at
the
key
features,
also
according
to
product
here
and
I,
bring
this
up
partly
because
I've
been
hearing
from
really
the
the
two
different
camps.
Occasionally,
things
like
it
seems
like
we
do
a
lot
more
for
core
than
we
do
for
premium
or
ultimate
or,
of
course,
the
opposite
from
other
people.
It
seems
like
you,
do
a
lot
more
for
paid
users
than
you
do
for
free
users,
and
that's
fine.
A
little
bit
of
that
tension
is
actually
generative.
B
People
advocate
from
what
they
want
great,
but
actually
we
look
at
key
features
over
the
past
six
months.
You
can
all
do
the
math
on
these
data.
It's
a
wash
it's
about
50/50
and
both
of
those
perspectives
are
kind
of
wrong,
even
if
in
one
version
or
another
they're
actually
kind
of
right.
If
you
do
zoom
out
there's
something
like
a
60/40
split,
favoring
free
over
paid
over
all
these
six
months
for
all
of
the
hundreds
of
significant
features.
B
But
again,
it's
not
zero-sum
in
both
directions,
right
something
that
makes
you
faster
and
was
there
four
core
makes
everyone
faster
to
state
the
obvious
and,
as
we
all
saw
from
skin,
Sid
and
scho
pardon
me
Sid,
it's
go.
This
was
I
really
liked
it.
His
double
flywheel
theoretical
model
of
how
it
all
works,
that
these
two
investments
benefit
each
other.
So
well,
if
something
like
this
slide,
incidentally,
doesn't
make
immediate
sense
to
you
and
I've
gone
a
little
fast
just
to
stay
on
time
down
into
those
speaker.
B
Notes
for
all
of
these
slides
is
often
more
explanation
and
links
to
references,
so
please
grab
a
copy
and
dig
in
as
you
like
now.
I
pulled
this
quote
in
yellow
here
from
the
interview
published
in
Business
Insider,
just
this
past
weekend
with
Sid
and
I,
also
looked
at
each
of
these
versions
over
the
last
six
months
and
what
we
were
doing
them
for
which
tier
and
as
you
can
see.
B
Yes,
sometimes
we
actually
did
do
a
little
bit
more
for
paid
than
for
free
users
or
vice-versa,
but
I
think
the
headline
is
rapid
innovation
here,
I
think
the
headline
is
372
significant
features
that
we
actually
mentioned
in
a
release
blog
post
over
those
six
months
and
yes,
the
increasing
velocity
over
time.
I
really
think
that's
the
big
headline
now
I
barely
showed
this
slide
earlier,
because
the
words
were
pretty
small
and
it's
a
lot
of
slide
form.
B
Some
of
these
features
so
I
filtered
again
looking
at
just
the
headline
features
what
actually
gets
into
the
headline
that
makes
a
baker's
dozen
over
half
a
year,
and
so,
let's
actually
zoom
in
and
talk
about
those
a
handful
of
those
headline
features,
including
the
Web
Application
Firewall
here
or
laughs,
as
the
cool
kids
say,
are
available
to
the
core
products
here,
but
again,
it's
not
like
that
only
makes
Korra
more
secure,
of
course
provides
value
for
everyone.
This
was
the
first
iteration
for
both
laugh
and
product
analytics.
B
B
For
other
reasons
like
we
want
to
get
early
adopters
and
their
feedback,
but
maybe
it's
not
time
for
everyone
to
sell
against
that
feature
yet
and
then
move
the
other
cases
where
it
is
exactly
time
for
you
to
start
working
into
your
conversations
or
connect
it
with
somebody,
you
know
is
looking
for
it
MRR
dependencies
into
for
those
were
released
for
premium.
This
feature
is
helpful,
especially
if
you
have
multiple
developers
working
toward
a
larger
goal
and
then
those
changes
need
to
be
merged
in
a
certain
sequence
so
that
they
ultimately
work
as
intended.
B
B
You
know
oftentimes
in
the
headlines,
we're
abbreviating
the
proper
title
of
a
feature,
and
so
you'll
hear
some
discrepancy
and
what
I
actually
say
see
some
discrepancy
inside
of
the
post
versus,
what's
in
the
headline,
just
a
general
FYI
there,
but
easily
creating
and
deploying
to
an
Amazon
EPS
cluster
is
Dhin
core
that
maps
both
to
our
belief
in
multi
cloud
and
to
our
optimization
for
kubernetes
in
terms
of
differentiators,
it's
similar
to
what
we
had
done
for
Global's
gke
automates.
A
lot
does
in
that
regard,
make
people
more
efficient.
B
Similar
things
could
be
said
for
environments
dashboard
for
DevOps
teams.
Really
it's
for
premium.
Very
much
makes
you
more
efficient
with
that
you
can
manage
the
status
and
the
health
of
environments
where
your
code
is
deployed
across
multiple
projects,
but
all
in
one
place
in
12:6
security
scorecards
go
by
at
least
several
names
kind
of,
depending
how
you're
looking
at
it
they're
also
called
security
grades.
B
You
actually
get
vulnerabilities
graded,
like
ABCDEF,
so
you
know
roughly
how
severe
they
are
and
how
many
of
which
level
of
severity
you
have
sometimes
they're
referred
to
in
Docs
as
project
security
status
panel,
because
that's
where
in
the
UI
they
show
up.
So
that
makes
it
easier
to
understand
just
where
your
projects
have
vulnerabilities.
B
What
level
of
severity
these
evidence
is.
One
of
those
things
that
thank
you,
automation,
really
liberate,
speak
from
those
manual
processes,
especially
in
terms
of
compliance
for
documenting
and
demonstrating
compliance
that
evidence
file
is
created.
It
links
automatically
milestones
and
issues
and
then
that
ultimately
streamlines
the
future
ODS
12:7
parent-child
pipelines.
It's
one
of
those
features
that
people
many
many
people
were
asking
for
over
many
moons.
Both
of
these
headline
features
here
were
very
much
in
demand
and
are
in
core
parent-child
pipelines.
B
Functionally
help
when
pipelines
get
very
large
and
very
complex,
that's
harder
for
both
the
machines
and
the
people
they
take
longer
to
run
they're
harder
to
understand
separating
those
out
and
simplifying
ultimately
makes
things
faster.
You
can
run
some
things
concurrently
then,
and
makes
things
in
many
ways
more
efficient
as
well.
Even
that,
though,
as
we're
breathing
through
these
things
just
to
demonstrate
why
you
do
have
to
click
through
and
read
some
more
yourself,
it
doesn't
tell
the
whole
story
like
we
saw
at
schoo
with
parent-child
pipelines.
B
B
Please
do
dig
in
if
you
breezed
past,
that
at
scope
and
kind
of
missed
some
of
that
detail
there
and
then
just
to
go
back
windows
shared
and
runners
great
for
people
building,
Windows
applications
who
previously
needed
to
set
up
their
own
runners
to
kind
of
state
the
obvious,
but
now
they
can
take
advantage
of
shared
runners
on
get
lab.
Comm
finally,
12.8
released
just
this
past
weekend.
We
squeezed
three
features
into
the
headline
here
with
super
abbreviation
lock.
A
B
Them
which
more
immediately
means
you
can
search,
and
that
means
when
you're,
in
the
heat
of
an
incident
management
management
type
of
moment,
your
logs
are
actually
useful
to
you.
They
were
sort
of
barely
useful
at
before
they
were
aggregated.
This
is
overall,
just
an
awesome
step
forward
adds
a
lot
of
value
to
ultimate.
It's
particularly
worth
a
shout
here.
You
get
is
a
super
abbreviation,
that's
shorthand
for
built
in
the
built
in
to
get
lab,
nuget
or
dotnet
repository.
B
Compliance
here
is
shorthand
for
the
compliance
dashboard
out
in
its
first
iteration
with
12.8,
but
already
useful
in
its
way
as
part
of
a
larger,
build
out
of
compliance
management
and
a
lot
more
is
planned
as
explained
in
that
release,
post
and
then.
Finally,
because
we
are
covering
again
so
much
crowd,
I
wanted
to
zoom
back
out.
B
Yes,
we've
got
the
key
features
organized
by
value
driver,
but
you
can
also
organize
them
functionally,
and
this
is
a
shout
to
Kenny
in
the
go-to-market
update
a
couple
weeks
ago,
thanks
Kenny
for
this,
there
are
three
buckets
really
where
a
lot
of
these
updates
fall
compliance,
visibility
or
analytics
and
then
ecosystem
improvements.
You
can
map
a
lot
of
the
updates.
You
see
here
to
those
through
functional
buckets
that
sort
of
puts
a
bow
functionally,
what
we've
updated
in
the
last
half
a
year,
compliance
just
to
say
a
few
of
these
things
out
loud.
B
That's
for
open
source
security
scanning,
improved
integration,
where
the
shout
for
Jager
that's
for
visualizing
stack,
traces
with
sentry
for
error,
tracking
and,
of
course,
the
registries
for
Konya
or
c++
packages,
and
that
new
get
or.net
repository.
Now,
even
that
doesn't
mention
all
the
stuff
on
this
page,
which
again
is
just
the
top
10%
of
all
those
significant
features
comprised
by
something
like
10,000,
merge,
requests
and
all
this
time
so
yeah,
rapid
innovation
and
yeah
I
sort
of
wish
I
could
channel
their
cousin
disaster
for
this
kind
of
stuff.
B
So
we
could
poetically
cover
all
of
these
features
in
such
a
short
time.
Maybe
next
time
disaster
we
can.
We
can
brine
this
in
three
months
and
actually
do
it
for
three
months
instead
of
six.
We
are
also
doing
this
to
talk
a
little
bit
about
the
future,
as
is
obvious
by
this
slide.
We
all
know
the
future
is
going
to
be
awesome.
B
I'll
do
this
in
about
four
minutes,
so
we
can
still
get
a
couple
questions
and
the
big
price
jump
to
ultimate
I
think
it's
already
worth
it,
but
also
a
huge
amount
of
value
was
planned
for
ultimate
in
the
fairly
near
future.
I
stole
this
from
Zambia
and
Cindy.
It's
go.
Thank
you
very
much
for
that.
Also
in
the
notes
on
this
slide.
B
So
do
watch
that
video
linked
to
from
the
speaker
notes
on
this
slide
and
then,
as
far
as
what's
coming
here
worth
a
shout
out:
value
stream
management,
a
lot
of
customers
still
struggling
with
their
whole
value
chain
and
understanding
that
from
planning
through
to
delivery
of
that
value,
and
we
can
provide
that
insight
because
our
most
unique
differentiator,
of
course,
being
a
complete
DevOps
platform.
Similarly,
for
compliance,
incidentally,
because
your
whole
DevOps
process
fits
into
get
lab,
that's
why
we're
uniquely
positioned
to
help
ensure
that
compliance
so
from
a
lot
of
different
directions.
B
We
end
up
back
on
that
really
core
plank
and
our
bridge
to
the
customer.
There
are
also
just
a
ton
of
security
features
coming
this
year
that
mapped
ultimate
now
in
the
very
near
future.
Of
course,
law
meet
again
in
Prague
spare
a
thought
as
you're
landing
for
the
team
members
that
get
that
who
will
also
on
that
day,
March
22nd
be
landing
12.9.
B
If
you
are
new
enough
not
to
know
this,
then
here's
your
clue.
We
do
a
product
release,
kickoff
that
is
live
streamed
to
the
world,
actually
a
few
days
for
each
released.
A
few
days
before
the
previous
release
is
actually
released,
so
on
the
18th
of
February
we
did
the
12.9
kickoff
call
that
video
is
very
much
worth
your
time.
B
It's
not
very
long,
high-level,
really
juicy
stuff
about
what's
coming
up
in
the
next
version,
and
it
points
to
the
handbook
page,
which
I
also
give
you
a
link
to
you
here
for
12.10
and
partly
I
raised
it
just
so.
We
all
understand
the
versioning
scheme
here,
yes,
we're
going
12.9,
then
twelve,
ten
and
thirteen,
oh
no,
it
hasn't
always
been
that
way.
And
yes,
it
could
change
again,
but
that's
the
plan
right
now.
In
this
case,
you
want
to
go
to
the
Direction
pages.
B
There
recently
improved
a
great
deal
organized
by
section
and
again
a
shout
out
to
Kenny
for
this.
It's
not
just
what
we're
going
to
do
and
why
and
when
for
which
product
here
by
the
way
is
also
there.
It's
also
what
we're
not
gonna
do
and
why
really
useful
to
to
all
of
us
in
our
conversations
and
some
new,
very
clear
investment
themes
that
help
to
frame
all
of
this.
B
So
if
you
haven't
hit
those
Direction
pages
in
a
while
hit
them
sometime
soon
super
useful
and
then
of
course,
13.0
coming
May
22nd
to
a
screen
near
you,
a
border
wrap
greatly
closer
to
20
minutes
for
my
personal
soliloquy
portion
here.
So
I
won't
really
read
all
of
these
product
investment
themes
that
we
heard
about
from
schoo.
B
What
I
will
say
is
that
I
found
it
extremely
useful
a
week
or
two
after
to
actually
go
back
to
the
slides
from
just
these
six
rockstars,
who
gave
us
in
earth-shattering
twenty
minutes
that
I
couldn't
possibly
retell
in
one
minute
here.
What
I
can
do
is
dig
up
links
to
all
of
their
slides
and
give
you
those
links.
So
here
they
are
from
the
comfort
of
your
laptop,
where
you
can
google
anything
you
need
to.
Please
go
back
and
look
at
this
again.
It's
the
best
view.
B
You're
gonna
have
really
juicy
stuff
at
what's
coming
up
in
fiscal
21
and
then
finally,
just
a
meta
word
about
the
way
this
session
was
organized
and
you
intend
to
do
these
updates
quarterly,
and
you
should
expect
one
a
few
months
from
now
this
one
we
tried
to
do
it
war
using
our
value,
drivers
and
differentiators
that
weren't
even
really
on
board
with
us.
The
last
time
we
did
this
we're
also
introducing
in
product
marketing
and
strategic
marketing.
B
What's
been
called
a
pivot
to
the
customer
use
case,
I
would
say
it's
not
so
much
a
vivid
only
because
we're
not
pivoting
away
from
anything
we're
already
using
in
our
strategy.
This
is
an
additional
lens
that
will
help
bring
into
focus
really
those
customer
problems
and
initiatives
that
have
attracted
budget
inside
of
their
organization
and
are
ultimately
the
reasons
that
they
will
choose
get
laugh.
So
the
use
cases
put
things
in
their
perspective.
B
They
help
us
help
them
and
then
to
really
be
that
advisor
to
our
customers,
I'm,
really
looking
forward
to
we're
actually
already
working
on
several
can't.
Do
it
all
at
once.
This
reorganization,
plus
a
little
bit
of
material
to
create
in
these
cases,
even
this
map
may
actually
be
a
little
out
of
date.
Now
that
I
look
at
it
posts
go,
but
so
you
have
an
idea
where
we're
mapping
our
priorities
and
strategic
marketing
to
all
those
that
also
are,
in
effect
throughout
marketing
and
sales.
C
B
D
Yeah,
certainly
I
I
appreciate
the
sort
of
the
composition
of
where
the
development
is
coming
from
and
which
releases
it's
actually
being
targeted
toward.
What
I
wanted
to
understand
was
to
what
extent
are
the
contributions
in
core
coming
from
the
open
source
and
global
contributors
versus
what
we're
doing
internally,
just
to
understand
what
that
looks
like
and
whether
or
not
we're
spending
a
whole
heck
of
a
lot
of
time
on
core
internally
versus
the
paid
releases.
That's
sort
of
mine,
I,.
B
Just
for
posterity,
I
will
say
that
in
the
actual
text
of
the
blog
posts
we
say
that
fart
out
loud,
so
somebody
could
manually
count.
I'm
curious,
like
you
are
where
we
can
say
those
efforts
are
and
then
yeah.
Sometimes
a
contribution
comes
in
and
by
the
way
that
also
creates
work
for
us
to
really
make
it
on
completely
work
or
more
integrated.
It's
not
always
just
as
simple
as
accepting
a
contribution
necessarily.
D
C
Have
the
next
one
I'll
jump
in
Brian
thanks
for
the
overview
initiated?
My
question
was,
with
the
kind
of
pivot,
to
a
more
of
a
use
case,
focus
that
you
highlighted
and
well
that
unpack
the
way
your
team
is
writing
their
release
posts
so
I
know
right
now
they
focus
heavily
on
kind
of
features,
and
so
will
there
be
at
least
for
this
moment
kind
of
features.
Really
it's
gonna
give
them
released.
Will
they
focus
more
on
the
use
cases
as
well
on
the
first
I.
B
Hope
so,
and
I'm
quite
sure
will,
insofar
as
those
release
blog
posts
are,
to
a
certain
degree,
ghost
written
by
people
on
the
product
marketing
team
on
John,
Jeremiah's
team.
So
we'll
all
definitely
do
that
and
that'll
go
a
long
way
a
lot
of
times.
You
know
it's
like
saying:
are
we
using
our
differentiators
to
affect
the
way
we
write?
Those
absolutely
they're
not
always
spelled
out
like
that.
E
Hey
I'll
go:
this
is
DT
solution.
Architects
come
to
you
from
a
Santa
Cruz
Sunday
Santa,
Cruz
California.
Thank
you
very,
very
much
for
doing
this
holistic
overview
of
all
the
releases
I've
been
here
for
almost
three
years
and
it's
refreshing
to
see
that
an
overview
all
the
details.
You
did
a
really
really
good
job.
E
B
My
pleasure,
the
one
biggest
thing
I
hope
you
take
away-
is
to
carve
out
a
couple
hours
if
you
need
that
much
from
scratch
to
actually
read
the
tops
of
all
those
blog
posts
and
to
watch
the
couple
of
videos.
I
said
everybody
on
this
call
should
probably
watch
it'll,
probably
take
a
couple
hours
if
you
haven't
done
any
of
those
things
and,
of
course
less
if
you've
done
some
of
it,
you'll
get
a
lot
more
out
of
that,
then
you'll
get
out
of
these
twenty
minutes,
including
just
by
doing
some
of
that
homework
yourself.