►
From YouTube: 15.11 Monthly Release Kickoff (Public Livestream)
Description
A
A
For
those
who
don't
know
our
fiscal
years,
product
investment
themes,
they
are
build
a
world-class
desktop
experience
that
includes
first
class
usability.
Additional
collaboration
capability
and
AI
assisted
workflows
next
is
to
provide
Advanced
securing
compliance,
adding
depth
to
our
ultimate,
offering
bringing
software
Supply
and
shading
security
to
the
Forefront
of
software.
Development
next
is
to
bring
observability
analytics
and
feedback
into
our
devsecos
platform.
A
Empowering
organizations
to
close
the
sdlc
loop
with
user
data
and
finally
get
left
for
data
science
enables
data
scientists
and
data
engineers
into
the
devsecops
platform,
giving
them
all
the
benefits
everyone
else
has
from
devops,
including
collaboration,
reversibility
and
streamline
deployment
into
production
before
I
hand
it
over
to
Josh.
We
have
a
short
public
service
announcement
on
this
live
stream.
We
will
be
discussing
our
product
roadmap,
which
includes
upcoming
features,
and
functionality
is
important
to
note
that
the
information
presented
on
this
live
streamer
for
informational
purposes.
Only.
A
B
Thanks
David
and
I'll
be
going
through
our
enablement
section
as
David
mentioned,
and
so
hopefully
you
can
see
my
screen
here.
I
will
go
through
a
small
section
of
what
we're
working
on.
We
have
a
lot
more
that
we
are
doing
so.
Please
do
take
a
look
at
the
videos
to
learn
more,
but
we'll
jump
in
first
with
the
world-class
and
devop
experience.
Work
that
we're
doing
support
this
theme.
The
first
one
is
our
search
group
is
consuming
their
work
on
transitioning
from
elastic
to
a
newer
Zoot
based
code
Source
engine.
B
Just
looking
forward
to
having
this
be
more
available
here-
and
this
is
an
area
again
with
the
search
team-
is
working
on
driving
forward
here
and
we'll
Target
Miss
initial
phase
gitlab
dashboard,
because
it's
public
and
it's
a
great
test
for
all
lots
of
dog
food
and
make
sure
everything's
working
from
there.
We
can
move
over
to
the
Geo
team
and
we
are
working
to
add
a
new
option
to
specify
the
maximum
file
size
for
the
git
repositories.
B
B
Moving
over
to
the
Geo,
the
application
performance
team,
we
are
working
to
do
two
things.
One
is
we
want
to
go
through
and
improve
and
real-time
support
in
the
epics
area
of
our
product
to
allow
you
to
have
real-time
updating
of
description
edits
and
along
with
that
work
that
we're
doing
there.
We
also
want
to
go
through
and
improve
the
documentation
for
our
community
on
how
to
contribute
to
real-time
features.
B
Now
over
to
our
Geo
team.
We
are
continuing
our
work
to
support
a
resolve.
Ssh
pushes
to
secondaries
right
now.
If
your
push
takes
over
60
seconds,
perhaps
there's
a
large
push.
For
example,
it
times
out
this
can
break
some
workflows
and
some
pushes
and
so
we're
working
to
resolve
this
to
change
that
and
we're
pretty
confident
it
will
ship
here
in
1511.,
moving
over
to
the
maintenance
side
of
our
themes.
We
have
some
a
lot
of
work
going
on
here
as
well.
B
B
B
You
could
potentially
run
out
of
primary
key
address
space
and
by
moving
to
a
larger
index
a
larger
table
size,
we
can
go
ahead
and
resolve
that
risk.
So
that's
one
key
work
that
we're
doing
on
working
on
and
then
the
last
one
is.
We
are
work
working
to
improve
how
we
can
detect
any
kind
of
schema
differences
between
what
we
expect
on
instances
and
what
is
actually
there.
B
This
is
more
a
sanity
check
for
us
in
the
database
group
to
make
sure
that
all
of
our
self-managed
instances
have
the
consistent
and
correct
schema
that
we
would
expect
to
have
from
them
and
the
last
bit
is.
We
want
to
go
ahead
and
finish
up
our
support
of
two
databases:
a
CI
database
and
the
main
database
for
a
self-managed.
D
D
So,
let's
get
started
I'm
going
to
start
with
a
product
planning
team,
they're
working
on
some
exciting
things,
or
one
of
them
is
allowing
reordering
of
tasks
and
okrs
and
the
child
issues
within
them
in
the
work
items.
So
it'll
look
a
little
bit
like
this
they're,
also
adding
some
new
capabilities,
such
as
the
ability
to
subscribe
to
a
work
item
notification
which
you
can
see
here,
as
well
as
the
ability
to
promote
a
key
result
to
an
objective
which
I'm
very
excited
about
as
we're
dog
footing,
Au
pairs
at
gitlab.
D
This
also,
they
should
allow
users
to
convert
work
items
to
different
types
in
the
future.
So
after
okrs,
another
issue,
ux
Improvement,
that
they're
working
on
is
ability
to
hide
the
ad
option.
That's
the
one
here
when
a
user
doesn't
have
permission
to
create
tasks.
Today
it's
displayed
and
there's
a
strange
error.
That's
shown
if
someone
without
permission
does
that
then
we're
just
going
to
remove
that
that
ability
from
existing
in
the
UI
going
over
to
the
knowledge
group.
D
Next,
is
the
foundations
group
they're
working
on
a
new
navigation
that
you
can
see
here,
so
this
isn't
available
yet
for
people
outside
of
gitlab,
but
what's
really
exciting
is
that
during
15
and
11
we're
going
to
allow
all
gitlab
team
members
the
option
to
turn
on
the
new
navigation,
and
this
will
take
us
into
initial
closed
beta,
which
we're
going
to
collect
feedback
on
and
then
later
on.
Allow
this
to
be
open
for
the
public.
D
Moving
on
to
our
Integrations
and
import
team,
they're
going
to
be
working
on
some
really
interesting
things,
one
of
them
is
showing
comprehensive
summary
on
finished
GitHub
projects.
So
today,
when
you
finish,
it
shows
the
numbers
of
entities
imported,
but
it
doesn't
inform
which
entities
were
not
successfully
imported.
D
If
something
went
wrong,
we're
also
going
to
be
adding
an
ability
to
sync
existing
branch
and
commit
data
when
a
namespace
is
added
to
gitlab
for
the
jira
app.
So
in
previous
releases,
we
added
a
worker
that
that
sends
merge,
request
data,
but
it's
only.
It
only
contains
merger
Quest
information.
It
doesn't
have
any
details
about
branches
or
permits.
So
in
this
release,
we're
going
to
be
working
on
syncing.
D
With
jira
so
that
we
can
also
extract
data
from
jira
that
has
additional
data
for
the
pull
request
entity
and
the
branch
entity
moving
on
to
code
review,
we're
going
to
be
removing
some
limitations
on
murder
plus
dependency
to
support
more
complicated
dependencies
trade
treat
structures.
Currently,
it's
not
possible
to
create
a
dependency
structure
if,
like
a
is
dependent
on
B
and
B,
is
C.
D
Today
we
restrict
the
ability
to
create
dependencies
for
murder,
quests
that
already
have
a
dependency
and
we're
going
to
be
removing
those
limitations,
so
that
things
like
that
part
will
be
possible.
Wrapping
up
the
world-class
devops
experience.
Work
is
our
source
code.
True
group,
who
is
we're
going
to
be
working
on
two
things?
One
is
improving
the
forking
experience
for
better
contribution.
Experience
on
open
source
projects
can
enable
large
organizations
to
keep
right
access
to
on
projects
to
a
minimum.
D
This
is
done
by
both
fetching
the
new
Upstream
contact
content
when
a
fork
is
behind.
So
in
this
iteration
we're
going
to
intend
to
enable
users
to
create
a
merge
request
in
Upstream
projects
if
the
fork
is
ahead,
in
addition
to
allowing
users
to
merge
from
a
quark
repository,
we're
going
to
introduce
a
feature
that
lets,
you
contribute
back
to
the
Upstream
project
by
creating
a
merger
quest
in
the
UI,
when
your
branch
in
the
fork
is
ahead
of
the
Upstream
project,
and
it
will
look
like
something
like
this.
D
Moving
on
to
our
Advanced
security
and
compliance,
our
authentication
and
authorization
team
is
going
to
be
adding
customizable
roles.
So
we're
going
to
add
the
ability
to
view
vulnerability
report
as
a
customizable
permission
that
you
can
add
to
an
existing
gitlab
role
to
give
the
user
the
ability
to
view
vulnerability
reports,
and
this
is
something
we
heard
from
customers.
I'm
excited
to
see
this
being
added,
and
our
last
theme
that
the
dev
team
will
be
contributing
to
is
observability
analytics
and
feedback.
D
D
So
please,
let
us
know
if
you're
interested
and
you'll
be
able
to
see
the
Consolidated
View
for
the
dashboard
and
in
addition
to
that,
we'll
be
adding
additional
metrics
to
the
value
stream
dashboard
we're
going
to
be
adding
vulnerabilities,
metrics
and
merge
request
throughput
metrics,
so
the
comparison
panel,
which
is
what
I
showed
before
this
is
going
to
allow
decision
makers
to
understand
how
different
metrics
are
performing
relative
to
each
other
or
to
identify
Trends
and
patterns
in
the
data.
That
concludes
all
the
work
for
the
deaf
section.
E
Awesome
thanks:
Marie
y'all
have
a
lot
of
really
good
stuff
coming
up,
particularly
excited
to
see
the
the
updates
to
the
value
stream
dashboards.
That's
really
cool
yeah,
so,
as
I
mentioned
I'm
going
to
be
talking
through
the
updates
in
the
SEC
section
for
this
Milestone.
So
first
up
we're
primarily
focused
on
Advanced
security
and
compliance
as
per
usual,
and
we
have
a
number
of
projects
in
flight.
This
Milestone
that
are
intended
to
improve
user
workflows
across
our
governance
capabilities,
in
particular.
E
So,
first
up
the
thread.
Insights
team
is
working
on
delivering
a
project
that
will
add
pre-selected,
vulnerability,
dismissal
types
or
reasons
to
the
vulnerability
dismissal
workflow.
So
today
we
don't
consistently
give
users
a
really
quick
way
to
add
a
reason
for
dismissing
a
vulnerability.
They
have
to
just
write
a
comment
for
each
vulnerability
that
they
want
to
dismiss,
and
so
this
Milestone
the
team
is
adding
five
specific
dismissal
reasons
to
the
workflow
and
those
will
be
acceptable,
risk
false
positive,
mitigating
control,
not
applicable
and
used
in
tests.
E
So
those
are
really
common
reasons
why
folks
might
want
to
might
want
to
dismiss
a
vulnerability,
and
so
the
the
Quick
Picks
will
make
it.
It
will
make
the
process
less
time
consuming
and
more
consistent
for
teams
that
want
to
be
able
to
look
back
and
easily
see
the
main
reasons
why
vulnerabilities
have
been
dismissed
next
up.
The
compliance
team
is
working
on
group
level
compliant
on
improvements
of
the
group
level,
compliance
framework,
reporting
and
management
capabilities.
So
last
Milestone
they
released
an
MVC
of
the
compliance
framework
report.
E
And
finally,
the
compliance
team
is
working
on
UI
filtering
for
streaming
audit
events.
So.
Currently,
users
have
to
use
the
API
if
they
want
to
add
filters
to
audit
event
streams.
So
if
you're
only
trying
to
send
certain
types
of
events
to
an
external
system,
that's
a
little
bit
difficult
to
do
today
because
you
have
to
just
use
the
API
for
that,
and
so
the
team
is
adding
the
ability
to
do
this.
E
Do
this
filtering
in
the
UI
so
that
it's
easier
to
Pare
down
those
events
that
are
set
in
the
Stream,
the
Securities
policy
security
policies,
team
is
working
on
role-based
approval
for
scanned
result,
policies
and
plans
to
ship.
This
feature
this
amount
in
this
Milestone,
so,
in
addition
to
being
able
to
specify
approvers,
either
individually,
like
by
name
or
by
specifying
a
group
like
you
can
do
today,
users
will
also
be
able
to
Define
approvers
in
a
policy
based
on
their
role.
E
So
identifying
approvers
based
on
role
is
a
more
scalable
approach
to
setting
approvers
for
a
lot
of
organizations,
and
so
this
capability
Maps
more
closely
to
how
many
folks
want
to
be
able
to
divide
responsible,
yeah
divide
responsibilities
and,
finally,
the
composition.
Analysis
theme
is
going
to
continue
work,
this
Milestone
on
the
on
continuous
vulnerability
scanning.
So
this
feature
is
not
expected
to
be
delivered
this
Milestone.
E
So
today,
if
you
want
updates
to
to
your
vulnerability
mappings,
basically
you
have
to
run
a
scan
in
CI
in
order
to
see
that,
and
so
having
this
sort
of
automatically
running
in
the
background
will
be
a
huge
Improvement
to
you
know
the
overall
always-on
security
experience,
Within
gitlab
we'll
give
users
a
better
and
more
continuous
view
of
the
vulnerabilities
that
affect
their
projects
and
with
that
I
will
hand
it
off
to
Mike
to
take
us
through.
What's
coming
up
in
Ops
awesome.
C
C
F
Sure
hi
everybody,
my
name
is
Taylor
McCaslin
I'm,
our
group
manager
for
data
science
today,
I'll
cover
both
anti-abuse
and
our
model
Ops
stage.
To
start,
let's
begin
with
our
anti-abuse
stage,
this
is
focused
on
our
product
theme
of
observability,
analytics
and
feedback.
I've
talked
previously
about
our
efforts
to
improve
and
protect
our
sign
up
to
reduce
spam.
F
We
won't
talk
much
about
this,
but
there
continue
to
be
efforts
to
reduce
the
amount
of
spam
that
comes
onto
our
platform,
so
there
may
be
changes
to
our
sign
up
flow.
Moving
on
to
our
abuse
management.
We
are
in
the
process
of
releasing
our
abuse
reports,
broad
project.
This
basically
allows
management
of
different
abuse
reports
we're
in
the
process
of
building
actions
into
this,
so
that
you
can
actually
take
action
against
these
specific
reports.
F
So
this
is
being
developed
right
now
to
give
more
control
over
various
abuse
vectors
across
get
lab
now,
moving
to
our
model
up
stage,
our
Focus
here
is
world-class
devops
experience
and
you
may
recall:
we've
released
code
suggestions
available
on
a
coast
beta.
This
is
basically
generating
code,
as
you
type
Within
gitlabs
vs
code,
plugin,
we're
in
the
process
now
of
moving
towards
an
open,
Beta
And.
F
So
there's
a
variety
of
things
that
we're
doing,
including
improving
the
model
to
make
it
run
or
to
make
to
have
better
results
and
also
support
more
languages,
we're
also
in
the
process
of
simplifying
the
way
that
you
enable
this
right
now.
It's
part
of
our
vs
code,
workflow
plugin,
which
has
a
lot
of
different
features
associated
with
it,
we're
pulling
it
out
into
a
separate
plugin
to
make
this
very
easy
to
manage.
F
This
also
sets
us
up
to
load
this
into
our
new
web
IDE
experience
with
that
Standalone
plugin
it'll
be
easier
to
manage
this
in
the
web
ID,
and
we
actually
do
have
this
running
in
the
web
ID
today
generating
code.
So
this
will
be
shipping
with
our
open
Beta
in
the
next
month
or
two
additionally,
we're
in
the
process
of
working
on
how
gitlab
admins
will
control
this
right.
C
We're
focusing
on
a
few
different
things,
including
a
lot
of
work
around
some
bugs
and
maintenance,
but
we're
taking
a
look
at
merge
trains
and
specifically
we're
undertaking
a
spike
to
ascertain
level
of
effort
to
do
some
work
around
fast
forwarding
support
within
retrains.
This
is
a
really
commonly
requested
capability,
so
we're
super
excited
about
delivering
that
and
we're
looking
at
in
this
Milestone
unblock
is
some
work.
C
That'll
allow
us
to
to
to
progress
here
and
there's
also
some
work
we're
doing
around
cleaning
up
help
text,
there's
a
lot
more
information
on
the
release.
Kickoff
video
I
encourage
you
to
to
watch
so
exciting,
exciting
stuff
there
within
the
runner
group
a
lot
of
work
that
we're
doing
around
reducing
backlog
of
existing
bugs
working
on
some
optimizations
across
the
platform
from
a
new
feature
standpoint
we're
working
on
an
alpha
release
for
Auto
scaling
virtual
machines
using
the
AWS
ec2
plugin.
C
So
it's
really
kind
of
the
first
chance
that
we're
giving
the
community
to
test
out
that
capability
so
really
excited
about
working
with
the
hyperscalers,
and
this
will
lay
the
groundwork
not
just
for
AWS
but
down
the
road.
You'll
see
us
supporting
other
hyperscalers
like
gcp
and
Azure,
so
so
super
excited
about
that.
C
Moving
on
to
the
the
delivery
group
and
configuration
we're
continuing
to
progress
on
our
initial
iteration
of
our
kubernetes
dashboard
and
the
environment
page
which
kubernetes
can
be
complex
and
so
giving
giving
people
more
insight
into
exactly
what's
going
on
is
something
we're
really
excited
about
there.
So
we
continue
to
to
do
that
work
and
so
there's
some
really
good
information
in
the
dashboard.
Epic.
C
That
encourage
you
to
take
a
look
at
here
as
well
as
really
well
documented
blueprint
that
we
continue
to
continue
to
work
towards
so
really
excited
about
the
work
we're
doing
around
that
world-class
Dev
psychops
experience
theme
continuing
things
out.
You
know,
as
as
Taylor
alluded
on
the
the
data
science
front,
we
can
you
continue
to
do
work
to
support
additional
capabilities,
so
we're
one
thing
we're
particularly
excited
about
is
extending
our
GPU
support,
so
we're
better,
supporting
GPU,
enabled
SAS
Runners.
C
C
The
pipeline
Security
Group
is
doing
work
to
encourage
users
to
switch
to
oidc,
as
opposed
to
using
known
Cloud
providers,
storing
secrets
in
their
CI
CD
variables,
which
is
not
not
a
great
security
practice.
So
we're
going
to
be
doing
some
research
around
the
best
ways
to
prompt
adoption
of
oidc
instead
and
excited
about
that
capability.
And
finally,
going
back
to
the
gitlab
sorry
to
the
runner
group.
A
Thanks
Mike
and
thank
you
to
all
the
presenters,
and
you
can
see
we
iterate
here
clearly
Mike
did
have
a
little
bit
of
zoom
problem,
I.
Think
on
my
first
call,
my
camera
didn't
work
so
I
guess
that's
right.
A
passage.
We're
like
welcome
to
your
first
kickoff
call
the
thank
you
all
to
the
presenters.
Some
of
the
great
things
were
released.
A
I
can
only
highlight
a
couple
of
them
in
the
last
minute
here
under
world
class
devsecops
experience
looking
to
switch
our
back
end
for
code
search
to
a
more
reliable
and
complete
solution
wanting
to
improve
the
experience
with
SSH
timeouts
with
Geo
secondaries
reading
the
work
on
the
CI
component.
Catalog,
that's
exciting.
To
me:
that's
gonna,
be
a
great
usability.
Improvement
Mike
just
mentioned
a
spike
on
building
fast
forward,
merge
support
for
merge
trains,
we're
doing
the
initial
kubernetes
dashboard
environment
page,
which
will
also
be
great.
A
The
content
editor
if
you've
not
used
on
the
wiki
having
that
everywhere
is
going
to
be
amazing.
So
can't
wait
to
see
that
happen
with
the
plan
team,
reordering
of
work
items
and
the
ability
to
hide
the
tasks
add
task
option.
If
you
don't
have
permission
to
use
tasks,
both
great
improvements
and
then
our
reach
showed
the
new
navigation
I
love,
the
new
navigation
I
can't
wait
to
see
that
VGA
for
advanced
security
compliance
things
like
new
vulnerability
type.
A
A
All
great
please
check
out
the
release.
Kickoff
page,
as
well
as
the
full
list
of
items
feel
free
to
like
and
comment
on
them
and
engage
with
the
team.
Again,
I
was
only
able
to
touch
on
a
very
small
list
of
them
here
on
the
kickoff
before
we
sign
off
the
there
is
a
important
Milestone
happening
today,
so
this
will
be
a
wreath's
last
kickoff
call
and
she's
leaving
gitlab
in
early
April
I
mean
I
wanted
to
take
a
moment
to
thank
you
for
your
leadership
and
your
dedication
to
gitlab.