►
From YouTube: Monthly Release Kickoff - 13.10 (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
welcome
to
the
monthly
release,
kickoff
call
for
gitlab
for
release
13.10.
If
you
want
to
follow
along
with
us,
you
can
come
join
us
at
the
release.
Kickoff
page
on.
A
About.Release.Gitlab.Gitlab.Com
slash
direction,
slash
kickoff,
where
you
will
see
videos
and
issues
that
we
are
working
on
this
year,
one
as
usual.
I
want
to
remind
everybody
that
we
plan
ambitiously,
which
means
we
emphasize
velocity
or
predictability,
and
if
some
of
these
things
don't
make
it
that's
that's
because
we
plan
ambitiously.
A
The
second
piece
I
want
to
talk
to
you
about
this
time
is
the
fiscal
22
product
investment
themes.
I
think
I
touched
upon
this
last
time
in
january,
but
we
made
some
more
refinements
to
it.
Two.
A
Fiscal
22
product
themes
are
emphasis
areas
and
not
necessarily
the
comprehensive
view
of
everything
we're
going
to
do
for
the
year
of
fiscal
22,
and
therefore
you
will
see
certain
explicit
areas
of
emphasis
as
opposed
to
a
comprehensive
list.
So
the
second
piece
is,
it's
really
just
three
items
of
focus
for
this
year:
application
security,
testing
leadership.
A
A
The
fiscal
year
theme
is
sas
first,
not
sas
only,
and
it's
really
to
make
sure
that
we
bring
parity
to
the
sas
of
the
feature
sets
that
are
available
on
self-managed
we've
had
a
couple
of
years
where
we
know
we
have
started
to
slip
in
terms
of
the
parity
and
we
want
to
just
bring
it
back
on
track.
So
that's
the
focus
area
here
with
that.
A
Let
me
share
the
roll
call
today,
we'll
start
off
with
dev
and
sec,
which
david
will
cover
followed
by
ops
where
which
kevin
will
cover
here
kevin
will
introduce
himself.
He
works
in
the
ops
team
and
then
enablement
with
josh
that
let's
get
started,
take
it
away
david.
C
Thank
you
noob
and
welcome
everyone
to
the
kickoff
call
before
I
get
started.
I
just
want
to
take
a
moment
to
acknowledge
the
difficult
times
a
lot
of
people
are
experiencing,
whether
it's
the
hundreds
of
thousands
in
texas
who
still
don't
have
their
power,
their
water
or
others
across
the
country,
because
this
storm
was
impactful
to
a
lot
of
states.
I
want
to
let
you
know
that
our
hearts
are
with
you
and
we'll
keep
you
all
and
your
families
in
our
thoughts.
C
So
with
that,
let's
hop
in
nuke
just
mentioned
the
themes
and
we'll
start
with
the
dev
section.
First,
the
dev
section
updates
are
primarily
around
the
usability
component,
starting
off
with
create
we're,
adding
the
ability
to
allow
force
push
onto
protected
branches.
C
C
The
first
focus
is
actually
on
these
top
three
menus
here.
They,
this
will
be
a
multi-milestone
project.
Our
first
goal
is
to
combine
these
three
buttons
into
one.
All
this
work
was
done
all
the
research
by
our
ux
research
team,
identifying
best
workflows
and
improving
the
overall
usability
of
the
product.
So
here
is
a
working
prototype
of
what
that
would
look
like
you
can
now
see.
I
have
a
single
button
at
the
top.
I
can
click
on
it,
go
down
and
select,
say
groups
and
then
save
view.
C
C
C
C
It's
a
known
problem
that
git
has
a
very
hard
time
with
doing
incremental,
backups
and
usually
they're
just
full
snapshots
and
with
our
technology
we
have
today
with
getaway
and
the
stuff
we've
built
into
git
lab
itself,
we're
going
to
be
able
to
offer
that
incremental
backup
allowing
to
get
snapshots
and
time
and
be
able
to
run
backups
faster,
especially
on
a
large
instance
and
finally,
to
wrap
up
the
updates
for
create,
with
ecosystem
we're
beginning
to
improve
how
our
jared
integration
works.
C
Today
and
obviously
this
is
not
a
jira
integration,
because
I
work
at
gitlab
and
I'm
using
our
issues,
but
you
have
something
similar
I'd
say,
get
jira
issues
and
you
can
click
on
a
list.
You
see
the
list,
you
click
on
one
of
these
items
and
takes
you
over
to
jira.
We
want
you
to
be
able
to
stay
within
the
con
context
of
git
lab,
especially
if
you're
a
developer,
who
spends
95
of
your
time
there.
C
Taking
you
over
to
jira,
to
make
an
update
to
come
back
to
gitlab
is
very
annoying,
and
so
this
is
a
mock-up
of
what
that
would
kind
of
look
like.
So,
to
start
off
with
1310
it'll
just
be
the
detailed
view,
as
you
see
here,
not
editable,
and
over
the
next
milestones
will
begin
to
add
the
ability
to
edit
see
comments,
add
comments
and
so
forth
over
to
manage
the
item
I
wanted
to
highlight
for
you.
It
ties
both
back
to
usability
as
well
as
the
ast
leadership
and
you've
talked
about
the
beginning.
C
C
Let's
talk
about
plan
first
item
on
highlight
is
we're
beginning
our
multi-milestone
work
on
customizable
issue
types
today,
there's
obviously
just
the
one
primary
we've
added
incident
recently,
but
we
want
to
expand
beyond
that
and
give
you
options
and
you'll
see
here
on
this
example.
Here
I
think,
such
as
feature
bug,
enhancement
and
tech,
debt
and
that'll.
C
As
the
tell
this
issue
says,
delay
deletion
would
be
a
great
feature
by
default
to
avoid
catastrophes.
So
today
you
can
actually
set
a
window,
but
it's
not
the
default,
and
we
want
that
behavior
to
be
exactly
like.
It
is
today
for
groups
where
it
is
put
into
this
temporary,
pending
deletion
status.
So
if
you
did
make
a
mistake,
you
can
easily
recover
it.
C
This
will
also
allow
us
to
inherit
the
results
in
the
settings
from
above
down
into
the
project
level
and
then
to
kind
of
wrap
us
up
here
with
the
sex
section.
This
first
item
from
the
stack
analysis
team,
I'm
very
excited
about.
We
talked
about
recently
on
a
kickoff
call,
but
improving
our
accuracy
of
tracking
vulnerabilities
with
sas
and
secret
detection.
C
Today
we
do
that
by
using
the
git
commit
history.
However,
what
will
happen
is
if
multiple
people
have
all
opened
up.
Mrs
off
the
same
section
of
code
and
people
are
making
changes.
Now
those
merge
requests
are
no
longer
in
sync.
So
what
we're
wanting
to
do
is
create
a
unique
fingerprinting
component,
so
we
can
track
that
vulnerability
across
the
project.
No
matter
where
you
are,
this
will
help
address
some
of
the
false
positive
issues.
You've
all
reported.
C
It
will
also
enable
us
to
be
working
on
our
longer
term
goals,
which
is
tracking
vulnerabilities
across
the
entire
groups
across
projects.
So
if
you
dismiss
in
one
location,
dismiss
it
for
your
entire
organization
test
on
demand,
we're
looking
to
begin
the
next
step
in
that
process.
This
is
here
talking
about
selecting
a
branch.
You
want
to
run
the
on-demand
scan
against
you
see
here
in
our
prototype,
we
have
the
option
to
click
on
which
branch
we
want
it's
going
to
default
to
the
default
branch,
which
is
what
it
does
today,
but
that'll
be
customizable.
C
You'll
also
be
able
to
be
kicked
over
there,
so
you
can
create
the
commit
as
well,
but
that'll
make
it
a
lot
easier
for
people
to
get
api
closing
configured
and
online
and
then
wrap
up
secure,
we're
going
to
continue
our
work
on
our
generic
security
report
schema.
This
is
a
big
step
forward
for
us.
This
is
going
to
allow
us
to
have
a
single
report
structure
for
all
the
security
scanners
that
we
have
today.
C
C
C
C
And
so
here
you
can
see
in
our
mock-up
the
ability
to
select
which
project
you
have
your
policy
in
that
you
want
to
apply
to
this
this
project,
which
is
named
test
project
and
then
from
there
you'll
be
able
to
save
it,
and
then
it's
applied
to
this
test
project.
So
if
someone
goes
into
on-demand
scans,
you
can
see
the
settings
are
grayed
out.
They
can't
change
them,
so
that's
enforcing
that,
so
it
cannot
be
overridden
and
lose
control
of
your
security
posture.
C
A
B
B
What
you're
looking
at
here
is
the
pipeline
view
for
the
gitlab
project.
This
is
probably
a
view
that
you
are
familiar
with.
It's
a
pretty
decent
overview
of
your
pipeline
shows
you
all
the
stages,
as
well
as
all
the
jobs.
However,
you
might
notice
that
the
edges
between
the
jobs
they
actually
don't
tell
you
a
whole
lot
of
information,
the
jobs
and
all
the
stages
already
tell
you
everything
there
is
to
know
about
your
specific
pipeline
and
the
edges
actually
doesn't
add
anything
new.
B
B
B
B
The
details
is
buried
within
the
text,
but
our
eyes
tend
to
shift
towards
the
icons
and
this
problem
gets
bigger.
When
you
have
lots
and
lots
of
tests,
it's
actually
quite
difficult
for
the
user
to
find
things
that
are
actionable
things
that
they
can.
They
can
do
something
about
in
1310,
we're
going
to
change
that
so
to
start
out,
the
results
are
nested
and
they
can
be
either
collapsed
or
expanded,
and
there's
there's
updated,
icon
designs
that
draws
your
attention
without
distracting
you
from
the
details
of
the
things
you
should
pay
attention
to.
B
B
B
We
understand
that
the
editor
is
particularly
helpful
in
helping
you
get
started
with
your
ci
cd
pipeline.
You
will
then,
instead,
after
1310,
hopefully
see
a
empty
screen
that
has
a
call
to
action
to
enable
you
to
get
started.
Building
your
new
pipeline.
B
Oh,
that
is
the
wrong
one.
The
last
thing
I
want
to
show
you
is
something
different,
but
instead
of
showing
you
that
thing,
I'm
gonna
turn
it
over
to
josh.
D
Thanks
kevin,
that's
really
exciting
features
coming
from
the
app
section,
can't
wait
for
those
let's
dive
into
the
enablement
section
of
features
and
we'll
kick
off
with
adoption
through
usability.
Global
search
team
is
primarily
focused
on
this
theme.
For
this
release
and
the
primary
topic
they're
working
on
is
addressing
the
latency
we
see
we
have
seen
with
global
search
on
gitlab.com.
D
This
is
a
chart
showing
the
latency,
obviously
we're
unhappy
with
it
being
as
high
for
the
outliers
we've
been
working
hard
to
address
it.
You
can
see
some
recent
progress
and
improvements
we've
had
we,
of
course,
aren't
satisfied.
We
want
to
continue
to
improve
the
we're
working
on
a
few
items
in
this
release.
The
biggest
one
will
be
moving
comments
to
their
own
index.
D
This
release
focusing
on
the
getting
started
process
for
administrators
as
well
as
also
ensuring
that
the
documentation
is
clear
for
end
users
for
what
they
can
use
and
how
they
can
use
the
tools
available
to
them,
with
global
search
to
find
the
content
they're
looking
for
in
gitlab
from
them,
we're
also
looking
to
expand
gitlab
to
other
markets,
in
this
case
openshift.
If
you've
been
listening
to
a
few
of
our
kickoff
celestial
releases.
This
has
been
a
theme.
D
The
great
thing
here
is:
not
only
can
we
help
our
customers,
who
are
selected
openshift
as
our
platform
deploy
and
run
gitlab
there,
but
this
also
as
part
of
this,
we
are
building
an
operator
which
gives
us
a
control
plane,
which
we
see
as
the
future
of
the
cloud
data
distribution
of
gitlab
for
both
openshift
and
kubernetes.
D
The
idea
here
is
that
you
can
automate
more
of
the
day-to-day
operations
with
this
operator
and
overall
reduce
the
maintenance
burden
of
running
gitlab
in
native
and
overall,
improve
the
experience
of
our
initiators
so
very
excited
about
this
again
we're
targeting
beta
for
this
release,
which
is
really
exciting
from
there.
We
are
working
on
the
single
platform
aspect
of
things
as
well.
A
lot
of
enabling
work
happens
in
this
theme.
D
D
You
can
see
working
a
couple
topics
here.
We
just
released
support
in
alpha
last
release
and
we're
targeting
ga
and
14.0
from
there
we're
also
working
to
continue
to
improve
overall
our
disaster
recovery
product
we
hit
viable
in
13.9,
or
I
guess
we
will
in
four
days,
which
is
exciting,
and
we
are
continuing
on
to
focus
on
complete
the
main
area
here.
D
We're
working
on
this
release
is
verification
of
replication
so
confirming
for
our
users
that
the
content
isn't
deputed
correctly
we're
adding
this
to
the
self-service
framework
which
underpins
a
lot
of
our
content
types
and
we're
selecting
package
file,
verification.
The
cool
thing
is
by
adding
us
the
framework
we
get
this
not
only
for
packages
but
for
all
the
other
content
types
that
utilize
the
salesforce
framework.
D
So
a
lot
of
acceleration
there
with
the
framework
we
wouldn't
have
otherwise
been
able
to
see
we're,
also
taking
two
other
content
types,
uploads
and
lfs
and
shifting
those
into
the
framework
as
well.
This
is
where
we
get
them
on
that
go
forward
path
and
they
get
all
the
great
benefits
like
verification
for
free
from
there.
We're
also
working
to
continue
our
efforts
to
overall,
allow
gitlab
to
run
better
on
small
memory,
constrained
environments,
we're
following
two
kind
of
prongs
here
in
this
regard.
D
The
most
exciting
one
I
want
to
highlight
is
that
we've
actually
patched
the
ruby
interpreter
to
be
able
to
output
information
to
help
us
allocate
memory
use
to
features
what
you
can't
measure
you
can't
improve
and
so
having
a
ruby
monolith
can
make
peering
inside
of
it
and
getting
insights
a
little
difficult
but
being
able
to
instrument
this.
We
can
now
target
our
efforts
and
also
better
empower
the
overall
product
groups
in
gitlab
to
manage
this
on
their
own
as
well
right
how
much
memory
they're
consuming
the
trend.
D
D
Of
course
we
have
to
run
database
migrations,
and
so
we
want
to
make
sure
the
work
we're
doing
here
ends
up
back
in
gitlab,
so
others
can
also
benefit
all
of
our
customers.
So
excited
about
that
and
finally,
here
we're
also
working
to
address
a
potential
overflow
risk
for
certain
tables
on
gitlab.com.
To
be
clear.
Gitlab.Com
is
the
risk
here,
it's
much
larger
than
most
of
our
other
instances
and
has
been
around
for
a
lot
longer.
D
Other
instances
are
not
at
risk
here,
but
we
are
approaching
the
kind
of
top
level
of
the
potential
size
of
our
integer
key
on
some
indexes,
and
so
we
want
to
go
ahead
and
shift
those
over
to
a
larger
index
to
make
sure
we
have
headroom
to
continue
to
grow
on
gitlab.com
and,
of
course,
customers
as
they
approach
those
scales
as
well.
If
they
do
so,
that's
it
for
enabling
I'll
pass
it
back
to
a
new
that
wrap
up
our
kickoff
here.
A
Thanks
josh,
I
heard
a
lot
of
incredible
and
exciting
things.
I'm
just
going
to
rattle
a
few
linking
to
single
line
number
and
web
id
sounds
like
a
small
change,
but
it's
an
incredibly
useful
change
in
quality
of
life
for
developers.
A
Every
minute
we
can
save
them
is
a
great
great
service,
in
my
opinion,
incremental
repo
backups,
pretty
hard
thing
to
do
great,
to
see
us
taking
and
attacking
a
big
big
problem
and
solving
it
customizable
issue
types
I
think
they're
going
to
be
great.
As
soon
as
we
have
more
customizable
issue
types,
I
I'm
sure
we'll
have
more
requests
for
various
other
types
of
issues,
making.
First
testing
approachable
amazing.
I
think
that
will
lead
to
a
lot
of
adoption
and,
more
importantly,
value
to
users.
A
I
love
the
x-ray
view
into
the
pipeline.
I
just
call
it
the
x
review,
but
it's
amazing
to
see
the
dependencies
just
by
clicking
through
it
pipeline
edit
and
improvements
all
over
amazing
gitlab
operator
for
openshift
search,
latency
improvements
and
all
the
other
infrastructure
work.
It's
incredible
to
see
the
amount
of
things
we
try
to
pack
into
a
single
release.
So
thank
you.
Everyone
for
doing
an
incredible
job,
I
think
13
bill
10
is
going
to
be
an
amazing
release.