►
From YouTube: 15.0 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
A
I'm
also
joined
by
some
of
our
amazing
product
product
team
members
that
was
a
tongue
twister
for
myself.
There
they
are
in
the
order.
They
will
be
presenting
tim
rizzi,
principal
pm
for
our
package
stage
and
he'll
be
providing
us.
Our
ops,
section,
updates,
josh
lambert
director
of
product
for
our
enablement
section,
we'll
be
providing
our
enablement
section
updates,
melissa,
usherkov
group
manager
for
the
planned
and
ecosystem
stages
we'll
be
providing
our
dev
section.
A
Updates
hillary
benson
director
of
product
for
our
sex
section
we'll
be,
of
course
providing
our
sex
section
updates
and
then
finally,
taylor,
mccaslin
principal
product
manager
for
our
model
upstage,
and
he
will
be
bringing
us
home
with
some
exciting
mlai
and
model
ops
focus
updates
this
year,
we're
focused
on
providing
value
iteratively
across
our
three
product.
Investment
themes
they
are
get
live,
hosted
first,
improve
key
workflow
usability
and
extend
our
latency
icd.
A
A
It
is
important
to
note
that
the
information
discussed
here
is
for
informational
purposes.
Only.
Please
do
not
rely
on
this
information
for
purchasing
or
planning
purposes.
We
plan
ambitiously
here
at
gitlab
and
all
the
details
discussed
in
this
live
stream
are
subject
to
change.
The
timing
of
products
features
and
functionality
remain
at
the
sole
discretion
of
get
lab,
and
with
that
I
will
kick
it
over
to
tim
for
the
op
section,
thanks
david.
B
B
I
myself
have
a
quick
service
announcement.
It
is
15-0,
so
this
is
gitlab's
chain
chance
to
introduce
any
breaking
changes
and
each
stage
in
the
op
section
has
at
least
one
breaking
change
scheduled
for
15-0.
I
recommend
that
you
check
out
the
documentation
and
see
if
any
of
the
upcoming
changes
will
break
any
of
your
critical
workflows,
so
you
could
prepare
for
those
so
on
to
the
individual
features.
David
mentioned
some
of
the
gitlab
themes
for
the
year.
B
I
would
like
to
highlight
today
two
of
those
themes:
improving
workflow
usability
and
extending
our
lead
in
ci
cd,
so
starting
with
the
usability.
The
first
item
that
I'd
like
to
mention
is
an
improvement
to
the
repository
analytics
page.
So
this
was
previously
difficult
to
understand,
because
the
timeline
and
scope
is
not
necessarily
clear.
So
if
I
pull
up
the
design
here,
I
could
show
you
a
few
improvements
that
we're
making.
B
So,
first
we're
see
adding
a
link
to
the
documentation
here.
Just
so
at
any
point
you
could
click
and
say
see
how
this
page
works
and
what
you're
looking
at
we're,
also
clarifying
the
timeline
of
each
of
these
events.
So
you
could
see
when
was
test
coverage
last
ran
and
what
is
the
window
of
this
chart
here?
We're
also
adding
in
some
functionality
here
so
that
you
could
download
the
historic
data
as
a
csv
and
also
helpful
tool
tips
throughout.
B
The
next
feature
I
wanted
to
highlight
is
adding
visibility
for
shared
runner
usage
for
user
namespaces.
So
as
a
user,
I
have
an
account
account
named
t
rizzy
and
I
may
have
dozens
or
even
hundreds
of
projects
under
that
namespace.
But
previously
there
was
no
way
for
me
to
understand
how
many
ci
minutes
I
was
using
and
what
my
shared
runner
usage
was
like.
So
now
in
150
we'll
be
adding
that
data
to
the
usage
quotas
page.
B
So
I
could
go
here
and
I
could
see
very
quickly
how
how
my
projects
are
consuming
data,
and
here
you
can
see
a
table
view
by
project
and
you
can
see
your
shared
runner
usage
and
your
ci
cd
minutes
usage.
So
hopefully
this
helps
you
to
better
manage
your
projects
under
your
user
name
space.
B
The
next
item
I
wanted
to
highlight
is
the
ability
to
approve
a
deployment
from
from
the
environment
detail
view
view
previously.
You
could
only
do
this
from
the
high
level
environments
page,
but
in
15
0
we're
adding
an
efficiency
saving
you
a
couple
of
clicks
here.
So
from
the
details
view
you
could
very
easily
just
click
this
thumbs
up
and
you
could
approve
or
reject
a
given
deployment,
and
you
can
add
in
any
optional
comments
here
you
want
as
well.
So
hopefully
this
helps
you
to
be
more
efficient.
B
The
next
item
I
wanted
to
highlight
is
part
of
a
broader
epic
to
improve
our
incident
timelines,
but
in
15
0
we
have
a
really
cool
mvc
that
we're
working
on.
So
when
you're
managing
an
incident,
you
often
want
to
be
able
to
add
what
you're
working
on
to
resolve
it
so
from
the
ui
you'll,
be
able
to
add
a
new
timeline
event
with
the
click
of
a
button
and
you'll
also
be
able
to
edit
or
delete
those
items,
just
in
case
you
typed
in
something
by
accident.
B
B
So,
looking
at
the
data
we
saw
that
there
are
projects
with
hundreds
of
thousands
of
runners
that
have
not
contacted
gitlab.com
in
several
months.
This
can
hurt
database
performance
and
can
impact
all
users
on
gitlab.com,
so
starting
in
15
0
will
be
automatically
purging.
Those
there
should
be
little
impact
on
you,
since
these
have
been
inactive
for
a
while,
but
it's
just
something
to
be
aware
of
also
in
15
0,
we'll
add
support
for
podman
to
get
labrunner.
So
podman
is
an
open
source.
Linux
distribution
that
helps
you
to
manage
your
containers.
B
Previously,
we
would
tell
users
that
we
were
not
going
to
officially
support
it
and
that
they
should
use
a
custom
executor,
but
after
hearing
from
the
community
and
our
customers
and
working
with
red
hot
product
management
and
engineering,
we've
decided
to
add
official
support
for
podman,
so
if
you're
using
that
service.
B
Hopefully,
this
makes
your
life
a
lot
easier
when
you're,
building
and
deploying
your
containers
and
finally
one
change-
that's
near
and
dear
to
my
heart
is
starting
in
15-0
we
will
be
migrating
the
gitlab.com
container
registry
to
the
next
generation,
which
will
include
significant
performance
improvements
and
also
unlock
a
variety
of
features
down
the
road
such
as
a
newly
redesigned,
ui
and
security
features
like
signing
and
of
images
using
cosine,
but
in
15o,
specifically
we'll
focus
on
migrating,
the
free
tier
images
with
less
than
100
tags.
B
B
B
Imagine
a
lot
of
folks
will
find
it
valuable,
as
a
lot
of
folks
use
a
lot
of
ci,
let's
jump
into
enablement
here,
as
tim
had
mentioned,
we
have
a
lot
of
our
focus
on
deprecations
and
removals
here
in
the
15.0
release,
so
you
can
check
out
the
links
on
our
dedicated
removals
and
duplications
pages.
B
So
do
please
look
at
those
I'll
be
focusing
on
mostly
the
other
features
working
on,
but
again
we
are
working
on
a
few
of
these
key
large
changes
like
duplicating
pg-13,
starting
in
15.0,
to
be
removed
in
16.0,
we're
switching
some
omnibus
libraries
we're
using,
which
is
a
big
change
as
well
as
also
working
to
upgrade
to
rubric
3.0,
so
lots
of
good
stuff
coming
there
kind
of
mostly
under
the
hood,
but
that's
where
a
lot
of
our
focus
will
be
this
milestone.
Moving
on
to
get
that
hosted.
B
First,
we
have
a
few
notable
features
I
want
to
talk
through
today.
One
is,
we
are
continuing
our
work
to
support
the
solstice
framework
and
move
more
and
more
of
our
application
over
to
it.
B
The
value
here
is
that,
as
you've
heard
from
probably
previous
milestones,
that
we
have
a
lot
of
custom
code
for
each
different
type
of
content,
we're
replicating
and
the
cell
framework
consolidates
that
into
a
single
common
tool
and
framework,
and
so
we
get
a
lot
of
new
features
when
we
migrate
over
and
we
get
a
lot
of
extra
velocity
reduce
tech
debt.
So
we
can
go
faster
in
the
future
with
geo
by
having
a
single
place
to
add
new
features.
B
So,
looking
forward
to
that
and
we're
just
finishing
up
the
last
few
pieces
of
content
here
with
projects
and
wikis
from
there,
we
are
continuing
our
work
to
separate
and
improve
our
metrics
exporter.
Currently
on
git
lab
the
metrics
exporter
is
built
into
all
of
our
web
server
and
other
application
processes.
This
means
that
if
it's
slow
or
has
a
problem,
it
can
impact
the
overall
ability
of
the
larger
software
to
do
its
job,
and
so
what
we
are
working
on
here
is
splitting
it
out.
B
We've
done
that
in
the
past
release
for
puma-
and
we
are
continuing
on
that
process
here
with
rerouting
the
the
actual
exporter
itself.
We've
seen
improvements
of
overall
eight
times
faster
than
the
old
exporter,
and
it
has
a
bunch
of
other
nice
improvements.
You
can
see
here
on
the
requirement
side
of
things,
so
this
will
overall
improve
stability
and
reduce
the
consumption
of
resources
as
well
over
on
global
search.
We
are
working
to
support
open
search
as
well
as
elastic
search.
B
Eight,
so
we'll
have
support
for
both
of
these
two
here
going
forward
in
15.0,
and
the
reason
this
is
a
major
breaking
change
is
that
we
have
to
drop
support
for
older
versions
of
elasticsearch
to
make
this
happen,
so
that
is
happening
now
and
we're
looking
forward
to
having
both
of
these
back
ends
available
for
our
customers
to
use
last,
we
are
continuing
our
work
on
bashed
background
migrations,
these
as
a
common
framework
for
all
of
gitlab
engineers
to
utilize
to
improve
how
migrations
are
run
so
how
we
modify
our
database
over
time
to
support
new
features
and
changes.
B
We've
made
a
lot
of
enhancements
to
this
migration
process.
That's
completely
new
from
the
ground
up,
and
it
has
a
lot
of
improvements
over
the
previous
background
migration
framework
as
part
of
rails.
We
can
automatically
start
automatically
tune
the
performance
of
migrations
and
then
restart
them
as
well.
So
there's
a
lot
of
additional
stability
improvements
for
these
large
background
migrations
as
customers,
data
sets
increase
to
help
make
sure
we're
running
them
performantly
and
reliably
within
the
gitlab
instance,
especially
for
again
some
very
large
ones
that
can
otherwise
impact
the
system.
C
That's
definitely
going
to
be
very
useful,
all
right,
so
I'm
melissa
and
I'm
representing
the
dev
section
today,
just
as
a
reminder,
dev
section
is
comprised
of
manage
plan
create
and
ecosystem
stages
and
the
highlights
for
15-0
mostly
aligned
to
our
usability
theme,
starting
with
work
by
the
code
review
team.
So
we're
going
to
be
introducing
a
way
to
signal,
merge,
requests
that
need
your
attention.
C
C
So
I'm
excited
about
this
feature
because
I
want
to
know
if
I'm
the
one
blocking
nmr.
So
this
gives
me
a
cleaner
signal
and
it
also
gives
me
a
really
great
way
to
nudge
someone
if
I
need
their
attention.
C
This
milestone
we're
also
introducing
gitlab
sshd.
C
Again,
aligning
to
the
usability
theme,
the
editor
group
is
going
to
be
introducing
a
quick
way
to
copy
code
blocks
from
the
content
editor.
Today
you
have
to
highlight
text
and
copy
paste
with
your
keyboard,
which
is
error
prone
and
looks
a
little
bit
like
that
gif.
C
Moving
back
to
the
key
workflow
theme
door:
four
metrics
are
four
metrics
that
have
become
industry
standards
for
measuring
devops
success
for
organizations.
C
Just
as
a
reminder,
here's
what
the
page
looks
like
today
and
here's
what
it's
going
to
look
like.
You
see
that
door
is
clearly
separated
out.
So
it's
a
good
improvement.
C
So
this
is
a
good
reminder
for
users
that
unmet
dependencies
may
mean
that
your
work
isn't
done
or
that
you
have
a
little
bit
of
cleanup
work
to
do
on
your
epics
before
you
can
close
them.
This
functionality
is
going
to
be
really
similar
to
what
already
exists
for
issues
and
we're
introducing
it
to
epics.
C
Finally,
the
foundations
team
continues
to
lead
the
way
with
pajamas
component
migration,
so
this
is
migrating
over
to
our
design
system.
This
quarter
we've
made
a
lot
of
progress.
We've
already
migrated
over
270
components
and
in
this
milestone,
the
team's
going
to
start
discovery
work
for
next
milestone
for
next
quarter
by
basically
doing
an
analysis
to
see
where,
in
our
code
base,
we
have
legacy
component
implementations
for
six
pajamas
components.
D
All
right,
so
the
sex
section
has
a
number
of
things
going
on
this
release.
We're
largely
focused
on
work
that
supports
our
theme
of
improving
key
workflow
usability
similar
to
other
teams.
We
do
have
a
number
of
removals
happening
in
this
release.
I'll
highlight
a
couple
today,
but
be
sure
to
check
out
the
full
list
on
your
own
so
to
get
started
here.
It's
a
big
release
for
the
container
security
team,
so
first
off
for
them
we'll
be
moving
aspects
of
container
scanning
down
to
the
free
tier
on
15.00.
D
This
issue
here
outlines
in
detail
which
features
will
become
core
features
and
which
will
stay
in
ultimate,
but
the
gist
is
that
free
users
will
be
able
to
scan
container
images
in
ci
and
generate
a
json
report
of
dependencies
in
that
image.
But
then
things
like
the
ability
to
take
action
on
vulnerabilities,
using,
for
instance,
mr
approvals
or
to
leverage
auto
remediation
view,
vulnerabilities
in
the
security
dashboard
or
the
ci
pipeline
security
tab.
All
those
things
will
stay
in
ultimate.
D
And
then
the
container
security
team
will
also
be
migrating
vulnerability,
check
rules
to
become
scan
result
policies.
So,
if
you've
been
following
along
security,
approval
policies
were
released
in
14.8
and
are
the
replacement
for
vulnerability
check
rules,
so
vulnerability
check
will
be
removed
in
15.0,
which
means
this
work
is
all
about:
providing
a
smooth
migration
path
for
users
to
start
leveraging
scan
result
policies
instead
and
then
finally,
for
container
security,
we'll
be
removing
the
container
network
and
container
host
security
functionality
that
was
deprecated
in
14.8.
D
The
dynamic
analysis
team
expects
to
ship
two
significant
improvements,
this
release.
The
first
is
delivery
of
a
new
design
for
the
das
on
demand
configuration
workflow,
so
these
changes
are
focused
on
improving
learnability,
with
better
explanations
of
dash
scanning
concepts
and
the
options
are
available
to
users
focused
on
minimizing
context,
switching
and
on
kind
of
improving
the
relationship
between
ci,
cd
and
on-demand
das
configuration
dynamic
analysis
team's.
Second
major
improvement
is
around
parallel,
parallelizing,
the
processing
of
api
security
work
in
order
to
significantly
speed
up
scan
speeds.
D
D
So
this
release,
the
team
is
removing
esl
ghostek
and
bin
analyzers
and
analyzers
entirely
and
then
also
removing
spot
bugs
for
java
as
well
and
then
they'll
be
releasing
a
new
major
version
of
security
code
scan
this
release.
D
The
thread:
insights
team
is
primarily
supporting
git
lab,
hosted
first
work.
This
release
actually
with
continued
performance,
disability
work
but
they're
also
working
on
this
enforcing
validation
of
security
reports.
So
we've
been
talking
about
this
for
the
past
couple
kickoffs,
but
it's
worth
a
reminder
that
we
will
actually
begin
enforcing
schema
validation
in
15.0,
so
the
new
schema
validation
has
been
in
place
for
several
releases
now,
but
it'll
be
enforced
for
the
first
time
this
release.
D
So
that
means
that
any
security
report
that
doesn't
conform
to
the
new
schema
won't
be
ingested
into
their
security
report
at
all
previously.
If
we
would
attempt
to
ingest
these
reports,
even
if
they
didn't
match
the
schema,
which
often
resulted
in
kind
of
bad
or
incomplete
data,
so
this
work
resolves
that
and
with
that
I'll
turn
it
over
to
taylor
to
take
us
through.
What's
coming
up
in
model
ops,.
E
Awesome
thanks
hilary
hi
everyone.
My
name
is
taylor
mccaslin
and
I'm
a
principal
product
manager
for
gitlab's
new
stage
model.
Ops,
modelops
is
focused
on
enabling
and
empowering
data
scientists
to
data
science
workloads
across
gitlab.
Today,
we'll
talk
about
two
groups
within
model
ops.
Both
are
focused
on
our
key
theme
of
improving
key
workflow
usability.
The
applied
ml
group
is
focused
on
making
gitlab
more
intelligent
with
machine
learning
and
15.0.
Our
applied
ml
group
is
starting
work
on
implementing
the
ui
integration
for
a
new
ultimate
feature
called
suggested.
E
Reviewers
suggested
reviewers
uses
a
novel
machine
learning
algorithm
to
suggest
reviewers
likely
having
context
to
review
code
changes
in
a
merge
request.
This
ui
brings
this
ui
integration
brings
the
functionality
to
the
existing
code,
reviewers
ui,
making
it
easy
to
choose
relevant
reviewers
for
a
merge
request.
E
There
is
a
blog
post
from
january
that
overviews
our
plans
with
this
functionality
to
make
it
easier
for
you
to
choose
a
code.
Reviewer
I'll
also
mention
that
this
is
a
a
beta
feature
that
we're
opening
to
ultimate
customers.
So,
if
you're,
an
ultimate
customer
and
interested
in
trying
this
out,
visit
this
form
and
fill
it
out
and
we'll
get
you
integrated
into
this
beta
program.
E
Our
second
functionality
is
our
ml
ops
group,
which
is
focused
on
making
it
easier
for
customers
to
run
ml
and
ai
workloads
on
gitlab,
with
15.0
we're
improving
how
python
notebooks
work
in
merge
requests
to
make
to
improve
data
scientist
workflows
in
a
previous
release.
We've
made
python
notebooks
more
readable
by
rendering
them
in
the
commit
view.
I'll
show
you
what
this
looks
like.
Here's
a
python
notebook
very
raw.
It's
a
hard
file
to
read.
E
If
I
just
click
this
button
here,
we
render
it
so
this
is
available
today
in
the
commit
view
in
15.0
we're
making
this
we're.
Bringing
this
functionality
to
the
merge
request,
view
to
make
it
easier
to
code
review
python
notebook
changes.
This
is
a
feature
for
all
gate
lab
users.
So
this
is
just
the
beginning
for
model
ops,
and
we
have
many
great
plans
for
the
future,
so
be
sure
to
check
out
our
direction
page
for
details
on
our
future
plans
and
I'll
hand.
A
And
thank
you
presenters.
It
was
another
great
kickoff
call,
so
many
great
things
are
coming
in
15.0.
I
don't
have
the
amount
of
time
you
all
went
over
it,
but
I
wanna.
I
just
had
a
couple
things
that
jumped
out
to
me
for
our
gala
piston.
A
First
theme:
production,
readiness
for
our
gitlab
metrics,
explorer
or
exporter,
support
for
elastic
8.x
releases,
moving
our
batch
fabric
batch
background
migrations
to
ga
that
was
a
tongue
twister
for
me,
provide
visibility
for
our
shared
runner
usage
for
user
name
space
and
implement
gitlab
sshd
for
get
lab
sas
for
improved
key
workflow
usability,
merge
requests
that
require
my
attention.
I
will
state
that
I'm
also
looking
forward
to
melissa
having
a
way
to
nudge
people
once
you
want.
A
This
merge
request,
reviewed
updates
to
our
value
stream
analytics,
including
some
new
tiles
for
better
visibility,
block
epic
warning
when
closing
new
workflows
for
our
guest,
on-demand
configuration
workflow
also
very
excited
about
container
scanning,
moving
down
to
free
being
able
to
really
drive
the
community
a
lot
more
here
and
migrating.
The
vulnerability
check
to
scan
result
policies,
and
then
taylor
just
touched
on
some
things
exciting
in
our
model.
Ops
area,
including
integration
of
our
suggested
reviewers
directly
into
the
code
review
experience
and
the
improved
diffing
of
python
notebooks.
A
For
our
last
theme
of
extend
our
lead
in
cicd,
we
heard
about
adding
a
new
action
named
verified,
allow
users
to
validate
and
check
the
deployment
was
successful.
Add
support
for
pubmed
to
get
lab
runner
runner
sas,
including
mac
os
x,
8664,
limited
availability
and
then
automatically
purging
runners
that
have
been
inactive
for
a
long
time.
A
Please
check
out
the
release
kickoff
page
for
a
full
list
of
everything
and
please
make
sure
to
review
the
issues
like
them
and
comment
on
them
and
engage
with
the
team
before
we
wrap.
I
just
want
to
share
that
everyone's
very
excited
about
what
gitlab
15
will
bring.
Please
stay
tuned
for
updates
on
what
themes
good
live.
15
will
be
focused
on
including
things
such
as
ai,
assisted
capabilities,
observability
and
enterprise,
agile
planning
and,
of
course,
so
much
more.