►
From YouTube: Release Functionality Project
A
All
right
sean,
so
a
while
back,
I
would
say,
probably
in
february
you
and
I
discussed
a
little
bit
in
slack
about
having
you
know,
a
single
place
where
all
of
our
release
features
get
instrumented
after
we
deliver
them,
and
it
would
be
a
really
great
opportunity
for
one
me
to
have
like
a
playground
to
demo
to
customers,
because
today
I
have
like
three
or
four
different
test
projects
that
they
use.
A
A
As
a
part
of
our
normal
workflow,
so
I've
created
this
issue
that
I
just
chatted
here,
which
is
just
creating
a
test
project
that
allows
us
to
demonstrate
a
couple
of
features
that
we
have
available
to
us.
So
I
think
one
creating
a
release
generation
for
mammal
project.
A
You
know
and
having
that
like
displayed
and
maybe
showcasing
a
couple
of
different
options
on
like
when
a
tag
is
created
versus
when
it's
not
that's
one
thing
to
consider
the
ball
integration
using
a
jwt
and
building
that
out
and
I'm
happy
to
one
help,
of
course
create
this
project
with
you
happy
to
assign
other
engineers
like
craz
to
do
work
in
this.
A
I
just
really
want
like
a
partner
to
help
build
out
some
of
the
more
technical
pieces
in
this
project
and
then
instrumenting
a
deploy
freeze
so
that
we
have
an
example
of
what
that
looks
like
because,
right
now
it
is
challenging
for
me
to
go
through
and
demo
a
deploy
freeze,
because
I
don't
have
like
a
cluster
set
up
anywhere
and
I
can't
show
a
customer.
B
So
does
it
should
it
be
on
gitlab.com.
A
It
can,
if
you
feel
like
it,
would
be
better
on
a
self-managed
project.
Then
we
can
do
that
as
well.
I'm
open
to
both.
B
B
So
I
totally
understand
where
you're
coming
from
in
terms
of
you
know,
there's
quite
a
lot
of
complex
features
that
require
you
know
they
require
quite
a
bit
of
setup
data
to
already
be
there
and
you
know
for
for
it
to
look
realistic.
It
should
actually
be
some
type
of
you
know.
Semi-Real
looking
releases
over
time,
not
just
kind
of
all
done
in
the
last
10
minutes.
B
So
and
in
fact
you
know,
I've
also
been
kind
of
running
into
a
kind
of
related
challenge
around
this.
Just
as
an
engineer
which
is
you
know,
we
don't
really
have
seed
data
for
many
of
our
features,
which
is
a
slightly
different
problem,
but
it
is
related.
It's
you
know
it's
well,
it's
kind
of
the
same
problem,
but
the
solution
might
be
a
bit
different
right
because
for
seed
data
I
mean
we
can
just
kind
of
like
it
can
be.
B
B
Yeah,
so
there's
a
lot
of
different
things
here
that
we
are
obviously
using
all
of
them
and
I'm
just
wondering
if
maybe
we
might
have
maybe
a
group
and
then
have
a
couple
of
different
projects.
B
So
as
because
you
know
I
find
when
I
when
I
look
at
example
code
if
everything's
in
one
place
it
becomes
confusing.
What's
what
so
you
know
we
might
work
out
how
some
of
these
features
could
easily
coexist
in?
Maybe
we'd
have
to
two
or
three
projects
or
something
that
would
you
know
like.
Maybe
the
vault
should
be
kind
of
in
his
own
world
or
whatever,
but-
and
so
I-
I
guess
the
way
I
I
I'm
thinking
about
this-
is
we're
really
looking
at
scenarios
right
like
what?
What
are
some?
B
B
And
so
I
I
feel,
if
you
know,
maybe
we
can
kind
of
map
them
out
in
the
issue
just
I
can
also
do
this
in
text.
You
know
this
is
this
type
of
organization.
B
I
think
we
can
kind
of
hack
them
out
pretty
quickly
and
then
they
can
drive
into
so
seeds
would
be
kind
of
no
brainer
from
that
and
with
with
seeds,
there's
sometimes
there's
a
bit
of
pushback
on
on
adding
seeds
to
gdk
because
they
need
to
be
maintained,
but
within
the
within
the
seed
loading
there's
different
commands
you
can
give
and
there's
kind
of
like
so
we
could
potentially
add
a
new
command
which
is
release
seeds,
and
then
you
know
we
would
solely
be
responsible
for
them,
and
so
I
think
that
would
you
know
they
can
be
optionally
loaded
by
anyone
who
wants
to
work
with
that
data
and
then
how
we
would
get
it
into.
B
I
think
gitlab.com
would
be
the
best
place
for
it.
You
know,
because
you
know
you
can
just
be
publicly
viewable
then
and
we
don't
have
to
worry
if
the
environment's
up
or
all
those
type
of
issues.
B
So
I
guess
don't
know,
maybe
we
can
consider
just
kind
of
manually.
You
know
if
we
have
kind
of
map
out
some
scenarios,
we
can
do
the
manual
setup
and
then
I
don't
know
we
could
even
have
a
script
or
something
that
would
populate
with
an
api
and
we
could
kind
of
run
that
regularly
or
whenever
you
needed
a
refresh.
You
know
we
can
run
a
little
script.
That
would
just
kind
of
fill
the
data
in
because
you
know
when
you're
giving
a
demo
right.
B
B
On
the
on
gitlab.com
through
the
api,
I
think,
but
that
would
be
you
know
no
problem.
I
think
we
should
have
access
for
everything
we
need
just
a
matter
of
writing.
You
know
some
type
of
script
or
something
perfect.
A
So
here's
what
I'll
do
from
a
next
steps
perspective.
I
will
go
ahead
and
add
several
linked
issues
to
this
release.
Functionality,
project
issue
about
examples
for
each
of
the
features
that
I'm
looking
to
instrument
and
we'll
have
use
case,
a
description
of
the
persona,
we're
trying
to
meet
and
talk
a
little
bit
about
what
organization
they're
a
part
of
and
like
what
we're
trying.
What
experience
we're
trying
to
showcase
and
I'll
do
that
for
two
of
them
and
send
them
over
to
you
to
see.
A
If
that's
enough
detail,
and
then
you
can.
B
B
A
I
I
would
love
to
do
that.
I
think
it'd
be
cool.
If
we
can,
would
we
ask
like
an
sre
about
that?
How
could
how
would
we
get
access
to
that
data.
B
Yeah
well
yeah.
I
guess
I
guess
we
would
obviously
have
to
ask
the
customer,
but
we
could
present
it
in
a
way
that
you
know
we
would
even
have
a
different
industry
or
whatever
for
that
and
why
I
asked
that
is
because
you
know
I
used
to
work
in
erp
and
I
did
a
lot
of
scenario.
Creation
work
and
we
always
started
with
an
actual
customer,
because
you
know.
B
It's
more
realistic,
yeah
yeah,
exactly
yeah,
okay.
The
challenge
here
is
not
to
take
on
too
much
detail
and
just
focus
on
that,
but
it
just
kind
of
gives
it
a
bit
more
flavor.
You
know.
A
I
like
that,
I
can
I'll
post
in
the
product
channel
about
people
who
have
experience
doing
this,
and
maybe
we
can.
We
can
see
like
what's
out
there
today,
maybe
they're,
maybe
the
the
sales
engineers
or
something
have
a
customer
that
they
already
pull
and
anonymize
it
they're.
They
could
already
be
doing
this
so
I'll
bring.
B
That
up
I
mean
we
can
certainly
start
with
gitlab
right.
You
know
as
there's
a
release
of
gitlab.com
but
it'd
be
interesting
to
look
at
some
other.
You
know
completely
different
use
cases.
B
This
is
a
cool
project.
I
like
this.
A
Bill,
I'm
so
glad
you're
we're
willing
to
to
help
out
on
it.
I
don't,
I
think
some
people
would
find
it
boring.
So
thank
you.
A
And
I
I
know
that
you,
I
added
the
ad
seed
data
issue
to
this
issue
as
like
something
for
us
to
consider
as
a
part
of
this
effort,
and
I
feel
like
that'll-
be
a
really
big
help.
If
we
can
get
that
in
there.
B
And
something
we
might
consider
you
know
more
downstream,
as
coming
out
of
this
might
be
to
add
a
couple
of
guides,
or
you
know
examples
to
to
you
know
the
gitlab
examples.
A
I
like
that,
okay
and
there's
this
other
project
called
guided
explorations.
I
don't
know
if
you've.
A
But
I've
I'm
gonna,
chat
this
issue
to
you.
So
one
of
the
essays
so
strategic
account
executives
has
this
project
which,
where
they
build
out
like
very
heavy,
lift
on
the
user
experiences
and
they
use
guided
this
idea
of
a
guided
exploration,
which
is
like
an
example
project
or
all
the
things.
A
B
A
So
all
out
of
task
here
in
this
issue
about
researching
other
examples
in
the
guided
explorations
project.
So
maybe
that'll
give
us
some
time
to
just
kind
of
like
think
through
how
other
people
are
are
considering
this,
and
then
we
can
build
out
our
scenarios
and
create
them,
create
the
projects.
A
Okay,
yeah-
I
I
scheduled
this
meeting
longer
so
that
we
could
have
some
time
like
on
our
own,
to
do
our
follow-up
actions.
So
I
think
I
wanted
to
protect
our
calendars
a
little
bit,
so
we
can
dedicate.
A
So
are
there
any
other
thoughts
or
questions
on
this
project
that
you
have.
B
No,
I
think
I
think
it's
a
great
idea,
so
what
what
time
frame
would
we
would
we
be
looking
at
doing
it?
Do
you
think
so.
A
Spend
the
next
three
milestones
chipping
away
at
this
effort.
I
think
that
would
be
my
my
hope,
yeah.
A
I
know
that
like
this
is
we
have
like
dog
fooding,
and
we
have,
of
course,
just
our
regular
future
work,
so
there's
always
competing
priorities,
but
I
feel
like
this
will
be
a
really
great
value.
Add
for
our
sales
team
it'll
help
make
that
sales
motion
cheaper,
so
I'm
just
trying
to
think
of
ways
to
build
back
our
expertise.
So
just
q3
is
kind
of
the.
B
Sure,
well,
in
fact,
yeah,
I
think
thinking
in
terms
of
like
yeah,
that's
a
good
way
to
frame
it.
Also,
it's
like
you
know.
How
could
someone
use
it
for
a
sales
demo
and
you
know
so?
How
can
you
do
a
demo
in
10
or
15
minutes
right
we've
given
some
type
of
base,
you
know,
or
maybe
you
run
a
script
or
something,
and
so
I
think
I
think
that
yeah,
it's
really.
I
don't
think
it
shouldn't
be
too
complicated.
B
I
think
most
basically,
you
know
just
kind
of
working
out
the
different
scenarios
and
then
it'll
just
be
a
matter
of
scripting
and
it
should
be
fairly
mechanical.
A
Perfect
perfect,
that's
awesome!
Well,
yay!
Thank
you
for
your
partnership.
Here
I
went
ahead
and
added
a
due
date
to
that
issue,
just
so
that
we
have
like
a
target.
A
It's
october
31st,
so
three
months
from
now,
hopefully
we'll
have
a
project
that
we
can
use
to,
so
that
I
can
confidently
go
into
like
these
ultimate
demos
and
not
do
like
my
favorite
thing
is
that
I
have
all
these
tabs
opened
up
of
like
screenshots
of
mocks
that
I'm
just
kind
of
like
hand
waving
for,
because
I
I
can't
always
show
the
features
that
I
want
to
show.
So
I
would
love
to
get.
B
B
Yeah,
in
fact,
if
we,
I
think,
if
we
focus
on
gitlab.com,
I
think
that's.
I
think
we
don't
need
to
worry
about
the
seeds,
because
we
focus
on
gitlab.com
and
we
have
some
base
kind
of
starting
point
project
or
projects
which
we
can
then
possibly
have
some
type
of
scripting.
B
I
mean
I
would
just
initially
I'm
just
thinking
about
like
a
shell
script,
but
maybe
we'll
do
something
a
bit
more
elaborate,
but
we
can
start.
You
know
with
a
shell
script
and
we
wish
you
would
then
just
give
your
api
key
to
and
then
it
would
do
everything
but
then
actually
for
the
developers
or
the
engineers.
If
it's
a
public
project,
they
can
just
import
it
straight
into
their
jdk.
A
B
A
Okay,
that's
perfect,
awesome!
Well,
we'll
definitely
be
in
touch
about
this
I'll.
Let
I'll
give
you
back
some
time,
but
thank
you
for.
B
I
love
where
release
management's
going
actually
and,
and
I'm
just
you
know,
I'm
so
glad
we've
got
environments.
Actually
I
think
environments
are
such
a
crucial
part.
B
A
Good
scope
to
like
really
make
this
like
production
deployment
path,
super
fruitful
for
our
users.
I'm
excited
all
right
I'll,
go
ahead
and.