►
From YouTube: Monthly Release Kickoff 13.2
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
Please
release
kickoff
call
and
when
you
put
a
noob
tower,
the
vice
president
of
product
management
at
gate
lab
and
today
we
will
kick-off
release.
13.2
planned
for
July,
22nd
2024
or
for
product
leaders
will
cover
the
updates
in
four
sections,
we'll
start
off
with
secure
and
defend
with
David,
followed
by
enablement,
led
by
Josh,
then
dev
with
Eric
and
finally,
Kenny
will
bring
us
home
with
ops
like
to
remind
you
that
we
have
a
kickoff
page
on
git
lab
website
at
about
doc.
A
Kit
lab
dot-com,
slash
direction,
slash
kick-off
if
you'd
like
to
follow
along
or
use
it
as
a
reference
later
you'll
find
informative
videos
and
links
to
issues
of
all
plant
functionality.
We
invite
everyone
to
contribute
by
providing
your
inputs
and
feedback
on
the
issue.
Threats
keep
in
mind
that
we
do
plan
ambitiously
and
some
of
the
things
we
talked
about
here
may
not
make
it
into
13.2,
although
we
do
intend
to
ship
them.
Therefore,
our
plans
are
dynamic
and
may
change
with
that
like
to
hand
it
over
to
David.
Take
it
away.
David
thank.
B
You
very
much
new.
Let
me
get
my
screen
shared
here,
so
there's
a
lot
of
items
that
are
going
on
today
with
secure
independent,
I,
highly
recommend.
You
watch
the
videos
that
the
team
has
provided.
They've
done,
a
very
good
job
going
through
their
areas
of
focus
kind
of
get
us
kicked
off
here.
We've
been
focusing
on
one
central
theme
off
the
last
several
releases
and
it
will
continue
with
this
release.
B
That's
obligation,
security
testing
leadership
and
we're
focusing
on
bringing
our
three
primary
categories
of
SAS
test
and
dependency
scanning
to
complete,
introducing
fuzz
testing
and
bringing
that
to
viable
maturity,
and
with
that
I
just
want
to
highlight
that.
Last
week
we
announced
two
acquisitions,
one
a
fuzz.
B
B
The
results
themselves
will
not
be
in
13.1
available
within
the
vulnerability
management
components,
including
the
merge
request,
widget
pipeline
report
and
on
the
dashboard.
However,
we're
going
to
make
them
available
to
be
downloaded
as
raw
file,
so
you
can
review
them
within
the
configuration
spot,
you'll
begin
to
see
buzzing
showing
up
and
again
primarily
the
coverage
guided
buzzing
and
then
on
your
pipeline
report
for
security,
you'll
see
there'll,
be
abundances
buzzing
results
and
from
there
you
can
click
that
and
download
all
the
raw
output
from
the
engine
and
see
the
results
the
engine
is
found.
B
The
next
big
thing
I
wanted
to
highlight
for
you
is
that
the
threat
insights
team
and
the
vulnerability
management
category
moved
from
defend
over
to
secure
and
that's
because
the
focus
of
the
vulnerability
management
category
today
is
been
helping.
You
triage
the
security
findings
and
secure
categories.
Fine
and
there's
two
major
items
that
are
coming
out
in
13.2.
B
The
first
is
extending
what
you
can
see
on
the
project
level
dashboard
and
there's
some
really
great
new
data,
that's
being
pulled
out,
so
you
can
see
it
directly
from
that
view,
and
this
will
be
an
ongoing
project.
As
you
can
see,
there's
multiple
steps
here.
Well,
the
first
one
I'll
highlight
for
you
our
two
new
columns
that
you'll
see
on
that
project.
Dashboard.
The
first
is
the
scanner
column
and
on
there,
you'll
see
not
only
just
the
category
but
the
scanner
that
found
the
result.
B
This
is
really
important
when
you're
dealing
with
not
only
a
gitlab
scanner,
say
this
example
using
our
sassed,
but
then
you're
also
using
a
scanner
from
a
third
party
and
leveraging
our
third-party
integrations.
Then
here
you
can
see
in
this
example,
white
sources
listed
as
the
scanner.
This
is
the
beginning
of
us
being
able
to
deduplicate
results
and
allow
you
to
see
just
the
finding
you
need
and
not
have
multiple
entries,
one
for
each
scanner
type
again,
we're
also
adding
a
column
for
identifiers.
B
This
will
also
help
with
our
deduplication
efforts,
and
here
you
can
see,
apparently
cv
ids-
that's
usually
the
identifier
for
vulnerability.
We'll
also
have
the
proprietary
expose
identifiers
as
well
as
in
this
example,
hacker
one
as
well
as
things
like
cwe's
for
numerating
common
weaknesses.
The
final
thing
I
want
to
highlight,
for
you
here,
succeed
on
this
finding
here:
processed
there's,
an
entry
that
says
line
and
a
line
number
so
again
directly
from
the
dashboard
you're
able
to
jump
in
and
begin
resolving
that
issue
also
from
the
scanner.
B
Drop-Down
you'll
also
see
the
scan
types
as
you
have
before,
but
also
the
scanner
that's
related
to
that
we
can
drill
in
just
like
scanner
results
from
the
dashboard.
The
other
item
is
we're
extending
how
you
can
attach
your
issues
to
the
vulnerabilities
that
are
crowned
with
13.0
and
saniland.
Vulnerabilities
vulnerabilities
are
not
treated
as
a
first-class
item
in
our
product
that
includes
looking
like.
They
are
an
issue
and
again
you
see
the
information
we're
now
exposing,
but
we
have
move
the
crate
issue
down
to
the
bottom
and
we've
added
an
add
issue.
B
Did
you
do
that?
Okay,
there?
You'll
click.
Add
issue
you
can
see
the
ability
to
add
in
related
issues
and,
of
course,
just
like
on
the
view
that
you
have
on
issues.
We
have
the
related
issues
here
on
the
standalone
vulnerability
and
you
can
see
the
ones
have
been
related
as
well
as
created
next
to
kind
of
go
into
static
analysis,
focusing
again
on
bringing
static
analysis
and
sass
to
a
complete
maturity.
We've
talked
about
the
expansion
of
the
UI,
so
off
again
off
the
configuration
you'll
have
manage.
B
I,
don't
want
to
highlight
for
you
because
we've
walked
through
this
previously
is.
It
will
now
open
up
the
merger
class
for
you
to
merge
in
your
configuration
changes
that
way,
you
don't
have
to
manually
figure
out
how
to
take
the
UI
changes,
bring
them
over
and
put
them
back
into
your
file.
It'll
auto,
create
that
merge
request
for
you
to
approve.
B
This
is
rescanning,
but
there's
the
option
to
create
a
profile,
and
from
that
you
can
see
we'll
have
both
site
profiles
where
you
can
define
different
paths
or
different
sites
that
are
part
of
this
project.
You
want
to
be
able
to
scan
you'll,
see
whether
or
not
we've
actually
verified
that
they're
yours
and
you
can
actually
skinned
them
so
you're,
not
inadvertently
scanning
someone
else's
application
and
then
also
profile
scan
type.
So
that
way
you
can
actually
define
what
is
a
quick
run
for
you,
an
active
run
and
so
forth.
B
B
Finally,
to
wrap
this
up
with
defend,
defend,
has
two
items
within
the
container
security
section
that
is
focused
on
policy
management,
they're,
both
labeled
as
stretch
but
I,
wanted
to
highlight
them
for
you,
first
we're
working
on
taking
what
we
did
in
earlier
releases
on
the
on
the
threat,
monitoring
page
and
extending
what
you
can
do
so
again,
you
can
see
your
policies
under
the
policies,
tab
on
prep
monitoring
and
be
able
to
create
your
policy.
But
now
you
can
actually
edit
that
and
you
get
a
nice
point-and-click
GUI.
B
You
can
be
able
to
name
it
come
in
and
take
great
roles
select
the
type
of
traffic
where
you
want
it
to
go,
say
we
want
to
limit
this,
to
listen,
Vic,
IP
address
and
maybe
a
specific
port
and
we're
focusing
on
HTTP.
You
can
see
it's
actually
showing
you
the
role
in
English
format.
If
you
want,
you
can
always
so
grab
the
yellow
or
if
you
just
want
to
view
what's
being
generated
by
the
animal.
What
you
know
was
being
generated
by
the
policy
editor.
B
C
Thanks
Anup
and
thanks
David,
that's
some
really
excited
changes
there
and
D
secure
in
defense,
section
go
ahead
and
get
my
browser
shared
and
we'll
talk
about
an
ailment.
So
like
David,
we
have
a
lot
of
really
interesting
things,
so
please
do
check
out
the
cacao
videos
for
each
of
our
groups.
I'm
not
gonna,
have
time
to
cover
everything
here
in
this
section,
but
instead
we'll
focus
on
the
highlights
and
a
lot
of
them
in
this
release,
focus
around
primarily
performance
and
availability,
but
also
we're
continuing,
of
course,
to
improve
some
teachers
as
well.
C
So
let's
get
going
and
talk
about
the
database
of
the
get
live
instance,
which
is
super
interesting.
At
least
we
find
it
interesting.
The
first
thing
we're
doing
here
is
you
want
to
add
support
for
post
res
12.
We
launched
a
requirement
for
pushes
11
in
13
doe
last
month
and
we're
working
to
support
push
for
s
12
here
in
this
release,
as
an
opt-in
fashion
for
new
customers.
So
taking
a
bit
of
approach
here,
that's
a
pre
12,
but
it
brings
on
a
number
of
benefits.
C
The
first,
of
course,
is
the
engine
is
much
faster
and
so
by
upgrading
to
this,
you
can
simply
get
your
instance
to
move
more
quickly
and
get
a
better
responsiveness,
but
also
there
are
some
distributions
out
there
that
didn't
have
packaged
for
PG,
11,
and
so
adding
support
for
this
well
early
will
continue
to
allow
these
customers
to
upgrade
to
get
lab
on
PG
12,
with
their
package
manager
of
choice.
So
we're
very
excited
about
that,
and
along
with
PG
12
is
also
the
switch
over
from
Brett
manager
over
to
Patroni.
C
These
tools
are
a
key
part
of
the
multi
node
post
res
service
that
we
offer
and
Patroni
is
required
to
support
post
for
us
12
rep
manager
3.
This
is
not
so
it's
very
important,
there's
also
a
number
of
benefits
as
well.
We
think
it's
more
reliable
than
rep
manager
3,
and
it's
also
some
quality
of
life
improvements
for
our
administrators,
in
the
sense
that
previously
403
when
a
PG
node
went
down,
you
can
bring
it
back
into
the
cluster.
C
Here
to
date,
but
we
wanted
to
expand
that
and
make
sure
we
have
improvements
for
everyone
in
particular,
so
many
cases
that
we
might
not
be
seeing
on
get
lap
comm.
It's
looking
forward
lateral
entry
coming
back
to
help
us
better
target
improvements.
That
said,
we
are
course
working
on
improvements
in
general
as
well.
C
One
of
the
ones
is
the
controller
that
actually
renders
files,
and
so,
for
example,
would
you
go
to
put
an
overview
page
will
awesome
time
to
show
a
markdown
file
if
you
look
at
them
a
ton
of
Fallot
and
you're,
also
in
the
UI,
this
same
code
still
runs,
and
it
hasn't
been
very
fast.
We've
looked
into
it
and
it
looks
out.
It
looks
like
a
lot
of
the
time
it
takes,
has
actually
done
an
XML
parsing
and
a
lot
of
it.
We've
done
some
analysis
here
and
some
improvements
in
caching,
and
you
can
see.
C
We've
actually
seen
some
dramatic
improvements
already.
This
will
land
and
perching
that,
in
particular,
the
HTML
parsing
time
has
gone
down
for
this
particular
file
from
12
seconds
and
a
half
a
second,
which
is
a
significant
reduction
the
overall
time
it
takes
to
load
this
file.
Now
this
file
is
a
kind
of
a
stress
test,
and
so
I
want
to
give
an
intuition
that's
40
seconds
to
load
all
files
I'm,
certainly
not,
but
you
can
see
here
the
size
of
improvement
that
we're
launching
here
with
this
change,
so
we're
very
excited
about
that.
C
We're
also
making
some
memory
improvements
here,
primarily
by
pre
loading
before
before,
and
so
to
make
sure
we
load
as
much
as
possible
before
we
fork,
and
that
way
this
process
can
share
as
much
memory
as
possible.
You
can
continue
to
drive
down
our
memory
requirements
for
our
application,
so
we're
doing
that
for
a
sidekick
as
well
as
also
a
cable
on
the
web
processes
and
then
I'm.
C
So
really
excited
about
that
and
moving
on
to
our
last
topic
here,
which
is
the
advanced
global
search
rollout
a
key
benefit
here,
is
that
we
were
rolling
the
vegetable
search,
all
paid
groups
on
github.com
by
July
1.
So,
even
in
a
couple
days
here,
we've
been
able
to
show
that
we
can
run
and
the
increased
velocity
for
indexing
would
that
mid
patent
to
give
that
a
connoisseur
vez
and
so
by
the
current
through
publicly
learning
through.
C
There
are
some
villa
mirrors
which
you
don't
do
a
good
job
of
handling
for
certain
languages,
and
that
means
that
we
sometimes
miss
results
and
we're
going
through
and
improving
those
things,
in
particular,
so
special
characters
in
13
that
to
to
make
sure
do
a
better
job
of
indexing
code
and
showing
results
where
users.
So
if
drag
said
what
then
as
well.
So
it's
the
highlights
for
enablement.
I'll
pass
it
back
to
a
new.
Take
us
from
here.
Thank.
D
Right
thanks,
everyone
I'm
gonna
talk
through
what's
cooking
for
the
dev
section
in
13.2,
we've
got
some
awesome
stuff
lined
up
I've,
grouped
our
enhancements
into
three
kind
of
big
themes,
and
those
themes
are
enterprise,
enhancements,
easier
collaboration
and
visibility
and
deeper
integrations
and
so
I'll
just
walk
through
each
of
those
themes
in
order
so
for
enterprise.
Enhancements.
D
We
also
want
to
make
it
easier
for
admins
to
understand
which
of
their
credentials
are
expired,
and
so
we're
going
to
do
this
in
both
the
SSH
and
personal
access.
Token
credential
inventory
list
by
providing
a
status,
column
or
status
indicator
that
highlights
which
of
their
team
members
access
tokens
or
SSH
keys
might
be
expired
so
that
they
can
go
and
fix
that
issue
with
those
particular
users.
D
Following
on
to
our
group
compliance
dashboard
that
we
released
a
few
months
ago,
we
are
also
going
to
add
the
mr
author
on
to
that
group
dashboard
and
the
primary
reason
we
want
to
do.
This
is
for
separation
of
duties,
types
of
reporting,
so
we'll
quickly
add
the
mr
author.
Here
we
already
have
the
approver
on
this
and
I
would
imagine.
D
We
continue
iterating
here
by
highlighting
these,
mrs,
that
didn't
adhere
to
separation
of
duty
type
auditability,
and
then
our
our
last
issue
that
I
want
to
highlight
for
Enterprise
enhancements
is
really
a
better
backup
strategy
for
really
large
repositories.
We
have
a
number
of
ways
to
back
up
repositories
today,
but
they
don't
work
very
well
for
really
large
repositories
and
for
those
customers
that
have
a
ton
of
really
large
repositories.
D
So
there's
a
few
workarounds
here
in
this
current
issue,
but
really
the
things
that
we're
going
to
be
focused
on
in
13,
2,
R,
1,
parallel
wising,
the
backup
process.
Currently
it's
a
serial
process
and
you
can
take
a
lot
of
time,
and
so,
if
that
process
actually
takes
longer
than
then
you're
your
backup
period,
you
can
run
into
big
problems
where
you're,
just
always
executing
a
backup
which
is
a
really
bad
spot
to
be
in.
D
And
the
second
thing
we're
going
to
do
is
to
implement
an
incremental
repository
backup
strategy
so
that
once
you've
done
your
first
backup
you're,
now
only
backing
up
the
increment
or
what's
changed,
which
should
really
help
a
lot
of
our
enterprise
and
larger
instance.
Users
at
gitlab
I,
don't
have
issues
to
show,
but
we
also
are
going
to
continue
as
always
working
on
get
early
cluster
by
focusing
on
strong
consistency
as
well
as
redistribution
across
all
of
the
clusters.
D
So,
moving
on
to
the
easier
collaboration
and
visibility
theme,
I'm
gonna
highlight
some
really
really
cool
stuff,
I'm
very,
very
excited
for,
and
the
first
is
the
launch
of
what
we're
calling
iterations
inside
of
the
git
lab.
So
iterations,
if
you're
familiar
with
other
planning
tools,
is
what
might
be
called
externally
as
Sprint's.
D
D
Well,
we're
also
going
to
continue
working
on
something
I
announced
last
release,
which
is
epic
swim
lanes
on
issue
boards,
and
so
just
a
quick
view
of
what
this
might
look
like
is
once
you've
got
your
board
scoped
to
the
issues
that
you
want
on
it.
You
group
by
epic
and
it'll
group
them
by
the
epics
that
they're
attached
to,
and
so
a
great
MVC
really
excited
to
see
this
one
land
and
I
think
it's
great
work
by
the
team.
D
So
far,
we
have
a
really
great
feature
called
value
stream
analytics
that
helps
people
define
visualize
and
then
measure
individual
stages
in
their
value
stream.
But
the
problem
is,
you
only
can
only
have
one
view
for
the
group
or
the
O's
or
the
project
and
so
similar
to
issue
boards.
What
we're
going
to
do
is
allow
you
to
create
multiple
value
stream
views
so
that
you
can
capture
a
specific
value
stream
view
for
your
team
or
for
your
process
or
for
your
initiative,
which
will
really
help.
This
feature
be
much
more
valuable
to
those
users.
D
For
design
management
we're
going
to
make
that
feature
a
little
bit
more
visible
as
well.
So
if
you've
used
our
design
management
feature
which
recently
came
down
to
core,
you
can
see
that
it's
kind
of
a
buried
feature.
You
have
to
scroll
about
halfway
down
your
issue
and
then
you
have
to
click
on
this
button
just
to
find
it,
but
really
those
designs
attach
there
should
be
front
and
center
to
the
process
and
with
respect
to
collaboration.
D
And
so
what
we're
going
to
do
is
remove
this
design
section
up
kind
of
at
the
bottom
of
the
issue,
description,
which
will
help
make
those
designs
front
and
center
so
that
everyone's
looking
at
the
latest
designs,
all
at
once
and
then.
Lastly,
for
enhanced
collaboration.
I'm
super
excited
about
this.
One
is
real-time
feedback
for
editing,
gitlab,
CI,
EML
files
in
the
web
IDE.
So
if
you're
familiar
edited,
get
lab
CI
mo
files,
you
know
that
they
can
be
complicated
and
they
have
a
ton
of
parameters.
D
These
CI
demo
files
so
really
really
excited
to
see
cross
collaboration
here
between
multiple
stages
and
lastly,
moving
on
to
my
last
name:
deeper
integrations:
we've
got
some
awesome
stuff
coming
here,
so
I'll
quickly
walk
through
this.
We
are
going
to
invest
into
an
expanded,
JIRA
integration
and
we
want
to.
We
have
a
ton
of
customers
that
use
git,
lob
and
use
JIRA,
and
we
want
to
make
that
experience
just
a
lot
better.
D
We
already
have
a
jitter
integration,
so
what
we're
going
to
do
is
iterate
on
that
integration
and
we're
going
to
display
JIRA
issues
right
inside
of
your
git
lab
instance.
We're
gonna
start
here
just
by
doing
a
simple
display
and
then
we'll
continue
iterating
by
making
these
issues
configurable
and
interactable
by
allowing
you
to
edit
them.
But
we
really
excited
for
this
and
excited
to
kind
of
just
allow
those
customers
that
are
using
both
JIRA
and
get
mom
to
stay
in
the
same
application
as
they
as
they
utilize
the
various
pieces
in
gitlab.
D
So
they
can
quickly
see
their
JIRA
issues.
Similarly,
we
have
a
same
story
for
confluence,
and
so
we
want
to
kind
of
iterate
and
test
out
an
experiment
on
an
on
an
MVC
to
load,
an
external
confluence
workspace
into
a
get
lab
instance.
So
this
is
a
potentially
what
it
could
look
like
and
we'll
continue
iterating
here
and
then.
Lastly,
the
my
last
issue
for
us
is
that
I
want
to
announce
that
we
are
planning
on
an
official
get
loud,
figma
plugin.
E
E
I
wanted
to
highlight
I'll
jump
straight
to
one
specific
theme,
and
that
is
the
theme
of
adopting
the
additional
stages
in
the
DevOps
loop
and
in
the
ops
section
we
specifically
focus
on
verify,
release,
package,
monitor
and
configure,
and
the
reason
why
I
want
to
highlight
this
is
many
of
our
customers
come
from
source
control
from
using
us
as
a
source
control
platform,
and
we
really
want
to
show
them
the
benefit
of
a
single
DevOps
platform
and
we're
gonna
I
want
to
highlight
the
features
we're
working
on
that
enables
a
kind
of
more
rapid
and
easier
adoption
of
additional
stages
throughout
the
DevOps
platform.
E
That
is
get
loud.
So
I'll
start
with
verify
verify
is
a
critical
one
of
moving
from
create
to
verify
and
the
critical
component
of
adopting
get
Web
CI
and
verify
tools
is
having
a
runner
and
so
there's
a
bunch
of
great
work
happening
within
the
runner
team
to
add.
What's
a
visual
of
a
guided
install
for
when
installing
a
runner?
So
today
you
typically
choose
that
you
want
to
install
a
runner
in
our
jumps
to
our
documentation.
This
kind
of
is
guided
it's
a
more
interactive
version
of
our
documentation.
E
We're
also
adding
support
in
the
runner
for
a
very
popular
distribution,
the
IBM
Z,
so
we're
adding
a
first
step
of
having
a
docker
image
that
can
run
in
Linux
on
IBM
Z
that
will
unlock
a
number
of
customers,
your
weren't
able
to
utilize
the
power
of
integrated
source
control
in
CI,
because
the
docker
runner
wouldn't
run
where
they
need
to,
and
then,
lastly,
for
the
runner,
there's
also
work
going
on
in
13.2.
That
will
enable
the
better
management
of
a
fleet
of
runners.
E
So
this
is
a
visual
of
the
run
or
management
page
which
will
allow
you
to
see
what
types
of
projects
are
running
jobs
in
with
those
specific
runners,
any
tags
for
those
runners
and
better
manage
multiple
runner
types
that
might
be
needed
for
your
various
projects.
You
to
utilize,
get
lab
CI.
The
next
major
jump
is
from
to
release
and
I
wanted
to
highlight.
A
couple
of
things
were
working
on
to
improve
the
ability
to
start
using
gitlab
for
your
continuous
delivery
or
general
release
process.
E
We're
gonna
be
adding
support
for
deploying
the
EECS,
where
the
target
type
of
that
ECS
cluster
is
actually
AWS,
Fargate
containers.
So
that's
a
really
exciting
for
our
AWS
customers
who
are
wanting
to
utilize
that
type
and
then
the
next
is
add
continued
in
iteration
on
our
feature
flags,
and
so,
if
you're
familiar
with
feature.
Fogs
are
a
really
important
component
of
enabling
progressive
delivery
in
organizations,
especially
for
more
container
based
applications.
E
But
our
previous
feature,
flag
capabilities,
did
not
allow
you
to
control
when
rolling
out
the
percentage,
the
experience
of
how
that
percentage
was
perceived.
So
it
wasn't
necessarily
based
on
sessions.
It
was
based
on
percentage
based
for
the
logged
in
users.
This
new,
flexible
feature,
flag
type
for
a
percentage
rollout
will
allow
you
to
choose
what
the
that
percentage
is
based
on
giving
application
managers
more
control
over
how
they're
rowing
out
feature
flags.
E
The
other
type
of
common
use
case
for
adopting
our
release
features
is
actually
for
your
kind
of
more
traditional
may
be
manually,
deployed
projects
that
need
more
control
over
their
release,
and
so
I'm
really
excited
to
the
team
is
going
to
be
working
on
adding
and
the
ability
to
read
your
vault
variables
directly.
Ncis
has
been
a
lot
of
of
work.
Coming.
E
We've
had
previous
releases,
where
we've
allowed
you
to
interact
more
in
a
more
integrated
fashion,
with
vault
directly
in
your
CI
mo,
but
this
is
really
kind
of
the
culmination
that
allows
you
to
directly
reference
your
vaults
variables
in
CI
and
then.
Lastly,
many
of
the
organizations
that
are
adopting
give
live,
release
features
need
to
have
release
blackouts
and
so
will
be.
E
We've
previously
announced
the
ability
to
define
release
blackouts
in
llamo
definitions,
we're
gonna
be
adding
a
UI
to
define
when
releases
when
release
jobs
should
or
should
not
run
and
having
that
be
configurable
directly
in
the
UI.
The
last
adoption
phase
that
I
really
wanted
to
focus
on
was
on
monitor,
and
this
is
really
important
for
the
process
of
getting
the
actual
feedback
loop
in
DevOps.
So
after
monitor,
you
go
back
into
plan
and
you
want
to
make
sure
that
you're
getting
great
feedback
to
improve
your
product.
E
One
of
the
things
that
has
been
kind
of
rapidly
expanding
was
in
git
lab.
Is
the
ability
to
integrate
with
your
existing
alert
system
and
have
those
alerts
show
up
and
get
labs
so
that
you
can
triage
them?
So
I
wanted
to
highlight
that
we'll
be
adding
the
ability
to
win
setting
up
that
configuration
easily
test.
E
If
your
endpoint
is
getting
the
information,
you
need
to
showcase
more
alert
information
like
the
metrics
coming
from
the
alerts
and
the
logs
in
right
there
in
the
alert
detail,
as
well
as
adding
integrations
like
pager
duty,
as
well
as
opportunity
to
more
readily
get
your
alerts
and
feedback
loop
back
in
to
get
lab
and
with
that.
Those
are
the
highlights
from
the
ops
section,
I'll
hand
it
back
over
to
you,
and
you
have
to
close
this
out.
Thank.