►
From YouTube: How to Update the Release Post Intro
Description
This video provides instructions for updating the introduction to a published release post.
Related to: https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/6564
A
Hey
marketing
team:
my
name
is
Brian
Ray
I'm
with
product
operations
here
at
gitlab,
and
this
is
going
to
be
a
walkthrough
of
how
you
will
update
the
intro
after
one
of
the
release,
posts
has
been
published
and
so
as
you're
all
familiar
with.
You
know
this.
This
intro
gets
published
with
each
with
each
release
post
and
we
have
a
template
that
our
release
post
manager
uses
to
choose.
A
You
know
a
handful
of
the
top
and
primary
items
and
then
link
to
those
in
in
the
post
now
for
for
you
all
after
this,
after
the
post
gets
published
and
it
has
merged
into
master
and
you
want
to
revise
or
improve
or
add
to
the
intro.
These
are
the
steps
for
how
you
will
do
that
so
I
would
recommend
bookmarking
this
directory
and,
as
you
can
see
there
are,
you
know
quite
a
few
files
in
here.
A
So
how
do
you
know
which
one
you
want
to
you
want
to
edit
you'll
want
to
be
sure
that
it
is
the
that
it's
the
minor
release,
the
actual
you
know
in
this
case
15.4
or
in
this
case
15.3,
not
15.3.3
or
a
security.
You
know
security
release
intro,
and
so
you
will
know
which
one
it
is
because
there
will
always
be
published
on
the
22nd,
so
it'll
be
8,
22,
922
and
so
on.
A
But
in
addition
just
be
sure
that
there's
only
that
it
follows
this
exact
format,
the
date
which
the
date
the
publication
day
being
the
22nd
and
then
15-4
or
15-5,
and
it
won't
include
you
know
any
other
yeah.
It
doesn't
include
any
other
numbers
or
any
other.
You
know
text
in
there.
So
let's
just
pretend
that
we
are
going
to
update
the
the
dot
four,
so
you'll,
just
click
on
that
file
and
you're
going
to
see
a
you
know
a
preview
of
it
here.
A
The
easiest
way
for
you
to
be
able
to
edit
this
file,
commit
it
to
a
new
branch
and
then
create
a
merge
request
from
that.
Branch
will
be
to
use
this
edit
button
right
here
now,
there's
a
chance
that
when
you
open
this
up,
it's
going
to
say
open
in
web
IDE
I
strongly
suggest
that,
because
you're
only
editing
one
file
use
that
little
drop
down,
switch
it
over
to
edit
and
then
and
then
click
edit
open
in
web
IDE.
A
A
This
is
the
existing
intro
that
the
release
post
manager
and
the
product
team
and
and
marketing
team
or
yeah
what
would
have
created
during
the
process
you're
just
going
to
hop
in
here
and
either
before,
or
you
know
after
depending
upon
what,
depending
upon
what
you
all
decide
in
your
process,
that's
what
you're
going
to
you're
going
to
do.
You'll
add
in
your
revisions
and
then
all
you'll
need
to
do
is
to
scroll
down
here
and
describe
in
this
commit
message.
A
What
is
it
that
you're
doing
and
I'm
not
going
to?
Actually,
you
know,
merge
this
in,
but
I'm
going
to
say
that
we're
update
the
15
for
release
post
intro,
okay
modifying
the
target,
Branch
name-
is
entirely
optional.
If
you
would
like
to
you
know
if
you
all
end
up
having
some
sort
of
syntax
or
or
policy
that
you
follow,
that
that
will
be
up
to
you
and
then,
when
you
commit
your
changes
and
be
sure
that
the
check
box
is
checked
to
start
a
new
merge
request
boom.
A
Here
we
are,
and
the
title
is
going
to
be
populated
by
that
that
commit
message
and
then-
and
here
you
will
describe-
describe
the
changes
that
you're
making
and
why
marketing
may
decide
to
have
a
a
Mr
template
for
this
particular
type
of
change
apply
the
necessary.
You
know,
follow
whatever
steps
you
all
decide
upon
for
who
it
should
be
assigned
to
who
should
review
it,
give
it
a
milestone
and
any
appropriate
labels.
A
And
then
all
you
have
to
do
now
is
to
just
click,
create
merge,
request
and
that's
it
as
far
as
the
process
for
finding
the
file
that
you
would
like
to
edit
how
to
edit
it
how
to
commit
that
edit,
basically
save
the
change
and
then
create
an
MR
that
contains
that
change.
That's
all!
That's
all
you
need
to
do
right
there.