►
From YouTube: 13.4 Monthly Release Kickoff
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
we
will
be
prioritizing
monthly,
active
users
and
we
believe
that
a
lot
of
the
adoption
and
monetization
in
the
future
is
going
to
come
through
making
discoverability
usability
and
performance
improvements.
So
look
forward
to
that
and
third,
you
will
see
all
the
issues
that
we
are
working
on
on
the
product
kickoff
page
and
you
can
contribute
to
them
or
put
in
your
comments
to
help
make
the
product
better.
A
Finally,
last
but
not
least,
we
plan
ambitiously,
which
means
things
we
say
here,
are
subject
to
change
without
notice.
Please
don't
make
any
material
decisions
based
on
that,
but
keep
checking
out
on
the
keep
coming
back
to
the
issues
to
see
what
the
latest
state
for
the
issue
is
today,
we'll
start
off
with
eric
on
dev,
followed
by
kenny,
who
will
go
over
the
ops
section,
defendant,
section,
defend
and
secure
with
david
and
finally
enablement
with
josh.
With
that
take
it
away
eric.
B
Thanks
so
much
anub,
my
name
is
eric.
I'm
the
product
director
for
the
dev
section,
and
I'm
excited
that
we've
got
two
big
themes
of
work
slated
in
gitlab
13.4.
The
first
is
enterprise
readiness,
and
this
is
not
a
theme
that
is
unfamiliar
as
I've
talked
about
it
before,
but
it's
really
around
implementing
the
controls
and
safeguards
needed
to
have
an
enterprise
grade
experience
on
both
self-managed
and
gitlab.com.
B
The
second
thing
we're
going
to
continue
working
on
is
exporting
our
audit
events
table
table
to
csv.
So
we
have
an
audit
log
section
in
the
product
here
and
you
can
see
very
simply.
What
we're
going
to
do
is
add
and
export
a
csv
button
up
here
which
will
allow
our
customers
to
export
that
data
and
import
it
into
any
other
reporting
or
sim
tool
that
they
may
have.
B
The
next
improvement.
We're
going
to
make
is
to
add
a
revoke
button
to
the
personal
access
token
tab
of
the
credential
inventory
screen.
So
the
credential
inventory
screen
is
something
we've
been
iterating
on
for
quite
a
while
and
we're
trying
to
balance
really
two
things
here:
one
developer,
efficiency
and
security.
B
So
we
provide
a
whole
bunch
of
warnings
when
personal
access
tokens
expire,
but
we
don't
really
provide
a
great
way
for
administrators
or
group
owners
to
revoke
those
credentials
and
so
we're
going
to
add
a
very
simple
button
for
administrators
and
group
owners
here
in
the
credential
inventory
screen
to
revoke
someone's
personal
access.
Token.
B
In
case
you
know
an
organization
or
you
need
to
do
that
on
some
sort
of
schedule
or
in
the
case
of
some
sort
of
event,
where
we
need
to
manage
the
credentials
a
little
bit
more
tightly
and
then
also
we're
going
to
iterate
on
our
requirements,
management
feature
and
so
a
lot
of
regulated
industries
use
our
requirements.
Management
feature
which
is
over
here
in
the
sidebar
to
list
the
requirements
and
then
mark
those
as
satisfied
via
ci
test.
B
What
this
means
in
general
is
that
we're
going
to
allow
you
to
select
how
many
times
you
want
a
specific
repository
to
be
replicated
right
now.
That's
currently
set
to,
however
many
clusters
you
have
and
for
large
repositories.
That
can
mean
an
enormous
amount
of
storage
required
to
actually
run
gitly
clusters.
So
we
want
to
be
able
to
have
that
configurable,
which
is
just
a
great
way
to
start
iterating
towards
a
lot
more
flexible
configurations
in
goodley
cluster.
B
If
you
have
used
github
in
any
sort
of
fashion,
you
have
already
probably
taken
advantage
of
this
feature,
but
what
this
is
going
to
do
is
it's
going
to
add
a
reviewer
section
in
the
sidebar
of
a
merge
request
so
that
you
don't
have
to
use
the
assignee
field
to
tell
who
and
when
something
is
going
to
be
reviewed.
So
very
simply
in
this
first
iteration
we're
going
to
allow
you
to
select
reviewers
and
then
we'll
follow
on
in
the
subsequent
releases
to
make
this
experience
better.
B
But
I'm
really
excited
to
to
add
this
into
the
product.
Finally,
we're
also
going
to
make
an
iteration
related
to
to
do's
and
design
views.
If
you
use
git
lab
a
lot,
you
likely
use
our
to-do
feature,
which
is
a
really
nice
feature
to
help.
B
So
today,
in
order
to
go
to
the
web
ide,
you
have
to
navigate
back
out
to
the
overview
tab
of
the
merge
request
and
then
up
into
the
kind
of
the
middle
widget
and
find
the
web
ide
button.
And
very
simply
what
we're
going
to
do
is
add
a
web
ide
button
right
here
on
the
diff
screen.
So
you
can
find
that
and
load
that
really
easily.
B
Our
last
our
last
improvement
related
to
an
enhanced
user
experience
is
one
that
is
really
exciting,
which
is
moving
our
gitlab
for
jira
app
and
our
dvcs
connector
for
jira
features
down
to
core,
and
so
both
of
these
things
really
do
the
same
thing.
They
connect
your
your
jira
instance
to
git
lab
and
help
facilitate
a
data
transfer
between
the
two,
but
we
want
to
really
expand
the
the
installation
success
rate
for
these
two
applications
and
just
make
sure
that
our
customers
are
having
a
great
experience
if
they
use
both
gitlab
and
jira.
B
So
I'm
excited
to
see
this
move
down
to
core
and
I
hope
that
they'll
provide
any
sort
of
feedback
that
you
have
if
you're
able
to
use
it
and
then,
lastly,
while
not
directly
related
to
something
that
you
would,
you
know,
visually
experience.
A
change
with.
I
wanted
to
highlight
this
because
it's
really
important
we're
going
to
fix
an
n
plus
one
query
problem,
which
is
in
our
notification
controller.
B
So
if
you've
ever
gone
to
your
notification
section
in
gitlab
and
you're
a
part
of
a
lot
of
groups
or
projects,
you
probably
notice
that
it
takes
a
really
long
time
to
load.
So
we're
going
to
finally
prioritize
this
and
fix
this.
This
hard
to
fix,
m
plus
one
query,
which
should
increase
the
performance
of
this
page
and
just
in
general,
increase
the
overall
experience
of
that
particular
settings
section.
C
Just
a
reminder
to
everyone:
the
ops
section
covers
the
verify
package,
release,
configure
and
monitor
stages.
I
wanted
to
follow
up
on
eric's
theme
about
moving
items
to
core,
as
my
kind
of
primary
top
highlight,
and
that
is
our
in
134.
We're
going
to
be
moving
our
feature,
flags
capabilities
to
core
if
you're
not
familiar
with
feature
flags,
it's
a
really
important
capability
that
allows
teams
to
start
taking
not
just
continuous
delivery
approaches
to
providing
value
to
their
customers,
but
progressive
delivery.
C
It's
also
a
kind
of
thing
that
allows
teams
to
not
have
to
strike
this
balance
between
shipping
fast
and
shipping
safely,
because
by
managing
your
feature,
flags,
you
can
be
more
concerted
in
your
rollout
of
new
features
and
capabilities
and
new
code
to
your
users
in
production.
So
I'm
really
excited
about
moving
this
to
core
and
giving
the
opportunity
for
more
developers
and
more
users
to
make
use
of
our
feature
flag
capabilities.
C
So,
with
that
I'll
jump
through
a
couple
of
highlights
across
the
stages
in
verify
in
132,
we
released
the
capability
to
do
matrix
builds.
This
allows
you
to
in
your
ci
definition,
create
a
kind
of
fan
out
of
different
builds
based
on
different
parameters.
The
primary
one
is
using
different
stacks
and
providers.
You
can
see
an
example
here.
What
this
ended
up
doing
was
creating,
however
many
jobs.
C
In
this
case,
I
think
it's
seven
jobs
with
just
the
job
name
and
a
reference
to
how
many
of
the
count
it
was
so
job
name,
one
of
two
and
job
name,
two
of
two
that
wasn't
super
descriptive.
It's
hard
for
users
who
are
then
trying
to
troubleshoot.
What's
going
on
in
that
job
to
know
which
one
am
I
specifically
looking
at,
so
in
thirteen
four
we're
going
to
be
adding
the
ability,
we're
going
to
automatically
add
an
append
append
to
the
job
name,
the
variables
that
are
used
when
defining
the
matrix
build.
C
We're
also
going
to
be
adding
a
graphic
visualizer,
while
writing
your
ci
yaml
file.
So
today
it
can.
It
can
often
be
confusing,
while
writing
your
yaml
and
using,
even
even
when
using
our
linter
understanding
exactly
what
jobs
are
going
to
be
created
by
adding
this
direct
visualization
we'll
make
the
process
of
authoring
and
editing
your
ci
yaml
much
more
smooth
again
in
verify,
and
this
is
in
our
testing
group.
C
We
have
always
provided
code
coverage
reports
and
if
you
work
in
a
monorepo
or
any
environment,
where
you're
producing
many
junit
reports
that
apply
to
your
merge
request,
we
would
typically
take
the
average
of
the
results
of
that
code
coverage
when
presenting
it
in
the
merge
request.
Well,
we
realized
from
users
that
that
was
difficult
to
understand
exactly
what
was
going
on
and
how
that
was
calculated.
So
we're
going
to
add
this
tool,
tip
and
explanation
that
says
which
jobs
reported
junit
coverage
and
what
was
the?
C
C
This
one
is
one
of
my
favorites:
it's
a
really
minor
adjustment,
but
shows
the
kind
of
research
that
we
did
to
understand
what
details
are
important.
Today
we
have
in
our
package
stage
a
package
repository
and
each
package
has
a
has
a
header
that
gives
a
set
of
information,
and
we
realized
when
talking
to
users,
our
great
ux
design,
team
and
research
team
did
that
it
was
better
for
us
to
adjust
the
ordering
in
which
we
were
presenting
that
information.
C
Today,
the
information
is
presented
in
this
order
with
tag
coming
and
then
the
type
of
repository,
and
then
the
branch
that
was
created
it
was
created
from
and
instead
we're
going
to
adjust
that
order
to
to
showcase
more
the
size,
and
then
the
branch
name
at
a
later
point
again,
just
making
sure
that
the
information
that
users
find
most
valuable
is
front
and
center
kind
of
the
first
thing
they
naturally
come
to
in
our
release
stage.
Again,
this
is
a
small
iteration
that
helps
and
also
connects
multiple
devops
stages.
C
In
our
release
stage,
we
have
the
ability,
in
the
environments,
view
to
roll
back
recent
changes,
especially
if
they're
deployed
with
containers
to
roll
back
in
that
environment
to
a
previous
version.
Well
in
this
iteration
we're
going
to
be
adding
a
connection
between
an
alert
that
you
might
get
and
on
that
environment
and
that
environments
page,
so
you
are
one
click
away
from
the
ability
to
roll
back
that
change.
A
pretty
minor
text
change
to
showcase
exactly
what
that
environment
is
but
allows
for
a
much
smoother
user
experience.
C
In
our
configure
stage,
we've
recently
added
a
number
of
features
around
enabling
you
to
manage
terraform
state
files
with
gitlab.
One
of
the
things
we
found
was
that
it
was
difficult
to
set
up
because
the
experience
for
performing
that
setup,
this
kind
of
main
call
here.
You
can't
even
see
the
total
configuration
that
it
goes
for.
It's
a
really
long
call.
C
And
lastly,
in
our
monitor
stage,
I
want
to
highlight,
over
the
last
four
to
five
releases,
we've
added
a
lot
of
great
capabilities
in
our
incident
management
features,
and
one
of
the
things
that
we
realized
was
that
the
process
of
interacting
with
incidents
was
radically
different
than
interacting
with
issues.
So
we're
going
to
be
doing
a
whole
redesign
of
how
you
interact
with
instance
by
giving
you
this
tab
view
to
show
summary
alert,
details,
metrics
and
logs
right
there
in
context
in
the
incident
as
you're
triaging
it.
That
will
really
help
teams
that
are
firefighting.
C
D
Thank
you.
Let
me
get
my
screen
shared
okay,
so
to
kind
of
dive
into
the
secure
defense
section.
Let's
first
talk
about
our
strategic
objectives
or
themes.
We've
been
talking
a
lot
in
earlier
kickoff
calls
about
our
offline
environment,
support
that
did
ship
as
an
npc
back
in
1210.
D
A
lot
of
security
products
today
do
not
allow
you
to
run
within
that
offline
or
air
gap
environment,
and
this
was
a
nice
differentiator
for
the
company.
Next
is
our
application.
Security
testing
leadership,
as
I
shared
in
the
last
kickoff,
call
we're
a
little
bit
behind
of
our
target
of
being
done
by
the
end
of
this
year.
D
D
This
is
super
important
to
the
team,
because
if
we
can't
make
ourselves
happy
with
our
own
product,
how
do
we
expect
other
people
to
be
paying
for
it
and
so
we're
going
to
be
spending
a
lot
of
time,
rolling
out
all
different
scan
types
and
leveraging
our
vulnerability
management
over
the
next
quarter
here
so
kind
of
dive
into
the
items
for
application,
security,
testing
leadership
and
dog
fooding.
First
for
stack
analysis
sas
is
beginning
to
support.
D
Ultimately,
the
goal
is
to
help
you
reduce
your
false
positives
and
get
to
the
actual
items
you
need
to
fix,
and
we
touched
on
this
in
the
last
kickoff
call
the
role
of
our
new
sas
based
configuration
ui,
and
you
can
see
those
custom
roles
are
showing
up
directly
as
an
editable
option
and
then,
finally,
you
were
able
to
just
go
down
and
click
create,
merge,
request
and
then
we'll
auto
generate
the
ci
configuration
for
your
sas
scanners
on
the
dash
side,
we're
continuing
to
iterate
and
improve
our
scanner
profile
on
this
release,
we're
looking
at
adding
in
timeouts,
so
spidering
timeout.
D
D
Also
within
desk
we're
improving
our
site,
validation
components
it
it.
One
thing
to
kind
of
consider
with
secure
security
is
offensive
security
testing,
so
we're
actually
attacking
I'll
put
that
in
quotes
your
applications
on
your
configuration,
and
so
here
we're
adding
in
a
site,
validation
component
where
you
can
define
which
option
you
want
to
use.
So
we
can
validate
that
that
app
is
actually
your
app
and
you
inadvertently
type
in
the
wrong
information
and
now
you're
running
a
desk
and
against
an
asset.
That's
not
yours!
D
If
you
have
not
validated
the
target,
you
can
only
run
a
passive
scan,
but
once
you
validate,
you
can
go
back
to
running
a
full
active
scan
on
the
dependencies
scanning
side.
We've
added
new
language
support
this.
This
includes
c
and
c,
plus
plus,
as
well
as
dot
net
and
c
sharp
support
again
coming
out
in
13.4
on
the
fuzzing
side,
our
mvc
for
api
fuzzing
will
be
coming
out,
so
we're
very
excited
about
that
as
well.
D
This
brings
in
the
last
acquisition
that
we
made
back
at
the
beginning
of
the
year
and
you'll
then
have
access
to
the
api
closing
starting
with
thirteen
four
included
in
that
is
also
going
to
be
the
support
for
authenticating
off
the
rest
api,
we're
going
to
be
supporting
basic
and
digest
authentication,
allowing
you
to
not
just
test
what
the
fuzzer
can
see
without
signing
in,
but
also
going
beyond
that
and
testing
the
rest
endpoints
that
have
authentication
on
them.
D
This
is
readyliveon.com,
as
you
can
see
in
the
browser
bar
here,
but
if
we
scroll
down
we're
giving
you
a
lot
of
information
on
this
initial
nbc,
not
only
just
information
about
the
endpoint
and
the
security
findings,
but
also
all
the
way
down
to
what
we
identify
would
be
a
valid
request
for
the
api,
how
we
actually
mutated
that
request
to
find
the
security
issue
and
then
the
response
that
we're
getting
from
that
so
giving
you
all
the
data
you
need
up
front
to
be
able
to
quickly
triage
and
address
the
findings
on
the
thread.
D
Insights
side,
we're
continuing
to
iterate
on
the
security
dashboards.
Here's
a
sneak
peek
of
what
the
instance
level
dashboard
will
look
like
you
can
see
here
at
the
top.
We
have
now
a
menu
on
the
side
when
you
go
underneath
it,
you
have
dedicated
widgets
on
the
dashboard
now
and
we'll
continue
to
add
more
and
improve
upon.
D
What
is
here
today
and
then
you'll
see
that
the
list
of
vulnerabilities
are
now
on
their
own
page
vulnerability
report
is
allowing
us
to
get
you
a
lot
more
information
within
the
single
view,
including
things
such
as
the
line
of
code.
That's
impacted,
what
scanner
found
it
are
there
issues
created
and
so
forth.
D
We're
also
finishing
up
our
redesign
of
the
project
level.
Security
dashboard
as
well,
and
you'll,
see
that
same
sort
of
thing
has
rolled
out
down
here
where
you'll
see
in
the
project
will
be
a
dedicated
security
dashboard
and
then
a
vulnerability
report
on
this.
I
want
to
highlight
for
you
the
improvements
we're
now
able
to
start
making
on
the
dashboard
components.
D
D
The
defense
side,
as
shown
on
the
kickoff
page,
there's
not
a
lot
of
new
content
coming
out
for
defending
thirteen
four,
and
that's
because
the
team
is
heavily
focused
on
our
first
objective,
which
is
emphasizing
usability
and
convention
over
configuration,
and
so
with
that
you
can
see
here
our
work
on
that
policy
manager
that
we
rolled
out
recently
and
here's
a
nice
screenshot
of
it
as
well.
So
the
team
is
working
on
improving
things
such
as
the
natural
language
rule
builder,
as
well
as
allowing
you
to
manage
your
policies
across
your
projects.
D
That's
a
lot
of
information
really
quickly.
So
please,
if
you
have
any
questions,
feel
free
to
comment
on
the
comments
or
on
the
issues
on
the
voice.
Kickoff
call
page
and
with
that
I'm
going
to
hand
it
over
to
josh
awesome.
E
Thanks
david,
that
is,
super
exciting,
like
others,
we
have
a
lot
of
really
awesome
features
that
we're
working
on
here
in
13.4,
and
we
only
have
time-
and
this
call
to
cover
the
highlights.
So
please
do
look
through
the
videos
that
we
have
for
each
group
to
contain
more
information,
more
detail
and
we'll
help
provide
more
context
on
all
of
what
we're
working
on
here
in
enablement.
E
The
goal
here
for
13.4
is
to
actually
start
rolling
this
out
an
experimental
fashion
for
com,
but
also
customers.
You
want
to
potentially
opt
in
and,
as
part
of
that,
we'll
also
be
working
on
making
sure
we
address
any
security
needs
to
ensure
we
can
do
this
in
a
safe
manner,
as
resizing
images
can
potentially
have
some
challenges
there.
So
that's
super
exciting,
really
looking
forward
to
that
improvement,
we're
also
continuing
to
work
through
the
biggest
you
might
say,
offenders
of
the
cash
sql
calls.
E
Next
up,
we
are
shifting
over
towards
more
the
scalability
side
of
things,
and
we
are
continuing
to
work
on
driving
towards
pg-12,
which
has
a
lot
of
performance
improvements,
but
also
additional
improvements
for
partitioning,
and
we
actually
are
pretty
close
to
being
done
with
the
opt-in
phase.
Here
we
have
a
few
items
left
to
go.
E
So
we
are
essentially
wrapping
up
the
work
here,
largely
with
pg12
and
patrony,
which
is
very
exciting,
and
we
can
now
focus
on
other
things
like
we
can
continue
to
work
on
our
moving
the
cloud
native
installation
from
viable
to
complete
and
so
we're
going
through
and
addressing
more
of
the
crew
nice
distribution,
the
gaps
that
we
have
and
addressing
them.
E
Some
of
the
key
ones
we're
guessing
here
in
13.4,
is
support
for
smart
card
and
cac
authentication,
and
also
addressing
some
additional
documentation
needs
that
we
have
for
a
few
of
the
various
charts
that
we
support.
This
will
help
round
out
support
across
the
features,
as
we
continue
to
do
things
and
target
areas
like
pages
once.
E
We're
also
working
on
additional
schema
and
migrations.
We
continue.
We
started
this
work
off
with
audited
events
and
we'll
be
wrapping
that
up
here
in
13.4,
but
we're
also
working
on
a
couple
other
new
areas
as
well,
one
of
which
is
the
container
registries
databases,
it's
working
on
to
add
the
ability
to
look
and
see
what
projects
and
groups
are
actually
consuming.
E
Moving
on
from
there
we'll
be
continuing
to
round
out
support
in
geo
for
additional
replication
types.
The
goal
here
in
13.4
is
to
essentially
have
support
for
everything,
with
the
exception
of
pages
and
so
we're
going
through
and
finishing
up
external
merge
request,
diffs
terraform
states
and
snippet
files,
and
then
we'll
also
be
working
on
adding
support
for
postgres,
h.a
or
multi-node
postgres,
and
this
way,
if
you
want
to
have
a
secondary,
which
has
a
multi-node
installation
of
postgres
to
more
kind
of
more
closely
mirror
your
primary.
E
This
way
you
can
have
a
if
you
have
a
failover,
it's
more
likely
to
be
able
to
instantly
handle
the
load
that
is
transferred
over
without
having
to
additionally
scale
and
so
for
customers
that
are
large
that
want
this
level
of
assurance.
We
cannot
provide
it
and
we're
working
on
providing
it
here
in
13.4,
but
last,
but
certainly
not
least,
we're
working
on
some
major
ux
improvements
to
global
search.
I
am
really
excited
about
this.
E
We
are
starting
off,
of
course,
in
iterative
fashion
here
with
13.4
we're
addressing
adding
the
ability
to
sort
on
issues
and
merge
requests
based
on.
You
know
how
you
want
to
order
them,
whether
it's
relevance
or
last
updated,
and
things
like
that.
We're
also
updating
the
titles
and
a
couple
other
areas
we're
ultimately
driving
towards
is
this
design
which
we
have
aligned
on
here
with
the
global
search
team,
and
I
think
it's
really
compelling
a
consolidated
result,
view
left-hand
side
fastenings.
E
You
can
drill
down
across
different
types
of
content
and,
as
you
drill
down,
you
can
get
a
different
ways
to
filter
it,
whether
it's
an
epic,
a
milestone
or
user
and,
of
course,
as
you
change
from
issues
to
merge,
requests
to
code.
These
things
will
change
as
well
so
really
exciting
for
the
improvements
here
in
global
search
and
with
that
I'll
pass
it
back
to
anew.
A
Thank
you,
josh.
That
is
exciting.
That's
amazing
amount
of
work
that
the
team's
doing.
Thank
you
very
much.
Also.
One
final
note:
don't
forget
to
check
out
13.3
release
that
is
slated
to
come
out
in
about
four
days.
I'm
particularly
excited
about
the
fact
that
package
registry
is
going
into
core.
We
have
new
coverage,
guided
first
testing
for
go,
nc,
plus
plus,
and
also
the
ability
to
create
a
matrix
of
jobs
using
a
simple
syntax.
It's
up
for
your
ci
pipelines
with
that.