►
From YouTube: GitLab 15.4 Kickoff - Create:Editor
Description
Planning issue: https://gitlab.com/gitlab-com/create-stage/editor/-/issues/104
A
Hi
everyone,
my
name,
is
eric
schroeder
and
I'm
the
product
manager
for
the
editor
group
here
at
git
lab,
and
I
am
excited
to
share
with
you
what
we
have
planned
for
the
15.4
milestone,
as
always
I'll
link
to
the
planning
issue
here
in
the
video
description.
So
you
can
click
through
to
our
milestone
board
and
see
all
the
issues
that
we
have
planned.
A
First
off,
we
have
been
we're
about
six
or
seven
weeks
into
an
investigation
into
a
new
category
called
remote
development.
This
category
focuses
on
providing
a
cloud-based
development
environment
that
mirrors
what
you
would
have
locally
and
connect
our
web
ide
or
another
ide
of
your
choice.
To
that,
that's
our
that's
our
vision,
we're
figuring
out
the
architecture.
We
have
a
few
different
technical
directions
that
we're
exploring
and
in
15
4
or
really
over
just
the
next
couple
weeks
we're
going
to
be
looking
at
a
couple
specific
themes
here.
A
First
of
all,
around
security
and
sandboxing
of
the
vs
code
web
implementation
in
the
web.
Ide
we
want
to
make
sure
that
we
are
doing
the
right
thing,
but
also
providing
a
way
to
get
out
of
the
web
ide
and
connect
from
the
vs
code
web
client
to
a
remote
instance
of
vs
code
server.
That
would
allow
us
to
have
you
know,
terminal
output
and
the
file
server
access
and
things
like
that
in
the
remote
container
and
provide
the
feedback
in
the
web-based
vs
code
web
ide.
A
So
very
soon,
we'll
be
able
to
solicit
feedback
on
early
builds
and
start
testing.
The
usability
of
it
and
and
pretty
soon
it'll
be
in
your
hands.
So
we're
very
excited
about
that.
In
15
4.
We
will
have
it
behind
a
feature
flag
and
we
will
be
working
on
rounding
out
the
rest
of
the
features
that
that
we
need
to
build
around.
A
A
The
experience
here
is
lacking
a
little
bit
of
context
when
you
commit
from
the
repository
view,
the
single
file
editor,
so
we're
going
to
make
it
more
clear
what
branch
you're
committing
to
whether
you
can
commit
to
the
main
branch
or
not,
and
whether
you
want
to
start
a
new
merge
request
with
that
commit.
So
look
for
that
ux
improvement
that'll
be
a
very
welcome
and
long-awaited
simplification
of
the
commit
flow.
A
On
the
pages
side,
we
continue
to
work
on
our
on
our
overall
effort
to
make
it
more
resilient,
more
performant
and
more
stable.
So,
as
I
mentioned
in
last
month's
video,
we're
working
on
internal
api.
Caching,
that
is
wrapping
up.
As
you
can
see,
the
last
couple
merge
requests
are
in
progress,
we'll
put
that
behind
a
feature
flag
and
start
rolling
it
out
slowly
to
test
the
impact,
but
look
for
some
changes
there
behind
the
scenes
in
15
4.
A
Hopefully,
the
only
thing
you
will
notice,
as
a
user
of
pages
is
that
it's
more
stable
so
on
the
content
editor
side-
I
mentioned
this
last
time,
but
we
are
working
to
bring
auto
complete
suggestions
for
things
like
app
mentions,
an
issue
and
quick
actions
and
things
like
that
to
the
wysiwyg
editor
in
the
wiki.
This
is
all
in
preparation
for
making
it
as
feature
complete,
as
we
can
before
we
bring
it
into
other
markdown
editing
areas
within
gitlab,
like
issue
editor
or
comments
or
in
the
web
editor
when
you're
opening
like
a
readme.markdown.
A
So
we
have
near
we're
nearing
the
finish
line
for
this
merge
request.
We
were
working
on
in
15,
3,
we'll
get
it
merged
in
15
4,
and
then
we
have
some
other
behind
the
scenes.
Improvements
for
content,
editor
related
to
performance
and
stability
and
security.
So
that's
all
I
really
wanted
to
highlight
today.
I
hope
that
you
get
a
chance
to
take
a
look
at
our
planning
issue
and
I
will
see
you
at
the
next
kickoff
video.
Thank
you.