►
From YouTube: GitLab 15.1 Kickoff - Create:Source Code
Description
Create:Source Code - Planning of 15.1
https://about.gitlab.com/direction/create/source_code_management/
https://gitlab.com/gitlab-org/create-stage/-/issues/13012
A
Hello,
everyone,
my
name
is
thorsen
and
I
want
to
present
to
you
our
plans
for
15.1,
for
the
source
code
management
team
and
on
our
group
directions
page.
You
can
find
information
on
what
we're
currently
working
what's
up
next
and
also
links
to
our
planning
issues
and
we're
gonna
go
now
to
the
planning
issue
for
15.1.
A
A
So
let's
look
at
the
documentation
directly,
so
it
has
been
possible
to
do
to
restrict
the
access
to
gitlab
based
on
the
ip
address.
So
you
have
an
allow
list
with
ip
addresses
that
are
allowed
to
have
access
to
your
to
your
content
on
gitmap.com,
and
this
has
been
available
for
the
ui
and
for
the
api,
meaning
http
requests.
A
A
All
right,
that's
the
first
bullet
here.
Second,
we're
going
to
continue
working
on
a
security
and
availability
box
to
reduce
risk
for
you,
the
customers,
users
and
also
for
gitlab.
A
Then
we
have
failed
to
deliver
against
our
availability
target,
we're
slightly
below
the
target
and
we
haven't
been
below
the
target
for
many
months
but
may
april
we
have
been
below
and
we
need
to
understand
why
that
is
so
that
we
can
fix
it
to
get
back
to
on
target
to
do
these
three
big
ticket
items.
A
A
Then
the
next
two
items
are
mainly
work
for
the
front-end
team,
so
the
front-end
team
will
continue
and
finalize
the
work
on
highlight.js,
which
will
put
us
in
the
position
to
render
source
code
on
the
browser
rather
than
pre-rendering
it
on
the
server
and
then
sending
html
to
the
browser.
This
will
have
a
significant
performance
increase
on
especially
large
source
code
files.
A
Then
the
second
topic
that
they're
concentrating
on
is
starting
to
work
on
bringing
source
code
rules
into
one
place.
So,
as
you
know,
you
can
apply
protections
and
and
different
rules
on
each
branches,
and
currently
they
are
in
many
different
places.
Settings
for
those
and
it's
very
hard
to
understand
which
settings
apply
to
a
branch
and
we
want
to
put
them
all
together
in
one
place
and
the
team
is
going
to
start
this
work
in
15.1.
A
A
Then
we're
going
to
continue
to
improve
our
documentation
on
merge
options.
We
have
already
made
some
changes
there
recently
and
we're
going
to
continue
the
work
and
make
further
improvements.
Yeah,
that's
basically
a
whole
packet
of
15.1.
I
think
it's
a
lot
of
different
work
and
I'm
excited
to
see
this
is
happening.