►
From YouTube: GitLab 13.3 Kickoff - Create:Source Code
Description
Source PM (Daniel Gruesso) walks through the items planned for release 13.3, shipping on 2020-08-22.
A
Hi,
my
name
is
Daniel
Caruso
and
I
am
the
product
manager
for
the
create
source
code
group
here
at
give
lab,
and
today
I
like
to
share
with
you
the
kickoff
for
our
13.3
to
release,
which
is
slated
to
be
released
on
August
22nd
of
2020.
Let's
get
right
to
so.
The
first
couple
of
issues
were
going
to
focus
on
as
we
started,
work
on
them
in
13
and
we're
going
to
work
on
getting
them
over
the
line
as
part
of
13-3
first,
one
of
those
being
showing
the
approve
button
for
merged
requests
in
core.
A
So
an
important
part
of
for
the
code
review
process
is
kind
of
giving
that
clear
signal
that
the
changes
have
been
reviewed
and
they
are
good
to
go
for
merging.
And
ideally
we
have
a
clear,
signaling
and
mechanism
to
do
that.
Well,
our
merger
request
users
in
core
currently
do
that
in
a
couple
of
different
ways,
such
as
giving
an
emoji
thumbs
up
or
simply
a
comment
on
the
mr,
as
there
is
no
other
clear
mechanism
to
do
it
as
I'm
showing
them
on
my
screen
here.
A
So
what
we're
going
to
focus
on
is
basically
bringing
the
approve
button
for
the
merge
requests
that
are
done
in
core.
So
one
important
know
there
is
that
merge,
request
approvals
which
basically
require
that
an
approval
is
made
before
the
merge
requests
can
be
merged
will
remain
a
starter
feature
and
basically,
the
approve
button
in
core
will
be
entirely
optional
and
you
will
still
be
able
to
urged
even
in
the
virtual
quest
does
not
have
approval.
A
The
second
issue
that
we're
working
to
get
over
the
line
is
finding
is
around
code
intelligence
and
it's
the
ability
to
find
references
for
a
particular
term
in
your
code.
So
the
part
that
we
already
released
allows
you
to
go
to
definition
and
that's
great
and
then
the
second
part
that
we're
going
to
add
this
show
you
the
references
where
that
definition
is
being
used,
which
you
will
see
here.
It's
going
to
be
a
separate
tab
in
the
code
intelligence
model,
so
very
excited
about
that
as
well.
A
A
So,
for
example,
if
you
have
a
development
team
and
a
compliance
team
that
want
to
be
able
to
be
involved
in
changes,
they
can
now
do
so
with
sections
and
how
we're
tying
it
with
approval
rules
is
that
today,
you
are
able
to
address
either
users
or
groups
in
approval
rules,
and
what
we
want
to
do
is
give
you
the
ability
to
address
a
section
that
you
have
previously
defined
in
your
code
owners
file.
So
this
will
give
you
the
ability
to
do
that.
A
Mecs
were
working
towards
the
role
of
reviewers
on
merged
requests.
So
we
recognize
that
having
a
dedicated
reviewer
for
your
merge
request
is
an
important
distinction,
and
it
kind
of
gives
you
that
clear
separation
between
author
and
reviewer
and
the
first
step
that
we're
going
to
take
towards
that
is
showing
a
reviewed
by
column
in
the
merge
request.
A
Widget,
so
today
you
will
see
how
many
pending
approvals
you
have
and
who
has
approved
additionally
we're
going
to
add
the
reviewed
by
column,
which
will
indicate
who
has
participated
in
the
merge
request,
and
that
can
be
in
the
form
of
a
comment
in
the
form
of
a
suggestion.
And
that
way
you
will
know
who
is
involved-
and
this
is
kind
of
the
first
step
that
we
will
take
to
having
a
dedicated
reviewer
section
in
merge
requests
so
excited
about
this
one.
A
The
next
three
issues
that
I'm
going
to
chat
about
have
to
do
with
the
maintenance,
cleanup
and
managing
the
size
of
your
repo.
So
today
will
give
you
a
couple
of
options
to
manage
the
size
and
the
contents
of
your
repo,
and
we
want
to
enhance
those
so
there's
more
tangible
feedback
to
the
user.
The
first
one
of
those
is
going
to
be
ruining
all
loose
objects
as
soon
as
you
run
repo
cleanup.
A
So
just
that's,
when
you
want
clean
up
any
LFS
object
that
it's
not
referenced
by
any
part
of
your
repo
should
be
immediately
cleaned
up
and
then
finally,
we
want
to
give
you
another
that
tangible
feedback
and
updating
the
stats
immediately.
It's
a
it's
an
important
part
of
that.
We
will
see
that
in
two
places
the
first
one
is
going
to
be
here
on
your
repo
overview.
A
We
tell
you
about
the
size
of
the
files
and
the
size
of
the
storage
that
is
being
used,
so
we
want
to
make
sure
that
that's
updated
immediately
and
the
second
one
is
on
your
profile
in
the
usage
quota.
So
today,
if
you
visit
your
user
settings,
you
will
see
an
option
on
the
bottom
left.
That
is
usage
quotas,
and
here
you
have
a
storage
column,
and
this
indicates
the
space
that
is
being
used
by
each
one
of
your
projects.