►
From YouTube: Monthly Release Kickoff
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
Many
many
of
our
contributors
and
customers
are
scrambling
right
now
to
figure
out
how
to
work
remotely
or
leaving
offices,
and
such
this
is
something
that
gitlab
has
done
for
years.
We've
been
committed
to
an
all
remote
company
structure,
and
so
we've
learned
a
lot
as
we've
done,
that
in
a
typical
gitlab
fashion
have
written
down
how
we
work
and
a
lot
of
the
things
that
we've
learned
so
in
case
you're
in
a
situation
where
you're
trying
to
learn
how
to
do
remote
on
the
fly,
we
have
a
ton
of
helpful
resources
for
you.
A
A
So
with
that,
let's
get
back
to
the
usual
kickoff
business,
we
are
planning
for
12.10.
We
have
a
kickoff
page,
it's
about
get
lab,
comm,
slash
direction,
slash
kickoff!
If
you
would
like
to
follow
along
or
reference
the
things
we
talk
about
later.
It's
all
here,
we're
gonna,
have
four
of
our
leaders
talk
about
what
we're
doing
in
each.
What
we
call
section
a
section
is
a
grouping
of
stages
and
categories
that
we
are
working
on
and
we're
going
to
start
from
the
bottom.
This
time
and
josh
josh
is
going
to
cover
enablement.
A
A
Of
smaller
items
that
were
working
on
here
that
are
framed
up
in
issues,
if
there's
anything
in
particular
that
interests
you
here,
we
encourage
you
to
jump
in
the
issue,
provide
your
feedback,
help
us
think.
Through
these
things,
we
will
not
have
time
to
cover
each
of
these
in
depth.
So
each
of
the
section
leaders
will
talk
somatically
and
at
a
high
level
about
some
of
the
highlights.
So
with
that
I
will
stop,
sharing
and
I'll
turn
it
over
to
Josh.
C
C
Moving
on
to
distribution,
as
well
as
also
a
key
theme
of
our
tiers,
which
is
push
perez,
11
support.
We
are
making
significant
progress
here
with
the
goal
of
having
PG,
10,
plus
Rizal
10
being
knocked
out
in
1210.
This
will
mean
that
the
default
version
of
Postgres
will
be
Delta
10
for
both
new
customers
and
existing
customers.
So
if
you,
if
you
utilize
our
own
database
within
the
omnibus
package
or
on
the
helmet
chart,
we
will
upgrade
you
from
9
at
6
or
10
up
to
11.
This
is
really
key
for
us.
C
It
provides
number
1,
just
general,
across-the-board
performance
improvements
over
the
previous
versions
of
Post
Christ.
It
also
allows
us
to
take
advantage
of
some
new
features
like
partitioning
that
can
continue
to
help
us
accelerate
performance
and
increase
the
scale
of
gitlab
and
what
I
can
achieve,
and
so
we're
doing
a
lot
of
work
here
for
PG
10,
in
preparation
for
actually
removing
PG,
9,
PG,
11,
I'm,
sorry
in
9.6
and
Q
10
and
13
at
O,
and
then
lend
the
foundation
here
for
partitioning
coming
up.
C
And
so
you
can
see
we're
also
making
some
additional
kind
of
planning
support
for
auditioning
here
in
the
database
group,
so
that,
when
we're
ready
to
take
advantage
of
PG
11,
we
can
do
so
and
we're
seeing
so
that,
for
example,
some
increases
in
planning
times
when
we
can
only
utilize
partition
tables,
and
so
we're
trying
to
in
this
case,
get
a
better
handle
on
what
that
looks
like
and
how
they
can
avoid.
Those
increases.
C
Moving
on
to
our
memory
team,
another
key
objective
here
is
enabling
Puma
across
all
of
get
lab.
We're
re
running
Puma
on
get
lab.
Comm
Puma
is
a
multi-threaded
application
server,
which
offers
around
a
40
percent
reduction
in
memory
versus
our
previous
application
server
unicorn,
and
so
this
can
allow
our
customers
to
decrease
their
operational
costs
of
get
lab
or
potentially
to
just
have
an
increased
throughput
on
the
same
amount
of
machines
and
so
we're
going
through
and
addressing
some
remaining
areas.
C
We
announced
GA
support
for
Puma
in
child
at
nine,
or
both
to
be
doing
so
in
four
days
here
and
we're
going
through
addressing
a
couple,
last-minute
things
and
some
documentation
in
preparation
for
making
Puma
opt
out,
and
the
default
in
13.0
here
so
definitely
check
it
out
and
give
it
a
try,
we're
seeing
great
performance
here
and
calm.
We
want
to
bring
that
to
everyone
and
those
savings,
a
efficiency
improvements
for
all
our
Gil
abusers,
also
in
the
database
team
or
memory
team.
C
Here
we
are
also
working
to
try
to
help
improve
the
develop
practices
of
gitlab
and
so
we're
adding
some
Robocop's
for
particular
kind
of
degenerate,
use
cases
or
inefficient
programming
models
and
hoping
to
solve
those
before
they
even
get
into
code
base
at
all.
For
example,
something
as
simple
as
what
iterator
you
choose
can
have
some
significant
performance
impacts.
For
example,
each
with
index
is
30%
slower
than
the
simple
index
based
array,
and
so
this
will
help
to
provide
higher
code
quality
and
better
performance
across
gitlab
for
all
of
our
customers
and
users.
C
And
the
final
item
here
out
of
our
memory
team
is
you
want
to
make
plan
limits?
This
is
our
application
limits
for
gitlab,
where
we've
been
going
through
and
adding
some
limits
so
that,
if
you
have
unintentional
or
potentially
intentional
abuse,
these
can
be
stopped
and
right
now
we're
running
this
in
get
lab
comm.
C
We
have
it
around
to
a
few
percentage
of
our
current
paid
groups
today
and
we
are
executing
towards
10%
or
more
coverage
in
this
release
in
1210
and
we're
well
on
our
way
there,
and
so
we're
very
comfortable
about
hitting
that
milestone
in
this
release,
and
so
we
have
a
couple
items
we're
doing
here
to
just
continue
to
improve
with
things
like
zero
downtime.
You
re
in
dexing
and
increase
in
this
ability
of
our
pipeline,
but
overall,
that's
the
main
objective,
which
is
just
increase
this
coverage.
B
Okay,
so
to
kind
of
kick
us
off
here,
I
first
wanted
to
let
you
know
there
were
a
couple
shifting
around
of
what
our
focuses
are
and
so
as
a
high-level
goal.
Our
first
objective
for
the
year
is
air
gap.
Support
within
secure
and
you'll
see
that
trickled
through
the
update
related
to
the
secure
stage.
We
also
want
to
become
an
application
security
testing
leader
and
so
there'll
be
some
items
around
that
as
well
as
we
go
through
this
conversation.
B
So
first
for
the
stack
analysis
group,
the
main
thing
I
wanted
to
highlight,
for
you
is
our
support
for
the.net
framework,
so
SAS
will
be
extended
and
we're
on
track
to
have
that
as
a
highlighted
item
for
1210,
and
if
you
want
to
read
more
about
that,
you
can
go
and
look
at
the
issue.
You
can
also
go
in
and
comment
if
you
have
any
questions
and
the
product
team
will
respond
to
you
next
from
dynamic
analysis.
B
B
The
one
I
wanted
to
highlight
for
you
is
showing
the
list
of
URLs,
so
that's
available
today
in
the
console
view,
but
this
will
be
bringing
it
into
the
UI
where
you
can
begin
to
see
what
the
desk
scanner
found
and
you
then
can
adjust
your
scan
accordingly,
if
it's
missing
some
paths
to
test
the
other
item,
that
I
think
it's
pretty
exciting
is
on
the
schema
on
the
group
level.
Dashboard
we're
adding
in
tracking
of
when
the
last
curie
test
was
run.
B
This
is
allowing
you
to
understand
where
you
are
missing
coverage
on
your
testing
and
here's
a
screenshot
of
what
is
coming
out,
so
you
can
see
at
the
top.
This
is
the
dashboard
here
and
on
the
right
side,
we've
added
a
project
scanning
area
and
the
first
area
is
showing
how
long
it's
been
since
certain
projects
have
been
scanned
and
then
you
can
also
still
see
the
list
of
things
that
have
not
yet
been
tested.
B
Multiple
containers
at
once
so
scan
multiple
containers,
as
opposed
to
needing
to
do
that
as
different
jobs
itself.
On
the
defense
side,
we
did
reconsolidate
some
of
the
teams
down,
so
the
team
names
will
be
new
on
this
call
on
both
Sam
and
Matt
in
their
individual
videos.
They
hacked
I
recommend
you
watch.
They
did
a
very
good
job
of
explaining
the
details
of
that.
But
the
first
is
the
threat
insights
group.
B
This
is
the
taking
the
threat
management
group
and
extending
what
they're
focused
on,
and
this
is
really
focused
on
the
the
view
of
your
security,
whether
that
is
the
dashboards
and
the
first
class
vulnerabilities.
We've
been
talking
about
a
user
and
entity
behavior
analytics
or
you
EBA
of
your
kit
lab
instance,
as
well
as
our
new
functionality.
Later
this
year,
focused
on
responsible
disclosure
and
helping
you
get
cv
IDs
and
report
vulnerabilities
in
your
own
application
for
this
release
for
1210.
B
That
third
insights
team
is
very
much
focused
on
finishing
up
the
NB
c--
for
the
first
class
vulnerabilities
with
that
will
begin
to
allow
extension
of
what
we
can
report
on,
including
things
like
exporting
reports
into
your
own
template
and
other
historical
here
are
six
based
reporting
for
the
container
security
group.
This
is
the
combination
of
application,
infrastructure,
security
and
runtime
application
security,
they're
heavily
focused
on
what
you
can
add
to
your
environment,
to
protect
yourself.
B
The
first
thing
I
was
the
web
application
farlow,
which
we've
been
talking
about
since
last
year,
container
network
security
just
went
out
as
minimal
in
the
last
release,
that's
also
very
exciting
and
then
later
in
the
air
they're
focused
on
behavioral
monitoring
within
your
container.
The
one
thing
I
want
to
highlight,
for
you
is
being
able
to
see
the
logs
outside
of
the
container,
and
so
we've
added
the
ability
to
send
logs
to
an
external
log
collector.
You
can
see
off
the
settings
you
can
get
in
and
configure
your
seam
settings
and
then
down
here.
B
You
can
enter
in
the
information,
and
this
is
gonna
work
for
both
the
waveform
security
and
psyllium
or
container
network
security
offering,
but
lots
of
more
exciting
things
are
coming
with
the
fund.
We
can
talk
about
those
in
future
calls,
but
with
that
I'll
hand
it
back
over
to
Scott
to
move
on
to
Kenny
thanks.
D
Here
we
go:
okay,
all
right
yeah,
my
name
is
Kenny.
Johnson
I
will
be
covering
the
ops
section.
We
recently
think
of
it
as
a
recombination,
but
the
knob
section
now
includes
to
verify
package
release,
configure
and
monitor
stages.
I'll
admit
that
I'm
fairly
new
to
some
of
this
scope,
so
I
would
highly
encourage
you
to
look
to
the
experts
and
the
videos
that
have
been
recorded
by
the
teams
to
get
a
lot
of
this
detail.
D
I
have
spent
some
time,
ramping
up
and
so
I
have
been
thinking
about
a
number
of
the
issues
that
we
are,
including
in
this
section
in
terms
of
themes
and
so
I'll
go
through
them
by
themes
and
they'll
kind
of
jump
around
between
different
groups.
The
first
primary
theme
that
I
spotted
was
just
get
lab,
adding
support
for
new
application
types,
and
so
you
can
see
that
in
examples
like
the
runner
team
working
on
support
for
new
and
updated
Windows
Server
the
ability
for
the
runner
to
work
on
new
and
updated
Windows
servers.
D
You
can
see
that
in
our
support
for
pi
PI
repositories,
so
you
can
expand
the
usage
of
gitlab
when
you're
working
in
python
to
to
our
package
stage.
You
can
see
that
in
our
this
issue
is
about
adding
vault
support,
so
if
you've
got
applications
that
require
retrieving
secrets
from
vault.
This
allows
you
to
use
a
JSON
web
token
to
authenticate
with
vault
in
your
CI
jobs
and
fetch
those
fetch,
those
vault
secrets
and
return
them.
So
your
CI
job
can
complete.
D
Another
core
theme
is
about
expanding
the
breadth
of
our
usage,
so
this
is
about
current
users
of
get
lab
using
additional
stages.
We
believe
in
the
single
application
and
we're
trying
to
encourage
the
support,
encourage
the
usage
of
these
other
stages,
with
your
current
typically,
customers
start
with
source
control,
so
they're
about
expanding
on
source
control.
The
first
is
really
about
getting
helping
users
adopt
gitlab,
CI
and
today
lots
of
folks
are
coming
from
Jenkins
and
it's
difficult
to
quickly
migrate
between
Jenkins
and
get
lab.
D
There
are
different
parameters
and
paradigms
for
how
you
should
construct
your
pipelines,
so
we're
going
to
be
adding
this
ability
to
run
a
to
execute
Jenkins
within
your
git
lab
CI
jobs.
It's
kind
of
you
can
think
of
it
as
a
wrapper
around
get
or
Jenkins
jobs
within
get
lab.
We
think
that
that
will
be
helpful
and
by
that
and
a
significant
amount
of
documentation
around
just
how
to
do
that
and
how
to
migrate
between
Jenkins
and
get
lamp
see.
D
I
will
speed
that
process
along
for
users
who
are
beginning
their
journey
to
get
lap
CI.
The
next
is
about
adding
the
ability
to
do
to
have
the
results
of
your
accessibility
scans
directly
in
the
merge
request,
widget,
and
so
when
you're.
Looking
at
your
merge
requests,
you
can
see
this
in
this
design.
You
would
get
the
results
of
accessibility
scan
right
here
in
your
merge
request.
D
The
next
is
and
issues
about
our
progressive
delivery.
So
today
you
can,
and
many
users
do
use
get
lab
for
Bluegreen
deployments,
but
it's
not
well
documented.
So
we
think
a
first
step
here
is
to
make
sure
users
are
well
aware
and
can
easily
set
up
through
documentation,
CI
pipelines
that
allow
this
kind
of
blue-green
deployments.
D
Next,
we'll
be
working
on
this,
the
usage
of
the
release
stage
and
the
ability
to
edit
your
release,
content
and
the
milestones
associated
with
the
release
directly
in
the
edit
page.
Today.
That
can
only
be
done
when
you
originally
create
the
release,
and
so
we're
adding
this
improved
capability.
So
more
users
will
adopt
our
released
stage
features.
D
Next,
we'll
be
working
on
converting
so
get
lab
is
if
you're
familiar
dashboards
that
get
lab.
Comm
has
a
whole
host
of
the
dashboards
that
get
lab
uses
to
support
our
production,
get
lab
comm
instance
and
we'll
be
converting
one
of
these
dashboard
charts.
The
kind
of
triage
dashboard
chart
that
that
team
uses
to
get
lab
dashboards
that
are
in
the
monitor
stage.
This
important
component
of
dog
fooding
for
us
will
also
showcase
to
our
users
that
these
that
are
dashboarding
capability
directly
within
the
gate.
Lab
UI
is
ready
for
primetime.
D
The
next
is,
if
you're,
a
user
of
gitlab
dashboard
charts
you've
seen
that
we
automatically
add
this
annotation
anytime
there's
a
deployment
which
is
a
great
example
of
our
kind
of
single
application.
We
know
when
deployments
happen,
and
we
can
showcase
that,
on
appropriate
dashboards,
we're
going
to
be
adding
the
ability
to
add
custom
custom
annotations.
D
So,
instead
of
a
deploy
icon,
you
get
these
kind
of
custom
icons
and
you
can
add
the
text
that
you'd
like
to
your
metrics
charts,
we'll
also
be
adding
expanding
on
our
ability
to
on
our
recent
addition
of
the
log
explore
by
adding
the
ability
to
filter
that
those
logs
and
search
within
those
logs.
So
that's
here
and
then
something
I'm
particularly
excited
about
get
lab
comes
with
our
metrics
capabilities,
come
with
a
set
of
out-of-the-box
charts
for
things
like
nginx,
so
that's
the
the
service
response
time
and
error
rate.
D
Typically,
you
get
from
nginx
of
your
application
when
deployed,
we
want
to
expose
the
ability
to
set
up
alerts
in
respond
to
those
alerts
to
more
users,
and
so
we'll
be
adding
kind
of
out-of-the-box
alerts
set
up
to
auto
dev
ops.
The
next
theme
that
I
wanted
to
highlight,
so
the
first
themes
were
adding
more
application
types
and
the
next
one
was
about
adding
Bret.
This
is
really
about
showcasing
new
users
to
new
experiences,
whether
that's
with
a
specific
application
type
or
a
new
stage
that
their
application
is
going
to
be
using
within
get
lab.
D
The
next
theme
is
really
about
efficiency
for
those
who
are
already
using
so
and
I've
noticed
within
the
verified
package
and
release
stage,
there's
a
lot
of
focus
on
making
sure
that
we
do
things
fast,
that
we
really
want
to
make
sure
our
users
are
are
efficient
in
their
usage
of
our
tool.
So
the
first
one
is
about
ensuring
that
when
you
add
an
after
script-
and
you
cancel
a
job
that
that
after
skip
still
runs,
it's
the
expected
behavior
of
many
users.
D
So
we're
going
to
be
adding
that
within
the
runner
team,
the
next
is
adding
support
for
AWS,
Fargate
and
auto
scaling
CI.
This
allows
our
users
to
not
have
to
manage
a
bunch
of
different
CI,
a
bunch
of
different
runner
groups,
and
they
can
they
can
easily
connect
to
their
AWS
Fargate
account
and
know
that
there
are
CI
jobs
will
kind
of
scale
automatically
for
them.
D
The
next
is
to
run
tests
when
you're
in
your
CI
jobs
on
the
new
files
first.
So
this
is
important
because,
instead
of
having
to
wait
for
the
entire
test
to
run
including
tests
on
on
changes
that
weren't
on
code
that
wasn't
changed
in
this
in
the
commits
that
you're
testing,
you
can
get
the
results
of
those
files
that
were
changed
quickly
to
speed
up
the
feedback.
Loop
next,
we'll
be
adding
the
ability
to
purge
your
dependency
proxy.
D
So
the
dependency
proxy
is
a
really
useful
tool
for
users
who
are
using
get
lab
package
staged
features
to
not
have
to
continually
retrieve
various
artifacts
from
get
lab
services,
so
you
can
cache
specific
images,
for
instance,
or
packages
so
that
they
are
available.
This
is
this
allows
users
to
purge
that
if
they
want
to
kind
of
force
the
reset
of
their
cache,
we're
also
adding
a
couple
of
just
UX
improvements
to
enhance
the
efficiency
of
using
the
features
in
the
package
repository
in
the
package
stage.
D
The
first
is
ability
to
filter
package
in
the
package
list
in
your
package
registry
by
things
like
package
name
and
the
other
is.
Let
me
see
if
I
can
get
this
yeah
when
you're
when
you're.
Looking
at
your
registry,
there
is
no
quick
link
to
how
to
build
an
image
or
push
an
image
to
that
registry.
It
is
available
when
you
first
create
it
and
there's
nothing
in
the
repository,
but
not
after
that.
So
this
keeps
that
top
of
mind
for
any
user.
D
Looking
at
the
registry
and
then
next
in
the
release
stage,
when
you're,
when
we
when
you've
setup,
merge
trains,
we
still
had
this
quick
action
for
a
slash,
merge,
and
that
was
not
necessarily
clear
what
was
going
to
happen
if
you
did
a
slash,
merge,
quick
action.
If
merge
trains
were
set
up
or
if
the
pipeline's
were
had
succeeded
or
not
this
improved
UI,
so
that
you
know
when
you
are
using
the
slash,
merge
action.
D
What
action
that
that
is
going
to
take
there's
an
example
of
the
preview
of
that
and
then
the
next
two
are
in
from
the
monitor
stage.
The
first
is
ability
to
automatically
add
the
chart
for
the
metrics
that
was
triggered
when
an
incident
issue
is
triggered.
This
makes
it
so
that
you
don't
have
to
go,
look
at
a
chart
and
then
paste
back
in
the
chart
link
it's
automatically.
They
are
right.
D
A
E
Thanks
so
much
Scott,
my
name
is
Eric
Brinkman
I'm,
the
product
director
for
the
Dead
section,
and
the
dev
section
is
the
first
three
stages
of
the
DevOps
lifecycle.
So
it
includes
the
manage
plan
and
create
stages.
I'm
gonna
go
ahead
and
share
my
screen
and
walk
through
each
of
those
stages
quickly.
As
a
as
a
reminder,
the
dev
section
has
16
groups
and
so
I'm
not
able
to
talk
about
each
of
the
groups
today,
just
due
to
time.
E
So
please
go
ahead
and
check
out
that
kick-off
page
that
Scott
mentioned,
and
each
of
the
groups
did
record
a
video
and
they're
all
doing
some
amazing
work,
and
so,
if
I
don't
highlight
them,
it's
not
because
I
don't
want
to
it's
just.
We
don't
have
time
to
do
it
today,
but
please
do
check
out
those
videos
and
some
of
the
items
that
those
teams
are
releasing.
E
E
But
it
doesn't
work
great
in
highly
regulated
environments
or
where
environments,
where
you're
employing
a
least
privileged
methodology,
where
you
need
people
to
really
be
isolated
and
have
very
specific
access,
and
so
we're
going
to
provide
an
optional
toggle
to
disable
group
membership
inheritance,
which
will
happen
at
the
top-level
group.
And
so
you
can
set
this
at
the
top-level
group
and
then
a
sub
group
you
make
below
that
will
not
inherit
group
group
membership.
E
E
The
second
group
membership
item
is
extending
group
managed
accounts
to
all
groups,
and
so
in
12:1
we
introduced
the
concept
of
a
group
managed
account
which
works
great
if
you're
using
sam'l
SSO,
and
it
allows
you
to
basically
say
you
have
to
be
using
this
user
in
this
group,
and
you
can't
do
anything
else
outside
of
the
group.
That's
great
if
you
want
a
whole
bunch
of
control
and
isolation,
but
we
see
no
reason
to
limit
this
if
you're,
just
using
sam'l
SSO.
E
We
have
a
very
robust
issue
framework
and
so
we're
going
to
release
an
NBC,
that's
going
to
allow
you
to
very
quickly
generate
all
the
issues
that
you
would
need
to
prove
a
HIPAA
audit
protocol
right
inside
of
get
labs.
So
if
you
create
a
project
template
based
off
of
this
based
off
of
this
template,
then
you'll
will
generate
all
the
issues
that
you
need
to
essentially
prove
to
an
auditor
that
you
are.
You
know
passing
your
or
HIPAA
out
of
it.
Now.
E
Moving
on
to
the
plan
stage,
we
have
one
big
theme
in
plan,
which
is
the
JIRA
importer
and
and
so
we're
going
to
be,
releasing
a
minimum,
viable
change
for
our
JIRA
importer,
which
will
bring
over
JIRA
issue
summaries
and
bring
those
in
to
get
live.
Issue.
Titles
and
then
JIRA
issue
descriptions
and
bring
those
into
key
5
issue
descriptions.
E
And
this
is
really
important,
because
when
we
see
people
adopt
to
get
lob,
they
start
with
source
code
management
in
CI,
and
then
they
realize
we
have
all
this
other
great
functionality
to
the
left
and
right
of
those
stages.
And
so
can
I
talk
about
Kenny
and
David
talked
about
some
of
our
monitoring
and
security
features,
but
to
the
left
of
source
code
management.
We
also
have
issue
tracking.
E
We
have
a
whole
bunch
of
great
features
like
issue
tracking
and
epics
and
roadmaps,
and
you
can
do
all
sorts
of
product
and
project
management
work
right
inside
of
gate
lab,
and
we
want
those
customers
of
ours
that
realize
that
hey.
You
can
just
consolidate
all
these
use
cases
into
one
application
to
very
easily
migrate
from
other
tools,
and
the
first
of
those
is
obviously
JIRA
which
has
the
most
market
share
of
any
project
or
portfolio
management
tool
on
the
market.
E
So
we
delivering
our
nbc4
JIRA
importer
in
1210,
which
is
very
exciting
and
then
of
course,
following
on
with
other
features
to
pull
in
other
required
data
elements
that
some
customers
may
need
to
bring
over
from
JIRA
as
well,
and
one
other
cool
feature
that
I
think
I
wanted
to
highlight.
Really
quickly
is
that
you
can
have
confidential
issues
today
inside
of
gate
lon,
but
you
can't
have
confidential
epics
and
so
we're
going
to
allow
the
confidential
toggle
to
be
set
on
epics.
E
So
this
is
both
for
new
epics
as
well
as
epics
that
already
exist,
so
pretty
exciting
functionality
there
and
then
moving
into
our
home
stretch
our
create
stage.
We've
got
really
three
big
themes
and
they
really
shouldn't
be
too
surprising.
The
first
theme
is
obviously
guilty
for,
like
Gil
tha,
which
is
Gilly
high-availability.
We
have
a
theme
on
multi-line
comments
and
another
theme
on
static
site,
editing
and
so
we'll
go
ahead
and
start
with
multi-line
comments.
E
E
You
can
comment
on
a
single
line
in
a
in
a
diff
if
you're
do,
if
you're
walking
through
some
sort
of
some
sort
of
code
review
process,
but
a
single
line
isn't
always
necessary,
isn't
always
adequate
because
you
might
have
a
function
or
a
block
of
logic
that
you
want
to
have
a
comment
that
applies
to
that
entire
line,
and
so
we're
going
to
release
an
NBC
in
1210.
That
will
focus
on
multi-line
murdered
across
comments.
E
So
really
really
exciting
that
to
bring
us
up
to
a
feature
that
really
a
lot
of
developers
really
do
need
as
they're
working
through
code
review,
and
then
we
recently
created
a
new
group
and
create
called
a
static
site.
Editing
group
and
this
group
has
been
one
that's
been
performing
over
the
past
few
months
and
is
now
ready
to
start
delivering
features
into
the
product,
and
so
we've
been
thinking
about.
E
How
do
we
deliver
a
static
site,
editing
experience
inside
of
gitlab,
and
if
you
look,
if
you
think
about
that
on
as
a
as
a
huge
feature
inside
you
get
lab,
it's
it's
a
little
bit
daunting
to
think
about.
Do
we
have
to
build
authentication
systems?
Are
we
building
an
entire
CMS,
but
we
took
a
step
back
in
a
typical,
get
lab
fashion.
We're
going
to
deliver
a
very
pared
back
MVC
to
get
us
started
to
take
that
first
step
on
the
static
site,
editing
journey
and
how
we're
going
to
do.
E
This
is
we're
going
to
provide
functionality
to
edit
a
single
middleman
page
using
a
very
specific
and
simplified
markdown
editor,
and
so
it's
going
to
be
a
very
scoped
that
will
obviously
be
extended
over
time
and
the
reason
we're
starting
with
middleman
is
because
the
gait
lab
handbook
is
written
and
served
via
middleman,
and
so
obviously
dog
fooding
I
get
love
is
very
important.
We
want
to
make
sure
that
whatever
we're
developing
is
getting
used
because
the
more
people
that
use
it
the
better
that
it's
going
to
be
over
the
long
term.
E
So
our
hope
is
that
we
can.
We
can
develop
this
static
sight,
editing,
experience,
dog
food
it
and
improve
it
very,
very
quickly
and,
of
course,
support
up
there
frameworks
in
the
future,
but
a
really
excited
to
see
the
first
iteration
here
on
static
site,
editing
and
then
the
last
thing
that
I
just
went
out
highlights
is
our
continued
work
on
a
che
Italy
and
so
in
twelve
nine.
E
We
released
our
alpha
version
of
of
HTA
Italy
or
we're
going
to
release
our
off
of
version
of
hig
delete
here
in
another
four
days
and
then
in
1210
we'll
continue
building
on
the
functionality
to
make
it
more
robust
and
marching
towards
our
general
availability
for
I
availability
get
with
inside
of
gate
lab.
So
that's
it
for
the
Deaf
section
and
back
to
you,
Scott.
Alright,.
A
Thank
you
to
each
of
the
presenters
and
all
the
teams
and
contributors
behind
it.
This
certainly
looks
like
it's
gonna,
be
the
best
release
ever
and
to
all
who
joined
us
on
this
call.
Thank
you
for
your
time.
I
forgot
the
usual
disclaimer
that
we
do
plan
ambitiously,
so
the
things
we
presented
today.
This
is
what
we're
aiming
for
in
twelve
ten.
However,
things
can
and
will
change.
So
please
don't
be
this
as
a
promise
and
otherwise
stay
safe
out
there
and
we'll
see
you
next
month.
Thank
you.