►
From YouTube: 13.8 Release Kickoff (Public Stream)
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
All
right,
it's
nine
o'clock,
hi
everyone,
my
name
is
anubhav,
I'm
the
vice
president
of
product
management
here
at
kit
lab
and
welcome
to
the
final
release.
Kickoff
call
for
2020.,
as
we
bid
goodbye
to
2020.
I
wanted
to
acknowledge
how
hard
this
year
has
been
for
many
of
us
and
to
be
honest
personally,
I'm
blessed
to
be
surrounded
by
the
amazing
team
members
here
at
gitlab
and
the
async
by
default
culture
that
has
made
it
possible
for
me
to
have
less
stress
and
focus
on
my
friends
and
family
during
these
hard
times.
A
A
The
other
thing
that's
super
interesting
is
how
we
have
contributed
to
the
broader
community
and
to
the
monetized
skier.
So
this
shows
the
number
of
features
and
improvements
that
went
into
core
starter
premium
and
ultimate,
and
I
love
the
fact
that
we
have
been
able
to
do
this
across
all
the
tiers
and
finally,
there
have
been
262
687,
merch
requests
contributed
by
the
community
in
here
to
date,
even
during
this
typical
time.
A
So
I
want
to
thank
the
entire
community
for
living
with
us
and
embracing
the
everyone
can
contribute
value
for
the
rest
of
the
call.
I
just
want
to
start
off
with
saying
that
we'll
we'll
start
with
secure
and
defend
stage
followed
by
enablement
and
then
kenny
and
eric
will
walk
us
through
ops
and
dev.
As
usual,
we
plan
ambitiously.
So
what
we
are
trying
to
do
for
this
january
13.8
release
may
not
happen,
but
we
try
really
hard
to
make
it
happen
with
that.
Take
it
away.
A
B
Happy
holidays
to
everyone
from
the
sex
section
I
this
morning
finally
realized
there
was
a
use
for
my
pandemic
beard
and
it
was
to
make
sure
you
all
have
a
safe
and
happy
holiday
season.
So
with
that,
let's
hop
into
the
updates.
B
Also,
within
the
static
analysis,
team
they're
focused
on
also
making
it
easier
to
adopt
within
the
I'm
sorry,
it
tops
sas
within
the
core
and
free
tier
with
that
we're
actually
aiming
for
all
users.
The
security
and
compliance
menu
users
will
get
this
nice
carousel
to
see
screenshots
of
what
ultimate
or
gold
looks
like
and
then,
finally,
because
sas
is
in
core
they'll
just
be
able
to
click,
enable
merge
request
and
sas
will
be
enabled.
B
B
B
Here's
a
screenshot
of
what
that
looks
like
again,
you'll,
be
able
to
set
your
configurations
for
your
api
fuzzing,
including
all
the
options
that
are
advanced
and
then.
Finally,
on
the
secure
side,
some
updates
from
thread
insights,
the
final
component
of
our
work
of
enabling
the
ability
to
create
jira
issues
directly
from
standalone
vulnerability
will
be
shipping
in
the
upcoming
release.
We're
very
excited
about
this.
B
Of
course
we
want
people
to
be
using
plan,
but
we
do
understand
some
customers
are
using
jira,
so
we
want
to
be
able
to
support
you
in
being
able
to
track
your
vulnerabilities
safely
as
well
as
give
you
the
path
to
move
over
to
our
plan,
offering
also
the
ability
to
filter
by
the
vendor
name
on
your
vulnerability
report.
B
Here's
a
screenshot
of
what
that
would
look
like.
So
today
you
can
only
select
the
type
of
scanner,
you'll
have
the
ability
to
obviously
gitlab
and
all
of
our
scanners,
but
if
you're
using
a
third-party
scanner
as
part
of
our
security
integration,
you'll
be
able
to
filter
by
that
result.
So
give
you
an
example
check
marks
is
one
of
our
integration
partners
and
they
would
have
sassed,
and
here
at
the
bottom,
would
say,
check
parks
and
you
would
see
sas
there
for
you
to
select.
B
The
team's
also
working
on
bulk
vulnerability
updates
and
what
this
allows
you
to
do
is
not
just
do
we
do
today
to
select
them
and
set
a
state,
but
also
be
able
to
get
in
there
and
add
a
comment
as
to
why
you're
changing
the
state
and
then
finally,
from
the
secure
side,
we
started
working
this
a
couple
months
ago
on
when
we're
ready
to
start
looking
at
initial
integrations
with
it.
But
our
new
generic
report
schema.
B
This
will
allow
us
to
not
only
make
it
easier
to
onboard
partners
who
want
to
be
able
to
have
their
skin
in
front
of
part
of
our
dead
cyclops
workflow,
but
it
will
also
allow
us
to
be
able
to
begin
to
extension
or
extend
what
we
can
report
from
our
own
scanners.
This
is
going
to
add
a
lot,
a
lot
of
flexibility-
that's
not
there
today
and
I'm
personally
excited
about
this,
because
I
know
the
team's
been
working
very
hard
on
getting
it
to
find
and
begin
rolling
it
out
on
the
protect
side.
B
One
thing
that
I
think
is
very
exciting.
Oh
I
sorry.
I
should
also
mention
this
because
this
is
also
very
exciting:
vulnerability.
Management
switched
to
viable
maturity
this
month.
That's
a
testament
to
the
hard
work
of
the
team,
our
customers,
adoption
of
it
and
so
forth.
B
So
if
you've
not
seen
vulnerability
management
a
long
time,
please
check
it
out
and
with
that
for
protect,
the
main
thing
I
want
to
focus
on
is
we're
going
to
be
taking
security
orchestration
our
new
category
to
minimal
with
a
january
release,
the
focus
is
going
to
be
on
the
ability
to
schedule
das
scans
to
run
on
demand.
B
So
here's
a
snapshot
of
what
that
would
look
like
within
that
same
policy
view
you
use
today
for
your
container
host
security
container
network
security
settings.
You
have
the
ability
to
add
a
policy
for
das
once
you're
in
the
policy
you
can
see
here
you
have
the
ability
to
schedule
when
it
will
run,
and
then
you
will
define
the
scan
profile
that
will
be
used.
B
What
I
really
like
about
this
is
on
the
screen.
You
can
see
it's
highlighted
in
red.
That
means
there's
actually
no
profile
creating
you
can
click
on
that
and
create
that
in
line
to
wrap
up
here
before
I
hand
over
to
josh
it's
that
time
of
year,
it's
not
just
the
time
to
put
ornaments
in
your
beard
and
look
silly
on
a
company
call,
but
it's
also
the
time
to
start
giving
you
some
heads
up
on
some
of
our
deprecations
in
14.0.
B
B
So
with
that,
I'm
going
to
hand
it
over
to
josh,
and
everyone
have
a
good
holiday.
C
C
One
example
scenario
for
here
is
that
if
you
have
a
planned
failover
from
your
primary
to
secondary,
you
want
to
make
sure
that
you
have
a
complete
and
up-to-date
copy,
and
your
secondary
as
replication
can
take
a
few
minutes
now.
If
you
have
a
constant
stream
of
activity
coming
into
your
primary,
it
can
be
hard
to
know
when
you
can
do
that,
and
so
now
we
can
make
it
easy
to
simply
set
it
into
read.
C
C
We
did
a
lot
of
great
work
on
13.7,
we've
retired,
a
lot
of
the
risk,
and
so
we
have
been
able
to
have
our
first
service
essentially
built
out
using
our
operator
model
and
establishing
all
the
supporting
tools
and
services,
and
we're
also
been
able
to
have
our
first
container
image
as
well
certified
through
the
red
hat
process,
and
so
now
the
work
in
13.8
is
to
go
through
and
add
additional
services
to
the
operator
and
additional
container
images
for
certification,
and
so,
if
all
those
go
well,
we
can
have.
C
We
have
this
available
in
beta
in
13.8,
which
would
be
fantastic
from
there.
We're
also
working
on
some
single
platform
improvements.
We
are
working
to
have
content
specific
indexes
for
our
search
index
and
so
right
now,
they're
all
in
one
common
index,
and
the
impact
is,
is
that
we
can't
tune
and
optimize
the
indexing
per
content
type
and
so
code
is
indexed
similarly
to
the
the
language
and
the
text
in
an
issue.
C
The
reason
this
is
important
is
that
if
you
want
to
fail
over
unplanned
your
primary
to
your
secondary,
you
want
to
be
able
to
have
your
secondary
able
to
handle
the
load
of
your
primary
and
so
have
it.
If
you
have
a
multi-node
database
in
your
primary,
you
want
to
have
that
in
your
secondary
as
well,
and
this
will
let
you
do
that
and
to
wrap
things
up
here
on
memory
and
database.
We
are
continuing
to
work
on
reducing
the
overall
memory.
Consumption
of
git
lab.
C
C
Like
data
will
help
developers
reduce
the
number
of
cycles,
they
have
to
go
through
for
a
maintainer
review
and
also
hopefully
better
tune
their
queries
for
performance
against
again
common
real
kind
of
more
like
real-life
data
here
in
production,
and
so
the
overall
goal
again
is
to
increase
velocity
and
also
make
those
changes
safer
in
production.
So
that's
the
exciting
features
we
have
here
coming
for
enablement.
I
will
pass
it
over
to
eric
to
talk
about
all
the
amazing
things
coming
in
the
dev
section.
D
Thanks
so
much
josh,
I
thought
my
christmas
game
was
strong,
but
compared
to
david.
I
have
some
work
to
do
it's
great
to
see
all
of
you
and
I'm
excited
to
talk
to
you
about
what
the
dev
section
has
in
store
for
13
8.,
as
always,
we've
kind
of
bucketed
our
our
things
into
two
big
themes.
The
first
is
new
features
in
our
second
theme
is
usability
with
respect
to
new
features.
D
I'm
really
excited
that
we're
finally
going
to
get
to
this
feature,
which
is
allowing
group
owners
to
define
compliance
pipeline
configurations
at
the
group
level.
This
is
really
important,
especially
for
those
customers
that
have
organizational
policies
or
regulated
by
some
sort
of
legislation
to
have
separation
of
duties
between
multiple
people
in
the
organization,
whether
that's
the
compliance
team
of
developers
or
some
other
teams.
D
So
what
this
is
essentially
going
to
allow
you
to
do
is
to
have
a
group
and
then
have
a
compliance
project
with
a
compliance
template
and
then
a
developer
project
with
a
compliance
framework
label
attached
to
it
with
its
own
pipeline
and
then,
when
the
pipeline
gets
executed
for
this
project,
you'll
have
a
combined
pipeline
for
both
of
these
projects,
allowing
for
segregation
of
duties
between
the
compliance
team
and
the
development
team.
So,
in
order
to
actually
accomplish
this,
though,
we
have
to
do
two
specific
things.
D
What
we
previously
previously
have
called
force
includes
by
providing
specific
compliance
templates
in
the
pipeline
at
the
group
level,
so
really
really
exciting
stuff
and
should
help
a
ton
of
regulated
customers
to
provide
that
experience
right
inside
of
the
pipeline.
D
The
next
big
thing
that
we're
going
to
be
focusing
on
is
essentially
providing
parity,
a
parody
experience
on
gitlab.com,
with
self-managed
instances
for
settings
that
are
at
the
instance
level
on.com.
Today
you
don't
have
access
to
these,
but
we're
working
slowly
to
essentially
move
these
settings
into
the
group
level
and
then
provide
a
mechanism
to
have
those
settings
cascade
down
in
your
in
your
groups.
D
This
is
a
really
fundamental
piece
of
making
that
experience
to
be
at
parity,
between.com
and
self-managed,
and
then
the
last
new
feature
I
want
to
highlight-
and
this
is
likely
going
to
ship
in
13.9-
to
have
to
be
in
users.
D
Hands
is
epic
boards,
and
I
talked
about
this
last
time,
but
I
want
to
highlight
just
all
the
hard
work
that
this
team
is
doing
to
get
epic
boards
into
the
application,
and
so
in
13
8,
there's
going
to
be
a
whole
lot
of
preparation
work,
as
you
can
see
in
this
epic
there's
been
a
really
nice
breakdown
of
this
particular
work.
D
So
a
lot
of
work's
going
to
happen
in
13.8,
getting
us
to
epic
boards
and
then
we'll
likely
see
this
feature
chip
in
thirteen
nine,
with
respect
to
usability,
there's
so
many
great
improvements,
and
it's
the
dev
section.
We
have
so
many
users.
So
it's
really
important
for
us
to
focus
on
usability,
so
I'm
just
going
to
run
through
a
whole
bunch
of
these,
which
should
really
make
your
experience
decide
to
get
much
more
delightful.
D
The
first
one
is
that
we're
going
to
allow
group
owners
to
bypass
sso
enforcement.
This
is
important
because
we've
had
multiple
cases
where
group
owners
will
essentially
accidentally
lock
themselves
out
via
a
misconfiguration
saml
and
having
turned
on
that
enforcement
with
sso.
When
that
happens,
they
have
to
contact
gitlab
support
to
help
them
unlock
their
accounts,
so
they
can
even
log
back
in.
So
we
want
to
allow
group
owners
to
bypass
this,
allowing
for
a
little
bit
more
self-service
recovery.
D
The
data
in
this
feature
to
be
a
table
and
what
this
will
allow
you
to
do
is
to
sort
it
and
filter
it
and
for
it
to
be
a
common
experience
and
other
places
to
start
the
application
quite
a
while
back,
we
shipped
a
not
operator
so
that
you
can
filter
issues
with
saying
hey.
D
I
want
all
the
issues
in
a
specific
milestone,
but
not
assigned
to
me
or
not
assigned
to
someone
else,
and
then
we-
and
so
that's,
been
a
great
experience
and
we
want
to
expand
that
experience
by
shipping
an
or
operator,
so
you
can
say
hey.
I
want
all
of
the
issues
assigned
to
me
or
someone
else
on
my
team
as
a
way
of
potentially
pairing
or
another
use
case
like
that
and
so
excited
to
see
this
one
come
on
board.
I
know
that
a
lot
of
people
are
asking
for
this
particular
filter
option.
D
We
have
what
are
called
quick
actions
inside
of
the
application,
which
are
essentially
accessed
via
a
quick
slash
in
an
issue
description,
but
it's
often
hard
to
understand
or
discover
what
quick
actions
are
available
to
you
and
when
you
type
slash,
you
just
see
like
the
top
five
quick
actions,
but
there's
also
a
ton
more.
We
have
to
read
documentation
to
figure
out
what
they
are,
so
we're
going
to
essentially
expand
this
modal
to
make
it
scrollable.
D
So
you
can
understand
what
all
the
quick,
quick
action
options
are
to
you
when
you
start
typing
that
slash
command
in
an
issue
comment,
our
requirements,
management
team
is
going
to
continue
iterating
on
this
feature
by
providing
a
basic
export
of
requirements.
Last
release,
we
provided
an
import
of
requirements
via
casv,
now
we're
going
to
provide
an
export.
D
This
is
essentially
completing
the
full
round
trip
of
allowing
an
import
from
a
legacy
requirements,
management
tool,
satisfying
those
requirements
via
ci
jobs
and
then
exporting
them
to
prove
to
whoever
needs
to
be
whoever
needs
to
see
them.
That
requirements
have
been
satisfied
right
inside
of
gitlab.
D
One
great
improvement,
our
source
code
team
is
going
to
make,
is
the
ability
to
show
which
merge
request
was
a
squashed
or
merged
commit
came
from
so
today
we
already
link
merge,
requests
and
commits,
but
we
don't
do
it
in
two
cases
where
one
where
mr
is
squashed
and
two
for
the
merge
commit
itself.
So
by
making
this
link
you'll
be
it'll,
be
much
clearer,
which
merge
request
a
particular
commit
was
linked
to
we're
also
going
to
continue
iterating
on
our
vs
code
extension.
D
In
a
in
in
previous
releases,
we
released
the
ability
to
view
issues
and
merge
requests
inside
of
vs
code,
and
now
we
want
to
show
comments
on
changed
file
disks
inside
of
vs
code.
What
this
will
allow
is
for
developers
to
essentially
execute
a
code
review
right
inside
of
the
vs
code
tool,
so
meeting
developers
where
they
are
where
they
would
make
changes
now
we're
going
to
bring
comments
there,
making
that
a
great
experience.
D
Our
team
has
also
been
hard
at
work
at
improving
the
settings
and
navigation
experience
of
git
lab
and
we're
going
to
start
by
making
improvement
by
executing
a
proof
of
concept
to
add
in-page
search
to
a
project's
general
settings.
If
you
go
to
a
project
settings
today,
there's
a
ton
of
settings
and
some
of
them
are
embedded
in
various
subdirectories,
and
so
it
can
be
hard
to
find
what
you're
looking
for
so
we're
just
going
to
add
a
simple
search
box.
D
In
a
few
days,
we're
going
to
release
the
ability
to
send
build
and
pipeline
information
and
deployment
information
to
the
jira
connect
app
and
in
13.8
we're
going
to
display
feature
flag
information
through
the
jira
connect
app.
So
this
will
essentially
round
out
all
the
information
that
the
jira
connect
app
allows
us
to
send
providing
a
providing
a
great
experience
of
all
of
your
gitlab
data
inside
of
jira,
as
always,
there's
so
many
more
great
things
coming
from
the
dev
section,
but
I
can't
get
to
all
of
them
because
of
time.
E
Thanks
eric-
and
I
agree,
we
all
need
to
step
up
our
christmas
game
after
david.
My
name
is
kenny.
I'm
the
director
of
covering
the
ops
section.
I
wanted
to
walk
through
first
of
all,
a
reminder
about
what
is
covered
within
the
op
section:
five
stages:
eight
groups
within
these
there's
lots
of
great
content,
specifically,
if
you're
interested
in
our
verify
capabilities,
we
have
a
lot
of
upcoming
work
around
parent
child
pipelines
and
pipeline
authoring
and
a
vision
for
where
our
pipeline
authoring
and
template
include
experience
is
going
to
be
going.
E
I
would
encourage
you
to
watch
those
videos,
this
great
overview
by
the
product
managers
and
designers
in
those
groups.
I
wanted
to
specifically
highlight,
with
my
time
here
a
kind
of
overarching
concept
that
I
want
to
make
sure
any
user
customer
of
gitlab
understands
and
that's
that
at
gitlab,
when
we
talk
about
usage
and
usability,
we're
really
talking
about
sweating
the
details,
we're
looking
for
little
things
that
would
improve
your
efficiency
and
your
workflow
so
that
you
can
get
your
job
done
much
more
easily
with
git
lab.
E
So
I'm
going
to
highlight
just
a
couple
of
these
in
these
slides,
but
as
as
I
mentioned,
this
happens
all
throughout
all
groups
in
our
product.
The
first
one
is
our
pipeline
success.
Emails
we've
started
sending
notices
to
users
about
the
success
or
failure
of
their
pipeline.
E
One
thing
we
noticed
is
that
users
often
had
trouble
distinguishing
between
a
success
or
a
failure,
because
the
word
success
or
failure
was
buried
later
on
in
the
message,
and
so
what
we
are
going
to
be
doing
in
this
iteration
is
moving.
That
was
it
successful
or
was
it
failed
to
the
first
word?
Those
are
the
little
things
that
help
you
get
to
what
you
need
to
action
from
a
notification
really
quickly.
E
E
What
we
heard
from
users
is
that
there
was
a
kind
of
very
frequent
process
of
drilling
into
each
individual
state
and
then
taking
an
action
there
so
we'll
be
adding
a
kind
of
triple
dot
action.
Notification
to
perform
common
actions
right
here
from
this
table
view
on
the
managed
terraform
states
that
you've
added
to
gitlab.
E
The
next
item
is
that
previously
you
would
have
to
go
retrieve
the
artifact
from
a
job
in
a
ci
pipeline
by
going
to
to
the
specific
job,
and
now
we're
going
to
be
surfacing.
The
downloadable
artifact
from
the
merge
request
pipeline
right
in
the
top
level
merge
request
view
saving
you
a
couple
of
clips
not
having
to
go
into
the
individual
pipeline
view
to
download
your
artifact
and
then.
E
Lastly,
we're
going
to
be
we've
been
adding
a
lot
of
improvements
in
our
package
stage
around
enabling
you
to
set
kind
of
cleanup
enforcement
policies,
and
what
we
heard
from
users
is
that
okay,
I
created
this
policy.
I
think
it's
right,
but
I
would
really
like
to
know
before
I
push
execute
and
potentially
do
some
destructive
action.
E
Am
I
doing
what
I
intended
it
to
do,
and
so
we're
going
to
be
designing
and
implementing
the
experience
for
taking
that
expiration
policy
and
giving
you
a
dry
run
experience
of
what
that
would
actually
mean
in
your
environment
before
you're
really
sure
that
you
want
to
start
enforcing
it.
Those
are
some
of
the
examples
of
the
usability
improvements
that
we're
working
on,
but
I
also
want
to
highlight
some
of
the
single
platform
capabilities
in
the
13
7
release
kickoff
and
will
be
shipped
in
on
the
22nd
of
this
month.
E
We
added
the
ability
to
get
api
support
for
your
deployment
analytics
and
in
13
8
we're
going
to
be
adding
the
ability
to
see
those
deployment
analytics
in
your
ci
cd
analytics
dashboard,
we're
specifically
going
to
be
separating
between
your
pipeline
and
deployment
analytics
with
this
tabular
view.
So
you
can
get
a
quick
view
of
how
frequently
you're
deploying
what
the
deployment
frequency
has
been
over
time
in
recent
periods
and
which
pipelines
are
failing
or
succeeding
when
performing
deployments
again.
E
As
I
mentioned
this
is,
there
is
a
lot
of
great
content
from
the
teams
in
their
videos.
I
would
highly
encourage
you
to
watch
them,
as
others
noted,
happy
holidays,
and
thank
you
for
all
of
your
support
through
the
course
of
2020.
A
Yes,
thank
you.
Kenny
wow
13.8
is
gonna,
be
an
amazing
new
year
gift.
I
can
already
feel
it
have
a
healthy
and
happy
holidays.
Wherever
you
are
everyone
and
we'll
see
you
in
the
new
year.