►
From YouTube: GitLab 12.7 Kickoff - Overview
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
Right
welcome
to
the
gitlab
12.7
kick-off
review.
My
name
is
Scott
Williamson
I'm,
the
VP
of
product
for
gitlab
and
happened
to
be
your
emcee
today.
As
usual,
we'll
present
from
this
direction.
Slash
kickoff,
page
I
get
about
get
lab
comm.
So
if
you
want
to
follow
along
with
the
page
that
we're
on
you
can
go
there
as
you
scroll
down
a
bit
Eric
you'll,
see
we
we're
gonna,
ask
this
by
section
and
then
stage
so
dev
is
a
section.
A
We
have
various
stages
underneath
manage
plan
create,
for
example,
each
section
has
videos
you
can
see
for
a
deeper
dive
on
the
various
groups
that
we
have.
You
can
also
dig
into
specific
issues
and
provide
feedback,
so
we
would
love
your
your
interaction
and
feedback
on
the
things
that
we
have
planned
for
this
release.
A
We're
going
to
present
in
five
different
sections,
so
Eric
Brinkman
will
present
on
dev
Jason
Lenny
will
present
on
CI
CD
Kenny
Johnston
will
present
on
ops,
David
DeSanto
will
present
on
secure
and
defend,
and
Josh
Lambert
will
present
on
enablement
and
they'll
be
presenting
high
level
themes.
We
can't
cover
all
the
details
in
here.
So
if
there
are
specific
issues
or
aspects,
you're
curious
about
again,
please
please
weigh
in
in
the
issues
also
a
reminder
we
do
plan
ambitiously.
So
please
do
not
view
this
as
a
commitment,
but
rather
a
target.
A
B
So
much
Scott,
so
my
name
is
Eric
Brinkman
I'm
the
product
director
for
the
dev
section
and
as
a
quick
reminder,
the
dev
section
is
the
first
three
stages
of
the
DevOps
lifecycle
and
that's
the
managed
stage.
The
plan
stage
and
the
create
stage,
and
so
today,
I'll
be
touching
on
a
few
really
neat
things
that
we'll
be
planning
for
collab,
twelve,
seven
in
all
three
of
those
stages.
B
So
let's
go
ahead
and
get
started
with
the
manager
stage
and
in
the
manage
stage,
there's
a
lot
of
great
functionality
coming
for
group,
managed
accounts,
admin,
controls,
audit
logging
and
analytics.
Let's
start
with
group
manage
accounts
in
group.
Manage
accounts
will
be
releasing
functionality
that
will
allow
group
owners
to
disable
project.
Forking
outside
of
the
group
managed
account.
B
This
means
that
those
private
projects
in
the
organization
will
remain
in
the
organization
and
can't
be
forked
to
a
personal
namespace,
we'll
also
be
working
on
a
feature
to
prevent
those
projects
from
being
shared
outside
of
a
group
managed
account
group
today.
This
can
only
be
initiated
by
the
group's
owner,
but
it
does
have
the
potential
to
invalidate
single
sign-on
enforcement,
which
is
something
we
would
want
to
prevent
for.
B
Audit
logs,
while
very
useful
in
the
UI,
are
not
as
easy
to
use
as
they
should
be
because
they
don't
contain
sorting
or
filtering
in
12:7
we're
planning
for
the
ability
to
both
filter
and
sort
the
audit
log
table
in
the
UI,
which
will
make
that
experience
much
better
and
lastly,
and
managed
we
are
working
on
a
new
analytics
feature
that
should
help
users
get
much
more
visibility
into
their
code
review
process.
So
this
mock-up
shows
what
we're
thinking
and
will
help
teams
better
understand
which
merge
requests,
get
hung
up
in
code
reviews.
B
So
take
a
look.
Let
us
know
what
you
think
and
contribute
in
the
issue.
Moving
on
to
the
planned
stage
in
the
plant
stage,
we
continue
to
schedule
huge
improvements
in
all
three
of
our
groups.
So
that's
the
project
management
group,
the
portfolio
management
group
and
the
certified
group
in
the
project
and
portfolio
management
groups
we'll
be
focusing
on
adding
burn
up
charts
to
the
milestone
page
burn
up.
Charts
are
really
useful
because
they
help
you
understand.
If
scope
has
been
added
during
a
miles
and
just
help,
you
manage
your
Sprint's
better.
B
Overall,
we're
also
planning
on
continuing
milestone
improvements,
as
we've
talked
about
previously,
such
as
the
ability
to
include
multiple
milestones
to
an
issue
or
merge
request
and
define
the
types
of
these
milestones
and
while
we're
on
the
topic
of
milestones,
still
we're
planning
on
adding
milestones
into
the
roadmap
view.
We
have
a
few
mock-ups
in
the
issue
description,
but
so
go
ahead
and
poke
around
and
take
a
look.
But
you
can
see
what
we're
thinking
directionally
here
with
a
milestone
row
at
the
top
and
then
milestones
as
dotted
lines.
B
So
you
can
easily
see
how
your
epics
are
going
to
line
up
with
respect
to
your
milestones
and,
lastly,
for
plan.
In
our
certified
group,
we'll
be
continuing
to
make
progress
on
our
minimum,
viable
change
for
requirements
management,
but
I
wanted
to
highlight
one
really
neat
improvement
to
the
service
desk.
That
is
something
a
lot
of
customers
have
been
asking
us
for.
B
So
let
us
know
what
you
think
in
this
issue
and
if
this
is
something
that
you're
excited
about
and
moving
on
to
the
create
stage,
the
last
of
the
dev
stages
in
the
create
stage
for
source
code
and
get
Ally,
we
have
a
ton
of
really
great
stuff
coming
out
for
source
code.
One
of
the
things
that
we're
going
to
be
adding
is
a
minimal
nerd
draft
based
diff,
so
by
default
today
and
get
live.
B
The
diff
shown
in
the
merge
request
is
the
Delta
between
the
source
branch
and
the
target
branch
at
the
time
of
the
source,
branch
was
created
when
a
merge
request
takes
a
while
to
merge
and
stays
open
for
several
weeks.
Oftentimes.
The
target
branch
such
as
master,
can
have
atomic
changes,
and
when
this
happens,
a
common
developer
workflow
is
to
merge
the
target
branch
into
your
source
branch
before
moving
merging
the
source
branch
back
into
the
target
branch.
B
Additionally,
we'll
be
adding
a
feature
to
scope,
merge
request,
approval
rules,
only
two
protected
branches.
Another
common
developer,
workflow
is
merging
feature
branch
into
feature,
branch
or
merging
the
target
branch,
such
as
master
back
into
your
feature
branch,
as
we
just
mentioned,
and
these
don't
really
require
approvals
or
shouldn't
require
approvals
all
the
time
and
so
approvals
can
sometimes
slow
developers
down.
We
don't
want
that
to
happen.
B
We've
heard
feedback
that
people
love
using
the
gitlab
web
IDE,
but
it
can
be
a
bit
blinding
because
it
uses
a
white
background
in
12:7.
The
editor
team
is
going
to
spike
into
what
it
will
take
to
have.
The
web
IDE
support
your
syntax,
highlighting
preference
that
exists
inside
of
the
git
lab,
which
will
allow
you
to
create
an
experience
that
works
for
you,
whether
you
want
a
white
background
or
something
a
little
bit
darker
too,
to
emulate
that
dark
mode.
B
Experience
that
we
all
know
and
love
and
lastly,
for
the
web,
IDE
we've
also
heard
some
feedback
that
it's
hard
to
make
a
merger
question
the
web
IDE
and
remain
in
a
contextual
experience
that
makes
sense
where
you
might
want
to
make
a
second
commit
very
easily,
so
in
12:7
we'll
be
spiking
into
some
research.
That'll
help
us
provide
the
right
experience
for
creating
a
merge
request
right
from
the
web.
Ide
there's
so
many
more
great
things
coming
to
the
dev
section
today
in
12:7,
please
take
a
look
at
the
kickoff
page.
B
C
All
DS
not
sure
I'm
not
showing
up
here
at
the
moment,
but
the
but
I'll
correct
that
later.
The
the.
What
we're,
adding,
though,
is
the
ability
to
in
communities
1.7
use
host
aliases
instead
of
EDC
hosts
for
doing
the
configuration
file.
Your
pods
will
talk
to
each
other
that
was
causing
an
issue
in
the
latest
version
of
kubernetes
recently
for
some
of
our
users,
and
so
we're
excited
to
be
able
to
deliver
that
fix.
C
The
other
thing
that
I
just
want
to
touch
on
briefly,
which
is
not
here
but
is
more
of
an
ongoing
work,
is
that
we
are
continuing
our
work
on
these
shared
runners
for
Windows
beta
that
we're
going
to
be
rolling
out
in
January.
So,
if
you're
interested
in
participating
in
that
program,
if
you're
excited
to
use
Windows
runners
with
gitlab
in
the
shared
fleet,
we
would
love
to
hear
from
you
and
it
would
be
great
to
have
your
participation
in
there
on
the
package
side.
C
The
most
important
item
that
we're
delivering
is
the
new
nougat
or
dotnet
repository.
So
nougat
is
a
very
popular
package
manager
for
dotnet
or
Windows
users,
and
so
it's
going
to
be
great
to
add
that
and
help
improve
our
overall
windows
developer
experience.
This
one
is
close
to
my
heart
because
I
cut
my
teeth,
I'm
doing
Windows
development
and
using
c-sharp
net
back
in
the
day,
so
helping
people
who
are
kind
of
like
me
and
and
I
used
to
be
is
always
one
of
the
great
things
about
being
a
product
manager.
C
So
so
that's
that's
always
nice
to
do
and
it'll
be
great
to
deliver
this
feature
on
the
release
side.
We're
focusing
heavily
on
our
do
powerful
things
theme
where
we're
trying
to
make
it
possible
to
do
things
quickly.
Do
powerful
things
without
having
to
do
a
ton
of
research
and
set
up
complicated
things
that
have
all
of
those
work
in
a
nice
way,
just
when
you're
using
get
them,
and
the
first
feature
that
I
wanted
to
turn
here.
C
Is
that
we're
adding
release
actions
and
into
the
audit
log
and
get
left?
So
if
you
create
a
release,
if
you
edit
a
release,
if
you
do
anything
with
a
release,
including
downloading
the
the
content
of
it,
that
will
be
tracked
in
the
audit
log,
so
you
can
now
work
with
your
compliance
teams
to
to
make
sure
that
any
thing
that's
happening
with
your
releases
is,
is
being
tracked
just
like
it
should
in
any
good
release
process.
C
C
What
you're
going
to
be
able
to
do
is
when
you're
editing
a
feature
flag,
you
can
connect
it
to
related
issues
that
may
have
introduced
it
or
may
have
modified
it
or
in
some
way
provide
context
to
what
that
feature
flag
does
from
the
issues
side
then
you'll
see
the
related
feature,
flags
that
are
associated
with
that
issue.
This
is
kind
of
a
pattern
that
we're
taking
with
a
lot
of
the
features
that
are
going
to
be
coming
out
within
the
release.
C
Area
related
to
the
releases
feature,
feature
flags
and
really
taking
advantage
of
the
gitlab
single
application
to
tie
these
things
together,
provide
the
context
in
the
merge
request,
provide
the
context
and
the
issue
and
really
make
it
possible,
unlike
what
any
other
application
out
there
can
do
to
give
you
all
the
information
that
you
need
when
you're
delivering
software
at
the
time
you
need
it.
So
that's
a
really
really
great
one,
and
it's
something
that
we're
going
to
be
able
to
expand
on
in
the
future
and
deliver
a
lot
more
features
like
it
and
then.
C
Finally,
another
nice
improvement
for
when
you're
setting
up
your
projects
and
trying
to
get
things
up
and
running
quickly.
Is
group
deploy
tokens,
and
what's
just
this
one
here
at
the
moment,
deploy
tokens
can
be
set
up
on
a
per
project
basis,
but
not
at
the
group
level.
This
is
a
very
popular
issue
with
160
uploads,
and
so
it's
going
to
be
really
really
nice
to
get
this
out
there.
C
It
helps
simplify
CI
configurations
and
seedy
configurations
and
just
make
it
easy
to
get
up
and
running
to
deploy
your
group
together
and,
since
groups
typically
will
might
represent
a
collection
of
related
micro
services
or
different
parts
of
a
multi-tiered
more
traditional
application.
You
know,
like
monolith,
type
application.
This
will
just
make
that
much
much
easier.
So
another
really
nice
improvement.
That
I
hope
is
going
to
make
everybody's
day
a
little
bit
better
in
the
next
year.
C
A
D
Tan
I
love
it
yeah
Jason
that
that
feature
flag.
One
is
an
awesome
example
of
kind
of
the
power
of
a
single
application
and
having
that
kind
of
context,
around
various
parts
of
your
software
development
process,
all
right
in
one
in
one
UI,
so
super
cool,
I
love
that
one
yeah
my
name
is
Kenny.
Johnston
I
am
going
to
be
covering
the
ops
section
that
includes
the
configure
and
monitor
stages.
I'll
start
in
configure,
so
our
first
one
is
a
really
cool
MVC
that
I'm
excited
about.
D
That
is
about
adding
chaos
engineering
to
your
kubernetes
cluster.
So
today
you
can
attach
a
kubernetes
cluster
to
get
lab
and
there's
a
kind
of
burgeoning
movements
to
enable
you
to
test
various
failure
scenarios
to
ensure
that
your
application
remains
resilient.
Throughout
those
failure
scenarios,
failure
scenarios
that
kubernetes
in
general
and
great
microservices
application
architecture
practices
help
you
avoid
we're
going
to
be
starting
our
NVC
in
that
process
by
adding
a
open
source
tool
called
litmus
chaos
to
the
types
of
apps
that
you
can
install
to
your
kubernetes
cluster.
D
Litmus
has
some
great
generic
chaos,
experiments
that
you
can
run
on
your
cluster,
and
so
again
it
gives
you
the
peace
of
minds
to
know
that,
when
you're
deploying
your
application
to
kubernetes
that
you're
building
in
the
types
of
resiliency
that
kubernetes
can
can
provide
you,
the
next
one
that
I
wanted
to
highlight
in
the
configure
stage
is
about
moving
our
server
list
category
to
viable.
So
server
list
is
a
new
application
architecture
paradigm
that
involves
both
service
functions
and
applications.
D
We
have
had
this
capability
in
our
minimal
maturity
State
for
about
eight
months
now
and
in
12.7
we're
going
to
be
moving
it
into
viable.
One
of
the
big
components
of
that
is
enabling
you
to
set
up
a
instance
wide
domain.
So
as
a
git
lab
administrator,
you
can
set
up
a
instance
wide
domain
that
your
users,
individual
service
applications,
will
automatically
deploy
to
so
that
they
don't
have
to
do
a
bunch
of
configuration
and
addition
of
domain
names
on
their
own
and
also
provide
instance,
wide
servlet
ssl
certificates.
D
D
The
first
is
logging,
and
so
in
logging,
we're
going
to
be
adding
the
ability
to
not
just
search
across
aggregated
logs,
but
also
filter
those
logs
and
filter
them
in
a
view
like
I'm
showing
here
on
my
screen,
but
also
allow
you
to
jump
into
a
specific
time,
slice
of
those
logs
using
this
filtering
mechanism.
Now
that
these
feel
like
pretty
minor.
But
it's
a
really
key
step
for
us
in
enabling
what
we
consider
one
of
the
primary
workflows
for
users
of
monitor,
which
we
we
call
triage.
D
So
in
our
kind
of
initial
inception
of
the
triage,
workflow
you're
reviewing
a
metric
and
you
might
get
an
alert
on
that
metric.
And
so
an
issue
has
been
created
within
get
labs
incident
management
tool.
And
then
the
key
link
here
that
is
not
provided
today
is
the
ability
to
look
at
a
metric
and
kind
of
select
a
times
period
of
that
metric.
Maybe
it's
when
the
alert,
spiked
and
automatically
drill
down
into
the
relevant
logs,
helping
you
get
to
understanding
and
triaging
a
problem
with
your
application
much
more
quickly.
D
So
I'm
really
excited
about
some
of
these
initial
steps
and
we
hope
to
get
our
minimal
support
for
this
triage
workflow
in
the
coming
releases.
The
next
big
push
in
the
monitor
stay
is
around
moving
our
error
tracking
to
Bible,
and
our
error
tracking
involves
a
deep
integration
with
the
century
application
and
in
12.7
we're
going
to
be
adding
the
ability
to
ignore
you
can
see
here
adding
ignore
and
resolve
buttons,
both
on
the
error
list
and
error.
D
Detail
pages,
as
well
as
giving
you
a
bunch,
more
contextual
information
in
the
error,
detail,
page
itself,
so
in
this
case
I'm
showing
you
an
error,
detail
page
that
has
the
tags
from
century.
So
that's
things
like
the
severity
of
the
error,
as
well
as
the
language
that
generated
there.
Also
you'll
notice
this
gitlab
commit
link
and
the
get
lab
issuing.
Those
are
great
contexts
that
allow
you
to
stay
in
your
one
single
application
and
are
another
example
of
what
Jason
kind
of
highlighted.
D
Where
we're
making
connections
across
stages
and
across
different
parts
of
the
application
that
are
only
enabled
by
a
tool
like
get
lab
and
the
last
one
is
actually
in
the
stack
trace.
It's
not
displayed
here
so
I'm
going
to
jump
to
a
different
screen
where
you
can
view
the
file
for
that
stack
trace.
D
Those
are
the
kinds
of
workflows
that
you
know
only
get
lab
can
create
by
having
this
singular
application
for
your
whole
DevOps
lifecycle.
So
I'm
really
excited
about
the
improvements
that
we're
making
to
you
know
those
who
are
asked
to
do
if
you're
asked
to
do
production
support
for
your
application,
making
your
life
easier
with
some
of
these
kind
of
deep
integrations
with
other
parts
of
gitlab.
D
The
last
thing
I
want
to
highlight
is
not
a
feature
but
I
just
want
to
call
out
and
I'm
wearing
my
Santa
hat
so
I
think
it's
appropriate
that
yesterday
we
announced
that
we
are
going
to
be
moving
the
what
we
call
our
three
pillars
of
observability,
so
metrics
logging
and
tracing
to
our
core
product.
These
have
been
in
our
page
tiers,
but
part
of
get
labs
kind
of
annual
processes
to
bride
gift
to
our
community
by
open
sourcing.
D
Some
key
components
and
I'm
really
excited
as
someone
who
passionate
about
democratizing
operations
for
everyone
about
moving
this
specific
set
of
functionality
to
not
just
enable
developers
of
our
open-source
tool
to
use
them,
but
also
encourage
contributions
so
that
we
can
kind
of
more
rapidly
improve
this
experience
for
for
anyone.
Who's
asked
asked
to
observe
and
configure
and
respond
at
the
applications
in
production,
so
happy
holidays
with
that.
I
will
pass
it
back
over
to
you.
Scott
thanks.
E
Thank
You,
Scott
and
again
happy
Holidays
to
everybody
who's
watching
the
live
stream.
To
kind
of
kick
us
off
here,
we're
gonna
dive
into
the
secure
stage,
I'll
a
know
up
front
that
there's
these
a
little
bit
later
than
we
usually
talk
about
again
due
to
the
holidays.
We
have
a
bunch
of
people
taking
some
time
to
spend
with
their
family,
which
I
think
is
really
good,
destroy
with
static
analysis.
E
I
want
to
highlight
something:
that's
been
a
long-term
goal,
supporting
air-gapped
or
fully
offline
environments
and
during
our
testing
in
the
last
several
weeks,
we've
able
to
identify
SAS
should
be
able
to
do
that
for
on-prem
and
the
next
release
so
we'll
be
documenting
what
configuration
changes
you
need
to
make
to
be
able
to
run
SAS
in
that
air,
gapped
environment,
on
the
dynamic
analysis,
side,
we're
also
looking
at
expanding
what
you
can
see
within
the
different
components.
The
first
to
highlight,
for
you
is
showing
the
list
of
resources
scanned
by
DAST.
E
Now,
when
you're
looking
at
it,
you
can
see
this
within
the
merger
quest
itself
down
here.
At
the
end,
you
can
see
here's
the
dash
results,
and
now
it's
listing
how
many
girls
were
scanned
and
you
can
click
on
view,
details
and
well.
That's
going
to
do
is
take
you
to
that
part
of
the
results.
You
can
see
the
individual
URLs
to
make
sure
your
application
is
getting
fully
tested.
E
When
we
start
talking
about
defend
last
time,
we
talked
about
some
things
that
we're
being
worked
on
for
long
term
planning
and
those
are
bringing
our
intrusion,
prevention
and
our
container
network
security
into
place.
So
we
look
at
what
we
have
here
for
12.7
those
two
items
that
we
talked
about
as
stretch
goals
or
they're
listed
and
they're
on
track
to
be
part
of
the
12.7
release,
and
the
final
item
is
focused
on
the
policies
that
will
be
applied
to
both
of
those
new
features.
E
Finally,
within
the
runtime
application
security,
we're
exposing
last
statistic:
s',
this
is
helping
us
bring
it
from
minimal
to
viable
to
kind
of
show
you
what
that
looks.
Like
our
goals,
bill
would
begin.
Generating
stats
will
help
you
decide.
Is
the
wife
working
the
way
you
want
it
to
work
and
what
are
areas
you
need
to
address?
E
And
this
is
our
step
on
the
path
to
getting
to
what
Kenny
showed
you
during
the
ops
section
being
able
to
pull
our
logs
from
the
laughs
into
that
view
that
he
showed
related
to
pods,
which
really
way
I
think
is
a
really
cool
option
that
we're
working
on
for
everybody.
What
this
would
look
like
in
the
12.7
we're
adding
a
new
sub
tab
here
off
security
and
compliance?
It's
this
threat
monitoring
and
then
within
the
UI.
E
You
can
actually
see
the
stats
that
are
happening
so
this
example
it's
in
a
block
mode,
and
you
can
see
that
about
11%
of
the
attacks
or,
let
me
show
the
traffic
blocked,
was
tagged
as
attacks
I.
Also,
like
the
pegging
see
the
total
amount
of
traffic
going
through
able
to
drill
down
in
that
in
more
detail,
whether
that's
shorter
time,
thirty
days
or
longer,
so
that
that's
it
on
the
side
for
the
security
for
secure
and
defend
I'll
hand
it
back
to
Scott.
E
F
Scott
so
for
enablement,
we
have
a
few
really
key
important
themes
that
were
working
on
this
release
and
some
really
exciting
features
within
those.
So
the
first
thing
we're
working
on
is
improving
the
performance
of
the
gitlab
server
and
we're
doing
that
in
a
couple
days.
The
first
way
is
we're
working
to
establish
posters
11
as
the
minimum
required
version
in
13.0.
F
This
will
allow
us
to
take
advantage
of
all
the
new
features
and
functions
in
PG
11
right
now,
we're
kind
of
using
9.6
as
the
baseline,
and
this
is
a
bunch
of
improvements
we
can't
realize
without
doing
something
like
multiple
code
paths
which
we
trying
to
avoid,
and
so
we're
setting
a
new
floor
here
in
PG
11
and
one
of
the
key
improvements
here.
We
can
take
advantage
of
partitioning
and
that
will
allow
us
to
increase
the
scalability
of
gitlab
as
well
as
also
improve
spawns
with
some
queries,
and
so
that's
really
exciting.
For
us.
F
Kierra
working
on
is
the
project
API
we're
working
on
shifting
from
offset
based
pagination
to
key
set
based
pagination
because,
as
you
can
see
here,
as
you
kind
of
call
for
deeper
and
deeper
pages
or
deep
into
her
offsets
the
performance
on
the
offset
based
pagination
significantly
declines,
whereas
with
key
that
pagination,
it's
a
constant
time
operation.
So
this
will
improve
the
performance
for
both
the
API
clients.
People
who
are
trying
to
actually
put
it
back
out
they'll
see
faster
results
and,
furthermore,
loss
of
a
decrease
load
and
the
gitlab
server.
F
So
it's
a
win-win
for
everyone
and
I'm
really
exciting.
Moving
on
from
the
performance
theme,
we're
also
looking
to
make
it
essentially
allow
our
customers
have
a
quicker
time
to
value
and
we're
working
on
doing
that
by
making
easier
ploy
install
gitlab
to
a
one
of
our
reference.
Architectures
and
one
of
the
key
ways
are
doing.
This
is
working
on
producting
some
of
our
terraform
scripts.
They
have
within
get
lab
so
right
now
working
on
improving
the
Gila
prisoners
that
we
have
at
then
within
distribution
and
we're
working
to
enable
Geo.
F
A
Josh
great
progress
on
a
bunch
of
fronts
I
want
to
thank
all
the
presenters
for
running
through
this.
Also
thank
the
hundreds
of
people
who
are
working
with
them
to
deliver
all
this
value.
Sure
looking
like
the
best
release
ever
to
me
before
we
before
we
depart
I,
would
ask
that
I'm
going
to
go
back
to
the
so
about
that.
Gitlab,
calm,
slash
direction,
sauce!
Kickoff!
If
you
look
here
in
the
sense,
it
says,
provide
feedback.
There's
a
link
there
to
a
survey.
A
We
would
very
much
love
to
get
feedback
on
how
this
meeting
works
for
you
and
whether
you're
getting
the
maximum
amount
of
value
out
of
this
half
an
hour.
So
if
you
could
take
a
minute
to
fill
that
out,
we'll
learn
from
it
continue
to
iterate.
Otherwise,
thank
you
so
much
for
joining
in
happy
holidays
and
we'll
see
you
in
2020
Thanks.