►
From YouTube: 13.11 Monthly Release Kickoff (Public Livestream)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone,
gitlab
team
members
and
divided
community
to
the
monthly,
get
lab
release
kickoff
call.
Today
we
are
kicking
off
release
13.11
and
I'm
extremely
excited
about
it.
As
always,
we
plan
ambitiously
and
our
plans
are
subject
to
change.
I
want
to
remind
you
that
you
can
all
contribute
and
and
follow
along
with
us
on
the
issues
and
videos
for
everything
we're
going
to
talk
about
here
today.
A
I'll
also
share
a
quick
reminder
on
fiscal
22,
product
investment
teams.
These
are,
in
addition
to
our
regular
stage,
work
that
everyone
else
is
doing.
One
is
application
security,
testing
leadership.
A
The
second
one
is
adoption
through
usability
to
make
it
easy
to
discover
and
use
the
features
that
we
already
ship
with
focuses
areas
like
conventional
configuration
and
various
others
and
finally
sas
first,
which
does
not
mean
sas
only.
It
means
focus
on
improving
sas
for
our
sas
customers
and
those
customers
who
are
self-managed
but
also
want
to
have
sas
capabilities.
A
I
wanna
in
in,
in
the
spirit
of
that
I
wanna
share
another
change
we
just
did
with
on
our
general
prioritization,
where
we
removed
infra
dev
issues,
which
is
a
proxy
for
gitlab.com
in
various
ways.
Above
the
item
number
six,
which
are
customer
promised
features,
this
can
have
an
impact
on
features
that
are
promised
to
customers.
A
So
if
you
have
any
of
those
please
reach
out
to
us
and
we
can
figure
out
what's
going
on
there
and
give
you
more
details,
but
it's
important
to
note
that
we
are
prioritizing
reliability,
performance
and
availability
of
gitlab.com.
A
The
order
of
operations
today
is.
We
will
start
off
with
the
enablement
section,
sorry
with
the
op
section,
led
by
kenny
and
then
we'll
move
to
the
enablement
section
read
by
josh
and
we'll
wrap
it
up
with
dev
and
sex
section
led
by
david.
Take
it
away
kenny.
B
B
First
of
all,
I
wanted
to
highlight
something
and
nuke
just
mentioned-
that
a
number
of
the
teams
and
groups
within
the
op
section
are
participating
in
activities
to
make
sure
that
we
continue
to
provide
ongoing
performance,
availability
and
stability
to
our
services.
On
gitlab.com,
we've
seen
an
exponential
amount
of
growth
in
the
usage
specifically
of
our
ci
services
over
the
last
years,
and
so
in
many
cases.
That
means
we
need
to
make
sure
we
are
leaning
in
and
supporting
that
growth
to
make
sure
that
gitlab.com
remains
up
and
running.
B
So
I'm
going
to
jump
into
some
issues
and
they're
all
going
to
fall
in
a
primary
theme
of
focusing
on
user
experience.
Some
of
them
are
going
to
seem
minor,
but
I
just
love
the
fact
that
our
teams
are
finding
these
key
insights
from
users
and
making
small
iterative
improvements
to
make
their
lives
better.
B
The
first
is
we're
going
to
remove
the
job
artifacts
message
when
there
is
no
artifact.
So
today,
when
you
were
to
look
at
a
pipeline,
it
always
shows
you
this
job
artifacts
message.
Well,
that's
not
relevant
when
there
are
no
artifacts
being
created
in
this
pipeline
or
in
this
job,
so
we're
going
to
remove
it
and
have
a
better
empty
state
for
that
messaging.
The
second
one
is
another
removal,
and
I
get
excited
about
removing
parts
of
our
feature
because
they
make
the
product
more
usable
and
understandable,
and
that's
we.
B
We
were
looking
at
this
page
when
you
look
at
the
list
of
jobs
or
pipelines
in
gitlab.
There
is
this
little
button
for
ci
lint,
which
will
allow
you
to
make
sure
that
your
ci
configuration
is
working
properly.
We
found
out
that
users
never
click
on
that
and
never
use
it.
So
we're
going
to
remove
it
so
we'll
take
that
ci
lin
button
away,
reduce
the
cognitive
load
for
users
when
looking
at
their
jobs
and
pipelines.
B
So
by
doing
this,
we'll
be
taking
first
steps
to
enable
that
use
case,
but
it
will
also
make
it
easier
for
you,
when
creating
new
pipelines,
to
not
have
to
worry
about
making
sure
you
in
some
cases
the
workaround
is
to
create
kind
of
fake
stages.
For
yourself
as
you
go,
the
next
one
is
a
great
another
usability
improvement.
So
in
gitlab
you
can
provide
code
quality
feedback
to
developers
directly
in
their
merge
requests,
and
that
comes
in
the
form
of
a
code
quality
report.
That's
a
an
extension
of
the
merge
request
view.
B
Well
what
we
found
from
users
is
that
what
they
really
wanted
to
do
is
kind
of
inflow
of
reviewing
code
understand
any
code,
quality,
degradations
degradations
or
if
there
were
code
quality
degradations.
So
we
wanted
to
show
this
in
the
diff
view,
not
necessarily
in
the
central
code
quality
report
view.
So
in
1311
the
verify
testing
team
will
be
working
on
adding
this
kind
of
simple
link
and
callout,
while
reviewing
code
changes
in
the
diff
view
in
gitlab.
B
That
highlights
whether
or
not
there
were
code
quality
changes
associated
with
that
file,
another
great
quality
of
life
improvement
and,
lastly,
we're
going
to
be
continuing
to
iterate
on
our
support
for
the
door,
4
metrics
by
providing
median
time
to
merge
as
a
chart
in
our
ci
cd
and
other
analytics
dashboards.
So
you
can
see
that
here
it
will
start
measuring
the
median
time
for
your
merge
request
gets
to
time
to
deployed
to
production.
B
It
includes
places
where
you
might
not
have
had
merge
requests
deployed.
So
you
can
get
a
sense
of
your
overall
trend
lines
for
this
important
metric
for
measuring
the
performance
of
your
devops
teams.
So,
as
I
said,
super
excited
about
all
of
our
activity,
with
we're
a
kind
of
primary
focus
on
ensuring
security
and
for
stability
and
reliability
at
gitlab.com.
I'm
looking
forward
to
13
11
being
the
best
release
ever
over
to
you.
Josh.
C
Thanks
kenny,
those
are
some
pretty
amazing.
Updates,
can't
wait
for
those
I'll
go
ahead
and
start
talking
about
our
enablement
section,
and
we
have
broken
it
into
three
main
themes
here:
adoption
through
usability,
new
markets
and
sas
first,
so,
let's
jump
into
adoption
through
usability.
We
have
a
few
key
items
here.
The
first
one
is
on
the
geo
team,
where
we
are
working
to
improve
our
g-replication
functionality.
We've
made
a
lot
of
progress
which
you'll
see
coming
soon
on
in
sas.
C
Traffic
or
get
pushes
that
will
do
the
right
thing
for
you,
even
if
you
have
five
six
ten
fifteen
g
replica,
because
it
will
pick
the
right
one
and
it
will
just
work
and
you
can
forget
about
trying
to
choose
your
local
node
and
so
to
date.
We
have
support
for
that
with
ssh,
and
this
is
adding
it
for
the
web,
which
is
super
exciting.
You
can
now
have
an
accelerated
web
experience.
C
Well,
your
assets
will
be
cached
locally
and,
of
course,
anything
in
the
database,
and
things
like
that
will
go
back
to
the
primary,
but
still
a
great
improvement
and
a
great
user
improvement
we're
excited
about
next
up.
We
are
continuing
to
work
on
improving
our
search
latency
and
we're
going
to
be
doing
that
here
in
1311
by
continuing
to
break
out
each
content
type
into
their
own
indexes.
This
not
only
improves
performance.
C
C
So
we're
very
excited
about
this
will
allow
users
on
openshift
to
deploy
gitlab
the
server
there
and
also
lays
the
foundation
for
an
operator
based
pattern
in
kubernetes
for
all
of
our
customers
and
kubernetes
as
well,
so
it
affects
and
it
will
improve
both
openshift
and
kubernetes
folks
lives
in
the
future.
Here.
So
very
excited
about
that
as
well,
and
we
can
move
on
to
sas.
First,
we
have
a
number
of
items
here:
heavy
focus
for
us
here
in
enablement.
C
C
The
goal
here
is
to
have
a
like
for
like
architecture
on
both
primary
and
secondary,
so
that,
if
you
have
a
high
level
of
traffic
in
your
primary
and
you
need
to
fail
over,
you
can
handle
that
high
level
of
traffic
instantly
on
your
secondary
without
having
to
scale
up
your
database
to
meet
that
demand.
And
so
you
can
have
the
same
number
of
nodes
in
your
primary
as
you're
doing
your
secondary
to
make
sure
that
happens.
C
So
looking
forward
to
this,
and
we're
also
continuing
to
go
through
and
adding
additional
verification
for
snippets
and
blobs
and
other
content
types
here
in
geo
and
also
continue
work
as
well
on
our
lfs
support
for
the
self-service
framework.
So
we're
going
through
and
adding
the
last
few
bits
and
pieces
of
content
types
as
well
as
also
verification
as
well
from
here.
We
can
move
more
into
the
performance
aspect
of
the
sas
first
efforts
with
the
memory
team.
C
The
current
idea
is
that
we'll
probably
split
this
by
web
api
actually
controllers
and
then
also
sidekick
and
cluster,
it's
kind
of
a
larger
split,
but
we
can
still
save
a
lot
of
memory
here,
like
what
we
did
earlier
with
graphql,
in
particular,
where
we
only
load
those
requirements
for
graphql
and
save
a
lot
of
memory,
and
so
we're
looking
forward
to
this
we're
working
on
a
blueprint
right
now
to
help
establish
this
as
a
pattern
and
to
see
if
we
can
realize
these
gains
like
we
have
the
graphql
across
a
larger
part
of
our
code
base
from
there.
C
We're
also
working
to
continue
to
reduce
our
memory.
Consumption
for
both
puma
and
side
kick
endpoints.
In
our
last
release,
we
introduced
the
ability
for
us
to
actually
measure
the
merit,
consumption
of
individual
controllers
and
routes,
and
so
we
now
have
this
great
data,
which
we
know
exactly
how
much
memory
each
of
these
is
consuming,
and
we
can
now
go
through
and
target
some
of
the
worst
offenders
to
help
bring
those
down
and
make
sure
we're
not
having
a
very
large
upper
boundary
of
memory
allocation
across
our
common
monolith.
C
We
have
some
tables
that
have
an
infor
primary
key
and
we
are
approaching
in
some
months
out
exhausting
that
key
and
so
we're
working
to
shift
those
into
a
big
into
an
eight
butt
injury
to
make
sure
we
have
sufficient
growth
room
for
significantgrowthon.com
to
come,
and
so
you
can
see
some
of
the
tables
here
and
we're
working
on
the
migrations
and
making
sure
we
have
a
solid
migration
plan
that
we
can
tune
to
help
migrate.
C
These
tables
from
the
old,
smaller
primary
key
to
the
newer,
larger
one,
and
so
you
can
see
some
tables
are
working
on
here
and
we
are
progressing
with
a
high
focus
on
this
for
the
team.
C
Finally,
we're
also
working
to
continue
to
improve
our
automated
data
migration
testing.
We
have
a
number
of
migrations
that
run
here
at
get
lab
and
ensuring
they
run
successfully
and
predictably,
when
they
get
deployed
to
production,
is
a
key
focus
area
for
the
team
as
well
to
help
make
sure
that
we
deploy
code,
we're
confident
that
it
will
work,
and
so
these
features
here
that
we're
working
on
can
help
support
that
goal.
D
There's
a
lot
of
items
within
create
and
within
plan
that
are
in
preparation
for
14.0,
which
is
not
this
obvious
milestone
we're
talking
about,
but
the
one
after
that
first
one
I
want
to
highlight,
for
you
is
the
changing
of
the
default
branch
name
within
self-managed
instances
and
between
feedback
from
the
community,
as
well
as
the
get
maintainers.
D
D
Another
item
related
to
14.00
we're
getting
rid
of
italy
nfs
support,
and
with
that
we
want
to
give
you
enough
documentation
and
time
to
begin
understanding
what
you
need
to
do
to
begin
that
migration
in
preparation
for
14.0.
D
So
this
issue,
if
you're,
currently
running
gilly,
please
check
it
out,
read
through
what
is
planned
and
then
engage
on
the
documentation.
Let
us
know
if
you
need
any
other
guidance
to
make
that
change
at
14.00.
D
A
D
In
that
process,
and
then
you're
trying
to
bounce
multiple
windows,
so
what
we're
looking
to
do
to
improve
usability
is
actually
making
sure
that
those
changes
are
visible
in
line
for
you.
So
you
can
toggle
that
open
and
see
that
direct
change
so
very
minor,
but
a
huge
improvement
to
usability
and
then
finally,
for
create,
I
mentioned
in
the
last
caller-
are
prepped
to
begin
redoing
the
menu
in
14.0.
D
This
work
is
continuing
to
happen.
If
you
want
to
check
that
out,
you
go
through
the
issue,
but
high
level
we're
going
to
begin
collapsing
on
the
top
navigation
to
start
and
then
begin
improving
a
lot
of
navigation
after
that
to
switch
over
to
the
plan
stage,
and
this
is
focused
on
the
same
thing.
Kenny
highlighted
a
little
bit
ago
about
focusing
on
infrasupport
and
improving
the
dot-com
experience,
we're
continuing
the
work
we
talked
about
in
the
last
kickoff
call
related
to
delay
deletion
of
projects
on.com
in
1311.
D
Not
only
will
delay
deletion
be
there,
but
the
ability
to
set
whether
you
want
that
on
and
off.
So
you
may
decide
that
you
want
instance,
lead
of
your
projects
as
well
as
the
ability
to
set
that
delayed
time
window.
This
is
going
to
allow
customers
to
be
able
to
recover
their
projects.
They
may
accidentally
delete
without
needing
to
engage,
get
a
lot
of
support
in
the
live
infrastructure
team
to
get
those
projects
back
to
switch
back
to
adoption.
B
D
Usability
the
the
planting
is
also
working
on
the
ability
to
delay
opening
up
sub-ethics.
This
is
currently
an
issue
that
I
have
opened,
but
you'd
have
a
list
of
say:
child
ethics
off
of
an
epic.
If
you
go
to
rearrange
them
like
you
can
today,
if
you
end
up
hovering
over
an
existing
epic,
that
tree
will
open
up
today,
and
that
makes
you
get
stuck
in
that
one.
You
have
to
go
all
the
way
back
up
and
back
around.
D
D
The
first
thing
the
team
is
working
on
is
adding
in
the
time
that
you're
spending
in
that
stage
of
the
value
stream
process,
as
well
as
including
information
as
to
what
causes
the
event
to
start
and
what
causes
the
event
to
stop
and
move
to
the
next
stage.
This
is
just
going
to
provide
that
additional
visibility
to
understand
where
your
team
is
without
having
to
drill
in
deep,
as
well
as
understanding.
Why
is
causing
that
metric
to
be
generated?
D
D
D
D
D
Standard
they
can
generate
different
types
of
output
as
part
of
their
end
of
their
run,
and
we
want
to
make
that
a
unified
experience.
So
you
have
a
better
sense
as
to
what
happened.
This
is
going
to
include
consistent
error
code
messages,
error,
code,
numbers
and
messages,
so
you
can
better
plan
out
how
you
want
your
pipeline
behavior
to
be
so
example
being
you
can
actually
set
it
to
succeed,
but
have
the
jobs
fail
and
then
understand
why
the
job
failed?
D
It's
a
nice
big
improvement,
the
composition
analysis
team
was
taking
on
for
the
entire
stage
for
sas
and
secret
detection,
we're
improving
issue
or
vulnerability
tracking
within
your
source
code.
This
is
a
huge
step
forward.
It's
a
project.
We've
talked
about
in
the
past,
but
this
is
going
to
be
bringing
a
reduction
in
false
positives
within
your
projects.
This
is
also
building
the
baseline
to
begin
to
track
vulnerabilities
across
multiple
projects
within
a
group
allowing
you
to
eventually
just
dismiss
the
vulnerability
once
and
to
dismiss
that
type
in
your
entire
group.
D
So
a
nice
big
step
forward
a
desk,
we
haven't
talked
much
about
our
browser
project.
It's
an
open
source
dashed
engine
focused
on
single
page
apps
horizon
one,
which
is
our
first
release
of
our
crawler,
is
actually
going
to
be
coming
out
on
dot
com
near
charlotte
and
then
available
to
self-managed
customers
with
1311..
D
Logging
of
output
from
authentication
anyone
who's
set
up
a
das
scan
knows
this
is
probably
the
hardest
part
of
getting
gas
to
work
properly
and
a
lot
of
scans
today
do
not
give
you
the
output
needed
to
fully
understand
why
your
authentication
succeeded
or
failed,
and
in
1311
browser
is
going
to
include
the
concept
of
generating
an
authentication
report.
So
you
can
see
exactly
how
our
crawler
interacted
with
your
app
and
then
see
why
it
failed,
and
you
can
then
go
back
in
and
adjust
the
configuration
accordingly.
B
D
We're
just
continuing
to
make
iterative
improvements.
This
is
introducing
rows
and
columns
into
your
corpus
management,
again
focus
on
adoption
through
usability,
and
you
can
see
that
this
includes
now
multiple
rows
and
the
ability
to
take
action
directly
on
the
corpus
within
the
ui
and
then
finally,
to
finish
up
with
vulnerability
management.
The
threat
insights
first
thing
they're
working
on
is
continuing
to
expand
the
bulk
status
updates.
We
introduced
with
the
last
release.
D
And
finally,
this
has
been
a
big
request
from
customers
over
the
last
several
months
to
have
the
ability
to
create
superior
vulnerabilities
within
gitlab
that
are
not
coming
from
a
scanner,
and
so
this
is
going
to
allow
you
to
work
with,
say
your
bug,
bounding
programs
and
bring
in
the
vulnerabilities
into
the
vulnerability
dashboard.
The
security
reports
and
all
the
other
components
that
you
rely
on
for
tracking
your
overall
risk.
D
First
step
here
is
obviously
introducing
the
api
and
then
in
further
releases
will
include
the
ability
to
do
that
via
liquid
and
then
wrap
up.
The
second
section
with
protect
the
container
security
team
is
continuing
to
add
upon
what
we've
been
releasing
for
our
security
orchestration
that
went
minimal
last
month
and
now
we're
working
on
what
makes
it
viable.
This
includes
being
able
to
schedule
scans
for
advanced
against
in
that
on-demand
function
against
applications
running
in
production.
D
It's
a
nice
big
step
forward,
allowing
you
to
then
enforce
policies
within
the
project
that
cannot
be
disabled
by
users
again
great
addition
of
usability
also
ties
back
into
compliance
and
other
components
of
asd
leadership,
and
then,
finally,
this
is
another
big
work
across
the
community.
We're
looking
to
move
our
container
scanning
category
off
of
claire
and
clara.
The
two
scanners
are
used
today
and
move
over
to
trivia.
D
Trivia
is
an
open
source
project
by
aqua
security
and
together
we're
going
to
partner
to
continue
to
make
trivia
a
better
open
source
scanner,
including
the
ability
to
stand
against
containers
in
production,
which
is
something
we
do
not
support
today
and
in
partnership
with
them.
We're
also
going
to
be
making
a
big
step
forward
for
the
open
source
community
by
bringing
the
gitlab
vulnerability
database
down
to
core
and
available
to
the
open
source.
Community
that'll
also
be
a
time
release.
A
Thank
you,
david
wow,
so
can't
wait
for
the
door
for
metric
mean
time
to
merge.
I'm
super
excited
about
performance
and
usability
improvements
with
secondary
mimicry
and
search.
I
expect
openshift
will
be
very
popular.
I
look
forward
to
having
more
users
get
access
to
the
devops
report.
It's
been
a
long
time
coming
and
love
the
opinionated
consistent
default
behavior
in
line
with
our
product
principles
for
asd
scanners
and
jobs.
A
Prosecutor
improvements
will
be
a
game.
Changer
can't
wait
for
that
project
level.
Mandatory
dash
policies
are
in
extremely
high
demand
from
our
enterprise
customers.
So
great
to
see
us
do
this
13.11
promises
to
be
an
amazing
and
compelling
release,
and
I
didn't
even
cover
many
of
these
things
that
we
are
doing
so.
Thank
you.
Everyone.