►
From YouTube: GitLab 14.2 Kickoff - Create:Code Review
Description
14.2 Kickoff for the Create:Code Review Group
Planning Issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12871
Release Board: https://gitlab.com/groups/gitlab-org/-/boards/2159734?scope=all&utf8=%E2%9C%93&label_name%5B%5D=group%3A%3Acode%20review&milestone_title=14.2
- Sorting of MRs by merged and Closed: https://gitlab.com/gitlab-org/gitlab/-/issues/18458
- Retain location in Changes/Overview Tab: https://gitlab.com/gitlab-org/gitlab/-/issues/297440
Better defined mergeability: https://gitlab.com/groups/gitlab-org/-/epics/5598
Restructure MR Widget: https://gitlab.com/groups/gitlab-org/-/epics/5589
A
A
In
14.2
you're,
looking
at
the
release
board
right
now,
you
can
see
a
lot
of
the
issues
here,
I'll
link
down
to
this
below
the
video,
but
there's
a
lot
going
on,
and
so
I
want
to
touch
on
a
few
things
that
are
pretty
important
here.
The
first
is
a
couple
features
that
we're
going
to
be
working
on,
and
so
one
of
these
is
going
to
be.
A
But
you
can't
sort
those
by
merge
date
or
close
date,
and
those
two
are
really
important
options
that
help
you
understand
when
code
was
actually
added
to
your
code
base
and
can
help
in
diagnosing
issues
that
you
find
that
have
been
deployed
to
production,
you're
trying
to
isolate,
merge
requests
to
a
certain
time
period
or
they
can
just
help.
You
understand
the
order
of
things
that
are
getting
into
the
code
base
and
when
that's
happening,
and
so
we'll
be
adding
both
of
these
options
to
the
list.
A
A
Another
small
but
impactful
change
that
we're
going
to
make
is
retaining
your
location
and
the
overview
and
changes
tab
of
a
merge
request.
And
so,
if
you're
familiar
with
the
merge
request
page
when
you're
looking
at
a
merch
request,
there's
a
changes,
tab
and
there's
also
an
overview
tab
and
those
you
might
bounce
back
and
forth
between
both
of
those
tabs.
A
And
sometimes
your
position
can
get
lost
as
you
change
tabs,
and
so
you
switch
back
and
forth
and
you're
not
in
the
same
place.
You
were,
and
you
have
to
sort
of
reset
your
context
and
so
we're
going
to
be
tracking
your
positions
through
those.
So
that
way,
when
you
go
back
and
forth,
you
should
stay
in
the
same
spot
on
each
of
those
tabs
to
make
that
context.
Switch
a
little
less
dramatic.
A
A
We
expect
that
to
run
probably
three-
maybe
more
milestones
to
do
that,
so
that
we
can
come
out
of
this
with
a
simpler
to
develop
against
and
easier
to
understand
and
diagnose,
mergeability
sort
of
area,
and
the
key
benefits
to
that
is
you'll,
see,
there's
a
lot
of
issues
linked
in
here
that
are
bugs
and
other
things
that
are
they're
very
hard
to
diagnose
and
understand,
and
they
require
certain
conditions,
and
that's
just
because
the
logic
of
this
is
very
difficult.
A
So
we'll
get
some
usability
improvements
and
making
that
process
a
lot
stream
more
streamlined
and
we
won't
be
waiting
on
checks
from
the
back
end
and
check
from
the
front
end
and
various
other
places
to
happen.
And
so
you
should
see
some
improvements
into
the
reliability
of
the
merge
button,
but
also
this
will
help
us
close
out
new,
bugs
or
other
bugs
that
might
be
introduced
or
interesting.
A
Behavior
that's
introduced
later
because
we'll
have
a
simple
way
to
sort
of
go
through
these
and
how
all
of
these
should
be
processed
so
we'll
be
starting
on
this
in
14.2
expect
it
to
be
a
common
theme
and
look
for
improvements
in
the
merge
button
there
as
we're
doing
that
work
in
the
back
end.
We're
also
going
to
be
working
in
the
front
end
to
sort
of
refresh
and
redesign
some
of
the
merge
button
area.
A
What
we
call
the
merge
widget
inside
of
the
merge
request
page,
and
so,
if
you
take
a
look
here,
this
is
sort
of
what
the
the
merge
button
can
look
like
now
with
some
various
pieces.
A
This
is
what
we
want
it
to
look
like
in
the
future
and
there's
a
figma
file
here
that
I'll
I'll
go
ahead
and
we
can
look
at
just
one
of
the
base
states
here.
A
This
is
what
we
want.
The
new
structure
of
the
merge
request
button
to
look
like,
and
so
we
want
alerts
sort
of
attached
at
the
top,
a
title,
some
actions
and
then
merge
options
and
then
non-actionable
text
and
then
a
merge
button.
The
merge
button
today
can
sort
of
say
a
lot
of
different
things.
That's
inconsistent
in
how
it
does
that,
and
so
we
want
to.
We
want
to
build
some
more
consistency
into
that
and
you
can
go
through
the
sigma
files
linked
in
the
epic
I'll
link
it
down
below.
A
You
can
sort
of
look
at
all
the
various
pieces
that
are,
you
know
how
it
looks
today
and
then
how
this
will
look
in
the
future.
So
if
you
notice
in
this
one
we're
looking
at
threads
and
so
when
there's
unresolved
threads,
you
have
to
resolve
those
before
you
can
merge
and
there's
a
lot
of
information
in
here.
We're
going
to
simplify
that
and
say
look
the
merge
is
blocked.
All
your
threads
must
be
resolved.
Do
this
and
then
here's
your
other
actions
and
other
information
down
below
that'll
help.
A
You
need
to
get
that
code
merging
into
the
code
base,
and
so
we
want
to
make
that
process
more
reliable
and
make
it
easier
to
get
to
that
that
state.
So
I'm
really
excited
about
both
of
those
changes
and
the
progress
we're
making
there
in
terms
of
the
usability
and
reliability
we'll
provide
there
I'll
put
links
to
all
of
this
down
below.
If
you
have
any
questions,
feel
free
to
comment
in
those
epics
comment.
There
tag
me
in
issues
and
I'm
happy
to
take
a
look
thanks.