►
From YouTube: 14 0 Monthly Release Kickoff (Public)
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
I
was
collecting
some
really
odd
facts
and
found
some
really
interesting
ones
and
sonnet
is
a
protein
line
poem.
I
did
not
know
that
a
golf
in
golf
player
can
have
no
more
than
14
clubs
in
a
bag,
but
the
most
interesting
for
me,
as
I
like
to
follow
math
along,
is
the
keyboard.
Tetrahedron
has
fourteen
sides
and
it
has
six
squares
and
eight
equilateral
planck
is
pretty
fascinating
when
you
open
it
up,
that's
enough
about
14
as
a
number,
but
I'm
here's
another
interesting
thing
under
the
british
law.
A
When
you
reach
age
of
14,
you
can
go
into
a
pub,
but
you
cannot
buy
or
drink
alcohol.
People
in
emea
can
correct
me
if
this
is
still
true
or
not,
but
my
favorite,
you
can
contribute
to
gitlab
in
14.0
and
help
push
the
state
of
the
art
of
making
software
to
new
heights.
A
Adoption
through
usability,
we
believe
the
key
to
unlocking
the
power
of
single
application
is
to
have
customers
experience
the
value
of
all
of
the
stages
together-
and
this
is
the
primary
path
to
reduce
the
tools,
falls
that
many
of
you
are
facing
today
and
finally,
sas
first
sas
first
does
not
mean
sas
only.
We
are
committed
to
both
self-managed
as
well
as
sas
customers.
A
This
year
we
are
placing
emphasis
on
strengthening
our
sas,
offering
to
ensure
future
parity
with
our
markedly
self-managed
offering
in
other
news.
A
lot
is
happening
this
year,
which
you
will
see
into
coming
into
14..
First
engineering
allocations:
it's
a
method
for
us
to
create
some
space
for
our
engineering
teams
for
mid
to
long
term
efficiency,
performance,
security,
availability
and
scalability
improvement.
So
you're
going
to
see
a
lot
of
them
coming
through
in
14.00
and
second
single
engineer
groups.
A
A
great
method
to
kick
start
a
new
market
area
inside
git
lab,
and
we
have
lots
of
openings
here.
So
if
you're
interested
feel
free
to
reach
out
to
our
engineering
team,
there
are
openings
for
model
ops,
apm,
real-time
collaboration,
newer
ways
to
do
ide
development,
devops
for
mobile
apps
jam
stack
and
a
lot
more.
A
I
want
to
turn
to
the
regular
proceedings
we're
going
to
start
off
with
dylan
who
will
take
us
through
the
enablement
section
followed
by
david,
who
will
walk
us
through
damon's,
sec
and
kenny
will
walk
us
through
ops.
As
a
reminder,
we
plan
ambitiously
everything
we
talked
about
are
in
the
slash
release,
slash
direction,
slash
kickoff
page,
where
you
can
follow
along
with
issues.
You
can
watch
videos
about
what
we
are
building
so
with
that
take
it
away
till
then.
B
B
So
moving
right
along
into
our
first
section
here,
adoption
through
usability
within
adoption
through
usability,
we
have
a
number
of
highlights
across
global
search
and
geo.
First
up
we'll
be
working
on
sort
of
holistically,
improving
the
sorting
and
search
experience
for
project
and
group
drop
downs
in
the
global
search
menu.
So
some
nice
additions
here
and
within
that
encompassed
in
that
is
the
ability
to
search
across
multiple
projects
and
repositories.
B
B
Basically
include
the
scope
of
the
search
in
the
search
bar
for
global
search
when
we
are
defaulting
to
a
specific
project
or
group.
So
when
users
are
searching
in
the
top
bar,
you
can
deselect
or
select
scoping
items
right
there
in
context.
So
this
is
the
basically
previous
experience,
and
this
is
what
the
new
experience
will
look
like.
B
So
you
can
see
you
can
choose
different
context
items
in
the
global
search
bar
right
there
so
again,
moving
right
along
to
our
next
item
in
adoption
through
usability,
we
have
the
new
admin
site
for
our
geo
site
and
this
is
significantly
improves
the
experience
for
sysadmins
monitoring
the
health
and
replication
status
of
their
geosites
in
the
web
ui.
B
So
we've
added
more
useful
indicators
such
as
sync
verification,
summaries
for
data
types
and
verification
status,
bars
for
individual
data
types
and
components
in
general,
we've
improved
how
this
page
is
organized,
so
reducing
the
amount
of
clicks
needed
to
surface
important
information,
so
really
cool
stuff.
There.
B
Now
moving
on
to
new
markets
for
enablement,
we
are
continuing
our
thread
in
distribution
for
the
ga
release
of
the
operator.
So
this
is
our
main
focus
on
the
distribution
team,
and
this
is
the
epic
kind
of
encompassing
all
that
work,
and
you
can
see
the
number
of
must-haves
we
have
for
the
ga.
Now
the
mbp
has
been
released.
B
We've
begun
beta
testing
and
we
have
used
that
data
from
the
beta
clarify
issues
and
gather
new
information
in
14.0,
we'll
be
working
on
items
for
a
solid
experience
using
operator
to
install
gitlab
on
openshift
or
vanilla,
kubernetes
and
automate
day.
Two
operations-
ga
will
not
be
in
this
milestone,
but
is
the
main
focus
as
we
continue
moving
towards
ga.
B
Next
up
is
our
sas
first
mindset,
and
the
first
item
here
is
geo,
so
within
geo
we
have
basically
ga
support
for
postgres
sql
on
geosecondary
sites
using
petroni,
so
with
postpress
sql
required
in
14.0
petroni
replaces
the
rep
manager
as
our
solution
for
postgres
sql
high
availability.
One
benefit
of
this
is
that
geosecondary
sites
will
support
a
postgres
sql
high
availability
cluster
with
petroni.
B
So,
moving
on
to
the
next
item
we
have
in
memory,
we
are
working
to
shift
database
load
from
primary
to
replicas
by
enabling
sidekick
to
use,
read
only
database,
replicas
capabilities
and
to
allow
build
hooks
worker
worker
to
utilize
these
new
capabilities.
The
broader
goal
is
to
allow
sidekick
to
use,
read
replicas
so
that
only
read-only
jobs
don't
put
pressure
on
the
primary
postglass
instance
for
our
users.
B
The
next
item
here
is
addressing
primary
key
overflow
risk
with
an
integer
pk,
so
by
using
the
newly
introduced
framework
for
batch
background,
migrations,
they've
been
able
to
run
successful
migrations
over
multiple
ci
tables
and
update
more
than
2.5
billion
records.
In
the
past
three
weeks,
we
are
really
satisfied
with
progress
of
the
migrations,
as
they
are
progressing
at
a
steady
pace
and,
according
to
our
best
case
scenario,
expectations.
We
are
excited
for
the
prospect
of
using
this
framework
in
the
future
for
all
database
migrations.
B
We've
also
released
a
major
update
that
enables
migration
auto
tuning,
which
allows
the
migrations
to
automatically
pick
the
optimal
number
of
records
to
update
every
two
minutes
and
respond
to
dynamically
changing
conditions
in
a
production
environment
without
any
requirement
for
a
monitoring
by
a
database
expert
or
an
administrator.
This
is
important
on
multiple
levels.
B
It
allows
the
migration
to
quickly
respond
in
case
of
a
production
incident
and
protect
the
database
from
additional
load,
and
it
permits
the
migrations
to
increase
the
number
of
records
that
they're
processing
during
low
traffic
times.
For
example,
on
a
weekend,
it
will
help
us
ship
the
migrations
to
self-hosted
instances
with
various
hardware
specs
without
setting
up
their
parameters
using
the
lowest
denominator
or
requiring
additional
attention
by
the
instance.
B
Administrators
and
last
but
not
least
in
database,
we
are
working
on
automated
database
testing
using
production
clones.
We
have
successfully
completed
the
initial
automated
database
migration,
texting
testing
nbc
and
we
plan
to
move
forward
with
increasing
the
maturity
of
the
setup
and
expanding
coverage
to
data
migrations.
C
Hey
dylan,
thank
you
for
the
nibbling
updates,
let's
hop
into
the
dev
and
sex
section
updates
as
well.
I'm
first
starting
off
with
dev,
with
14.0,
we'll
be
making
the
official
cut
over
to
the
new
main
new
name
for
the
default
branch
which
will
be
made.
We
rolled
this
out
in
1312
to
gitlab.com,
and
that
has
been
successful
there.
We
are
now
looking
to
do
this
for
self-managed
instances
as
well
to
let
you
all
know
it
does
not
actually
change
existing
projects.
C
C
C
C
C
The
team
is
also
working
on
the
okr
for
improving
large
mr
experience,
so
this
kicked
off
with
the
last
milestone
and
is
going
to
carry
out
through
the
end
of
this
quarter.
For
us,
the
focus
is
on
improving
large
enough
larger
mrs
loading
40
faster,
as
well
as
using
substantially
less
memory
in
the
process
for
the
editor
team.
There's
a
lot
of
really
exciting
components
related
to
usability
they're.
All
items
we've
been
talking
about
they've
been
working
on
the
last
several
milestones.
C
That
includes
both
projects
as
well
as
groups
and,
of
course,
the
other
things
are
under
the
more
menu,
also
with
14.0
rolling
out
the
updated
left
bar
or
left
navigation
that
you
can
see
here
today
when
you're
looking
at
it,
you
can
have
things
such
as
rolling
over
requirements
has
a
single
option
of
list.
Those
are
things
that
we'll
be
addressing,
as
well
as
taking
user
feedback
in
as
to
how
the
menu
should
be
laid
out
on
the
issue.
That's
linked
directly
off
the
off
the
epic.
C
You
can
see
the
current
proposed
layout
and
here's
kind
of
a
screenshot
of
what
that
would
look
like
from
our
ux
design
team
as
well.
Both
those
very
excited
about
very
much
wanting
to
make
sure
gitlab
is
approachable
and
usable
and
improving
navigation
is
a
great
step
along
that
way.
C
Finally,
for
the
editor
team,
they're
rolling
out
the
new
content
editor
for
the
wiki,
what
this
allows
you
to
do
is
actually
have
more
of
a
wysiwyg
type.
Editor
be
able
to
go
in
and
with
simple
keystrokes,
be
able
to
set
things
such
as
bolded
lists,
headers
and
so
forth.
C
The
best
way
for
you
to
see
how
awesome
this
is
is
to
check
out
the
kickoff
video
for
the
editor
team.
Eric
does
a
really
good
job,
doing
a
demo
of
showing
the
old
versus
the
new
and
it's
a
great
usability
improvement
from
the
plant
stage,
we'll
be
rolling
out.
The
final
component
of
the
epic
ford's
npc.
This
is
actually
mvc3
it'll,
be
focused
on
improving
usability
and
providing
parity
in
this
release.
C
It'll
also
be
the
first
time
it's
not
behind
a
feature
flag,
so
you'll
be
able
to
see
that
as
a
default
workflow,
it
kind
of
gives
you
a
sense
of
what
it
looks
like
here's.
Actually,
a
gitlab
project
with
the
future
flight
currently
enabled-
and
you
can
see
similar
components-
is
actually
the
product
planning
support
where
they
have
their
workflow
plans,
as
well
as
their
development
plans
all
laid
out
nice
and
easy
on
the
board.
C
You
can
also
search
and
select
from
the
drop-down
as
well
and
then
finally,
from
plan
for
project
planning,
they're
focused
on
infrastructure
and
scalability
issues.
This
first
one
actually
relates
back
to
that
code.
Review
merge,
request,
improvement,
they're
focused
on
improving
the
discussions
control
of
the
product.
C
This
improvements
will
not
only
benefit
issues
and
ethics
with
a
large
amount
of
comments
on
them,
but
will
also
improve
the
nested
comments
that
you
see
onside
of
a
merge
request
and
then
finally,
they're
also
focused
on
lowering
our
error
budgets
so
focusing
on
making
sure
things
are
responsive
as
you
access
them
and
they
have
a
large
list
of
items.
You're
going
to
be
working
on
improving
endpoints
as
part
of
14.0
and
then
finally,
for
manage.
C
Most
of
the
managed
stage
is
focused
on
infrastructure
scalability
in
the
case
of
compliance
they're
working
on
an
additional
item
that
is
both
sas
first
and
adoption,
they
are
improving
the
auto
event
process.
That's
within
the
product
today
focused
on
rolling
out
a
new
web
hook
system,
so
that
spike
is
just
wrapping
up
and
then
they'll
be
moving
into
migrating.
The
existing
components
over
to
this
new
web
hook
we're
doing
this
for
a
couple
reasons:
the
first
it's
going
to
allow
us
to
rapidly
add
additional
audit
events
into
the
product.
C
A
lot
of
customers
request
things
such
as.
I
would
like
to
see
my
security
events
in
the
audit
event
and
on
the
security
view,
all
those
things
will
be
able
to
be
migrated
over
and
easily
added
to
the
audit
events.
It's
also
going
to
allow
for
customization
as
well,
where
you'll
be
able
to
also
create
your
own
custom
audit
events.
You
would
want
to
see
within
the
audit
viewer.
C
And,
as
I
mentioned,
the
scalability
and
usability
focus
of
the
rest
of
manage
optimize
is
doing
a
lot
of
work
on
the
back
end,
just
be
able
to
set
up
some
really
cool
things
that
will
be
coming
out
in
future
milestones.
So
please
stay
tuned
for
that
over
to
the
sex
section,
starting
with
secure
on
this
static
analysis.
Team
is
focusing
on
the
ast
leadership
component
as
well
as
adoption
through
usability.
C
The
first
item
is
our
vulnerability:
fingerprinting
that
we've
actually
renamed
now
to
vulnerability
tracking.
This
is
going
to
allow
us
to
reduce
false
positives
for
you.
A
good
example
of
this
is
sas.
Scanners
will
commonly
re-flag
the
same
vulnerability
as
new.
If
it's
been
shifted
all
in
the
source
code,
we
do
a
really
good
job
handling
that
today,
however,
this
is
going
to
make
that
a
lot
more
effective.
C
The
final
thing
to
highlight
with
that
is
long
term.
It's
going
to
allow
you
to
do
group
level
dismissals
of
vulnerabilities.
So
if
there's
a
vulnerability
type,
you
see
in
one
project
and
you
say
for
our
entire
group-
we
don't
want
to
see
this
vulnerability
again.
It
can
dismiss
across
all
the
projects.
C
C
C
If
you
scroll
down
on
that
overlay
in
the
ui
you'll
see
the
actual
data
flow
that
led
to
that
decision.
So
the
sas
engine
scanner
found
that
there's
an
exploitable
component,
that's
not
being
sanitized,
which
means
that
someone
could
take
advantage
of
it.
However,
following
the
data
flow
of
that
command,
we
can
see
it
comes
up
here
and
calls
user.list
and
we
go
up
to
user.list.
We
see
that
it's
actually
executing
a
printout
of
static
text,
and
so
because
of
that
it's
actually
not
exportable
vulnerability
and
that
would
actually
get
automatically
dismissed
for
you.
C
C
I
did
want
to
highlight
one
thing
for
you:
the
dynamic
analysis
team
is
making
the
move
in
14.0
to
move
off
of
zap
for
dast
api
over
to
ph
api
security,
which
was
part
of
an
acquisition
last
year.
This
is
very
exciting.
Not
only
is
the
api
security
solution
more
robust,
it's
also
going
to
provide
better
coverage
and
reduce
false
positives,
so
a
very
exciting
step
forward
to
improving
our
api
support
inside
of
dast
and
then
finally,
both
composition,
analysis
and
threat.
C
Insights
are
working
on
scalability
items,
they
say
hi
to
everyone
and
that
they'll
be
giving
you
more
exciting
things
in
the
future.
Here
to
finish
up
with
the
protect
stage.
The
first
thing
we
want
to
make
sure
you
realize
is
14.0
is
the
official
removal
of
the
gitlab
lab?
If
you
are
still
using
that,
and
you
want
to
continue
to
use
it,
there
are
some
documentation,
that's
available
on
how
to
continue
to
use
that.
However,
it
will
no
longer
be
an
official
part
of
the
ui.
You
will
not
be
able
to
manage
it
from
there.
C
14.0
is
also
a
big
milestone
for
protect
we're
switching
over
to
trivia
as
our
default
scanner.
This
is
very
exciting.
It's
going
to
give
us
a
lot
of
opportunity
to
help
improve
the
market
in
the
open
source
community,
as
well
as
work
closely
with
the
community
to
improve
security
overall,
and
that
leads
very
well
into
our
next
update,
with
the
switch
to
trivia
in
the
future,
we'll
be
able
to
begin
to
scan
running
containers
in
production.
C
A
big
step
forward
for
container
security
and
that'll
be
leveraging
starboard
as
well
as
working
with
aqua
security
on
implementing
that
into
the
product,
and
the
last
thing
which
I
am
probably
the
most
excited
about
that
I've
been
talking
to
you
today
is
our
move
to
reduce
the
time
until
we
release
vulnerability
data
into
the
open
source
community.
Back
beginning
of
the
year,
I
talked
about
how
we
were
going
to
begin
to
create
a
community
advisory
database,
so
open
source
users
into
the
open
source
community
can
benefit
from
it.
C
We've
decided
with
14.0
to
change
that
from
a
six
month,
delay
to
one
month
delay,
so
everyone's
gonna
be
able
to
get
the
advantage
of
our
vulnerability.
Research
team,
as
well
as
the
ability
to
integrate
this
into
more
scanners,
and
the
first
example
that
is
trivia
attribute,
will
be
modified
to
be
able
to
support
the
community
database
and,
of
course,
if
you're,
a
gitlab
customer
leverage,
the
ultimate
version
of
that
database
as
well.
C
D
Thanks
david
yeah,
my
name
is
kenny
johnston.
I
am
the
director
of
product
management
covering
the
ops
section.
Let
me
go
ahead
and.
A
D
My
screen
here
we
go
as
a
reminder.
The
ops
section
is
comprised
of
five
stages:
verify
package
release
configure
monitor,
not
just
stages.
I
was
doing
the
math.
It
has
enough
categories
to
cover
almost
three
of
anup's
octodeca
hedrons
that
he
mentioned
earlier.
Fourteen-Sided
cubes,
I'm
gonna
go
over
what
we're
working
on
in
14.0.
D
Like
many
of
my
colleagues,
most
of
the
groups
are
also
working
to
implement
deprecations
that
we
previously
announced
you
can
find
those
lists
of
those
deprecations
in
our
previous
release
posts.
So
I'll
encourage
you
to
look
there
first
up.
I
want
to
talk
about
a
feature
that
we're
adding
in
the
verify
ci
stage.
That
really
is
about
enabling
some
of
the
work
that
david
and
the
secure
group
are
doing
to
allow
for
auto
remediation
of
fixes.
So
when
you
use
gitlab
ci,
it's
a
really
powerful
automation
tool.
D
We
have
been
working
to
make
sure
that
when
you
use
a
bot
to
utilize
that
token
that
you
can
do
that
securely
and
so
in
14.0
we'll
be
adding
the
ability
for
you
to
limit
the
access
that
that
ci
job
token
can
have
on
a
project-by-project
basis.
It's
really
useful
for
users
who
might
want
to
have
a
more
restrictive
use
of
those
tokens,
while
still
enabling
users
users
to
use
it
for
things
like
parent
child
pipelines.
D
Also
in
verify
in
our
runner
group.
We're
focusing
our
support
on
adding
support
for
windows,
so
we'll
be
adding
the
ability
to
use
windows
build
pods
in
a
kubernetes
executor.
This
allows
you
to
have
a
kind
of
hybrid
environment
in
your
kubernetes
cluster
that
can
have
both
linux
and
windows
pods
at
the
same
time,
and
we're
also
going
to
be
adding
additional
support.
D
So
by
doing
this,
we
can
have
a
centralized
package
registry
for
all
your
python
modules
at
the
group
level
in
our
configure
stage,
if
you've
been
following
along
in
kickoff
and
our
release
notes,
we've
been
working
on
a
kubernetes
agent,
one
of
the
really
powerful
things
that
the
kubernetes
agent
can
do
when
you
have
it
installed
in
your
cluster,
is
tunnel.
Ci
requests.
D
So
today,
if
you
were
to
want
to
do
a
job
that
was
going
to
interact
with
your
kubernetes
cluster,
you
have
to
give
that
job
specific
credentials
to
access
the
cluster
since
you've
already
provided
access
to
the
agent
for
that
cluster.
D
The
tunneling
allows
you
to
more
readily
in
your
ci
definition,
pipe
the
the
specific
scripts
that
you're
wanting
to
execute
on
the
cluster
directly
to
that
cluster,
really
enabling
you
to
have
a
more
powerful
and
more
secure
interaction
between
your
ci
and
cd,
tooling
and
your
production
environments
and
in
the
same
vein
around
that
cluster.
We're
also
going
to
be
adding
a
new
ui
for
registering
your
agents,
your
kubernetes
agents.
So
today,
there's
a
there's.
D
A
couple
of
api
calls
that
you
have
to
make
in
order
to
access
token
to
utilize
the
agent
and
we're
going
to
be
adding
a
new
ui
for
that
walks.
You,
through
the
process
for
not
just
creating
the
necessary
component
tree
in
your
repository
to
configure
the
agent,
but
also
obtain
the
registration
token
and
then
install
that
agent
directly
into
your
cluster.
D
In
our
monitor
stage,
we've
been
working
on
incident
management,
on-call
schedule,
management
and
escalation
policies.
One
of
the
things
that
we've
found
from
users
who
were
creating
incidents
was
that
they
wanted
the
ability
to
switch
back
and
forth
between
whether
an
object
that
they
created
in
gitlab
was
an
incident
or
an
issue.
And
so
this
was
a
highly
requested
feature
that
will
increase
the
usability
of
our
incident
management
functions
by
giving
users
the
ability
to
quickly
adjust
the
the
type
of
of
an
object
between
an
incident
and
an
issue.
D
So
with
that,
I
will
hand
it
back
to
a
new
to
bring
us
home.
A
Thanks
kenny
and
because
this
is
14.0,
I
found
14
items
that
I
really
would
like
to
cover
and
re-emphasize.
I
love
the
focus
on
usability,
ast
leadership
and
sas
reducing
false
positions
from
scan
only
scans
against
running
containers,
super
exciting,
reducing
time
to
release
vulnerability
will
be
supe,
amazingly
appreciated
by
the
community,
merge
request,
reviews
in
vs
code.
We
know
devs
want
to
be
where
they
are
so.
Bringing
that
merging
view
request
into
vs
code
is
excellent.
A
I'm
a
big
fan
of
markdown
personally,
but
I
know
we
will
all
love
the
visibility
editor
in
the
group
in
the
wikis
automated
database
testing
using
clones
is
going
to
be
great
for
stability
and
cycle
time.
Large,
mr
performance
improvements
is
in
high
demand.
So
thank
you
for
the
focus
on
it.
I
can't
wait
for
the
waffle
top
nav
and
the
epic
boards
error
budgets
are
instrumental
for
us
to
drive
our
sas.
First
focus.
A
It's
some
something
that
everybody
over
time
is
going
to
adopt
in
the
industry,
love
the
search
improvements
and
the
geo
admin
ui,
making
things
easier
for
admins,
as
well
as
developers,
windows,
build
parts
and
kubernetes
a
great
extension
to
bring
all
the
different
operating
systems
into
the
same
umbrella
package
registry
endpoint
for
all
your
python
modules
at
group
level,
number
13
love
the
progress
on
kubernetes
agent.
It's
a
great
connector
from
ci
to
cd
and
14.