►
From YouTube: GitLab 13.1 Kickoff - Create:Source Code
Description
PM Daniel Gruesso goes over the planned work for the "Source Code" group for GitLab release 13.1. shipping on June 22nd, 2020.
A
Hello,
my
name
is
daniel
grusso.
I
am
a
pm
here
at
kit
lab
for
the
create
source
code
group,
and
today
I
want
to
share
with
you
the
kickoff
for
our
13.1
release,
which
will
be
released
on
june
22nd
of
2020..
So
let's
get
right
into
it.
The
first
couple
of
things
that
we're
going
to
work
on
are
things
that
we
started
working
on
13.0
and
we're
going
to
get
them
over
the
line
in
13-1.
A
First,
one
of
those
things
being
support
for
multiple
code
owner
sections,
so
code
owners
is
great
because
it
allows
you
to
specify
rules
that
can
be
applied
based
on
the
path
where
your
files
live,
and
that
is
really
great
how?
But
when
we
have
large
teams
or
enterprise
teams,
where
we
have
multiple
teams.
Looking
after
the
same
parts
of
the
code,
then
it
is
not
possible
to
have
multiple
parties
be
responsible
for
the
same
parts
of
the
code
as
we
can
only
enforce
one
rule
or
one
match
for
each
one
of
those
paths.
A
So
what
this
feature
will
allow
us
to
do
is
that
it
will
allow
us
to
create
basically
what
we're
calling
code
owner
section.
So,
for
example,
you
can
create
one
section
for
one
part
of
your
team
and
specify
files
or
paths
and
the
responsible
parties,
and
you
can
create
a
different
section
that
will
basically
allow
to
look
after
a
common
part
of
the
code.
A
In
this
example,
both
the
gl
docs
and
the
gl
database
groups
can
look
after
the
readme.md
file
and
just
as
we
can
do
it
for
files,
we
can
do
it
for
paths
as
well.
So
this
is
really
great
because
it
will
allow
teams
to
collaborate
better
and
it
will
allow
for
a
multiple
ownership
of
common
parts
of
the
code
and
based
on
on
the
sections.
The
very
next
thing
that
we
want
to
do
with
code
owners
is,
we
want
to
show
you
the
section
name
in
merge
request
approvals.
A
The
next
thing
that
we're
going
to
work
on
is
bringing
merch
request
reviews
to
core.
So
I'm
very
excited
about
this,
and
basically
what
this
will
allow
you
to
do
is
that
when
you
are
reviewing
a
merch
request
currently
in
core,
you
have
to
lift
multiple
individual
comments
when
you're
leaving
feedback
for
your
merch
request,
merge,
request
reviews
allows
you
to
batch
all
of
those
comments
and
send
them
out
as
a
single
unit,
and
this
is
really
powerful,
because
currently,
if
in
core,
I
am
leaving
multiple
comments
on
a
merge
request.
A
Those
may
be
addressed
before
I'm
finished.
With
my
review,
things
may
change,
so
it's
really
useful
that
all
of
that
feedback
is
sent
out
to
the
author
as
a
unit
and
we're
very
excited
to
bring
this
to
core,
and
it
aligns
very
well
with
our
pricing
model
where
which
we
think
this
is
a
feature
that
is
very
useful
for
individual
developers,
so
we're
very
excited
to
bring
this
to
court.
A
The
next
thing
that
we're
going
to
work
on
is
making
merch
rip
dips
the
default
comparison
mode.
So,
as
you
know,
in
a
previous
iteration,
we
added
a
new
diff
mode
that
allows
you
to
compare
between
the
latest
version
and
master,
and
this
is
very
useful,
for
example,
to
compare
when
in
situations
where
you,
when
you
have
merged
the
target
branch
into
the
source
branch,
and
then
your
diff
kind
of
becomes
quite
messy.
A
The
last
thing
that
we're
going
to
work
on
is
on
simplifying
the
code
intelligence
setup
for
gitlab
native
code
intelligence.
This
is
a
really
great
feature
that
we're
working
on
13.1
and
will
basically
allow
you
to
easily
set
up
a
job
in
your
gitlab
ci,
dot,
yaml
file,
which
will
specify
an
elsif
report,
and
once
you
have
that
hovering
over
objects
in
your
code,
will
give
you
all
the
available
code
intelligence
actions.
This
is
really
cool,
as
we
know
that
code
intelligence
plays
an
important
part
in
the
code
review
process.
A
So,
for
example,
if
you're
reviewing
a
merge
request
with
new
code
you're
going
to
have
those
code,
intelligence
options
right
there
in
that
code,
and
it
basically
will
allow
you
to
gain
a
better
understanding
of
the
code,
that's
being
written
and
ultimately,
that
will
result
in
better
quality
and
better
understanding
within
teams.
So
we're
very
excited
about
this
feature
and
we're
hoping
to
enable
it
by
default
for
everyone
as
part
of
13.1,
so
very
exciting
stuff
in
the
in
this.
In
this
release,
as
always,
your
feedback
is
always
encouraged.