►
From YouTube: Monthly Release Kickoff 13.5 (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
A
A
So
what
we
discuss
here
is
subject
to
change,
although
we
try
our
best
to
meet
what
we
say
here
for
the
release
with
that,
I'm
gonna
lay
out
the
the
play
today,
we'll
start
off
with
enablement,
led
by
josh,
followed
by
dev,
led
by
eric
who
will
hand
it
over
to
kenny
for
ops
and
finally,
we'll
wrap
it
up
with
secure
and
defend
with
david.
B
Of
course
we
have
a
lot
of
exciting
features
coming
here
in
this
release.
I
can't
talk
about
all
of
them,
so
please
do
look
through
our
videos.
They'll
have
a
lot
more
detail
on
each
of
our
groups
and
what
they
are
doing,
but
first
up,
let
me
go
ahead
and
talk
about
the
work
we
are
doing
to
improve
the
maturity
of
some
of
our
areas,
in
particular,
in
this
case
the
disaster
recovery.
B
So
to
that
end,
we
are
working
on
using
our
self-service
framework
to
replicate
terraform
state
version,
terraform,
state
and
external
merge
request,
diffs
we're
also
working
to
add
support
in
the
cell
service
framework
for
get
repository-based
data
types
which
aren't
report
supported
today
and
that's,
namely
for
snippets,
as
you
can
see
here
and
doing
those
four
remaining
data
types
again
will
get
us
to
all
data
types
supported
for
replication
for
both
geogecation
and
disaster
recovery,
which
is
really
exciting.
We've
been
working
on
this
for
some
time
we're
also
working
to
go
ga
with
patrony.
B
We
have
an
experimental
status
right
now
we
have
a
couple
items
we're
working
through,
but
troney
is
the
post
pres
multi-node
postgres
solution.
We
use
on
github.com
we'd
like
to
bring
that
proven
solution
to
our
customers,
we're
working
on
getting
rid
of
one
potential
split
frame,
a
couple
other
items
before
removing
that
exponential
label
and
encouraging
our
users
to
switch
over
it
also
support
for
postgres
12,
which
our
current
version
rip
manager
does
not
we're,
also
working
to
improve
the
support
of
gitlab
on
openshift
we're
doing
this
by
working
with
red
hat.
B
Thank
you.
So
much
for
their
participation
and
help
on
developing
an
operator
that
can
improve
the
deployment
of
gitlab
and
openshift
we're
working
on
doing
a
couple
of
things,
namely
building
a
package
with
the
operator
and
the
helmet
chart
inside
of
it,
so
that
you
can
more
easily
deploy
it
into
your
cluster
and
have
it
then
deploy
gitlab,
it's
a
pretty
big
requirement
for
beta
and
so
we're
working
to
resolve
that
this
release.
B
Among
a
couple
other
things
transitioning
from
the
feature
work
over
to
usability,
we
are
driving
forward
on
improving
performance
for
gitlab
itself.
One
of
the
big
aspects
of
this
is
the
fact
that
we
don't
currently
send
down
images
that
are
sized
to
the
size
that
they're
utilized
so
for
avatars,
for
example,
they
can
be
up
to
200
by
200
pixels
in
size,
which,
as
you
can
see
here,
we
oftentimes
don't
render
them
that
way.
This
really
slows
down
page
load
speeds
and
so
we're
working
to
resolve
this.
We
have
it
running
experimentally.
On
gitlab.com.
B
Next
up
we're
working
to
automate
the
reindeer
indexes.
This
is
an
important
to
make
sure
that
your
database
doesn't
get
too
bloated
and
it
remains
performant.
Today
you
can
run
this
manually,
but
even
for
those
who
are
aware
of
it
like
we
are
on
gitlab.com,
it
can
still
still
creep
up
on
you,
and
so
we
want
to
automate
this
and
remove
one
more
thing
you
have
to
do
when
running
your
gitlab
instance.
B
Last
but
not
least,
we
are
working
on
redesigning
the
global
search
user
experience
right
now.
If
you
used
it,
it
could
stand
some
improvements
and
we
are
driving
towards
this
as
an
interim
step.
So
you
can
see
here.
We
have
kind
of
the
left
hand,
side
pane
with
a
whole
lot
richer,
set
of
facets
or
filtering
options.
B
This
will
let
you
better
drill
into
the
content
you're,
looking
for
with
the
overall
goal
of
having
a
single
page
for
all
content
types
and
having
this
side
bar
be
dynamic,
based
on
what
you're
looking
for
and
what
results
are
actually
in
your
in
your
list
and
relevant
to
your
search.
Query
so
that'll
be
a
really
huge
improvement.
We've
been
iterating
on
this
already
by
the
addition
of
the
the
status
filter
on
the
left-hand
side.
B
Now
we're
also
adding
confidentiality
and
we're
also
working
to
add
support
for
epics,
which
today
aren't
indexed
at
all
in
global
search,
and
so
those
will
also
now
be
findable
as
well.
So
that's
it
for
enablement
really
about
these
features
again
check
out
our
videos.
There's
a
lot
more.
I
couldn't
cover
today
and
with
that
I'd
like
to
hand
off
to
eric
for
dev
to
talk
about
all
the
exciting
things
that
eric
has
for
us
and
his
team
coming
as
well.
C
Thank
you
so
much
josh,
that's
some
really
exciting
stuff.
Yeah,
I'm
going
to
spike
into
what
we
are
planning
for
the
dev
section
in
13.5.
C
I
have
grouped
our
items
by
three
different
themes:
the
first
one
is
usage
and
usability
and
let's
go
ahead
and
dive
right
in
the
first
thing,
our
access
group
is
going
to
work
on
is
an
optional
admin
approval
for
local
user
sign
up.
This
will
be
a
really
nice
feature
to
allow
gitlab
signups
to
still
be
open
to
anyone
who
wants
to
sign
up,
but
then
for
them
to
be
gated
by
an
admin
on
the
back
end
right
now,
the
the
selections
are
pretty
binary.
C
It's
either
turned
off
or
it's
like
in
invite
only
or
it's
fully
open,
so
someone
can
register
and
immediately
start
using
gitlab,
but
we
want
this
to
be
a
little
bit
of
a
middle
ground,
and
this
should
really
just
help
admins
control,
while
also
enabling
people
to
sign
up
and
get
to
use
gitlab.
C
C
Our
plan
team
is
going
to
work
on
a
few
usability
improvements,
namely
promoting
issues
to
epics
and
making
that
discoverable.
If
you
are,
if
you've
ever
used
this
feature
today,
you
know
it's
kind
of
hard
to
figure
out
how
to
actually
do
this.
You
have
to
do
it
via
quick
action,
which
is
a
slash
command
in
in
issue
comments.
So,
in
order
to
promote
an
issue
to
an
epic,
you
type,
slash,
promote
and
it'll
promote
the
issue
to
an
epic.
C
C
Clicking
on
an
issue
on
the
board,
and
then
you
see
the
sidebar
pull
out
and
you
can
edit
fields
right
here
on
the
issue,
we're
going
to
start
with
the
title
and
then
expand
this
and
and
continue
making
more
things
editable
right
on
the
board.
So
you
can
work
in
context
and
in
flow
really
exciting
change.
It's
a
small
one,
but
it's
going
to
make
a
huge
difference
to
those
that
work
on
ethics
and
boards.
All
the
time
for
our
source
code
group.
We
are
launching
a.
A
C
Very,
very
shortly
to
assign
reviewers
directly
on
the
merge
request.
So,
in
addition
to
an
assignee,
you'll
also
have
a
reviewer
section,
and
this
improvement
to
that
feature
basically
matches
up.
Merge,
request
approval
rules
to
the
reviewers,
so
you
can
tell
exactly
who
you
need
to
assign,
as
a
reviewer,
to
make
sure
that
you
have
the
correct
approval
rules
when
you
want
to
get
that
mr
merged
so
great
improvement
and
should
really
help
kind
of
decrease
the
time
it
takes
to
get
the
right
people
to
do
code
review.
C
We
also
have
a
feature.
That's
called
a
draft,
mr
used
to
be
called
a
whip
or
work
in
progress,
mr,
but
you
can
only
utilize
this
feature
if
you
actually
prepend
a
little
word
to
the
the
beginning
of
the
merge
request
title
I
want
to
make
this
feature
a
lot
more
discoverable
by
adding
a
button
to
essentially
mark
a
merge
request
as
draft
that
should
really
include
increase
the
usability
and
the
number
of
users
that
actually
make
take
advantage
of
this
feature.
C
C
Lastly,
I
am
so
excited
and
proud
of
our
knowledge
team
for
getting
to
this
point,
but
in
13.5
we
are
going
to
launch
group
level
wikis.
This
is
something
we
have
been
working
on
for
quite
some
time.
I'm
very
very
excited
that
this
is
going
to
show
up
in
13.5
and
then
not
only
is
group
level
wiki's
landing,
but
we're
also
going
to
start
reflecting
properly
the
wiki's
deep
nesting
structure
in
the
sidebar.
So
if
you
have
a
ton
of
pages,
you
know
that
sub
directories
don't
really
get
nested
appropriately
in
the
sidebar.
C
So
this
is
a
change
to
make
that
happen.
So
you
can
much
more
easily
understand
the
structure
of
your
wiki,
so
huge
improvements
going
on
here
really
excited
for
this.
I
have
a
few
more
things
and
a
few
of
the
themes.
The
first
one
is
competitive
features
and
we
are
also
going
to
launch
snippets
with
multiple
files
in
13.5.
C
In
fact,
if
you're
a
gitlab.com
user,
you
can
probably
see
this
go,
live
in
the
next
week
or
two,
as
I
believe
it's
already
on
staging.
But
if
you've
used
gist
on
github,
you
know
that
they
already
have
multiple
file
gists,
and
so
this
is.
This
is
a
really
nice
iteration
to
rest
of
this
feature
to
allow
for
multiple
files
and
then
we're
also
going
to
add
a
group
setting
for
default
initial
branch
name
for
new
repositories.
C
C
This
is
essentially
a
way
to
help
streamline
the
process
for
migrating
from
a
gitlab
self-managed
instance
into
gitlab.com,
or
vice
versa.
You
can
do
this
today,
but
you
have
to
export
a
group
to
a
file
and
then
import
that
file
back
into
the
other
instance,
and
it
can
be
a
little
bit
messy
and
it's
just
not
a
great
experience.
C
And
then
our
last
feature
I
want
to
highlight
is
something
that
we
are
going
to
approve
in
our
vs
code
extension.
We
recently
officially
supported
a
vs
code
extension,
it's
our
first
new
feature
to
that
extension
by
allowing
users
to
insert
snippets
into
the
current
file
that
they're
in
in
vs
code.
So
this
should
really
help
kind
of
streamline
and
make
the
development
process
more
efficient,
especially
for
if
you're,
using
the
plugin
to
have
a
list
of
snippets
and
easily
insert
those
into
your
file.
C
D
Hey
thanks
eric
my
name
is
kenny
johnston.
I
am
the
senior
director
of
product
management
covering
the
ops
section.
Here's
my
screen,
lab
section
includes
five
stages,
verify
package,
release,
configure
and
monitor,
and
there
are
actually
nine
product
groups
working
there.
D
So,
as
others
mentioned
not
able
to
cover
the
full
gamut
of
what's
going
on
across
these
different
groups,
I'm
going
to
highlight
a
couple
of
key
issues
in
specific
themes,
but
I
would
really
encourage
you
to
check
out
both
the
videos
and
the
linked
planning
issues
that
give
you
a
good
sense
of
kind
of.
What's
going
on
across
the
entire
section.
D
D
So
what
we're
going
to
be
doing
in
this
in
13.5
is
adding
the
ability
to
set
when
you're,
defining
those
variables
the
default
value
and
description
for
them,
which
will
mean
that
when
you're,
creating
and
running
the
pipeline
form
it'll
automatically
pull
those
values
in
and
so
that
it's
much
easier
to
get
to
adjust
what
you
need
and
use
the
defaults
that
you
want
to
keep
the
same.
It's
a
great
usability
feature
to
allow
more
pipeline
runs
and
a
smoother
experience
for
running
manual
pipelines.
D
Before
I
move
on
to
the
other
themes
that
are
spanning
the
section,
I
also
want
to
highlight
that,
within
our
verify
group,
specifically
in
the
last
release,
we
have
actually
created
a
new
group
that
is
called
verify
pipeline
authoring.
That
is
really
completely
focused
on
this
usability
experience
of
getting
started
with
gitlab
ci,
and
so
that
group
has
a
number
of
issues
that
they're
already
scheduled
for
13.5.
I
just
wanted
to
highlight
two
of
them
specifically
one
when
you're
writing
your
yaml
file
and
you
want
to
do
a
linter
on
it.
D
There's
a
linter
interface
directly
within
gitlab.
Previously
you'd
have
to
copy
your
gitlab
ci
eml
file.
That's
in
the
project
you're
viewing
this
linter
in
into
this
pane,
and
then
you
would
see
the
linter
warnings
from
as
a
result
of
that
yaml
syntax
check.
What
we're
going
to
do
in
135
is
automatically
load
that
so
when
you
go
check
the
yaml
lint,
you
can
immediately
see
any
syntax
warnings
that
were
generated
for
the
yaml
file
for
your
specific
project.
D
But
what
we
really
want
to
do
is
make
the
experience
of
troubleshooting
your
pipeline
once
you're
as
you're
authoring
it
much
more
smooth
by
giving
you
rich
context
into
to
look
at
the
kind
of
specific
syntax
that
you
might
be
missing
or
need
to
improve
for
your
pipeline
to
run
successfully
switching
gears
a
little
bit.
I
want
to
talk
about
places
where
we're
entering
new
markets
and
in
past
kickoff
releases.
I've
spoken
about
our
capabilities,
around
alert
and
incident
management,
and
it's
funny.
D
I
typically
talk
about
the
next
iteration
when
we
have
yet
to
ship
the
future
iteration,
and
so
I'm
going
to
talk
about
some
future
improvements
upon
things
that
are
shipping
next
week
in
monitor
incident
management.
This
is
all
geared
towards
us,
allowing
users
to
have
a
robust
incident
management
experience
right
here
in
gitlab,
a
really
exciting
feature,
and
there
are
a
number
of
future
iterations
going
into
incident
management,
one
that
I'm
most
excited
about.
Is
this
adding
an
sla
timer
to
your
instance?
D
What
this
does
is
give
you
that
context
in
the
in
the
application
that
you're
using
to
manage
your
instance
gitlab
in
this
case.
So
what
we'll
be
adding
in
13.5
is
the
ability
to
configure
the
slas
for
your
instance
in
the
incident
settings
tabs.
D
Also,
when
you're
in
the
incident
and
you'll
see
this
type
down
time
to
sla.
That
will
count
down
from
when
the
incident
is
created
to
the
sla
hitting
and
when
it
does
get
to
zero.
It
adds
a
specific
tag,
a
bot
as
a
specific
tag,
so
that
you
know
that
these
issues,
these
incidents
have
had
their
slas
violated
and
then
the
other
thing
is
when
looking
at
a
list
of
issues
you,
for
instance,
you
would
want
to
be
able
to
filter
them
based
on
how
much
time
they
have
until
the
sla
is
up.
D
So
that
we'll
be
adding
that
to
the
incident
list
as
well.
The
last
theme
that
I
wanted
to
highlight
is
about
single
platform
and
the
ops
section
spans
so
many
stages.
What
we're
really
trying
to
do
is
bridge
connections
between
different
parts
of
your
software
development's
life
cycle
and
make
those
easier
by
where
in
the
past,
you
might
have
had
to
connect
a
couple
of
different
tools
to
perform
these
actions.
We
can
do
it
in
one,
because
we
do
provide
a
single
devops
platform
for
you.
The
issue
I
wanted
to
highlight
specifically
is
automatic
rollback.
D
So
in
our
release
capabilities
we
have
progressive
delivery
and
continuous
delivery.
That
is
the
automated
deployment
of
your
application.
We
have
different
deployment
scenarios
like
canary
and
in
this
case,
what
we're
going
to
be
doing
is
connecting
to
some
of
the
capabilities
we
have
in
incident
and
alert
management
that,
if
a
metric
that
is
defined
for
that
environment,
has
an
alert
on
it
and
that
alert
fires
during
the
progressive
delivery
or
automated
deployment
process
it'll
automatically
roll
it
back
by
performing
the
pipeline
run
from
the
last
good.
D
D
E
Let's
get
browser
shirt
here
so,
like
everyone
else,
who's
touched
on
themes
for
this
release,
we're
primarily
focused
on
the
usability
and
usage
and
with
that,
let's
just
dive
right
in
and
see
what
we're
doing
with
that.
E
So
with
regards
to
static
analysis,
we
are
extending
the
non-ultimate
non-gold
experience
now
that
we've
moved
security
scanners
down
to
core
or
to
free,
if
you're
using.com,
the
only
way
you
can
see
the
results
today
would
be
going
out
to
the
artifacts
for
that
pipeline
and
download
the
json
file
directly
and
we
want
to
make
sure
security
is
approachable,
it's
usable
and
that
does
not
provide
a
great
experience
for
someone
who's
just
starting
to
adopt
secure.
E
So
today,
when
you're
looking
at
your
pipeline,
you
can
see
that
a
warning
occurred
on
the
job
which
in
this
case,
would
be
the
dojs
scanner.
What
we
want
to
be
able
to
do
is
alert
the
user
within
the
ui.
They
know
that
they
should
go.
Look
at
those
results,
and
here
you
can
see-
we've
added
in
a
bar
very
similar
to
what
our
ultimate
experience
is
today
on
the
merge
request
and
it's
highlighting
if
there
are
new
findings,
we're
adding
also
in
this
fund
that
says
download
results.
E
This
is
going
to
then
go
grab
the
relevant
security
report
and
bring
it
to
you,
so
you
can
review
it
that
way
without
having
to
go
dig
for
it.
It's
also
going
to
point
out
that
you
can
leverage
our
vulnerability
management
experience,
which
is
in
golden
ultimate
to
do
a
better
job
of
interacting
tracking
and
managing
that
risk.
E
Within
the
dynamic
analysis
team,
the
das
team
is
adding
the
components
for
our
scanner
profile,
the
scanner
profile
we
launched
a
couple
releases
ago,
which
is
some
very
basic
information,
we're
beginning
to
add
in
additional
options
as
well,
and
then
that
allows
that
scan
profile
to
be
reused,
as
you
begin
to
build
out
new
scans.
E
The
last
item
for
the
das
team
they're
also
adding
the
remaining
items
to
the
site
profile,
and
last
time
we
talked
about
the
validating
the
target
site,
allowing
you
to
scan
any
application
that
you
own
we're
also
down
here,
beginning
to
add
an
information
related
to
usernames
passwords
and
the
other
components
needed
to
be
able
to
sign
in
and
continue
to
test.
The
application
on,
the
software
composition.
Analysis
side
we're
getting
ready
to
release
our
first
version
of
our
full,
auto
remediation.
E
It
involves
that
step
and
the
ability
to
merge
it
back
in
when
you
enable
this.
The
gitlab
bot
will
see
that
there's
an
item
that
can
auto
remediate,
it'll
apply
that
fix,
run
it,
and
if
it's
successful
it
brings
it
back
into
your
existing
merger
class.
So
completely
automated
and
it's
a
first
step
on
our
long
term
goals
being
able
to
essentially
remediate
any
finding,
both
within
your
production
side
that
you're
using
secure
for,
as
well
as
on
the
development
side
on
the
secure
scanning
side
on
on
the
fuzz
testing
side.
E
To
be
specific,
with
the
release
that
comes
out
next
week,
our
api
fuzz
testing
will
be
available
as
an
nvc.
So
we're
very
excited
about
that.
That
ties
back
the
acquisitions
we
had
back
at
the
beginning
of
the
summer,
but
with
that
now
we
want
to
be
able
to
bring
you
a
viable
experience
and
be
able
to
interact
with
vulnerabilities.
E
E
Have
the
scanner
pick
it
up
and
get
a
much
better
buzz
testing
experience
and
the
final
part
for
secure
the
vulnerability
management
category
is
getting
some
nice
improvements,
we're
going
to
be
adding
in
an
activity
column
onto
the
dashboard.
E
As
you
can
see
here,
it's
showing
you
the
ability
to
see
all
issues
that
are
associated
to
vulnerability,
not
just
the
one
that
was
created
off
the
standalone
vulnerability
page
as
well
as
show
you
whether
or
not
there's
actions
you
need
to
follow
up
on,
such
as
in
the
top
screenshot.
The
vulnerability
is
now
identified
as
remediated
and
we're
wanting
you
to
confirm
that,
so
it
can
be
closed.
E
The
other
powerful
thing
that
gives
you
is
another
filter
option
on
the
dashboard.
So
now
you're
going
to
be
able
to
filter
out.
Probably
things
such
as
there's
been
no
activity
taken.
Are
there
issues
created?
Are
we
no
longer
seeing
it
as
a
valid
vulnerability?
We
want
you
to
look
at
it
so
give
me
that
additional
power
to
triage
even
deeper
than
you
can
today.
E
The
final
thing
we're
adding
to
the
dashboard
in
13.5
is
the
ability
to
see
the
current
status
of
the
vulnerabilities
that
you're
seeing
on
the
dashboard.
So
here
at
the
top
there's
a
new
box,
it's
showing
the
last
time
the
data
was
updated
in
this
case.
It's
showing
a
scan
ran
10
minutes
ago.
But
let's
say
you
want
to
know
whether
or
not
that
scan
is
showing.
There
is
a
say
two
weeks
old,
a
month
old.
That
would
then
be
a
visible
there
for
you
as
well,
but
then
also
if
the
last
pipeline
failed.
E
We
want
to
make
sure
you're
aware
that
the
results
are
not
complete
and
you
can
come
here
and
click
on
the
tag
here
and
I'll.
Take
you
over
to
the
failed
pipeline
view,
so
you
can
see
what
happened
and
be
able
to
fix
the
problem.
E
E
So
here's
a
snapshot
of
what
the
policy
manager
looks
like
and
you
can
actually
come
down
to
the
bottom
here
and
now
add
in
send
alert
to
gitlab
and
when
you
do
that,
it's
going
to
pull
it
into
the
new
alerts,
tab
off
the
threat,
monitoring
view
off
the
security
and
compliance
menu.
You
can
see
it's
a
nice
kanban
view
of
your
findings
or
your
alerts.
E
Here
you
can
triage
them,
move
them
over
to
in
review
or
confirmed,
but
you
could
not
only
just
drag
them,
but
you
can
also
interact
with
them
directly
on
the
card.
So
here
you
can
see.
I
clicked
on
the
card
that
says
unreviewed.
I
can
change
it
to
whatever
status.
That
is
as
well
as
if
it's
a
false,
positive
or
a
false
alert.
I
can
just
click
on
the
dismiss
and
get
it
off
the
board.
E
Our
goal
is
to
give
you
this
similar
workflow
as
to
what
you're,
seeing
in
kennedy
section
with
regards
to
alerts,
management
and
incident
management,
so
we're
bringing
that
single
platformer
experience
the
whole
way
across
the
platform,
and
I
can't
stress
enough,
as
a
team
we've
been
doing
a
kickoff
related
to
the
section.
I
just
touched
briefly
on
what
we
talked
about
in
that
that
session.
So
please
check
that
out.
It's
a
great
video
follow
along,
but
a
lot
of
great
content
in
there.
With
that
I'll
hand,
it
back
over
to
hadoop.
A
Thank
you
team.
This
is
incredible.
I
was
listening
to
searchable,
epics,
editing,
issue,
titles
and
swim
lane
sidebars
group
level,
wikis
pipeline
authoring
improvements,
automatic
rollbacks,
improving
experience
for
all
and
not
just
the
ultimate
users
on
security.
I
love
how
we
are
pivoting
to
usage
and
usability.