►
From YouTube: How to use What is New Since
Description
What is new since is a tool that aggregates all historical releases of GitLab to show off changes.
https://gitlab-com.gitlab.io/cs-tools/gitlab-cs-tools/what-is-new-since/?tab=features
and our GitLab Stages (and their respective categories)
https://about.gitlab.com/stages-devops-lifecycle/
A
All
right,
hey
everyone,
Peter
and
myself,
Tim
hoffenberger
are
here
and
we're
gonna
talk
about
a
tool
called
what
is
nuisance.
It's
a
release,
overview
tool
of
gitlab
and
essentially
the
the
Crux
of
what
this
does
is
the
static
website
page
and
every
single
month
after
gitlab
releases
on
the
22nd.
We
have
a
CI
job
that
scours
all
of
the
historical
releases
pulls
that
pulls
together
that
information
Aggregates
it,
and
then
we
create
this
visualized
illustration
of
all
the
things
that
are
going
on
in
our
product
Peter
had
asked.
A
B
So
my
thinking
is,
if
I'm
speaking
to
a
customer
for
the
first
time,
I.E
they've,
just
onboarded
into
gitlab
and
it's
the
introductory
call,
or
they
better
get
my
customer
for
a
couple
years
and
I've
just
inherited
the
account
their
view
of
me
as
an
AE
is.
Where
are
you
going
to
add
any
value
to
me
and
my
thinking
here
is
what
information
can
we
provide
to
an
account
executive
that
can
immediately
seem
like
we
have
value
which
isn't
just
commercially
focused,
it's
actually
in
product
adoption
or
tier
understanding,
or
anything
of
that
nature.
A
Yeah,
that's
a
that's
a
great
great
question,
so
this
is
organized
by
releases,
so
you
can
actually
see
so.
Let's
say
that
a
customer,
you
you
talk
with
a
customer
and
you
ask
them
the
question
or
you
look
in
Salesforce
and
you
recognize
that
they're
still
on.
Like
version
you
know
13.4,
so
we
can
go
through
and
pull
up
and
say
13.4
and
they
communicate
hey.
We've
had
a
real
hard
time
with
kubernetes.
A
There's
a
couple
different
things
that
you
could
be
doing
here.
You
could
just
do
a
quick
search
for
kubernetes
and
and
have
a
list
of
all
the
things
between
so
83
items,
83
changes
that
have
happened
between
13.4
and
15.3
that
are
related
to
kubernetes.
Now,
that's
a
lot
of
changes,
so
maybe
we
would
want
to
even
scope
that
down
even
further.
Maybe
they
care
about
future
Flags
so
being
able
to
like
search
for
Feature
Feature
Flags
might
be
the
the
right
thing,
so
we
have
26
items
there.
A
All
of
this
is
structured,
so
you
can
see
that
there
are
stages
and
categories
when
we
think
about
gitlab
as
a
whole.
We
organize
ourselves
into
the
the
10
devops
stages.
Protect
is
going
to
be
renamed
to
on
another
stage
pretty
soon,
but
we
have
these
10
Dev
app
stages
and
if
we
drill
into
like
create,
for
example,
and
click,
learn
more,
you
can
actually
see
subcategories
here.
A
So,
if
you're
ever
interested
in
understanding
like
okay,
what
are
a
part
of
these
that
that
would
be
able
to
be
a
good
thing
to
show.
So
here
we
can
actually
see
Wiki
is
here,
so
let's
go
ahead
and
just
search
on
Wiki
and
I
can
see.
So
now
we're
actually
going
to
limit
and
we're
only
going
to
show
things
that
are
about
the
wiki
between
13.4
and
15.3.
A
So
these
are
progressively
Advanced
so
and
if
they're,
maybe
looking
at
ultimate,
we
could
see
if
there's
any
capabilities
that
are
related
to
the
wiki
that
are
only
available
in
Ultimate.
So
because
I
was
able
to
set
that
minimum
tier,
and
you
can
see
that
there's
nothing
there.
But
if
we
were
to
potentially
look
at
like
alert,
management,
I
might
be
able
to
see
or
if
I
want,
to
take
a
step
back
and
actually
look
more
at
like
the
the
manage
stage.
A
So
so
one
one
Gap
here,
this
number
will
always
automatically
update.
Sometimes
the
application
doesn't
filter
appropriately,
but
the
URL
is
actually
updated
correctly.
So
if
you
refresh
you'll,
actually
see
those
42
features.
A
So
if
you
ever
have
a
problem,
that's
that's
the
issue
there
so
keep
an
eye
when
you're
filtering
playing
around
with
filters
that
that,
if
you
see
this
number
and
you're
not
seeing
any
results,
that's
why
so
being
able
to
go
into
here
and
filter
on
like
the
most
recent
features
or
if
you
know,
there's
something
that
they
really
care
about.
Being
able
to
scope
to
that
thing
as
well
as
to
maybe
just
the
ultimate
tier
would
significantly
help.
A
Overall,
it's
really
nice
to
be
able
to
show
them
this.
This
is
showing
you
a
graph
of
all
the
changes
that
are
going
on
across
the
the
the
organization,
but
if
you
actually
want
you
can
you
can
look
over
here
and
click
on
manage
and
what
this
is
going
to
do?
Is
it's
going
to
show
you
all
the
changes
just
specific
to
manage
that
are
being
rolled
out
or
I?
A
Can
click
on
verify
like
so
this
is
progressively
adding
so
if
I
know
that
they
care
about,
you
know
like
create,
manage
verify
and
secure
I
can
show
them
hey.
Here
are
the
ways
that
we're
we're
building
that
stuff
out.
Alternatively,
you
could
filter
that
by
the
features
by
version
and
be
able
to
show
those
same
exact
features.
It's
the
same
data
set.
This
is
just
rolling
it
up
in
an
aggregate.
It's
not
clickable
in
terms
of
actually
seeing
those
issues.
B
A
A
visual
representation,
but
the
the
same
data
is
over
here.
So
if
I
wanted
to
like,
let's
say
I
wanted
to
see
features
by
version
and
I
wanted
so
verify
and
secure
and
ecosystem.
So
this
is
the
same
kind
of
filter
that
I
was
having
over
there
now
I'm
gonna
see
all
those
features
in
this
list
here.
B
So
if
I'm
going
to
count
executive,
if
I'm
speaking
to
a
customer
for
the
first
time,
I'm
asking
them
questions
about
what
parts
of
gitlab
they're
using
and
what
they
could
adopt
next,
my
question
two
then
could
be.
What
version
are
you
on
today
versus
what
version
do
you
want
to
get
to
and
actually
then
you
can
narrow
down
areas
that
you
can
make
suggestions
so
Tim,
unfortunately,
you're
on
9.2,
it
looks
like
you've
not
been
doing
anything
for
a
while,
but
if
you're
looking
to
improve.
B
So
these
are
some
of
the
features
that
verify
run
a
fleet,
the
license,
compliance
that
you
could
get
access
to,
and
it
becomes
a
a
reaction
to
a
problem
that
they
may
have
that
you've
discussed
in
a
in
an
ask
me
anything
or
an
essay
has
been
involved
or
actually
they've
identified,
that
a
feature
could
be
available
of
interest
for
them,
and
you
can
use
this
as
a
point
of
interest
to
learn
a
little
bit
more
about
it.
Would
that
be
a
good
overview?
Yeah.
A
And
oftentimes
like
when,
so,
if
you,
if
they're
like
you
know,
I
I,
am
on
13.4
I'd
love
to
be
able
to
upgrade,
but
it
just
sounds
like
a
really
daunting
task.
We
have
this
button
here.
You
can't
just
go
from
13.4
to
15.3,
that's
not
even
possible,
you
have
to
upgrade
incrementally,
but
we
do
have
fastest
paths.
So
this
this
page
here
is
dedicated
to
allowing
you
to
you.
Do
like
13.4.7,
Enterprise
Edition
on
Ubuntu,
let's
go
ahead
and
say:
Auto
install
and
no
downtime.
A
This
is
going
to
generate
the
list
of
commands
that
you
need
to
run
in
order
to
get
your
system
upgraded.
So
it's
still,
you
know
quite
a
bit
of
commands,
but
at
the
same
time
it
allows
the
customer
to
to
know
the
clear
path
to
upgrade,
because
it
is
a
little
bit
daunting,
knowing
that
I'm
going
to
have
to
upgrade
all
of
these
to
all.
A
Gitlab
releases
on
the
22nd
of
every
single
month
and
when
I
used
to
manage
the
team
that
I
we
would
upgrade
on
a
weekly
basis.
Our
gitlab
instance
wow
at
any
given
point
in
time.
There
might
be
a
security
vulnerability
and
we
want
to
make
sure
that
we're
we're
kind
of
always
up
to
date.
A
B
Great
question
from
an
AE
to
a
customer
is:
what's
your
upgrade
schedule?
Are
you
aware
of
the
upgrade
path
to
take
advantage
of
the
latest
feature
releases?
That's
one
aspect
of
value
that
you
could
provide.
Second,
is
if
you're
on
a
previous
version
and
you're,
potentially
looking
to
move
to
a
future
version.
These
are
some
of
the
newest
capabilities
that
exist
in
that
Gap.
B
That
could
be
a
reaction
to
a
customer
problem
or
the
AE
trying
to
encourage
the
customer
to
go
down
a
specific
route,
namely
up
tiering
or
taking
advantage
of
more
of
the
stages
that
they're
not
currently
taking
advantage
of
yeah
and
it's
their
content
here
so
I'm
the
customer
and
we're
chatting
away.
Is
there
content
here
that
you
could
send
to
me
as
the
customer
that
would
allow
me
to
visually,
read
a
little
bit
more
about
what
is
on
offer
from
all
of
these
different
features?
Yeah.
A
So
one
anytime,
you
make
updates
here
it
automatically
populates.
This
is
available
to
all
of
our
customers,
so
if
I
log
in
to
gitlab
I'm
not
authenticated
into
gitlab
right
now,
this
is
available
to
everyone
in
the
world.
A
B
And
I'm,
looking
at
a
set
of
20
accounts,
10
accounts
and
thinking
right
I
want
to
look
at.
They
gain
site
scores
I'm
in
Salesforce,
they're
green.
Maybe
they
are
yellow,
so
they're,
a
healthy
user
of
gitlab.
How
could
I
use
this
tool
to
understand
some
of
the
value
of
how
I
can
approach
an
ultimate
conversation
with
them?.
A
Yeah,
so
if
they're
green,
you
know
oftentimes,
we
talk
about
our
adoption
path,
going
from
kind
of
like
Ci
to
more
of
that
security.
So
if,
if
they
are
green
in
CI
thinking
about
this
from-
and
we
do
have
like
a
greenhouse
score
for
just
CI
specifically,
but
what
I
would
probably
do
is
you
know,
look
at
this
secure
stage
and
being
able
to
show
like
if
I
just
want
to
look
at
the
last.
A
You
know
15
releases
I
can
see
all
right,
so
it
looks
like
there's
license
compliance
and
dust
and
license
compliance
and
SAS
and
code
quality.
I
might
thumb
through
here
and
say
you
know
what
I'm
gonna
ask
like
what
what
do
you
care
about
more
dependency
scanning
or
SAS,
and
then
I
can
filter
it
even
further
down
and
say
like
okay,
I'm,
gonna,
just
search
on
dependency
scanning
and
I'm
gonna.
Maybe
share
this
list
with
them
and
say:
hey
like
we've
been
making
consistent
Investments
in
the
last.
You
know
four
releases
in
dependency
scanning.
B
That's
perfect,
and
actually
at
some
level,
if
a
customer
is
on
the
fence
about
gitlab
or
unsure
as
to
how
committed
we
are
to
a
certain
stage.
This
could
be
the
proof
point
of.
Actually
we
can
visually
represent
you,
the
investment
that
we've
made
over
the
past
number
of
months
years
on
the
22nd
of
the
month,
and
then
we
can
match
that
with
our
maturity
State
for
the
future,
yep,
absolutely
okay,
very
helpful
Tim.
Thank
you
ever
so
much
for
going
through
this
absolutely.