►
From YouTube: Monthly Release Kickoff
Description
Please add feedback here: https://docs.google.com/forms/d/12-QPpvggEsqCvZnDCnuCjqP53joKwjRMPy4PH-Mqp-I/viewform?edit_requested=true Thank you!
A
9
kick-off,
my
name
is
Scott
Williamson
I'm,
the
EVP
of
product
management
and
I'm,
happy
to
announce.
We've
arrived
at
a
couple
of
milestones
lately
that
are
super
exciting
and
they
both
involved
the
number
100.
So
the
first
is
on
January
22nd.
With
our
12.7
release.
We
hit
a
hundred
releases
in
a
row
of
shipping
on
the
22nd
of
every
month,
so
an
amazing
testament
to
the
predictability
of
the
product
development
system.
We've
built
here
and
hats
off
to
everyone.
Who's
been
involved
with
that
along
the
way.
A
Secondly,
we
hit
right
around
then
a
couple
weeks
later:
a
hundred
million
dollar
a
our
our
milestone,
which
means
based
on
the
the
revenue
and
the
prior
month.
We
project
that
that
forward
at
a
hundred
million
dollars,
so
that's
a
huge
milestone
for
a
pre
public
company
and
we're
we're
proud
of
that,
and
so
you
know,
100
releases
100
million
in
ARR.
Those
two
go
hand-in-hand:
the
more
value
we
deliver
in
these
we.
A
Thanks
yeah,
so
by
delivering
more
value,
we
generate
more
revenue.
We
can.
There
therefore
continue
to
reinvest
and
continue
to
drive
even
more
value
in
the
product
going
forward.
So
thank
you
to
all
the
contributors
and
to
the
customers
for
both
sides
of
that
the
contributions
and
the
revenue
all
right.
So
with
that
I'll
go
back
to
Sharon.
Here,
oh
I
want
to
orient
you
to
the
product
kick-off
review,
page
I'm
on
about
gitlab
comm,
slash
direction,
slash
kick-off.
This
is
the
page
that
we
use
to
highlight
everything
that
we're
planning
for
the
12.9
release.
A
There
are
it's
organized
by
section
and
we
have
five
speakers
coming
up
who
I'll
introduce
in
a
minute.
Each
section
has
kickoff
videos
that
each
of
the
product
managers
record
and
they
go
through
their
specific
area
in
more
detail,
and
we
can
hear
we
also
linked
to
the
issues
that
are
we're
using
behind
the
scenes
to
plan
what
we
have
in
mind
for
12.9.
So
you
can
click
on
these.
You
can
go
check
out
or
thinking
you
can
go,
contribute
your
ideas
on
where
we
should
take
it.
One
more
thing,
keep
in
mind.
A
We
plan
ambitiously,
so
we
we
may
we
encourage
the
teams
to
plan
ambitiously.
We
don't
require
highly
accurate
planning,
so
some
of
the
things
that
we
talk
about
here
may
not
make
it.
We
do
intend
to
ship
all
this,
but
please
recognize
our
plans
are
dynamic
and
may
change
so
with
that
I'll
turn
it
over
to
Eric
to
go
through
dev.
C
All
right,
so
it's
a
level
set
real
quick.
The
dev
section
consists
of
the
first
three
stages
of
the
DevOps
life
cycle,
as
we've
defined
them
on
our
home
page,
and
this
is
simply
a
screenshot
from
of
the
table
from
our
home
page,
and
so
you
can
see
that
Devas
consists
of
manage
plan
and
create
and
just
keep
it
and
we're
going
through
some
of
the
items
here
and
we'll
start
with
manage
and
go
through
sequentially
there's
two
big
things
from
manage.
C
The
first
name
is
analytics
and
the
second
theme
is
improvements
into
our
audit
events.
So,
let's
talk
about
analytics
first
in
analytics,
we
have
this
feature
that
we
used
to
call
cycle
analytics.
It's
now
called
value
stream
analytics,
but
it
doesn't
really
provide
a
ton
of
granularity
with
respect
to
a
breakdown
between
lead
time
and
cycle
time,
which
are
commonly
used
times
that
have
specific
meanings
and
agile
software
development,
so
lead
time
is
typically
a
time
between
a
when
a
ticket
is
created
and
the
ticket
is
live
or
an
idea
to
production
and
cycle.
C
Time
is
really
the
time
between.
When
you
start
it
on
working
on
it
and
between
the
time
that
it
goes
live,
so
we're
gonna
segregate
those
two
things
and
make
those
clear
in
the
value
stream
analytics
feature.
So
you
can
see
a
little
mock-up,
a
screenshot
of
what
this
would
look
like
when
we
she
can
see
that
we'd
have
the
time
at
the
top
of
the
at
the
top
of
the
feature
that
would
highlight
the
lead
time,
as
well
as
a
cycle
time,
so
really
excited
to
see
this
improvement
into
value
stream
analytics.
C
So,
a
few
releases
ago
we
released
this
feature
called
cycle,
sorry
code
review
analytics,
which
essentially
helps
engineering
managers
and
other
leaders
identify
bottlenecks
in
the
code
review
process
and
the
way
that
it
currently
is
measured
is
when
the
first
comments
on
an
M
are
happens
to
the
time
the
M
R
is
merged.
That's
the
code
review
time,
but
code
review
time
can
also
start
when
someone
is
assigned
the
merge
request.
They
can
also
start
if
someone
doesn't
leave
a
comment,
but
just
approves
a
mem
R,
so
we're
going
to
include
those
events
as
well.
C
C
A
lot
of
system
administrators
are
required
to
work
in
external
tools
outside
of
gate
lab,
or
they
may
have
organizational
processes
that
they
have
to
funnel
this
data
into,
and
so
we
be
providing
them
capabilities
to
export
their
audit
events
via
CSV,
which
will
be
super
useful
and
then
we're
also
working
to
make
audit
events
just
a
little
bit
more
useful
in
general.
So
we'll
be
adding
project
deletion,
impersonation
events
and
project
import
events
into
the
audit
events,
logging
just
bolstering
the
the
things
that
you
can
actually
see
in
the
audit
log.
C
Moving
on
to
our
next
day,
which
is
plan
and
plan.
The
big
theme
here
is
getting
across
the
finish
line,
several
key
direction:
items
that
we've
been
working
on
over
the
past
few
releases
and
so
I'm
excited
to
say
that
we're
gonna
finally
finish
up
adding
burn
up
charts,
which
is
a
way
to
to
view
you
know
a
more
historically
accurate
scope,
history
of
something
being
added
to
a
milestone.
We're
also
going
to
continue
and
finish
our
work
on
weight
and
progress.
Information
moving
into
the
roadmap
bars.
C
So
you
can
see
here
that
we
want
to
make
the
roadmap
view
much
more
valuable
by
putting
in
the
milestones
as
well
as
the
progress
here
on
the
road
right
on
the
roadmap
view,
adding
an
ability
to
expand
an
epoch
in
the
road
map
view
via
drop-down
and
then
adding
the
ability
to
edit
the
health
status,
an
issue
sidebar
to
see
if,
if
an
issue
is
on
track
and
then
rolling
that
status
up
to
the
epic
level.
So
these
are
the
things
the
plan
team
will
be
working
on
and
moving
on
to
the
create
stage.
C
C
You
can
also
see
here
if
you're,
following
on
closely
you
care
a
lot
about
architectures,
that
right
now,
based
on
this
architecture,
diagram,
we've
kind
of
shifted,
the
burden
of
h.a
away
from
the
Italy
nodes
and
on
to
the
prefect
proxy,
and
so
this
also
is
considered
an
alpha
release,
because
we've
essentially
made
a
one-component
h.a,
but
we've
introduced
another
one,
that's
not,
and
so
before
we
get
to
general
availability.
This
component
right
here
will
also
become
a
che
as
well,
so
that
will
have
no
components
in
the
application
that
are
not
highly
available.
C
C
Dragging
a
picture
off
of
your
desktop
into
an
issue
would
work
well,
if
also,
if
you
drag
a
picture
off
your
desktop
and
kind
of
drag
it
on
top
of
another,
one
it'll
essentially
make
a
new
version
of
that
just
allowing
for
a
lot
better
usability
of
this
feature
supporting
better
zoom
functionality
for
longer
designs.
So
in
a
case
that
you're
designing
a
longer
web
page
that
has
a
lot
of
content
bent
below
the
fold.
There's
a
bug
right
now
that
you
can't
even
really
zoom
in
on
this
so
we'll
be
making
it
change.
C
D
I'm
Jason
money
I'm,
the
director
of
CIC,
forgive
for
I'm,
the
director
of
product
for
CI,
CDI,
cat
lab
and
I
want
to
cover
a
few
things
related
to
CI
CD
that
we're
releasing.
So
let
me
share
my
screen
mm-hmm
so
same
thing.
Here,
we've
got
our
videos
up
and
we've
got
a
bunch
of
great
items
that
we're
delivering,
but
I'm
just
gonna
cover
a
few
of
them.
If
you
have
any
questions
about
any
other
ones,
you
can
always
jump
into
these
and
we'd
be
happy
to
answer.
D
D
You
have
a
lot
of
different
data,
that's
flowing
through
and
artifacts
being
created,
and
it
can
be
complicated
to
manage
that
we've
had
for
a
while
this
expire
in
policy,
where
you
can
set
a
date
that
you
know
if
something
is
older
than
three
days
or
six
months
or
whatever
you
can
have
it
automatically
be
deleted.
But
what
that
didn't,
give
you
the
ability
to
do
is
say
you
know,
but
I
always
want
to
keep,
for
example,
the
latest
artifact
for
every
job,
that's
on
an
active
branch.
D
So
what
the
combination
of
this
event
plane
and
his
feature
will
do?
Is
it
will
let
you
have
a
very
aggressive,
expiring
policy,
so
things
are
being
cleaned
up
rapidly,
but
you're
always
confident
that
you've
got
the
latest
artifact
for
any
job
that
ran
on
an
active
branch
and
you
can
manage
your
disk
space
that
you're
using
in
that
way.
D
Another
super
super
exciting
one
is
making
it
possible
to
you,
configure
the
gait
lab
runner,
let's
we
backed
by
AWS
for
our
gate,
so
this
will
give
a
ton
of
flexibility
to
teams
that
want
to
use
for
gate.
Forget
ECS
in
particular
for
backing
the
container.
The
containers
that
are
run
as
part
of
your
CI
CD
pipelines,
so
it'd
be
a
great
way
to
scale
your
run
or
fleet.
Have
it
managed
automatically
as
part
of
the
building
that
you're
already
familiar
with
you're
already
using
AWS
and
just
really
get
a
great
experience.
D
D
Next
up
and
there's
a
ton
of
improvements
here
that
we're
making
on
the
package
side
around
kind
of
the
operation,
maintenance
you'll
see,
there's
a
couple
other
issues
there
that
are
about
cleaning
up
and
garbage
collecting
inside
of
the
package
repository.
But
this
is
another
one.
That's
just
going
to
make
it
easier
to
manage
that
container
registry
and
adding
deploy
tokens.
Removing
deploy
tokens
can
now
be
done
via
the
API
or
will
be
able
to
be
done
via
the
API
and
we're
continuing
to
focus
on
on
these
kind
of
quality
of
life.
D
Kickoffs-
and
this
is
another
really
exciting
feature
that
we're
excited
to
be
heading
to
the
to
that
capability,
and
this
will
automatically
generate
a
change
law
and
attach
it
to
the
release
for
you,
so
you
don't
have
to
worry
about
it
at
all.
It
will
use
the
the
commits
and
build
a
list
of
changes
that
are
a
part
of
this
release
for
you.
You
can
expect
us
to
continue
iterating
on
the
the
releases
feature
and
is
another
one
where
we
would
love
to
hear
your
feedback.
D
If
you,
if
you
started
using
this
and
then
next
up,
is
a
super
popular
feature
when
it
comes
to
managing
environments,
and
this
is
the
ability
to
set
truly
dynamic
environment
URLs
when
you're
using
review,
apps
or
environments.
So,
for
example,
here
you
can
see
that
you
get
a
basic
basic
example
of
what
we
will
assign
for.
You
will
generate
for
you,
but
this
issue
will
then
let
you
name
it
literally
anything
that
you
want,
and
one
really
really
cool
thing
about.
D
The
way
that
we're
implementing
this
is
that
we're
going
to
make
it
possible
to
pass
an
environment
variable
between
jobs,
I'm.
So
there's
a
related
issue
here,
that's
another
one
of
our
most
very
popular
items
in
the
CI
space.
That's
linked
to
you
here,
pass
variables
between
jobs,
so
we're
gonna
be
updating
this
one
potentially
pulling
this
in
as
well
and
delivering
this
feature
as
well,
if
not
at
the
same
time,
shortly
thereafter
and
as
you
can
see,
this
is
er.
D
E
Thanks
dad,
my
name
is
Kenny
Johnston
I'm,
the
director
of
product
covering
the
ops
section,
I'll,
show
my
screen
real,
quick,
I'll
jump
back
and
forth
between
sharing
and
not
this
is
ops
section.
It
covers
the
configure
and
monitor
stage,
there's
a
number
of
kind
of
key
themes.
The
primary
one
that
I'm
going
to
go
through
is
about
dogfooding,
we're
really
trying
to
ramp
up
our
use
of
these
stages
and
the
features
in
these
stage
within
the
gate.
E
Lab
teams,
so
I'll
highlight
some
of
the
places
where
we're
already
gotten
great
feedback
and
are
focusing
on
really
prioritizing
our
effort
to
make
sure
we're
building
a
tool
that
our
internal
teams
would
use.
The
first
one,
though,
is
a
little
bit
outside
of
that
and
that
is,
we've
had
ongoing
work
around
the
CI
based
cluster
configuration.
E
So
we'll
be
continuing
that
work
in
nine
in
the
configure
orchestration
team,
where
we're
adding
both
more
applications
that
can
be
configured
via
CI,
as
well
as
the
first
implementation
of
Auto,
creating
a
cluster
management
app
for
you
when
you
add
a
cluster
so
that
if
you
ever
wants
to
go
and
add
additional
configuration,
you
can
easily
have
a
project
there
to
do
so.
Also
in
the
configure
stage,
we're
working
on
adding
the
ability
to
utilize,
Auto
DevOps
are
kind
of
prescribed
to
find
state
for
complete
devops
pipeline
you
in
air-gapped
environments.
E
So
there
are
many
customers
who
use
git
lab
in
self-managed
instances
and
don't
have
access,
don't
allow
outbound
access
and
some
of
the
features
of
auto
devops
still
do
rely
on
the
live
fetching
of
packages
or
container
images
from
an
outside
source.
So
we're
working
to
move
that
so
that
you
can
do
it
in
air
gaps,
environments
and
then
also
using
cloud
native,
build
packs.
E
E
The
the
product
manager
here
has
done
a
bunch
of
customer
discovery,
but
where
the
engineering
team
is
learning
about
terraform
learning
about
some
of
the
best
practices,
they
already
have
an
mr
up
for
documenting
kind
of
the
preferred
terraform
flow
using
git
lab
and
one
of
the
first
things
that
the
product
manager
has
identified
victor
is
this
need
to
provide
and
surface
more
information
about
the
changes
in
your
terraform
plan
in
an
mr
widget
and
so
they're
going
to
be
doing
discovery
and
design
on
adding
an
mr
widget.
Just
like
this.
E
E
Other
things
were
just
bugs
that
we
encounter
it
around
color,
visualization
and
grouping,
but
some
of
the
key
ones
were
around
being
able
to
refresh
the
dashboards
with
a
click
of
a
button
and
I
know
that
they
were
immediately
refreshed
instead
of
refreshing.
Your
browser
and
adding
annotations.
This
is
annotations
are
something
that
we
do
in
the
metrics
charts
today
natively
for
deploys.
So
when
you
have
a
deploy
from
your
git
lab
project,
you
automatically
see
in
the
chart
a
little
rocket
icon.
E
That
shows
that
there
was
a
deploy
happened
there,
but
we
want
to
add
the
ability
to
add
kind
of
customized
annotations,
both
live
on
the
chart,
so
others
can
see
them
as
well
as
programmatically
through
an
API
we're
also
continuing
to
improve
our
dogfooding
or
so
our
logging
experience.
Let
me
show
you
a
screen
shot
here.
E
Lastly,
in
our
health
group,
we
are
continuing
our
dogfooding
of
our
error
tracking
service
with
sentry.
One
of
the
most
requested
things
was
to
be
able
to
filter
the
errors
to
those
that
were
left
unresolved,
so
we're
gonna
be
adding
that
in
12.9
we're
going
to
be
moving
our
alerting
features
to
core
that
was
one
of
our
promised
gifts
over
the
winter
holidays,
so
we'll
be
working
on
that
in
12.9.
E
We're
also
going
to
be
starting
a
dog
fooding
initiative
around
creating
a
Status
page,
and
so
our
team's
presently
use
a
Status
page
service
and
we'll
be
adding
the
ability
to
identify
any
incident
and
have
it
publish
an
external
status
page
of
the
incident
description
at
first
as
a
first
NBC.
But
the
idea
is
to
have
it
be
a
full-fledged
experience.
We
can
see
a
number
of
different
incidents.
E
Drill
into
them,
see
both
comment
updates
that
are
public
public
comment
updates,
as
well
as
images
to
that
incident,
so
that
when
you're
firefighting,
an
incident,
you
can
know
that
the
gitlab
issue
that
you're
working
on
is
publishing
and
communicating
externally
the
status
of
that
incident
to
your
customers.
Those
are
some
of
the
highlights
and
again,
our
primary
focus
is
on
dog
fooding
here
within
the
configure
stage,
and
we're
really
excited
to
see
not
only
these
improvements
ship
but
have
them
be
immediately
put
to
use
by
the
collab
teams
Thanks
over
to
you.
Scott
thanks.
F
F
This
is
a
really
nice
next
step,
with
a
lot
companies
being
API
first
and
being
able
to
scan
more
than
just
what
you
can
see
in
the
web.
Browser
itself
on
the
composition,
analysis
group
again
very
much
heads
down
on
several
items.
The
thing
I
would
like
to
highlight
for
all
of
you
is
support
for
air-gap
dependency
scanning,
and
this
is
part
of
our
goal
of
supporting
and
it's
getting
highlighted
earlier,
air-gapped
or
offline
environments.
F
So
the
first
scanners
that
we're
looking
to
support
relate
to
javascript
in
this
release,
and
it
will
continue
to
expand
what
we
can
do
within
dependency
scanning
offline
and
with
the
release
it's
just
about
to
go
out.
We
now
have
air
gap,
support
for
sassed
and
we're
working
on
dependencies
canning.
Those
are
really
nice.
Big
steps
for
our
customers
around
the
world
who
aren't
connected
to
the
Internet
for
defend
the
big
deliverable.
This
release
is
the
MVC
for
our
standalone
and
vulnerability
objects.
This
is
improving
our
dashboarding
and
our
reporting.
F
What
I
would
highly
recommend
his
watch
Matt's
video?
That
again
is
back
here
on
the
page.
He
does
an
amazing
job
walking
through
all
the
details
of
what
this
means
for
you
as
a
good
lab
user
and
there's
how
we're
really
excited
about
it.
It's
been
a
long
time
coming.
It's
a
big
major
changes,
the
back
end,
but
it's
going
to
improve
our
reporting.
F
The
final
thing
related
to
the
application
infrastructure
security
team.
We
are
on
track
to
release
the
last
statistics.
We
went
over
this
on
a
previous
call
in
great
detail.
I'd
highly
recommend
you
watch
that
video
as
well
as
watch
the
kickoff
video
for
it,
but
I
know
we're
running
short
on
time,
so
I
want
to
get
it
over
to
Josh.
Let
Josh
walk
through
enable
in
there.
As
always,
you
have
any
questions
on
anything
you
see
in
the
release.
F
B
Yeah,
we
are
working
on
two
key
themes
here
for
enablement.
This
release
broadly,
they
are
performance
and
scalability
as
well
as
also
features
to
improve
the
user
experience
on
some
of
these
large
scale
instances.
So,
first
one
of
things
that
we're
doing
is
we
are
working
to
roll
out
improvements
to
imports
and
export
tools.
Is
there
any
important
export
projects?
We
had
a
lot
of
great
improvements
here
in
the
last
release
and
12.8.
You
can
see
some
of
the
details
here,
really
compelling
for
trim,
speed,
improvement
for
exports
and
apes
and
memory
reduction.
B
Similarly,
on
the
topic
of
scalability
we're
also
moving
towards
posters,
11
and
12,
this
will
help
us
to
embrace
partitioning,
which
is
a
key
area
that
we
want
to
focus
on
here.
For
improvements,
you'll
be
aware
database
since
we've
some
very
large
tables,
and
so
we
are
working
to
Perdition
those
and
make
them
scale
better
and
so,
for
example,
we're
doing
a
couple
key
efforts
here
in
12.9,
we
are
working
to
improve
how
we
think
about
partitioning
these,
and
so
we
commissioned
the
impact
as
well
as
benefind
NBC
for
a
tenancy
model.
B
These
custom
post
rest
commands
versus
the
broader
format
support
which
we
had
in
place,
because
we
want
to
support
my
sequel
way
back
in
the
day.
Similarly,
on
the
performance
front,
we're
also
working
to
continue
to
improve
our
support
for
Puma.
We
have
a
number
of
great
performance
improvements
for
Puma,
it's
running
on
a
good
portion
of
our
fleet
in
get
lab
comm.
We
want
to
continue
that
rollout
and
get
lab
comm,
and
we're
also
working
to
prepare
to
offer
this
to
customers
and
recommend
it
to
our
customers.
B
On
the
instances
they
run
themselves
self
managed,
and
so
we
are
doing
that
by
working
into
the
fund.
The
best
felt
dyes
for
Puma
and
for
documentation
for
the
right
mix
of
workers
and
threads
based
on
their
node
sizes,
as
well
so
further
improvements
here,
as
you
can
see,
to
make
it
a
little
more
reliable
and
getting
ready
for
everyone
to
run
it.
B
Nine,
so
lay
the
foundation
tell
them
I'm
going
to
go
ahead
and
actually
add
support
for
GL
and
package
files
and
we'll
use
that
tool
that
framework
tool
and
continue
to
improve
it
and
then,
finally,
on
the
kind
of
ecosystem
side
of
things,
we
are
working
to
bring
in
sense
level.
Configuration
first
for
certain
integrations
instance.
Level
was
a
smaller
NDC
and
subgroups
will
come
next,
but
we
want
to
able
enable
things
like
JIRA
configuration
at
the
instance
level.
B
So
you
don't
have
to
configure
it
for
every
single
project
you
have,
which
might
be
hundreds
and
hundreds
of
times
manually,
which
is
a
current
path
that
you
have
to
kind
of
support.
So
it's
all
reduce
a
lot
of
the
mains
overhead
for
our
JIRA
configuration
in
particular.
So
we
have
going
on
for
the
enablement
section
and
back
to
you
Scott,
to
wrap
us
up.
Thank.