►
From YouTube: 13.12 Monthly Release Kickoff (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
Hey
everyone
and
welcome
to
the
1312
get
lab
kickoff.
I
am
kenny
johnston,
I'm
a
product
leader
leader
here
at
git
lab,
and
I'm
going
to
be
your
mc
for
today
we're
going
to
be
covering
the
1312
release
and
that
will
be
released
in
just
a
little
bit
over
a
month's
time
on
may
22nd.
If
you
want
to
follow
along,
you
can
go
you
can
visit.
So
let
me
share
my
screen
real
quick.
A
A
A
It's
been
a
lot
of
heads-down
work
across
a
number
of
teams
and
they've
delivered
some
great
real
results
over
the
last
four
to
six
weeks.
With
that,
let
me
go
through
a
roll
call
of
who
we're
going
to
hear
from
today
and
covering
what's
planned
in
1312,
we'll
start
with
david
who's
going
to
cover
the
dev
and
sec
sections
john
will
cover
enablement,
and
then
I
will
bring
us
home
covering
the
ops
section.
So
with
that,
let
me
stop
sharing
and
david
over
to
you.
A
B
You
kenny,
and
let
me
get
my
screen
shared
here
great,
so
we're
going
to
dive
into
the
dev
section
first
with
create
just
to
echo
what
kenny
you
mentioned,
a
big
thank
you
to
everyone.
Who's
been
working
on
the
infra
and
scalability
items
and
you'll
see
that
as
a
recurring
theme
as
we
talk
through
what
the
dev
and
sex
sections
are
doing
today.
B
So,
first
with
create
the
source
code
group
is
heavily
focused
heads
down
on
the
items
that
kenny
just
mentioned,
infradev
and
performance.
They
are
going
to
be
working
on
one
specific
item
I
did
want
to
highlight
for
you
that
is
more
feature
focus
which
is
changing
the
default
branch
name
for
new
projects
on
gitlab.com.
B
The
code
review
team
is
beginning
their
work
on
their
okr
for
the
next
quarter.
This
will
be
focused
on
improving
the
merge
request.
Experience
as
you
can
see,
highlighted
in
the
title
we're
going
to
be
focusing
on
making
the
experience
of
large
mrs
40
faster,
as
well
as
decreasing
the
amount
of
ram
that
is
needed
as
part
of
that
merge
request.
B
Editor
team
is
going
to
be
focused
on
by
continuing
their
work
on
improving
the
global
navigation
at
the
top
of
the
screen
and
kind
of
remind
you
what
that
looks
like
here's,
a
screenshot
so
we'll
be
collapsing
that
top
menu
down
into
a
single
option.
That'll
then
include
all
the
components
that
you're
commonly
used
to,
such
as
projects
groups
and
so
forth.
B
We
just
completed
our
user
research,
so
the
team
is
compiling
that
data
and
starting
with
1312,
to
begin
the
work
of
re-architecting
that
left
navigation
and
then
finally
concluding
create
with
goodly
again
focus
on
infradev
and
scalability,
and
here
this
is
one
of
the
items
they're
going
to
be
working
on
focused
on
improving
count
commits
by
leveraging
commit
graph.
You
can
see
in
the
snapshot
here.
B
The
getaway
team
is
also
continuing
their
work
on
incremental
backups,
and
this
is,
of
course,
leveraging
git
elite
to
be
able
to
do
something
that
the
gift
protocol
itself
doesn't
do
well
natively,
so
that
work
will
continue
in
1312
as
well.
Moving
over
to
the
plan
stage
same
thing,
they're
very
much
focused
on
infradev
and
improving
usability.
B
You
can
see
here
if
we
scroll
down
there's
a
bunch
of
items
related
to
performance,
quality
of
life
and
some
infra
items.
What
I
want
to
highlight
for
you
is
improving
our
api
responsiveness
for
the
group
issues
api
and
you
can
see
today
we
have
a
nice
high
spike
on
usage
and
memory
when
hitting
those
apis.
Our
goal
is
to
greatly
reduce
that
as
part
of
the
work
in
1312.,
the
product
planning
teaming
team
same
thing
very
much
focused
on
improving
the
availability
and
scalability.
B
However,
they
are
what
to
also
complete
their
mbt,
nbc2
work
on
epic
boards.
This
will
allow
reordering
and
editing
of
the
boards,
and
you
can,
of
course
see
that
here
as
part
of
their
work
and
then
finally,
the
certified
team
is
going
to
be
working
with
infradev
to
be
able
to
build
out
a
dashboard.
So
we
can
monitor
the
usage
of
the
certified
components
from
that
we'll
be
able
to
then
begin
outside
of
1312.
B
Also
looking
at
availability,
scalability
items
for
there
as
well
and
then
finally,
within
the
dev
section,
is
the
manage
stage
manage
age
again
will
also
be
working
on
those
same
items,
however,
to
the
themes
that
kenny
talked
about
the
beginning,
the
access
team
is
going
to
be
focusing
on
sample
enforcement
by
default.
When
it's
enabled
today,
you
can
see
a
screenshot
of
our
ui
here,
you
would
enable
the
saml
authentication,
however,
the
ssl
sso
only
authentication
was
not
enabled
by
default.
B
That
was
an
option
you
had
to
enable
so
for
projects
are
now
enabling
it
that'll
be
enabled
by
default,
along
with
a
warning
letting
you
know
that
disabling
that
does
actually
introduce
a
security
risk
for
the
certified
or
for
the
optimized
team.
They're
focused
on
improving
the
devops
adoption
report.
B
In
1311,
we
talked
about
how
that
was
going
to
move
out
of
the
instance
level
down
to
the
project
level,
they're
now
going
to
begin
to
expand
what
is
in
that
report,
and
that
includes
breaking
it
out
across
the
three
main
components
of
that
tech:
ops,
which
of
course
are
dev
sec
and
ops
where
it
works
out.
Well,
those
names
match
the
term
there,
but
that
allows
them
to
be
able
to
give
you
granular
detail
into
each
of
those
components
of
the
product
and
see
how
it's
being
adopted.
B
B
Today,
there
are
limits
on
how
large
a
project
can
be
to
be
brought
in
via
the
api,
and
this
can
allow
you
to
actually
grab
those
objects
from
an
object
storage,
as
opposed
to
grabbing
them
the
traditional
way
through
the
ui.
This
will
allow
us
to
be
able
to
import
larger
projects
without
that
same
timeout
that
exists
today
and
then
to
move
over
to
the
sex.
Section
first
was
secure.
The
stack
analysis
team
is
working
on
bringing
semgrep
from
experimental
to
generally
available.
It's
a
very
exciting
step
forward
in
this
milestone.
B
This
diagnosis
team
is
also
going
to
be
bringing
to
general
availability.
Our
new
improved
vulnerability
tracking
our
user,
for
this
is
vulnerability.
Fingerprinting
on
previous
release,
kickoff
calls.
But
again
you
can
see.
This
is
tied
back
to
us
moving
some
gupta
generally
available,
as
well
as
supporting
gosek
as
well
longer
term
stretch.
Items
for
this
also
relates
to
bringing
in
some
of
the
secret
detection
components
as
well,
however,
very
excited
to
see
our
new
vulnerability
tracking
coming
into
ga.
B
For
the
dynamic
analysis
team
they're
focused
on
the
on-demand
scheduling.
This
has
been
a
continued
iteration
that
we've
been
highlighting
on
each
call.
To
kind
of
give
you
a
sample
of
what
that
looks
like,
and
I
can't
stress
how
awesome
iteration
is
enough.
I
think
about
me
four
or
five
months
ago
on
the
kickoff
call,
I
said
we're
gonna
have
on-demand
scanning,
I'm
like
you
type
in
a
name
and
type
in
a
url.
B
Now
we
have
a
lot
of
settings
that
are
available
to
you,
whether
that's
scan
or
site
profile
configurations,
but
now
at
the
bottom
we'll
have
the
ability
to
schedule
a
scan
to
go
in
here.
You
can
check
it
set
when
you
want
to
run
and
hit
save
and
then,
when
that
time
comes,
that
scan
will
automatically
run
a
longer
term.
B
This
is
something
that's
been
a
big
project
for
them.
It
was
put
on
hold
as
part
of
helping
optimize.
Our
database
queries
for
again
availability,
scalability,
update
kind
of
show.
What
that
looks
like
like
the
other
scanners
before
it.
You'll
have
an
enable
button
on
the
configuration
page
from
there,
that'll
open
up
a
merge
request
and
we'll
add
the
default
configurations
for
dependency
scanning
into
your
gitlab,
ci
eml
file
and
then,
lastly,
for
secure
the
thread.
B
Insights
team
is
continuing
to
optimize
the
performance
of
the
dashboards
and
the
security
reports
in
this
milestone,
they're
going
to
be
working
on
introducing
vulnerabilities
by
age,
this
will
be
a
new
component
on
the
security
dashboards.
You
can
see
here
at
the
top.
You
have
the
option
to
select
between
stacked
or
tiered
and,
of
course,
it's
going
to
show
you
that
by
age
across
the
x-axis,
this
is
really
about
that
ast
leadership
theme
as
well
as
again
allowing
us
to
be
able
to
provide
you
additional
details
on
the
current
state
of
your
projects.
B
Of
course,
if
you
hover
over
it,
you
can
see
it
and
you
can
drill
down
to
it
as
well
and
then
again.
Finally,
but
not
last
or
at
least,
is
the
protect
stage.
They're
focused
on
two
items
I
wanted
to
highlight
for
you.
The
first
is
the
other
half
of
that
dynamic
analysis
with
on-demand
scheduling
and
they'll,
be
introducing
scheduled
scans
as
part
of
the
security
orchestration
component
of
our
product
very
exciting.
B
To
be
able
to
see
this,
where
you'll
be
able
to
set
which
profiles
you
want
run
when,
whether
that's
scanning
against
an
application
you've
deployed
in
production
or
setting
that
your
default
branch
could
scan
on
a
regular
schedule
and
then
wrapping
up
we're
also
going
to
be
finalizing.
Our
work
to
cut
over
to
trivia
from
claire
and
clark
for
container
scanning
in
1312
we'll
be
focused
on
doing
the
final
testing.
B
I
do
want
to
say
a
big
thank
you
to
all
the
users
who
are
using
trivia
over
the
last
couple
of
milestones
for
us
by
enabling
its
experimental
setting
we've
been
able
to
take
that
data
and
understand
what
we
need
to
finish
doing
to
make
sure
we're
ready
for
this
cut
over.
I'm
also
very
excited
about
it
because
it
means
the
gitlab
is
also
going
to
be
contributing
to
another
open
source
community.
B
C
All
right,
thank
you,
david
alright,
so
I
am
going
to
take
you
through
the
enablement
section
enablement.
We
have
three
focus
areas:
adoption
through
usability,
new
markets
and
sas
first
starting
off
with
adoption
through
usability.
The
first
thing
that
we
have
is
for
global
search.
We
want
to
lock
the
order
of
the
scope
tabs
that
appear
in
the
search
page
today
they
disappear
and
will
sometimes
move
around
we're
going
to
lock
this
order
in
so
that
it
is
easier
to
navigate
the
next
thing,
we're
going
to
be
adding
multi-select
to
project
dropdowns.
C
So
this
will
allow
you
to
select
more
than
one
project
at
a
time,
instead
of
actually
choosing
all
the
projects
or
one
project,
and
the
next
item
that
we
have
is
for
geo,
secondary
mimicry,
so
secondary
mimicry
is
the
idea
that
the
secondary
the
ux
on
the
secondary
site
should
behave
like
the
ux
from
the
primary
site.
So
the
next
thing
that
we're
going
to
be
doing
with
this
is
to
proxy
over
the
request,
the
primary
site.
This
will
allow
users
to
use
the
same.
C
Url
and
users
will
automatically
be
routed
to
the
closest
gitlab
node.
To
keep
it
super
fast,
the
proof
of
concept
for
this
is
already
complete,
and
you
can
see
this
in
in
progress
now.
So
the
next
piece
that
we're
going
to
be
going
to
is
new
markets,
so
with
new
markets,
we're
going
to
support,
deploying
gitlab
to
open
shift.
Ga
we
have
completed
part
of
this
already
and
we're
going
to
be
moving
to
the
pre.
C
The
pre-ga
component,
ga,
is
what
we
refer
to
for
generally
available,
so
our
beta
is
is
basically
complete.
Now
we're
actually
going
to
start
working
through
some
of
the
feedback.
That's
happened
from
this
this
beta
and
make
it
develop,
we'll
make
it
generally
available
all
right
and
the
next
area
that
we
have
is
for
sas
first
and
sas.
First,
we
have
three
different
pieces.
C
C
This
will
allow
for
secondary
site
to
handle
a
load
without
having
to
manually
scale
up
first
today,
you
can
actually
handle
that
load,
but
you
have
to
do
a
manual
scale
up
to
restore.
The
next
piece
is
for
reducing
memory,
consumption
in
puma
and
sidekick
endpoints
and
finally,
the
last
piece
that
we
have
is
coming
from
our
database
team.
So
the
database
group
has
made
serious
progress
in
the
effort
to
migrate
to
big
int.
C
It
used
to
take
us
about
45
days
to
migrate
a
billion
records.
We've
now
updated
the
migration
framework
for
this,
so
that
we
can
do
the
migration
with
live
tweaks
and
be
able
to
monitor
it
in
real
time.
This
new
framework
means
that
we
can
now
migrate
a
billion
records
in
as
little
as
three
days
with
zero
downtime.
While
we
do
it-
and
that
is
what
we
have
for
enablement
back
to
you
kenny.
A
Awesome
thanks
john
all
right.
I
am
going
to
cover
the
ops
section
before
bringing
us
home.
So
let
me
share
my
screen
as
a
reminder
to
everyone.
The
ops
section
is
comprised
of
five
stages,
verify
package,
release,
configure
and
monitor,
and
I'm
going
to
be
covering
scheduled
improvements
for
1312
in
those
five
stages.
A
The
first
item
that
I
wanted
to
highlight
was
an
improvement
to
the
actions
when
you're
viewing
a
pipeline.
So
today,
when
you
view
a
pipeline,
there
are
a
series
of
actions
and
we've
been
slowly
adding
to
that
series
of
actions
over
time
where
you
can
download
artifacts
or
rerun
a
pipeline
or
cancel
a
pipeline
all
with
these
actions.
A
I'm
I'm
moving
my
cursor
over
here
that
continues
to
take
up
more
and
more
horizontal
screen
real
estate
in
our
pipeline
view,
and
so
we
are
in
1312
we're
going
to
be
improving
that
user
experience
so
that
we
have
a
ellipsis
drop
down
for
those
items
which
will
also
allow
us
to
add
more
contextual
items
to
those
actions
that
you
can
perform
when
viewing
a
list
of
pipelines.
A
A
So
today,
when
you're
using
our
pipeline
editor
in
the
gitlab
application,
it
can
give
you
immediate
feedback
about
the
linting
or
what
how
your
pipeline
will
look
when,
before
you
submit
it
in
to
gitlab
your
gitlab
ci
yml,
but
we're
going
to
add
a
drawer,
a
right
side
drawer
to
this
editor
experience.
That
also
gives
you
at
the
moment,
tips
and
tricks
for
getting
started
with
gitlab
ci
pipeline.
But
we
plan
this
as
an
mvc
to
continue
to
add.
A
Well,
what
could
I
do
in
order
to
make
sure
there
are
tests
shown
here
I
mean
so
we're
going
to
start
by
adding
documentation,
link
in
this
empty
state,
so
that
you
can
immediately
read
documentation
about
how
you
could
ensure
your
pipeline
is
generating
and
supplying
a
report
so
that
it's
showcased
right
here
for
your
users
in
their.
Mr.
A
You
know
permissions
as
a
developer
to
deploy
to
lower
environments
like
a
dev
or
testing
or
maybe
even
a
staging
environment,
but
you
probably
don't
want
to
give
all
developers
permissions
to
deploy
to
staging
and
production
environments,
so
we're
going
to
be
adding
the
ability
at
the
group
level
to
assign
group
level
protected
environments
that
can
only
be
deployed
to
by
specific
permissions.
So
this
table
kind
of
outlines
our
plan
for
what
permissions
might
be
allowed
when
an
environment
is
defined
as
protected
at
a
group
level.
A
The
next
improvement
that
I
wanted
to
highlight
was
also
in
the
release
stage
where
today,
if
you
have
a
manual
pipeline
that
does
a
deployment
for
example,
and
you
click
the
the
button
to
manually,
perform
the
action
of
deploying
this
is
the
kind
of
current
state
where
you
click
deploy.
A
You
don't
immediately
get
feedback
that
that
deployment
job
is
running
and
so
we're
going
to
be
making
a
ui
enhancement
so
that
when
you
click
that
button
to
deploy,
it
actually
turns
gray
and
shows
you
that
it's
working
to
start
that
deploy
and
then
we'll
immediately
add
the
ability
for
the
stop
button
to
be
clicked
so
that
you
get
immediate
feedback
that
the
action
you
are
intending
to
take
is
being
taken.
A
The
next
feature
I
wanted
to
cover
is
in
our
configure
stage,
and
it
is
about
our
kubernetes
agent.
So
in
a
couple
of
days,
we're
going
to
be
announcing
the
ga
of
our
kubernetes
agent
available
on
gitlab.com
and
we're
planning
in
the
subsequent
milestone
to
add
a
more
robust
ui
for
adding
and
registering
that
agent
today
at
launch.
It
requires
a
couple
of
api
calls
in
order
to
officially
register
and
receive
a
token
for
your
agent
to
then
do
the
installation.
A
So
we
have
some
great
designs
for
the
process
of
installing
your
new
kubernetes
agent
and
as
a
reminder,
the
kubernetes
agent
will
allow
you
to
more
readily
do
pull-based
deployments
or
have
more
control
over
the
access
that
gitlab
or
other
entities
are
given
to
your
kubernetes
cluster,
so
that
you
can
maintain
some
separation
between
gitlab
and
your
gitlab
users
and
the
kubernetes
clusters
that
are
going
to
be
managed
or
deployed
to
from
gitlab.
A
Lastly,
we
have
an
mvc
in
our
monitor
stage
that
I'm
really
excited
about.
So
if
you've
been
keeping
track,
we've
added
incident
management
and
on-call
schedule
management
trying
to
build
a
kind
of
complete
incident
management
platform
for
within
gitlab,
and
our
next
process
is
going
to
be
adding
an
mvc
for
escalation
policies
which
allows
you
to
say
if
there's
an
alert
or
an
incident,
I
want
to,
in
a
progressive
fashion,
continue
to
escalate
higher
and
higher
either
within
my
org
or
the
method
of
communication.
A
So
maybe
from
a
gitlab
notification
to
an
email
to
pager
is
a
pretty
common
process
with
incident
responders.
So
as
an
mvc,
we're
going
to
be
adding
the
ability
to
populate
a
new
escalation
policy,
so
in
this
example,
you
can
set
time
bounds,
for
when
you
know
an
on
someone,
who's
scheduled
to
be
on
call
should
respond,
and
if
they
don't,
then
we
might
escalate
to
a
specific
user.
In
this
case,
it's
this
user
mentioned
here.
A
A
So
those
are
the
highlights
for
the
ops
section.
I
want
to
transition
to
kind
of
my
conclusion.
Overall.
First
of
all,
I
have
to
say
wow.
I
think
there
is
a
lot
that
we
cram
into
just
a
single
month's
release
and
I'm
really
excited
for
some
of
the
improvements
that
my
peers
mentioned
here.
Let
me
just
rattle
off
a
couple
of
them.
First
was
deploying
gitlab
to
openshift
ga
super
exciting.
Second,
one
was
improvements
to
the
large
mr
experience,
global
navigation
improvements.
I'm
excited
to
see
in
1312..
A
I
was
really
excited
about
what
david
described
in
the
devops
adoption
report,
where
we're
showcasing
two
users:
the
ability
how
much
adoption
there
has
been
of
gitlab's
complete
platform
within
within
git
lab
the
semgrep
general
availability.
Global
search
improvements
were
super
exciting.
One
thing
that
john
mentioned
that
I
want
to
highlight
the
primary
key
migration.
A
It's
important
to
note
that
the
reason
why
we're
experiencing
that
primary
that
need
for
a
really
robust
primary
key
migration
is
because
we're
scaling
so
large.
We
have
millions
of
ci
jobs
every
day
we
have
tons
of
usage
of
our
platform,
and
that
is
forcing
us
to
need
to
be
able
to
do
these
primary
key
migrations
to
larger
and
larger
order
sets
for
primary
keys
really
rapidly.
So
that's
an
exciting
thing
that
is
a
symptom
of
our
great
progress.
So
congratulations
to
all
the
teams
involved
there.
A
It's
really
inspiring
for
me
personally
to
be
part
of
this
team
and
the
kind
of
incredible
vision
that
we're
outlining
for
a
complete
devops
platform
and
providing
to
our
users.
I
personally
am
sure
that
1312
is
going
to
be
the
best
release
ever
if
you're
so
inclined.
Please
take
a
moment
to
provide
us
feedback,
the
the
feedback
link
here
on
the
kickoff
page
and
again,
thank
you
all
for
attending.