►
From YouTube: FY22 Q3 Product Release Update for Sales - Public
Description
What's new and upcoming in GitLab 14.1–14.4 and beyond, with Brian Glanz from Product Marketing. Public slides: https://tinyurl.com/3epkjxa3 and for GitLab Team Members, see the internal version: https://youtu.be/z6hFnUtm2Gk and internal slides: https://tinyurl.com/d2erzc2w
A
All
right,
happy
thursday,
everybody
thank
you
for
joining
us
for
our
level.
Up
this
week,
we've
got
brian
glantz
here
to
give
us
an
update
from
products
I'm
going
to
drop
our
notes
document
in
the
chat.
Please
help
us
to
take
notes
and
ask
questions
for
brian,
and
with
that
I
want
to
go
ahead
and
turn
it
over.
B
This
product,
if
you
are
new
here,
you
are
in
for
something
great
you're,
gonna
love
it
I'll
say
a
few
things
just
for
folks
who
are
new.
I
love
that
there
are
always
people
who
are
new
every
quarter.
We
do
this
product
release
update.
This
is
the
q3
product
release
update?
Yes,
it's
q4
now
a
little
bit
but
per
the
ipo.
This
got
pushed
just
a
little
bit
into
the
future.
B
Congratulations
again
everyone
and
we
are
covering
a
little
bit
more
than
we
had
otherwise
planned
to
do
accordingly,
so
we're
covering
four
instead
of
three
months
of
get
lab
shipping
every
month
on
the
22nd.
Now
more
than
10
years
of
consecutive
monthly
shipments
of
gitlab,
that's
amazing
14.1
through
dot
four
and
a
look
ahead
about
a
quarter
up
through
sco,
also,
if
you're
new
here.
Yes,
there
is
always
a
link
or
maybe
that's
wrong.
Maybe
there
are
always
like
a
hundred
links
and
always
to
the
handbook.
B
There's
one
for
product
release
updates
too,
where
you
can
find
the
last
few
quarters
worth
and
things
like
product
keynotes
at
conferences
and
at
last
year's
sco
and
and
all
that
sort
of
stuff
you
might
want
if
you
are
just
catching
up
with
the
latest
in
gitlab,
because
we
are
taking
a
look
ahead.
We
have
a
slide
like
this,
and
so
should
you
anytime,
you
are
talking
about
upcoming
products,
features
functionality
blessed
by
gitlab
legal.
B
This
is
the
real
deal.
Please
use
it!
What
to
know
when
we're
not
in
a
quarterly
enablement.
How
do
you
know
what's
new
and
a
lot
of
it
will
will
poke
at
you
usefully
monica
gomez,
the
inimitable,
the
one
and
only
sends
a
monthly
release,
email
to
sales
on
the
22nd
same
time
that
the
product
itself
is
released?
B
It's
based
on.
What's
in
the
release
post,
which
is
published
on
the
22nd,
even
if
it's
a
sunday
it's
published
when
the
product
is
released
and
what's
in
those
release,
posts
is
going
to
be
a
part
of
the
narrative
today
because
they
have
become
over
time
again,
a
little
bit
more
user
centered
and
a
little
less
buyer
centered
in
the
way
they're
describing
the
value
added
to
the
product
for
us.
Obviously,
in
this
context,
that's
a
concern.
B
It
means
we
have
to
do
a
little
bit
extra
work
when
we
look
at
what's
in
the
release
post
and
how
it's
described
to
then
talk
about
it
in
customer
terms,
right
and
so
monica's
doing
that
extra
work,
I'm
joining
with
her
to
do
it
going
forward.
It's
a
product,
marketing
exercise.
I
just
want
to
make
sure
we
in
product
marketing
are
doing
our
part.
We
will
be
co-writing
this
monthly
release,
email
to
sales.
B
B
If
there's
any
difference
between
like
this,
the
monthly
release,
email
and
that
the
field
flash
newsletter,
maybe
it's
that
field
flash
is
more
internally
focused,
but
you
should,
by
and
large
just
see,
consistency
there
and
one
feeding
the
next
I
mentioned
already
that
the
release
posts
have
become
more
user.
Centered.
Part
of
that
is
because
product
marketing
managers
are
no
longer
writing
a
marketing
introduction
to
the
release
post
I'll
talk
a
little
bit
more
in
a
minute
about
why?
Why
that's
the
case,
but
it's
actually
been
useful
and,
on
the
whole,
a
good
thing.
B
B
B
I
don't
actually
think
we're
being
any
less
innovative
or
we're
certainly
not
doing
any
less
work,
but
that
is
going
to
show
up
a
lot
of
sacrifices
have
been
made.
Of
course,
a
lot
of
you
are
already
intimately
familiar
with
specific
sacrifices
being
made
in
the
good
name
of
performance
and
reliability
and
security,
especially
around
the
ipo
event,
but
not
only
and
we'll
get
a
little
bit
more
on
that
before
I
click
past
this
I
want
to
say
a
word
about
just
an
example.
B
Like
the
bottom
item
on
this
list
use
variables
and
other
variables,
it
gets
my
my
programmer
heart
beating
a
little
faster
there.
It's
a
cute
little
feature
name,
isn't
it
use
variables
and
other
variables
yeah,
so
that
one
it's
free
but
significant
value
added,
also
for
premium
customers
and
ultimate
customers.
This
was
easily
the
top
of
the
list
for
the
pipeline
authoring
team.
This
past
northern
summer,
now
long
since
past,
here
in
seattle,
this
was
easily
the
number
one
thing
they
could
do
to
impact
arr
and
that
was
requested
by
customers
and
prospects.
B
A
five-year-old
issue
upvoted
500
times.
So
just
because
it
says
it's,
it's
free!
Don't
make
the
mistake
of
thinking
it's
not
adding
value
for
your
customers
in
premium
and
ultimate
and
then
similarly
just
another
point
off
the
same
thing.
I
remember
kenny
highlighting
that
in
the
14.1
kickoff
call
another
point
to
anyone
who's
new
around
here.
B
The
stuff
that
gets
highlighted
in
the
x.y
kickoff
call
doesn't
ship
in
x,
dot
y,
we
plan
ambitiously.
They
give
you
that
warning.
It
says
that
in
lots
of
places,
but
it's
still
easy
to
make
the
mistake.
If
you
see
an
issue
with
a
milestone
that
says
14.1,
it's
still
easy
to
think.
Oh,
it's
coming
in
14.1.
B
The
fact
that
we
plan
ambitiously
is
great.
It
helps
to
keep
our
feature
velocity
up
it.
It
keeps
us
moving
and
again
we're
very
transparent
about
that.
Just
like,
I
would
say,
roughly
like
90
percent,
even
of
what's
featured
in
the
x
dot
y
kickoff
call
is
not
shipping
in
x,
dot
y,
maybe
90
of
it
is
shipping
in
x,
dot
y
plus
one
did.
I
not
say
there
would
be
algebra
but
or
or
plus,
two
or
plus
three
right,
so
14.3
it
shipped.
That's
typical!
That's
actually
fine.
B
Per
that
request,
can
I
just
see
what's
in
premium?
Can
I
just
see
what's
in
ultimate?
Yes,
you
can
that's
easy
to
do.
I
made
it
even
easier
by
putting
on
on
this
slide,
but
also
I've
got
links
in
like
a
dozen
places,
maybe
more
to
martin's
amazing
tool
and
break
my
presentation
mode
just
to
click
through
on
one
of
those
links
on
the
slide,
so
you
can
easily
see
just
what's
in
premium
over
which
versions
here
it
all
is
still.
B
B
It
is,
but
I
pivoted
again
to
describe
the
top
10
in
terms
of
how
they
map
onto
our
value
drivers
better
faster,
that's
of
course
not
sacrificing
security
for
speed,
or
vice
versa,
or
compliance
or
quality
instead
of
security
right.
So
these
are
the
value
drivers
and
how
those
top
10
things
impact
those
we're
in
the
automation
business,
I'm
not
surprised
everything
lights
up,
efficiency,
especially
if
it's
something
important
operational
efficiency.
That
is,
but
even
that
didn't
feel
like
enough
of
a
pivot.
So
I
made
a
bigger
pivot.
B
I
took
a
bigger
step
back
for
positioning
and
messaging.
What's
new
in
gitlab,
this
is
the
the
key
recommendation
and
maybe
that
other
stuff
is
useful
to
you.
I
know
it's
actually
been
requested,
so
it's
I
brought
it
today,
but
what
you
should
really
do
to
position
what's
new,
let
me
back
out,
so
I
can
show
you
the
speaker
notes
on
this.
They
are
extensive.
This
is
a
talk
track
for
what
we
are
saying
to
analysts,
what
we
have
been
saying,
all
this
past
quarter
and
what
we
are
going
to
present
to
analysts.
B
Again
in
the
near
future,
so
this
is
current
stuff
for
the
positioning.
What
are
the
trends
in
the
market
that
led
us
to
this?
To
build
this
product?
Gitlab
14,
the
devops
platform,
now
what
we
called
it
a
quarter
ago
or
what
the
value
pillars
were
a
quarter
ago.
I
remember
saying
these
are
specifically
chosen
because
we're
going
to
keep
shipping
stuff
that
aligns
with
these
value
pillars.
B
So
velocity
with
confidence
built
in
security,
value
stream,
visibility
still
highly
relevant,
and
this
talk
track
describes
exactly
how
to
position
those
and
then
how
to
message.
What's
new
in
the
product-
and
I
like
these
next
few
slides,
even
like
the
most
because
they're
just
really
explicit.
This
is
the
customer
pain.
These
are
the
three
customer
pain
points
or
buyer
pain
points.
The
git
lab
promise
for
how
we
address
those
pain
points
and
then
the
product
proof
for
for
how
exactly
we'll
fulfill
that
promise.
B
That's
where
finally,
we
get
down
to
like
talking
features
a
little
bit.
That's
the
way
to
do
it
right.
We
all
know
that,
but
it's
one
thing
for
for
you
to
kind
of
know
it
in
theory.
It's
another
thing
for
me
to
hand
it
to
you
on
a
slide.
I
hope
these
slides
are
useful
to
you.
I've
intentionally
redesigned
them
to
fit
in
with
the
pitch
deck.
B
Clearly,
this
graphic
is
actually
stolen
from
the
pitch
deck
borrowed
stolen,
strong
word,
but
the
the
point
of
designing
them
is
that
you
can
use
it
either
in
that
deck
or
in
a
you
know,
in
a
follow-up
pitch,
you
can
just
reuse
these
things.
Of
course,
then
there's
a
case
study
with
relevant
quotes
and
metrics
and
a
link
to
the
full
case
study
per
each
of
these
value
pillars
along
with
again
that
talk
track
in
the
good
name
of
safe.
B
What
to
know,
let
me
jump
back
in
to
the
presentation
mode,
so
we
can
see
it
at
a
reasonable
size
because
we're
not
writing
the
introductions
to
the
release
posts
anymore.
One
of
the
things
we're
doing
in
exchange
for
that
as
product
marketing
is
writing
more
blog
posts,
and
that's
better
because
if
we're
talking
about,
I
don't
know
the
kubernetes
operator,
why
would
we
want
it
to
be
a
sentence
in
a
release
post
that
was
published
on
a
sunday,
because
that
was
the
22nd?
B
Why
wouldn't
we
want
it
to
be
a
blog
post,
where
we
can
stretch
our
legs
and
lots
of
associated
marketing
activity
dedicated
to
something
really
important
like
that
timed
with
kubecon
right?
So
this
is
a
good
pivot
to
separate
sort
of
product
launch
or
product
marketing
from
from
product
release,
we're
still
releasing
in
the
same
cadence,
but
we're
marketing
it
on
a
different
cadence
and
on
a
more
impactful
cadence
in
a
more
impactful
way.
B
I
still
want
to
make
sure
you
all
know
that
and
that
you
all
have
a
handy
short
list
of
blog
posts
written
recently
by
product
marketing
that
have
that
buyer-centered
messaging
in
there
that
are
cl.
You
know
lower
in
the
funnel
and
going
to
be
more
useful
to
to
us
in
the
field
at
least
one
per
each
of
those
value
pillars
that
I've
given
a
shout
to
and
stuff
up
through
yesterday
a
lot
on
devops
platform.
B
There's
that
cadence
there's
the
22nd
there's
that
cute
rocket
emoji
again,
I
don't
know
that
sco
is
going
to
be
space
themed,
but
that
would
be
cool.
I
just
throwing
it
out
there.
I,
like
the
I
like
the
rocket
the
major
release
in
june,
might
actually
be
in
may
or
conceivably
even
july.
In
the
last
couple
years,
they've
been
pulled
in
or
pushed
out
for
one
technical
reason
or
another.
So
this
isn't
like
an
iron-clad
promise.
There
will
be
a
thing,
we're
calling
it
get
lab
15
and
it
goes
on
june
22nd.
B
But
you
know
this
is
the
current
plan
and
plans
have
occasionally
changed
around
here
now:
performance,
reliability,
security!
Let's
talk
about
that.
We
all
know:
we've
made
this
big
pivot,
but
let's
flesh
it
out
a
little
bit
more
in
the
look
ahead.
It's
not
going
away
soon!
That's
why
it's
in
the
look
ahead
section
I
want
to
talk
about
the
window
for
it.
B
It
breaks
my
heart
a
little
bit
using
stock
photography
in
in
my
decks.
I
could
just
step
outside
here
in
first
avenue
I
won't
get
the
like
the
blue
sky,
but
I
could
get
like
one
of
these
tower
photos.
Isn't
it
nice
that
now
we
have
our
own
stock
photography
do
I
have
to
say
stock
photography
again
before
I
actually
hear
people
laughing
at
that
joke?
Okay,
pyle,
I
mean
I'm
glad
we
hired
a
model
in
worldwide
enterprise
sales,
so
we
can
actually
get
stock
photography
that
looks
so
amazing.
B
It
might
even
be
fake,
so
yeah
performance
and
reliability
right
now,
it's
been
characterized
as
of
a
month
ago
is
going
through
the
end
of
q1
and
fiscal
23.,
and
that's
already
been
pulled
back
into
okay.
Now
through
march,
and
even
that's
been
mitigated
where
individual
teams
like
I
know,
the
giddily
team,
for
example,
have
been
under
budget
in
terms
of
their
budgets.
They've
already
done
everything
they're
going
to
do
or
not
everything,
but
they've
done
a
lot
and
they've
pivoted
largely
back
toward
feature
development
awesome.
B
So,
as
individual
teams
are
ready
to
do
that,
they
will
product
managers
more
than
ever
want
to
talk
to
you
they've
been
really
helpful.
I
know
of
so
many
cases.
I'm
sure
you
do
as
well,
but
don't
be
shy,
even
though
we
are
heavily
focused
on
performance
and
reliability.
Yes,
as
demonstrated
earlier
we're
still
shipping,
particularly
things
that
are
high
impact,
still
shipping
features
and
individual
teams
are
returning
to
business.
As
usual.
B
There
was
a
nice
back
and
forth
between
francis
potter.
I
see
the
gentleman
right
there
and
and
scott
on
this.
Just
recently,
we
have
started
to
hit
our
numbers
for
availability
of
gitlab.com.
It's
too
soon
to
characterize
it
as
like.
Turning
the
corner,
but
early
indicators
like
being
under
budget
for
error
budgets
across
whole
parts
of
the
org
in
the
month
of
september,
led
to
yep.
We
hit
those
numbers
in
october
and
no
one
month
isn't
enough:
it
isn't
over.
Yet
there's
also
a
really
useful
link
here.
B
I
want
to
make
sure
I
click
it
just
to
show
it
to
you.
This
was
put
together
by
product
leadership
thanks
very
much
to
all
of
them,
and
what
does
this
mean
for
a
member
of
our
sales
org?
What
are
examples
of
the
business
value
actually
being
added
by
our
focus
on
performance
and
reliability?
Right,
of
course,
there's
business
value
in
that.
How
do
we
describe
that,
and
are
we
still
doing
all
that
stuff
on
the
ar
drivers
sheet?
Are
we
yeah
okay?
So
the
answers
to
your
questions
are.
B
Are
there,
but
also
I
wanted
to
give
you
that
fuller
characterization
and
these
are
public
data
right,
so
point
number
one
be
transparent.
There's
really
no
other
way
to
be
around
here,
don't
beat
around
the
bush
when
you're
talking
to
customers
and
prospects
about
this,
it's
actually
really
important
work,
it's
great
that
we're
doing
it
coming
soon
in
premium
and
in
ultimate.
Yes,
you
can
just
look
at
things
that
way,
there's
a
roadmap
for
that
there's
like
a
version
of
the
roadmap
that
is
just
per
paid
tier.
B
B
To
not
be
too
feature
centered,
but
still
give
you
that
stuff,
because
you
asked
for
it
there
it
is,
but
I
won't
talk
about
it
now.
The
gitlab
vision
and
characterizing,
what's
coming
up
per
each
of
those
value
pillars
is
how
to
talk
about
it.
This
is
how
to
position
and
message
what's
coming
up
in
the
product.
B
In
this
case,
I
don't
actually
have
a
transcribed
talk
track,
but
what
I
do
have
is
good
kenny
johnston,
giving
like
a
five
minute
version
where
he
presents
exactly
the
same
content
and
all
I've
done
to
it
is
make
it
look
like
it.
It
fits
with
the
design
of
our
pitch
deck
so
that
you
can
have
this
version
of
it,
but
also
deeper
in
this
deck.
B
I've
got
the
old-fashioned
version
of
it
in
case
you're,
still
using
that
kind
of
deck.
I'm
not
aware
of
any
edict
that
says
you
know:
thou
shalt
have
all
your
decks.
Look
like
the
pitch
deck.
I
don't
know
if
there's
a
template
quite
out
there.
Yet
that's
a
that's,
been
a
work
in
progress,
but
I
give
you
both
versions
of
that
just
so.
B
Let's
not
watch
him
like
right
now,
but
that's
actually
in
there
hi
kenny,
you
love
to
see
it
a
great
event
coming
up
with
yes,
francis
potter,
hello,
again,
francis
and
cindy
blake
in
the
context
of
github
universe.
Didn't
have
it
in
my
expectations
that
it
would
be
so
much
of
a
nothing
burger
but
never
mind.
B
My
extra
commentary
here,
they're
going
to
do
an
actually
intelligent
sounding
session,
all
about
universe
and
and
not
really
just
about
that,
but
why
the
devops
the
devops
platform
for
enterprises
to
be
a
great
event
and
we've
got
a
path
factory
link,
as
well
as
a
bamboo
link
for
sharing
there,
both
versions-
and
this
is
a
thank
you
very
much-
so
we
can
take
everything
previous
to
this
moment
and
keep
it
public
and
then
we'll
have
a
a
little
bit
more
conversation.
That's
internal!
Only.
There
are
some
things
that
are
internal
only.