►
From YouTube: 14.5 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
Hello
and
welcome
everyone
to
gitlab
monthly
release.
Kickoff
call
today
we'll
kick
off
release
14.5
slated
for
november
22nd,
I'd
like
to
remind
everyone
that
the
information
discussed
today
is
related
to
upcoming
projects,
features
and
functionality,
and
it's
for
informational
purposes.
Only
so
please
do
not
rely
on
it
for
purchasing
or
planning
decisions
and
just
like
with
all
projects.
What
we
share
here
is
subject
to
change
without
notice
at
the
sole
discretion
of
gitlab
inc.
A
B
Awesome,
thank
you
so
much
noop.
As
he
said,
I'm
here
to
talk
about
the
featured
highlights
of
the
dev
section.
Let
me
get
my
screen
shared
right.
We're
going
to
begin
within
the
create
stage
focusing
on
the
code
review
group
14.5
code
review
is
going
to
be
focused
on
a
feature
called,
merge,
requests
that
require
my
attention,
so
everybody
has
a
list
in
the
upper
right
hand
corner
of
the
screen
that
gives
you
a
list
of
merch
requests,
you're
assigned
to
with
the
release
of
the
reviewer
feature
earlier
in
the
year.
B
You
can
now
be
added
to
a
merge
request
for
someone
requesting
your
code
review
of
that.
Mr
I've
now
got
two
lists
of
merger
quests
that
I
have
to
manage
with
very
little
indication
of
relative
urgency
or
perhaps
which
mrs
are
awaiting
my
attention,
so
that
I
can
unblock
other
teams
reliant
on
my
review.
B
Moving
on
to
the
giddily
group,
also
in
the
create
stage.
So
as
of
late
we've
been
making
a
lot
of
improvements
to
a
service,
we
call
giddily
cluster
a
highly
available
option
for
git
repository
storage
in
14.5.
The
team
is
going
to
get
started
on
a
critical
feature.
We're
really
excited
about
called
repository
level
incremental
backups.
B
That's
a
mouthful!
Let
me
give
you
a
little
bit
more
detail
on
that.
So
this
is
a
disaster
recovery
method
that
allows
you
to
back
up
repositories
stored
in
a
gilly
cluster.
This
will
be
an
alternative
to
a
commonly
used
disaster
recovery
method
called
disk
snapshots
because
of
the
distributed
nature
of
gili
cluster.
It's
really
hard
to
back
it
up
using
disk
snapshots,
because
during
the
snapshot,
which
is
not
an
instance
on
time,
it
takes
multiple
minutes,
maybe
even
tens
of
minutes
to
take
one.
B
Your
disk
is
going
to
continue
to
change
to
utilize
the
snapshots
reliably
and
accurately
with
the
gita
cluster
service.
This
requires
you
to
take
your
systems
offline,
so
you
can
clear
the
get
operations
right,
cues
and
take
a
snapshot
that
you
can
recover
from
reliably
incremental
backups
aim
to
provide
a
reliable
disaster,
recovery
method
with
zero
down
time,
lower
operating
costs
and
simperable,
simpler
offerability
for
getaway
cluster
and
finally,
from
the
editor
group
within
the
create
stage
we're
putting
the
finishing
touches
on
what
we
call
the
web
ide
state
redesign.
B
This
multi-milestone
effort
was
focused
on
overall
improving
the
reliability,
maintainability
and
performance
of
the
web
ide
in
14.5.
We
are
focused
on
the
final
d
couple
of
decoupling
and
simplifying
the
utilize
file
system.
On
the
back
end,
these
enhancements
are
going
to
make
the
web
ide
more
performant
and
therefore
easier
to
use
for
users
to
help
them
reduce
cycle
time.
Overall,
moving
on
manage
stage
is
up.
Next,
let
me
move
my
zoom
bar.
Give
me
one
second,
okay,
the
manage
optimize
group
is
working
on
an
enhancement
to
the
issue
analytics
chart
today.
B
The
issue
analytics
charts
shows
you
a
monthly
account
of
all
the
issue
opened
within
a
single
project.
We've
gotten
a
ton
of
feedback
that
that
information
in
and
of
itself
does
not
give
you
great
insight
into
how
issue
adoption
for
your
team
overall
is
going
first
up
we're
going
to
be
adding
a
new
metric
to
that
chart.
B
The
first
version
of
iterations
was
released
at
the
group
level,
where
you
were
able
to
create
iterations
with
a
single
cadence.
Now
we
got
a
ton
of
feedback
that
was
a
bit
restrictive
for
teams
within
a
group
you
have
teams
operating
in
different
projects
that
may
be
faster
at
iterating
or
may
utilize
the
feature
in
a
different
way
for
their
unique
workflows.
B
That's
it
for
14.5
depth,
section
highlights
noop
back
to
you.
C
Great
thanks
and
nuke,
let
me
just
quick
share
out
my
screen:
okay,
hopefully
you're,
seeing
the
right
thing
there,
all
right.
So,
as
I
mentioned
up
top
sas,
reliability
and
performance
remains
a
major
area
of
focus
for
us,
and
this
milestone.
Much
of
the
sex
section
is
continuing
that
work
from
last
milestone
into
this
milestone.
So
the
das
threat
the
das
and
threat
insights
teams
are
both
primarily
focused
on
database
scalability,
improvements.
This
milestone
and
the
composition
analysis
team
is
primarily
focused
on
burning
down
security
issues.
C
We
do
have
a
couple
teams
that
are
planning
we're
planning
to
work
on
and
deliver
new
feature
functionality.
So
the
first
thing
I'll
touch
on
here
is
what
the
static
analysis
team
is
working
on.
So
the
sas
team
is
working
on
adding
additional
support
for
infrastructure
as
code
scanning.
So
today,
in
sas
we
support
scanning
of
files
containing
code
or
scanning
of
binaries.
C
C
You
reduce
your
overall
network
attack
surface
by
scanning
for
configurations
that
expose
applications
on,
for
instance,
an
unnecessarily
broad
set
of
network
ports,
or
you
might
want
to
scan
for
instances
where
encryption
or
logging
hasn't
been
turned
on
things
of
that
nature
and
we're
evaluating
adding
support
for
a
variety
of
configuration
file,
types
that
include
things
like
terraform
cloud
formation
and
ansible
for
customers
who
are
interested
in
this.
C
We
are
maintaining
an
issue
to
collect
customer
customer
input,
interest
and
feedback,
and
so
this
is
where
we
can
collect
that
information
and
then
also
the
container
security
team
is
working
on
a
number
of
items.
This
milestone
that
will
be
delivered
in
future
milestones
and
so
I'll
touch
on
a
couple
of
things
that
that
team
is
working
on
here.
The
first
of
those
is
adding
support
for
sas
scan
execution
policies.
C
So
today
we
support
scan
execution
policies
for
sas
and
secret
detection.
What
that
enables
you
to
do
is
to
make
sure
that
those
scans
are
running
at
defined
times
whenever
you're,
whenever
they
are
required.
So
the
work
this
milestone
will
incorporate
sas
support
for
that
as
well,
so
that
will
allow
users
to
ensure
that
staff
scans
are
running
when
required,
whether
that's
in
the
pipeline
or
on
a
daily
or
weekly,
scheduled
cadence
and
then
finally,
major
usability
improvement
coming
to
container
image
scanning.
C
This
will
illuminate
help
eliminate
duplicate
findings.
So,
when
scanning
an
image
today,
a
user
see
all
findings
from
both
the
main
branch
and
the
feature
branch
that
they're
working
on.
Even
if
those
findings
correspond
to
the
same
problems,
and
so
this
work,
this
milestone
is
to
eliminate
those
duplicate
findings
for
most
users,
so
that
only
the
security
issues
that
are
in
that
feature,
branch
are
what's
displayed
and
that
pretty
much
says
it
all
for
the
sex
section.
This
milestone.
So
with
that
key
to
talk
about
what
is
going
on
over
an
ops,
wonderful.
D
As
a
quick
introduction,
my
name
is
jackie
porter,
the
group
manager
for
the
verify
stage
and
for
the
14.5
kickoff
I'll,
be
subbing
in
for
kenny
johnston.
The
senior
direction
director
over
the
ops
section
and
the
op
section
contains
all
of
the
experiences
related
to
the
enabling
of
developers
to
effectively
leverage
configuration
and
operations
tasks
in
gitlab
after
a
developer
commits
code.
The
five
stages
within
this
section
are
verify
package,
release,
configure
and
monitor.
D
We
have
a
ton
of
great
enhancements
and
features
in
each
of
these
stages
for
14.5
and
I'm
unable
to
cover
all
of
these
in
seven
minutes.
So
I
definitely
encourage
you
to
check
out
the
direction
pages
for
each
of
these
teams,
for
this
kickoff
I'll
also
be
covering
two
main
themes:
get
lab
hosted
first,
which
is
about
supporting
our
gitlab.com
experience
and
adoption
through
usability
where
you'll
see
these
issues
are
about
deepening
the
user
experience
and
specific
features.
D
First
up
in
the
get
lab
hosted.
First
theme
is
the
first
iteration
for
expanding
ci
cd
minute
usage
quotas
to
the
group
view
for
you
to
have
better
visibility
into
your
cicd
minute
consumption.
In
this
particular
issue.
The
pipeline
execution
group
will
be
adding
a
graphql
endpoint
to
expose
the
data
to
monthly
charts
that
will
be
on
the
group
usage
quotas
page
in
a
subsequent
iteration.
D
Next
up
is
another
issue
from
the
verify
stage
where
the
pipeline
authoring
group
will
be
focusing
on
investigating
a
variable
endpoint
that
is
consuming
the
error
budget.
For
this
group,
air
budgets
are
the
mechanism
for
managing
availability
at
get
lab
in
the
product
area.
So
this
is
one
mechanism
we
can
use
to
triage
specific
endpoints
that
could
impact
availability
of
the
gitlab
product.
After
investigating
this
endpoint,
the
team
will
be
able
to
optimize
the
experience
and
ensure
variables
are
performing
per
our
availability
target
in
this
milestone.
D
D
Another
super
enhancement
for
this
theme
comes
from
the
pages
category
in
the
release
stage,
where
the
team
will
be
implementing
flags
and
tests
to
support
a
rate
limit
per
source
ip.
This
iteration
will
help
unlock
usage
limits
for
get
lab
pages
and
mitigate
potential
use
in
the
feature,
meaning
you'll
have
more
resilient
service
in
pages.
D
This
will
ensure
that
we're
able
to
give
you
a
speedy
and
fast
experience
in
the
configure
feature
set
transitioning
over
to
our
second
theme
is
adoption
through
usability,
where
we
deliver
features
that
are
focused
on
user
experience
and
deepening
the
functionality
of
areas
by
shipping.
Subsequent
iterations
of
those
features.
D
First
up
is
a
highly
anticipated
feature
from
our
package
stage,
where
the
group
will
be
investing
in
the
experience
of
mpm
packages
by
unlocking
the
ability
to
extract
metadata
from
npm
packages.
This
data
can
be
used
to
verify
the
correct
package
or
even
confirm
that
the
package
was
built
properly.
D
The
configure
and
pipeline
execution
groups
will
also
be
focusing
on
supporting
a
ux
okr,
which
includes
reworking
several
widget
experiences
across
git
lab
in
this
particular
issue.
The
configure
team
will
be
focusing
on
the
terraform
widget
other
issues
that
the
verify
stage
will
be
working
on
include
the
metrics
mr
widget,
and
the
test
summary.
Mr
widget.
Each
of
these
issues
will
be
about
implementing
the
ux
specifications
for
the
merge
request
reports
framework,
which
gives
you
a
seamless
experience
for
interacting
with
mr
widgets
across
gitlab.
D
Third,
up
in
our
adoption,
through
usability
focus,
is
from
the
release
stage
where
the
team
will
be
enhancing
the
environment's
management
experience
by
enabling
the
automatic
deletion
of
stopped
environments.
This
will
speed
up
your
jobs
by
removing
unnecessary
environments.
This
is
a
great
enhancement
that
will
make
navigating
environments
much
easier
and
more
efficient.
D
Next
up,
the
pipeline
execution
group
has
heard
from
you
that
it
can
be
really
challenging
to
navigate
the
pipeline
and
jobs
index
pages.
In
this
milestone.
The
group
is
looking
forward
to
restructuring
the
page,
to
give
you
a
more
intuitive
view
of
the
pipeline
index
page,
so
you
can
easily
identify
relevant
information
related
to
your
pipelines.
D
This
will
come
in
handy
when
you're
triaging
a
failed
pipeline
related
to
a
specific
commit.
Another
great
enhancement
comes
from
the
runner
group
in
the
verify
stage
where
the
team
will
be
adding
support
for
openshift
in
the
gitlab
runner.
Out
of
this
issue,
you'll
be
able
to
get
a
gitlab
supported
version
for
power9,
unlocking
your
ability
to
seamlessly
use
gitlab
with
openshift.
D
Lastly,
for
our
adoption,
through
usability
theme
is
from
the
monitor
stage.
There
are
a
few
planned
features
related
to
alerts
and
incidents
which
will
unlock
dog
fooding
and
more
advanced
use
cases
of
these
two
features.
One
such
experience
is
to
expand
the
post
responses
for
generic
http
endpoints,
which
will
include
the
alert
id.
E
Thanks,
jackie,
that's
some
really
exciting
features
and
changes
coming
up
from
the
app
section.
I
will
go
into
the
enablement
section
and
we
will
talk
about
get
lab
hosted
first,
as
a
theme
here
scallop
hosted.
First
is
areas
where
we're
working
towards
ensuring
that
gitlab.com
provides
a
great
experience
for
all
of
its
users
and
is
performant,
reliable
and
scalable
as
well,
and
we're
working
on
kind
of
two
features
here
that
work
together
and
that
is
decomposing.
The
overall
get
labs
database
to
improve
its
scalability.
E
We've
been
working
on
this
for
some
time
now,
but
the
overall
problem
is
that
you
can
only
buy
so
big
of
a
database
instance
and
postgres
only
lets
you
write
to
one
node
at
a
given
time,
and
so
that
sets
a
natural
ceiling
on
how
much
right
traffic
you
can
have
go
through
to
help
address
this.
We
are
moving
50
of
our
rights
to
a
secondary
database
cluster,
and
that
way
we
can
have
additional
headroom
by
having
kind
of
two
different
clusters
that
can
now
scale
independently
of
each
other.
E
However,
it
is
there
if
they
would
like
it,
and
so
we
are
making
sure
that
this
does
not
add
additional
maintenance
and
operational
overhead
to
self-managed
instances
that
don't
necessarily
need
it
going
forward,
and
so
we
are
working
on
addressing
some
features
that
need
some
changes
to
support
multiple
databases,
and
we
are
also
working
on
updating
our
tooling
across
the
overall
service
to
support
multiple
databases
as
well.
So
things
like
background
migrations,
re-indexing
functionality
and
partitioning,
as
well
as
things
like
how
we
run
some
migrations
by
our
db
migrate
command.
E
So
those
are
all
helping
to
provide
additional
headroom
for
gitlab's
postgres-based
database,
we're
taking
a
similar
approach,
also
for
our
reticent
senses,
and
so
we
want
to
ensure
that
these
can
continue
to
scale
as
well
into
the
future.
And
so
what
we
are
doing
is
we
are
similarly
decomposing
or
shifting
some
of
our
workloads
over
into
a
separate
redis
cluster.
This
is
optional
and
available
if
you
need
it
and
we
are
working
towards
this
on
our
com
service.
E
For
our
session
keys-
and
this
will
move
about
five
percent
of
the
overall
load
off
of
the
current
redis
cluster
and
onto
the
new
one,
to
continue
to
kind
of
provide
that
additional
headroom
availability
from
there.
The
last
item
on
the
sas
sas
first
or
hosted
first
theme
is:
we
are
working
to
improve
the
interoperability
between
gita
lee
cluster
and
prefect
and
geo.
There
are
a
couple
areas
where
this
is
not
where
we'd
like
it
to
be,
and
so
we're
working
to
fix
it.
E
The
geoteam
in
14.5
is
continuing
to
work
on
avoiding
repo
renames
between
these
two
services,
and
what
can
happen
is
that
the
geo
can
rename
a
repo
and
gilly
cluster
isn't
necessarily
aware
of
it,
and
so
these
two
things
can
become
out
of
sync
and
start
to
cause
problems,
and
so
we
are
working
towards
changing
geo,
so
it
no
longer
renames
repositories
which
can
trip
up
the
cluster.
So
those.
E
We
are
working
on
two
areas
here.
The
first
one
is
global
search
and
also
some
prunes,
the
geo,
the
global
source.
One
is
really
exciting.
A
lot
of
users.
A
Hello,
it
looks
like
josh's
screen
is
frozen,
can
you
all?
Can
the
rest
of
you
hear
me
just
if
you're
not,
I
will
yes,
okay,.
F
Yes,
we
can
hear
you
I'll
give
a
quick
summary
of
the
global
search
piece,
but
I'm
not
sure
what
else
was
in
josh's
agenda,
yet
so
in
global
search.
We're
going
to
be
working
on
bringing
labels
in
to
issues
and
merge
requests
to
allow
for
that
experience
to
include
filtering
and
fasting
with
labels
and
I'll
go
ahead
and
start
seeing.
If
I
can
pull
up
the
rest
of
his.
If
we
want
to
come
back,
oh
looks
like
josh
just
done
froze.
E
Hey
sorry,
I
briefly
lost
power,
and
my
internet
connection
went
down
there
for
a
second.
E
Great
thanks,
john
for
jumping
in
there
appreciate
it
so
moving
on
to
geosecondaries,
we
are
working
towards
improving
the
user
experience
for
geosecondaries
today,
users
end
users
have
to
be
aware
that
there
is
a
geosecondary
and
which
one
they
want
to
use,
and
this
provides
initial
cognitive
load
and
effort
to
you
know
from
our
administrators
to
get
the
word
out
and
ensure
usage,
and
so
we
want
to
make
sure
that
this
is
as
transparent
as
possible
and
so
going
forward.
E
We
are
working
to
support
a
single
url
for
all
git
lab
activities
and
workflows,
whether
it's
the
web,
git
and
so
on,
and
so
once
this
is
done
and
we're
getting
very
close
now
we're
largely
in
testing
phases.
Here
you
you
can
now
have
multiple
secondaries.
You
can
bring
them
up
as
as
demand
requires,
or
as
your
users
change
where
they
are
throughout
the
world,
and
this
is
completely
transparent
to
end
users.
E
All
they
will
see
is
actually
utilizing
gitlab
normally
and
it
will
just
not
be
faster
than
otherwise
would
have
been
without
that
secondary
in
place,
and
so
this
would
be
a
really
exciting
improvement
for
all
those
users
who
utilize
geosecondaries
for
gitlab
from
there.
We
can
move
on
to
new
markets
and
we
are
working
towards
two
areas
here.
E
So
folks
who
are
are
looking
for
that
stamp
of
approval
for
mad
at
can
be
confident
that
we've
met
the
requirements
from
the
red
hat
standpoint
and
we
are
also
continuing
to
work
towards
a
fixed,
compliant
git
lab
service
and
that
way
for
customers
who
are
in
public
sector
or
perhaps
worker
public
sector
can
more
easily
meet
this
compliance
requirement
with
gitlab
itself
as
a
self-managed
service.
So
looking
forward
to
those
items
from
enablement,
section
and
I'll
pass
it
back
to
you
a
new
to
wrap
us
up.
A
Thank
you.
Thank
you
team
for
a
very
thoughtful
prioritization.
I
know
we
do
this
monthly,
so
it's
really
important
and
I
appreciate
the
thought
that
goes
into
it.
I
heard
a
lot
of
amazing
things.
I
heard
usability
front
and
center.
I
love
the
mr
needing
my
intention
work
that
we're
doing
amazing
iteration
towards
the
vibe
ide
performance
and
ease
of
use.
We've
seen
a
lot
of
date.
Capabilities
come
on
that
over
the
last
several
releases,
multiple,
automated
iteration
cadences,
so
everyone
can
have
the
freedom
to
pick
what
works
for
them,
removing
duplicates
from
container
scanning.
A
We
know
that
lots
of
duplicates
make
it
hard
to
find
the
the
needle
in
the
haystack
if
you
will
better
visibility
into
your
ci
cd
consumption
at
a
group
level.
We
all
need
that
mr
widget
improvements,
it's
a
very
often
cited
improvement
that
our
sus
surveys
and
others
have
revealed
so
super
excited
about
that
intuitive
view
of
our
pipeline
index,
page
to
identify
relevant
information
and
triage
the
field
pipelines
that
sometimes
do
occur,
and
then
secondary
sites
proxy
into
primary,
with
a
single
url,
all
great
usability
stuff.
I
also
heard
a
lot
of
reliability.
A
Security
and
performance
focus
pips
compliance
for
kittly,
a
service
which
I
know
a
lot
of
regulated
and
government
institutions
require
from
us
reliable
disaster
recovery,
incremental
repo
backups
for
our
self-managed
customers,
improving
the
gitly
cluster
and
geo
interoperability
to
avoid
deeper
renames
all
stuff,
we
just
noticed,
josh
went
out
and
came
back
in
30
seconds.
A
We
want
to
do
that
for
all
our
customers,
with
git
lab
in
general
per
source,
ip
rate
limits
for
pages
again,
an
important
thing
deleting
stopped
environments,
automatically
cleaning
up
and
saving
dollars,
continued
focus
on
database
decomposition
and
dedicated
release,
cluster
for
session
keys,
awesome,
awesome,
stuff
and
then,
finally,
last
but
not
least,
ast
leadership.
A
The
enablement
for
ise
scanning
is
amazing.
Helps
you
detect
misconfigs
reduce
network
attack
surface
detect
unencrypted
loggings
as
such.
Why
wouldn't
you
want
to
use
that
and
then
sas
scan
execution
policies
to
run
them
on
required?
Cadences
again,
I
think
this
is
going
to
be
one
of
the
most
awesome
releases
ever
so
with
that.
Thank
you.
Everyone
for
attending
and
we'll
see
you
again
next
month.