►
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
Welcome
everyone
welcome
to
the
release
kickoff
for
milestone
15.2.
My
name
is
david
desanto,
I'm
the
vp
of
product
here
at
gitlab
I'll,
be
your
guide
on
today's
journey
into
the
depths
of
gitlab
15.2,
I'm
joined
by
some
of
the
members
of
our
awesome
product
team.
A
Cmy
principal
product
manager
for
the
protect
stage
will
provide
updates
for
our
sex
section,
tara,
taylor,
mccaslin
principal
product
manager
for
our
model
up
stage,
we'll
provide
updates
for
our
model,
ops,
section
knee
johnson
senior
director
product
for
our
ops
and
analytics
sections
we'll
provide
our
op
section
updates,
josh,
lambert,
director
of
product
for
our
enablement
and
sas
platform.
Sections
we'll
provide
our
enablement
section
updates
and
eureka
lewinsky
director
of
product
for
our
dev
section
will
bring
us
along
with
updates
for,
of
course,
the
depth
section.
A
We
are
focused
on
delivering
value
iteratively,
with
a
focus
on
our
fy23
product
investment
themes.
Our
first
theme
is
get
live
hosted
first,
I
want
a
note
for
everyone
that
does
not
try
again.
That
does
not
mean
get
a
lot
hosted.
Only
apparently,
my
tongue
needs
more
caffeine
today,
but
gitlab.com
is
the
largest
self
known,
our
largest
known
self-advantaged
deployment,
and
we
know
if
we
can
meet
our
requirements,
we
can
meet
our
users
requirements.
A
Our
second
theme
is
improved
key
workflow
usability.
This
team
is
focused
on
improving
the
workflows
most
critical
to
our
users.
We
know
improving
learnability
will
drive
multi-stage
adoption,
making
a
lot
more
valuable
for
our
users,
and
the
final
theme
is
extend
our
related
nci
cd
devops.
Does
it
until
applications
are
deployed
into
production,
and
we
want
to
make
this
as
seamless
and
frictionless
as
possible
for
our
users
before
I
hand
it
over
to
sam.
We
have
a
short
public
service
announcement
on
this
live
stream.
A
We
will
be
discussing
our
product
roadmap,
which
includes
upcoming
features
and
functionality.
It
is
important
to
note
that
the
information
presented
here
is
for
informational
purposes.
Only
please
do
not
rely
on
it
for
purchasing
or
planning
decisions.
We
plan
very
ambitiously
here
at
git
lab
and
all
details
discussed
on
this
live
stream
are
subject
to
change
the
time
of
any
products,
features
and
functionality
are
made
at
the
sole
discussion
of
gitlab,
and
with
that
I'll
hand
it
over
to
sam
to
kick
us
off.
B
Thanks
david,
so
today,
I'll
be
going
over
a
few
features
from
the
sex
section.
Almost
all
of
our
features
focus
on
the
key
usability
and
workflow
improvements
theme.
The
first
one
is
group
level
policy
management
and
this
one
actually
just
missed
15.1,
but
it
will
for
sure
be
going
out
in
15.2.
In
fact,
it's
already
been
enabled
on
gitlab.com,
and
this
allows
users
to
manage
their
security
policies
at
the
group
level.
B
One
of
the
other
features
that
we're
working
on
around
our
security
policies
is
improvements
to
allow
for
interactive
validation
in
the
security
policy
editor
itself.
So
this
is
when
you're
editing
in
yaml
mode.
It
allows
you
to
edit
that
yaml
and
see
any
errors
live
there,
similar
to
many
of
the
other
editors
in
gitlab.
B
Another
key
improvement
that
I'm
really
looking
forward
to
is
our
operational
container
scanning
feature
this
one
also
just
barely
slipped
out
at
15
1.
But
what
would
be
wrapping
it
up
here
in
15.2,
which
is
moving
this
functionality
to
general
availability
and
out
of
the
alpha
early
access
state
that
it
is
now
you're
already
able
to
manage
these
on
a
per
agent
basis
to
set
it
to
scan
your
production
cluster
for
vulnerabilities,
we're
looking
to
add
support
for
security
policies
so
that
you
can
have
a
scan
execution
policy.
B
That
also
does
the
same
thing
and
again
just
shoring
it
up
with
some
additional
bug,
fixes
and
usability
improvements,
so
that
it's
completely
ready
for
production
use
for
you
to
keep
your
production
cluster
secure.
B
Additionally,
the
das
team
is
going
to
be
continuing
their
work
on
their
browser-based
crawler,
which
is
a
really
exciting
feature.
It's
early
access,
it's
beta
right
now,
but
they're
going
to
be
continuing
to
improve
that
and
get
that
ready
for
general
availability
and
then,
lastly,
we're
going
to
be
continuing
improvements
on
our
sas
and
on
our
vulnerability
management
teams.
C
Hi
everyone,
my
name
is
taylor
mccaslin,
I'm
a
principal
product
manager
for
git,
lab's,
newest,
section
model.
Ops,
mobs
is
focused
on
enabling
and
empowering
data
scientists
to
better
power.
Their
workloads
across
gitlab
today
I'll
be
talking
about
the
applied
ml
group,
which
is
focused
on
making
gitlab
more
intelligent
with
machine
learning
in
15.2.
Our
apply
to
ml
group
is
continuing
work
on
implementing
the
ui
integration
for
a
new
ultimate
feature
called
suggested.
C
Reviewers
suggested
reviewers
uses
a
novel
machine
learning
functionality
to
suggest
a
reviewer
likely
with
the
context
to
review
a
code
change
in
a
merge
request.
This
ui
integration
brings
the
functionality
to
the
existing
code
review
ui,
making
it
easier
to
choose
relevant
reviewers
for
the
merge
request,
we're
also
integrating
a
new
settings
configuration
for
this,
so
that
you'll
be
able
to
enable
it
and
disable
it
via
the
settings.
C
Functionality.
We've
also
recently
published
a
blog
post
about
what
we've
been
up
to
over
the
last
year
since
we
acquired
unreview
the
technology
that
powers.
This
feature
so
definitely
check
out
this
blog
post.
If
you
want
to
hear
more
about
what
it
means
to
bring
machine
learning
to
gitlab
and
then
finally,
we're
also
accepting
ultimate
customers
on
gitlab.com
to
beta
test
this
feature
and
we're
still
looking
for
customers.
C
So
if
you're
interested
here
is
the
link
to
the
form
to
fill
that
out
and
we'd
love
to
get
you
testing
this
feature
and
that's
all.
I've
got
now
I'll
hand
it
over
to
kenny
to
talk
about
ops.
D
Awesome
thanks
taylor
and
I'm
super
excited
about
the
continued
improvement
to
our
suggested
reviews
capability.
Let
me
go
ahead
and
share
my
screen.
D
All
right,
so
my
name
is
kenny,
I'm
going
to
cover
the
ops
section
today.
I
just
want
to
share
that.
This
is
like
my
highlights
of
the
highlights,
so
obviously
go
check
out
all
the
other
kickoff
videos
from
each
individual
group.
There's
a
lot
of
really
exciting
stuff
happening
in
152
that
I'm
not
able
to
cover
today.
D
First,
a
couple
of
public
service
announcements
in
our
configure
group
we're
working
on
adjusting
our
maintenance
policy
to
ensure
that
we
have
a
very
consistent
view
of
what
versions
of
kubernetes
we
support
going
forward
so
stay
on
the
lookout.
D
We
will
be
announcing
that
likely
during
the
15.2
milestone
and
in
the
monitor
group,
we
are
performing
a
number
of
actions
that
are
deprecating
our
previous
metrics
logs
and
tracing
features,
because
actually
this
released
in
15.2
we
plan
on
releasing
and
launching
the
beta
version
of
our
integration
with
ops
trace
company
we
acquired
last
fall
that
will
enable
us
to
deploy
on
gitlab.com
as
a
starting
point,
a
complete
observability
solution
for
our
users
to
use
so
super
excited
about
that
going
through
the
themes.
D
Oh
and
lastly,
the
verify
group
is
doing
a
hackathon
which
I'm
really
excited
about.
We
should
see
a
lot
of
small
usability
improvements
and
new
investigations
into
kind
of
bold
ideas
around
being
able
to
trigger
pipelines
and
jobs
from
new
workflow
types
like
issue
adjustments
and
merge,
request
comments.
I'm
so
super
excited
to
see
the
results
from
that
hackathon
that
the
team
is
planning
in
the
15-2
release
on
the
themes
so
get
that
posted.
First,
we
have
a
number
of
scalability
and
security
issues
that
we're
working
on
across
verify
and
package.
D
We've
made
a
lot
of
strides
over
the
last
six
months,
enabling
ci
decomposition
in
our
database
tables
and
we'll
continue
to
lean
into
further
deconstructing
those
database
tables
so
that
we
can
not
just
allow
ourselves
scale
but
create
new
capabilities
for
our
users,
all
right
on
extending
our
lead
in
ci
cd.
First,
I
wanted
to
highlight
the
pipeline
simulator.
D
This
will
allow
you
to
more
rapidly
understand
if
the
ci
configuration
you've
written
is
going
to
perform,
as
you
expected,
reducing
the
cycle
time
for
making
ci
pipeline
definition
adjustments
next
this
one,
I'm
really
excited
about.
We've,
seen
increasing
interest
in
migrating
to
get
lab
package
registries,
and
so
we're
going
to
be
doing
a
spike.
This
release
in
15.2
around
the
automated
import
of
packages
from
existing
package
repositories
like
artifactory.
I'm
really
excited
about
this
work.
D
It's
testaments
to
how
mature
our
package
registry
capabilities
have
gotten
that
we
have
a
lot
of
interest
from
users
in
in
migrating
next,
in
the
configure
stage
in
our
kubernetes
management
capabilities,
we've
had
the
ability
to
attach
an
agent
that
is
installed
on
your
kubernetes
cluster,
to
your
gitlab
instance,
or
project
or
group,
one
of
the
trouble
troubling
parts
of
doing.
That
is
that
you
don't
necessarily
get
an
immediate
response
about
the
status
of
that
integration.
D
If
the
agent
and
your
gitlab
instance
are
effectively
connected,
and
so
in
15.2
we're
going
to
be
adding
this
integration
status
right
on
the
agent's
detail
page,
so
you
can
quickly
get
an
understanding
of.
What's
the
current
status
of
my
kubernetes
agent,
I'm
going
to
move
on
to
usability,
and
so
again
these
are
just
a
couple
of
the
really
fun
usability
improvements
that
we
have
and
I
like
to
highlight
ones
that
I
think
are
developed
from
a
deep
understanding
of
our
users
behaviors.
D
So
we
recently
added
an
admin
view
for
runner,
fleet
management,
enabling
administrators
or
group
maintainers
the
ability
to
more
effectively
manage
a
fleet
of
runners
that
they
are
using
for
their
to
enable
their
teams
to
perform
ci
cd,
and
one
of
the
first
things
we
realize
is
that
many
users
have
stale
runners,
and
so
we
wanted
to
not
just
show
highlight
that
to
them,
but
also
give
them
the
ability
to
bulk
delete
stale
runners.
So
we're
going
to
be
adding
that
functionality
in
15.2.
D
Next
again,
we
saw
from
user
behavior
interviews
that
users
were
creating
many
artifacts
in
ci
jobs
in
particular,
and
when
looking
at
a
complete
pipeline
results,
you
would
be
looking
at
hey.
I
want
to
download
an
artifact,
but
sometimes
that
list
got
very
large
and
it
was
hard
to
find
the
specific
artifact
you're
looking
to
download,
so
in
15.2,
we'll
be
adding
the
ability
to
search
when
clicking
on
the
download
artifacts
button
and
select
a
specific
artifact
that
you're
looking
for
for
download.
D
Lastly,
this
one
is
is
also
great
from
a
survey
that
we
did
with
users
where,
in
our
container
registry,
when
you
show
the
list
of
all
the
images
in
your
container
registry
a
lot
of
times,
the
path
for
those
container
images
is
generic.
D
And
so,
when
you
look
visually,
you
would
just
see
lists
and
lists
of
the
same
generic
path
and
so
in
15.2
we're
going
to
be
adjusting
that
display
to
show
an
ellipsis
for
the
common
parts
of
the
path
so
that
it's
much
more
straightforward
to
identify
the
distinction
for
specific
container
images
that
you're
looking
for
and
then.
Lastly
again,
this
is
more
about
the
maturity
of
our
package
and
container
registry
capabilities.
D
But
previously
you
couldn't
adjust
the
visibility
of
specifically
the
container
registry
in
the
package
registry,
independent
from
the
project
visibility
and
in
15.2
we're
going
to
enable
you
to
have
more
granular
control
over,
for
example,
having
code
that
is
not
visible
to
it's,
not
publicly
visible,
but
a
container
registry
or
a
package
registry.
That
is
so
another
great
usability
improvement
for
organizations
looking
to
adopt
more
and
more
getlab.
D
F
Thank
you
kenny,
I'm
really
excited
by
the
pipeline,
simulator
and
supposedly
to
more
users.
So
let
me
take
us
through
enablement.
I
have
a
multiple,
exciting
things
to
share
with
you,
but
also
first,
a
reminder
that
we
are
working
on
multiple
long
term
and
under
the
and
under
the
hood
updates
like,
for
example,
the
bus
background,
migrations
framework,
the
red
hat
operator,
certification
or
addressing
memory,
issues
for
women,
background
workers
and
other
initiatives
that
I'm
not
going
to
discuss
in
detail.
F
If
you're
interested
in
more
details,
please
check
our
the
kickoff
videos
by
the
enablement
groups
on
our
kickoff
page
and
let
me
get
started
with
the
gitlab
hosted
first
theme
and
the
first
one
is
from
the
starting
group.
We
are
planning
to
roll
out
the
composition
to
production,
to
gitlab.com
production
on
saturday
july,
2nd.
So,
as
a
quick
recap,
we
are
working
on
the
composition
for
the
past
year,
so
the
idea
here
is
that,
before
the
composition,
gitlab
worked
with
a
civic
database
cluster.
F
So
our
challenge,
right
now
is
that
we
can
add,
as
many
replicas
as
we
may
want
to
scale
up
reads,
but
in
poster
square
all
rights
have
to
go
through
the
main
database
server,
and
the
problem
here
is
that
there
is
a
limit
on
how
much
you
can
scale
a
database
server
as
sim
server.
There
is
a
limit
on
how
many
cpus
or
memories
that
you
can
add.
So
in
order
for
us
to
be
able
to
keep
on
scaling
for
gears
to
come,
we
have
to
approach
it
in
a
different
way.
F
So
what
we
are
doing
with
the
composition
is
that
we
are
splitting
the
database
to
two
databases,
so
we
will.
After
the
composition,
we
will
have
the
main
database
and
we
will
have
the
ci
database
where
we
will
store
all
the
data
related
to
the
cicd
features,
and
this
is
very
exciting
for
gitlab's
availability,
reliability.
F
We
expect
that
after
this
rollout,
we
will
more
or
less
double
the
capacity
the
database
capacity
for
gitlab.com,
and
we
also
expect
the
increased
performance
from
day,
one
after
the
rollout
and
also
in
years
to
come
and
in
addition
to
that
increased
ability.
Reliability
and
availability
with
less
incidents
happening.
So
this
is
a
very
exciting
feature
for
us
july.
F
2Nd
will
be
the
rollout
date
moving
to
the
jail
group
where
we
are
continuing
our
work
on
our
self-service
framework
and
improving
the
underlying
tools
that
are
for
replicating
content
from
primary
to
multi-secondary
secondaries.
F
So
the
value
here
is
that
we
have
a
lot
of
custom
code
for
supporting
each
different
type
of
content
that
we
want
to
replicate
so
by
moving
everything
to
our
self-service
framework,
we're
consolidating
everything
on
a
single
framework
and
that
allows
us
to
maintain
everything
more
easily
and
focus
on
adding
the
other
content.
F
More
features
that
that
value
rather
than
maintaining
old
code.
So
in
50.1,
the
geo
group
has
had
support
for
oci
images
and
15.2
we're
going
to
continue
with
adding
support
for
build
kit
cast
manifest
and
also
work
on
the
longer
term,
initiatives
for
moving
projects
and
wikis,
as
as
well
as
the
container
registry
to
search
to
the
self-service
framework
and
move
the
key
workflow
usability
improvements
and
then
global
search
group.
We're
planning
to
add
a
filtering
by
programming
language
to
our
code
search.
F
So
this
is
something
we
are
not
doing
right
now,
so
this
is
very
important
for
large
projects
where
you
can
have
terms
all
over
the
place.
You
may
have
the
same
term
on
files
related
to
the
backend
to
the
front
end
configuration
files
on
translated
projects.
F
So
we
anticipate
that
this
update
will
greatly
improve
the
usability
of
gitlab
as
an
online
source
viewer
and
browser.
So
in
15.2
we
are
planning
to
add
the
back-end
updates.
That
would
support
this
feature
and
then
move
on
follow-up
milestones
to
adding
the
front-end
components
and
releasing
to
the
github
users
and
moving
to
the
next
one.
We
know-
and
we
have
multiple
reports-
that
the
autocomplete
drop
downs
may
sometimes
take
some
time
to
load
and
this
behind
the
scenes.
This
is
related
to
trying
to
fetch
things
from
all
over
the
place.
F
So,
for
example,
if
I
write
memory,
we're
trying
to
fetch
things
from
merge,
requests
issues,
epics
and
everything,
so
here
we
want
to
speed
this
up
by
running
all
the
queries
of
the
in
parallel
and
fetching
the
the
results
and
shown
the
results
to
the
user
as
quickly
as
the
first
results
come
back
and
finally,
an
update
to
our
search
results,
page
we're
planning
to
move
the
the
scope,
the
scope
filters
from
up
here
that
they
are
right
now
to
the
left.
F
So
that
will
allow
us
to
push
up
the
search
results
and
move
more
search
results
above
the
fold,
which
is
very
important
for
search
results
because
users,
most
probably
most
of
the
times,
check
the
results
that
are
above
the
fold
and,
at
the
same
time,
time
increase
brazability.
F
That's
it
for
enablement,
or
it
is
yours.
G
Thank
you,
and
it's
really
exciting
things,
especially
around
the
improvements,
the
search
and
really
exciting,
to
see
the
the
composition
work
coming
to
production.
So
for
the
deaf
section
we
have
quite
a
lot
of
things
to
go
through
so
I'll,
try
to
rush
through
them
again
through
our
themes
for
get
lab
hosted.
First,
the
workspace
team
is
adding
two
features.
One
is
api
support
for
immediate
group
deletion.
G
With
this
feature,
users
can
mark
an
individual
group
for
immediate
deletion
via
group
settings
in
the
ui
the
curtain.
The
option
is
currently
only
in
the
ui
and
there's
no
option
to
use
it
for
api.
This
helps
users
create
cleanup
scripts
to
better
utilize,
their
storage
and
delete
unused
groups,
and
it
should
improve
performance
and
reduce
timeouts
over
time.
G
This
is
even
an
internal
request
from
our
own
qa
team,
so
excited
to
see
this
continuing
with
the
hosted
first,
the
workspace
team
is
going
to
continue
working
on
consolidation
of
group
and
project
member
management.
G
In
previous
milestones,
we
had
worked
on
creating
a
project
namespace
which
will
create
a
similar
experience
between
groups
and
projects
which
currently
kind
of
behave
differently,
and
this
will
allow
us
to
have
member
management
work
in
the
same
way
between
projects
and
groups.
And
this
is
a
stepping
stone
in
the
foundation
of
allowing.
G
G
So
it's
a
really
exciting
effort
that
we're
working
on
source
code
is
working
on
highlighting
source
code
syntax
on
the
front
end
they're,
completing
the
work
from
switching
from
server-side
transformations
for
files
to
client-side
syntax
highlighting,
and
this
will
reduce,
will
improve
the
rendering
time
for
large
files,
which
will
now
make
this
50
times
faster,
so
really
excited
to
see
this
performance
improvement
and
still
on
the
source
group
source
code
group
they're
going
to
be
working
on
applying
gitlab
sas
ip
allow
listing
for
ssh.
G
G
Moving
to
the
next
theme,
which
is
improve,
improving
our
key
workflow
usability,
the
compliance
team
is
going
to
be
working
on
enhancement
to
custom
http
headers
for
streaming
audit
events,
which
we
will
finalize
for
the
api
itself
and
start
working
on
the
ui
for
doing
this
as
well,
and
they
will
be
working
on
adding
event
type
information
for
audit
events.
G
This
is
really
important
because
currently
everything
has
kind
of
the
same
message,
and
here
you
can
create
custom
messages
that
will
allow
you
to
easily
differentiate
between
different
audit
events,
and
this
will
give
folks
an
easier
ability
to
see
what
type
of
audit
event
they're
receiving
without
having
to
write
a
complicated
parser
to
figure
it
out
themselves.
G
The
group,
authentication
and
authorization
are
going
to
be
working
on
two
initiatives,
including
security
and
performance
improvements,
which
is
supporting
email
sending
via
microsoft,
graph
api
with
oauth2.
G
So
microsoft
has
announced
they're
going
to
be
deprecating
the
basic
authentication
for
smtp.
So
we
will
upgrade
our
authentication
to
oauth
for
outgoing
emails
to
support
this
and
they're
going
to
also
work
on
a
really
exciting
effort
that
we've
been
hearing
from
a
lot
of
customers.
A
lot
of
customer
requests,
especially
around
enterprises,
which
is
domain
verification.
G
This
is
really
exciting
because
we're
going
to
be
using
our
pages
infrastructure
to
do
this,
and
what
this
is
going
to
do
is
that
any
user
matching
your
corporate
domain,
that's
already
verified
in
pages,
will
be
able
to
be
claimed
as
an
enterprise
user.
So
this
will
allow
easier
management
of
enterprise
users.
G
Group
import
is
working
a
lot
of
improvements
for
the
github
importer
among
them.
Two
that
I'll
mention
one
is
allowing
cancelling
improv
in
progress
imports
today,
there's
no
way
to
cancel
a
progress
import
that
started
so
now
we're
going
to
add
the
ability
to
cancel
that
and
in
addition
to
that,
they're
going
to
be
implementing
import
issue.
G
Moving
on
to
code
review,
the
merge
requests.
Widget
working
group
is
working
on
face
lifting
the
mr
experience,
so
I'm
just
going
to
show
you
what
this
looks
like
this
is
going
to
look
like
in
this
milestone.
You
can
see
this
new
merge
request
that
has
this
new
orange
exclamation
point
and
you
can
see
that
it's
pretty
easy
to
understand
the
degradation
and
improvements
with
that
happen.
G
This
is
the
new
ui
versus
the
old
one,
so
this
is
a
kind
of
a
sneak
peek
into
what
this
is
going
to
look
like,
and
this
is
going
to
be
also
integrating
with
yaml
extension
to
provide
gitlab
ciaml
autocompletion.
G
So
today,
when
you
want
to
kind
of
reuse
keys,
it's
really
hard
to
remember
what
you
need
to
do
and
you
usually
need
to
open
another
file
and
copy
and
paste
it.
And
so
what
this
is
going
to
do
is
kind
of
auto
complete
it
so
it'll
make
life
of
the
get
lab.
Ci
yaml
editor
easier,
the
person
who's
writing
it.
That's
so
excited
to
see
that
which
leads
us
into
our
extending
our
lead
in
ci
cd.
G
So,
on
top
of
this
specific
issue,
the
optimized
team
is
working
on
two
main
efforts.
This
milestone.
For
this
sorry,
I
skipped
so
continuing
with
the
usability
workflow.
The
project
management
team
is
working
on.
G
We
we
recently
are
going
to
enable
a
lot
of
work
that
we
did
around
task,
which
is
a
sub
issue
that
can
be
linked
to
an
issue.
So
a
task
we're
going
to
be
adding
support
for
adding
assigning
test
tasks
as
well
as
updating
weights
and
viewing
it
on
the
task
itself
and
now
back
to
optimize
and
what
we're
going
to
add
in
terms
of
lead
in
ci
cd
is
adding
the
fourth
dorametric
trans
chart.
So
we
recently
completed
adding
api
support.
G
Now
we're
going
to
follow
up
with
the
chart
itself
and
last
but
not
least,
we're
going
to
be
improving
the
way
that
people
can
view
usability
improvement.
Detect.
Sorry
as
usability
improvement
that
you
can
easily
see
today
on
the
test
by
type
chart,
it's
really
hard
to
find
how
you're
going
to
filter
and
sort
you.
This
goes
by
labels,
and
so
we're
going
to
be
improving
this
experience
so
that
it
will
be
easier
to
use
and
more
intuitive
and
passing
it
to
you,
david
to
taraba.
A
Thanks
marie
and
thank
you,
everyone
for
presenting
the
great
highlights
that
you
did
today,
there's
so
many
great
things
coming
up
with
gala
15.2.
I
only
have
a
moment
to
highlight
a
couple
ones
that
jumped
out
to
me.
I
will
repeat
what
kenny,
or
even
everyone
said
that
there's
way
more
than
what
I'm
going
to
mention
here.
A
So
please
check
out
all
the
details,
but
for
gitlab
hosted
first
moving
projects
and
wikis,
as
well
as
the
registry,
to
the
self-service
framework
applying
gitlab
sas
ipl
listing
for
ssh
and
the
role
of
the
decomposed
ci
database
for
gitlab.com
for
improved
workflow
usability,
adding
search
filtering
by
programming
language,
introducing
tasks
and
our
which
is
our
first
work
item
from
the
work
items,
initiative,
add
event,
type
information
to
audited
events,
groups,
subgroup
level,
scan
execution
policies
and
operational
container
scanning,
moving
to
ga
for
extender
lead
in
cicd.
A
Adding
the
fourth
story:
metric
change,
failure
rate
as
a
new
trend
chart
simulate
pipelines
under
conditions
with
the
pipeline
simulator.
I
got
to
say
I
geeked
out
a
little
bit
on
that
when
kenny
was
talking
about
that
one
child.
Mr
test
reports
linked
to
parent
pipelines
and
set
the
number
of
deployment
approvals
in
ci
cd
settings.
A
Again,
please
check
out
the
release
kickoff
page.
It
includes
a
full
list
of
items
and
make
sure
to
like
and
comment
on
the
issues
you
want
to
engage
with
the
team
on
also
in
just
two
days
on
thursday
june
23rd
at
8
a.m.
Pacific
time
we'll
be
hosting
a
special
event
for
get
lab
15,
where
we'll
unveil
the
latest
iteration
of
the
one
devops
platform.
A
As
part
of
this
event,
you
will
hear
from
the
best-selling
author
and
dora
co-founder
gene
kim
on
the
future
of
devops
you'll,
learn
about
how
gitlab
will
evolve
the
one
form
to
meet
that
future
and
support
your
aspirations
and
discover
how
good
left
15
will
help
your
team
deliver
secure
software
while
remaining
compliant
and
automating
manual
processes
to
learn
more
about
it.
There's
actually
a
great
landing
page
here.
A
So
let
me
see
if
I
can't
find
the
page
I
want
to
share
which
I
cannot
that
tells
you
have
too
many
windows
open,
but
it's
easy
to
register
you
just
go
to
about.getlab.com15.
You
can
use
the
numbers
1-5
or
spell
the
word
15
and
you
can
register
for
the
event
the
event's
going
to
be
awesome.
I
might
be
biased
because
I'm
presenting
on
it
but
trust
me,
it's
gonna
be
well
worth
your
time
to
register
and
check
it
out.