►
From YouTube: GitLab 13.2 Kickoff - Create:Source Code
Description
Create:Source Code PM (Daniel Gruesso) walks through the planned work for the 13.2 released, shipping on July 22nd, 2020.
A
Hi,
this
is
Daniel
Shaw
and
I
am
the
PM
for
the
source
code
group
under
the
create
stage
here
at
the
it
lab,
and
today
I
want
to
share
with
you
the
kickoff
for
our
13.2
release,
which
is
planning
to
ship
on
July
22nd
2020.
Let's
get
right
to
it.
The
first
couple
of
items
that
we're
going
to
work
on
are
a
couple
of
items.
We
started
working
on
thirteen
one
we're
going
to
work
to
get
them
across
the
line.
A
It's
part
of
13
the
first
one
of
those
is
making
merger
of
diffs
the
default
comparison
mode.
So,
as
you
know,
we
have
this
new
View
mode
called
merge,
ref
diff,
and
this
allows
you
to
prepare
the
latest
version
and
mastering
this
is
very
useful
when
you
merge
the
target
branch
into
your
source
branch.
Currently
that
you
know
can
be
a
little
messy
with
this
merger
active
view.
A
It's
a
lot
clearer,
and
since
that
is
the
case,
we
want
to
make
that
the
default
comparison
mode
so
excited
to
bring
you
that
second
item,
we're
going
to
work
on
is
multi-line.
Merge
request
comments,
so
this
is
one
that
I'm
very
excited
about,
and
basically
what
this
allows
you
to
do
is
when
you
leave
a
comment
on
your
diff,
you
can
currently
address
it
on
a
single
line,
but
a
lot
of
times
we
want
to
address
this
comment
to
a
whole
block
of
code.
A
A
Next
thing:
we're
going
to
work
on
is
renaming
whip,
merge
requests
so
currently
the
virtual
requests
that
are
not
ready
to
be
reviewed
use
the
term
whip
which
stands
for
working
progress.
Well,
so
we
currently
use
that
term
elsewhere
on
gitlab,
there's
kind
of
a
coalition
with
the
terminology.
First
and
second,
this
is
not
a
term
that
is
self-explanatory
for
non-english
users,
for
example.
So
we
feel
that
a
more
appropriate
term
is
that
of
draft.
So
in
this
release,
we're
going
to
work
on
allowing
you
to
either
use
whip
or
draft.
A
When
you
have
an
mr
that
isn't
worth
the
progress
or
graft
and
then
we'll
gradually
face
out
the
whip
terminology
in
favor
of
draft,
but
for
the
first
iteration
here
we
want
to
basically
introduce
the
term
and
allow
you
to
use
either
one
of
those
four
draft.
Mrs
the
next
thing
that
we're
going
to
work
on
is
showing
the
approve
button
on
merge
requests
in
por.
So,
as
we
know,
code
review
is
an
essential
practice
in
software
development
and
a
lot
of
times.
A
There's
peer
review
of
the
code
through
via
merge
requests,
and
we
use
different
signals
to
let
our
peers
know
that
this
is
something
that
has
been
reviewed
or
is
something
that
has
been
approved
currently
in
core.
This
happens
in
kind
of
informal
ways,
sometimes
with
an
emoji
of
thumbs
up
sometimes
with
a
comment.
We've
even
seen.
Some
people
have
bots
that
have
an
automated
comment
with
approval.
So
that's
great,
but
we
want
to
make
this
easier
and
we
want
to
standardize
it.
A
We
will
introduce
the
ability
to
find
references
so
right
now
we
can
go
to
definition
and
we're
adding
the
ability
to
find
a
number
of
references
where
certain
definition
has
been
used
in
your
code.
So
if
you're
excited
to
bring
this
one
as
well,
the
next
feature
that
we're
going
to
work
on
is
adding
an
instance
setting.
So
you
can
configure
your
default
branch
name
for
new
rebo's
so
currently,
when
you
create
a
repo
in
git
or
it
get
left
by
default
branch
that
has
created
this
pulp
master.
A
So,
there's
a
couple
of
reasons
why
we
want
to
update
that
first
is
this
master
is
not
an
equally
understood
term
or
users
that
are
new
to
get
or
get
lab,
and
the
second
is
that
master
references,
master,
enslave
terminology
that
is
coming
from
legacy
tools
and,
as
you
know,
over
time,
we've
worked
to
remove
such
terminology
from
from
gitlab,
and
we
want
to
continue
on
doing
so.
So
this
is
the
first
iteration
and
then
in
the
future.
A
We
hope
to
bring
this
configuration
to
groups
as
well
as
projects
individually
and
then
the
very
last
thing
that
we're
going
to
work
on
is
the
ability
to
copy
LFS
objects
when
a
repo
is
pushed
mirrored.
So
currently
you
can
mirror
your
project
to
another
repo
right
and
when
you
push
that
mirror
is
triggered
so
branch
projects
are
using
LFS
objects.
Don't
currently
have
those
elephants
objects
copied
over
when
they
push
so
this
feature
will
bring
basically
bring
parity
in
pull
mirror
where
we
already
pull
those
elephants
objects.