►
From YouTube: GitLab 13.11 Kickoff - Create:Code Review
Description
Kickoff for the upcoming 13.11 GitLab Release for the Create:Code Review group.
13.11 Release Board: https://gitlab.com/groups/gitlab-org/-/boards/2159734?scope=all&utf8=%E2%9C%93&label_name[]=group%3A%3Acode%20review&milestone_title=13.11
Merge Requests that require my attention: https://gitlab.com/groups/gitlab-org/-/epics/5331
MR Filter for "Waiting-For": https://gitlab.com/gitlab-org/gitlab/-/issues/324854
Display change that made thread outdated in-line: https://gitlab.com/gitlab-org/gitlab/-/issues/24468
Performance of discussions: https://gitlab.com/gitlab-org/gitlab/-/issues/209784
Merge Request comments in VS Code: https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/342
Removal of "WIP" for MR Titles: https://gitlab.com/groups/gitlab-org/-/epics/3879
A
Hi,
my
name
is
kai
armstrong
and
I'm
the
product
manager
for
the
code
review
group
here
at
gitlab
today,
I'm
here
to
talk
about
the
upcoming
gitlab
13.11
release
and
what
the
code
review
group
is
going
to
be
working
on.
So
let
me
go
ahead
and
share
my
screen
and
we'll
jump
right
in
here.
You
can
see
the
release
board
for
all
of
the
code
review
work
that
we'll
be
doing,
but
I
want
to
talk
about
a
few
specific
issues
and
what
we'll
be
doing
in
1311.
A
So
you
can
find
the
merge
request
that
you
need
to
work
on
as
either
a
reviewer
or
as
an
author,
where
you
are
the
blocker,
where
you're
holding
up
the
work
that
needs
to
be
done
there,
and
so
we've
got
some
things
that
we
want
to
go
through
and
do
here,
and
you
can
see
that
involves
some
is
on
the
merge
request.
Sidebar.
We
want
to
update
the
merge
request,
drop
down
to
only
focus
those
ones
that
are
waiting
on
you.
A
Another
often
requested
issue
is
displaying
the
change
that
made
the
thread
outdated
and
so
historically,
in
our
comments,
we've
always
showed
this
line
down
here
that
says
you
know
this
line
was
changed
in
some
version
of
the
diff,
and
this
required
you
to
click
into
that
go
and
find
that
version
see
what
the
change
was
decide.
Whether
or
not
it
addressed
your
original
question
without
having
the
context
of
your
original
question
and
if
you
need
to
go
back,
you'd
have
to
go
find
that
discussion
and
leave
another
comment.
A
So
what
we'll
be
doing
now
is
we'll
be
showing
you
the
change
in
line
in
that
comment
thread
to
show
you
what
the
change
was,
and
this
allows
you
to
easily
recognize
and
see
if
the
change
was
made
that
you
needed
to
be
made
and
if
not,
you
can
leave
another
comment
and
hope
to
get
that
feedback
address,
and
so
we're
really
excited
about
this
one.
This
will
be
a
really
nice
quality
of
life
improvement
to
that
whole
process
of
leaving
a
comment
on
a
discussion
and
seeing
that
resolved.
A
Another
area
I
just
want
to
quickly
touch
on
is
performance,
and
so
we
know
performance
is
really
important
to
everyone
in
their
merch
request.
Workflow,
and
so
this
is
a
issue
about
the
performance
of
the
merge
request
controller
for
discussions,
and
so
this
is
all
of
the
comments
and
just
and
notes
that
are
left
all
inside
of
a
merge
request.
We've
been
working
on
this
for
a
long
time.
A
The
last
feature
I
want
to
talk
about
is
in
our
vs
code
extension,
and
so,
if
you're
not
familiar,
gitlab
has
a
vs
code
extension
called
git
lab
workflow.
You
can
install
that
in
vs
code
and
gives
you
a
lot
of
really
great
functionality
to
connect
directly
to
gitlab
and
interact
with
the
platform
without
ever
having
to
leave
vs
code.
So
we've
been
working
on
doing
code
review
inside
of
vs
code
and
so
we're
getting
near
the
very
end.
Here.
A
We've
got
the
last
few
issues
that
we
want
to
get
lined
up
and
so
that
you
could
have
a
full
sort
of
code
review
experience,
and
this
is
now
down
to
commenting
so
inside
of
the
vs
code
extension.
If
you
open
a
merge
request
inside
of
there,
we'll
show
you
the
disk,
once
you
see
those
dish,
you'll
be
able
to
click
and
use
the
native
commenting
functionality
inside
of
vs
code
to
leave
a
comment
on
those
lines,
either
the
change
lines
or
the
deleted
lines
or
other
lines
that
are
involved
in
the
merge
request.
A
You
know
the
13.11
time
period
as
we
continue
to
release
pieces
here
inside
of
the
vs
code
extension
and
then
hopefully,
we'll
have
this
all
wrapped
up
and
complete
sometime
during
the
14-0
release
period,
and
the
last
little
thing
I
want
to
do
is
just
a
reminder.
We
introduced
draft
to
replace
sort
of
whip
or
work
in
progress
and
merge
request
titles.
This
was
done
several
milestones
ago.
A
As
a
reminder
we
are
that
was
depart.
Whip
was
deprecated
at
the
time
and
will
be
replaced
with
draft,
and
that
is
happening
in
14..
So
if
you've
got
any
automation
or
other
things
built
around
work
in
progress
and
width,
just
know
that
in
14.00
we'll
be
removing
support
for
whip
from
the
application,
and
so
you'll
need
to
use
draft
exclusively
at
that
point
moving
forward.