►
From YouTube: Creating release post items
Description
Patrick Deuley walks through creating a new release post item from both the command line and through the UI.
A
Hi
I'm
going
to
do
a
quick
rundown
of
our
release
post
process
and
specifically
walk
through
what
it's
like
to
add
a
release
post
item
as
a
product
manager.
So
the
first
thing
that
you
should
know
is:
each
month
we
do
release
on
the
22nd.
That
release
is
done
in
tandem
with
a
blog
post
that
highlights
all
of
the
individual
features
that
have
been
added
during
that
release.
The
release
post
manager
is
responsible
for
that
process
and
will
put
together
that
blog
post
and
collect
all
of
those
features
in
the
data
file
on
the
website.
A
So,
let's
walk
through
a
few
of
those
things:
real,
quick,
so
inside
of
the
wwg
lab,
calm,
repo
we've
got
a
date,
folder
called
data
and
there's
one
called
release
posts,
so
the
release
posts
each
one
of
these
represents
that
individual
release
and
then
we
also
have
a
folder
called
unreleased
inside
unreleased.
We
currently
see
four.
This
is
during
twelve
nine
or
in
the
run
up
to
twelve
nine
we've
got
charts,
gatsby
pages
post
grade
deprecation
right.
These
are
individual
feature
blocks
that
will
go
inside
of
that
release
post.
A
So
here's
a
secondary
feature,
there's
another
secondary
feature.
These
will
get
captured
by
the
release
post
manager
and
put
into
one
of
these.
So
this
is
one
of
the
full
release
posts
and
you
can
see
each
one
of
these
features
aggregated
here,
so
what
you'll
be
doing
as
a
product
manager
when
you're
adding
your
features?
You're
gonna
take
one
of
these
samples,
so
we
have
templates
here.
Four
primary
features:
secondary
features,
top
features
each
one
of
these
templates,
whichever
one
is
most
appropriate
for
your
particular
feature.
You'll
take
it
and
you'll
fill
it
out.
A
A
So
first,
let's
see
where
I
am
so
I'm
currently
on
master,
let's
pull
master
just
to
make
sure
I've
got
the
latest
and
you
can
see
that
I'm
on
branch
master,
when
I
run
git
status
and
I'm
running,
get
pull
to
make
sure
I
have
the
latest
copy
of
the
website
so
looks
like
I've
got
a
few
changes
that
I
haven't
seen
yet
and
I'm
gonna.
Do
it
check
out
it's
B
B
specifies
a
branch,
so
it
check
out
or
creating
a
branch
so
get
check
out
checks
out.
A
Now
I
am
on
a
new
branch.
Adding
demo
feature
block
great,
so
I'm
gonna
take
primary
dot,
yml
and
I'm
gonna
copy
it
up
to
the
unreleased
folder.
Now
you
can
do
that
from
the
command
line.
You
can
do
it
every
one
either
way
so
remember
we
had
these
charts,
gatsby
post
grade
application
right.
All
of
these
features
were
in
unreleased.
I
have
now
added
my
own
and
I'm
gonna
rename
it
adds
let's
say
feature
Y
edition.
A
A
18Y,
okay,
I'm
gonna,
describe
it
remember
it's
it's
why
it's
important
these?
What
it
does
myrrh
always
include.
Why
not
just
what
fill
out
the
rest
of
this
template,
but
let's
assume
that
I've
done
a
great
job
and
I've
added
a
really
great
release
post
item.
So
now
everyone
get
status.
You
can
see
that
that
file
has
not
been
added,
so
I
can
do
it
this
again,
we
can
see
that
this
is
the
new
change
that
I've
added
this.
A
Great
push
if
I
don't
have
that
branch
upstream.
Yet
that
means
that
branch
only
lives
on
my
local
machine.
It
doesn't
live
on
the
actual
repo
upstream.
Yet
so
I
need
to
run
this
command.
Git
push
set
upstream
origin,
adding
demo
feature
block
rates.
So
the
easiest
way
to
do
this,
for
me
at
least,
is
copy
and
paste
that.
A
A
Okay,
put
chrome
over
here
and
it's
still
pushing
here
we
go,
and
so
this
is
a
really
cool.
Little
function
to
create
a
merge
request
for
adding
demo
feature
block
visit
that
so,
if
I
just
visit
that
link
it'll
create
a
new
merge
request,
so
we
can
see
we're
on
WWF
comm
read
your
quests
new
awesome,
we'll
start
with
a
work
in
progress
and
it
buddy
accidentally
merges
it
and
no.
A
A
A
So
I
can
fill
up
each
one
of
these
sections
out
with
the
dris.
So
my
the
engineer
who
created
it,
the
PMM
who's
responsible
for
it,
a
technical
writer,
the
engineering
manager-
can
also
leave
links
to
the
feature
issue
the
feature,
mr,
if
I'm,
if
I'm
doing
a
release
post
specifically
for
that
thing
or
I
guess
maybe
this
is
the
the
12:9
release
post,
my
apologies.
We
can
link
to
each
one
of
those
things
and
then
there
are
some
descriptions
for
what
you're
going
to
be
doing.
A
A
So
now
I
didn't
fill
all
of
these
individual
pieces
out.
We
can
see
that
I've
been
assigned
appropriately,
the
milestone
is
assigned
appropriately
and
the
labels
are
filled
out
appropriately.
So
now
would
be
a
good
time
to
start
going
through
my
checklist
and
make
sure
that
each
one
of
these
things
is
checked
and
I've
done
all
of
the
appropriate
steps.
A
At
the
end
of
this
once
you've
gotten
the
reviews
that
are
appropriate
and
you've
gotten
all
of
the
content
fixed
up
the
way
you
want
it,
the
engineering
manager
should
be
the
one
to
merge
it
and
once
it
gets
merged.
So
let's
pretending
that
this
is
a
thing
that
got
merged
will
then
be
able
to
see
this
file
inside
data
inside
release
posts
and
inside
unreleased.
So
once
it
gets
purged
you'll
see
my
new
feature
also
here
on
on
the
master
branch
just
like
these
features
that
are
here
today.
A
So
that's
it.
The
release,
post
manager
can
take
it
from
here
once
those
items
have
been
added.
So
let's
do
it
one
more
time
from
the
web
I
from
the
web
interface
just
in
case.
That's
the
way
that
you'd
prefer
to
interact
so
starting
from
this
repo,
that's
gitlab
comm
/,
dub,
dub
dub
get
lab
come
so
this
is
the
website
project
we
can
from
here.
We
can
create
a
new
branch
and
then
we'll
just
do
the
same
thing
again
and
then
why
and
create
a
new
branch.
A
A
A
And
then,
now
that
this
has
been
added
so
there's
my
file
that
I
added
I'm
on
the
branch
where
I'm
I'm
creating
my
future
block
and
then
I
can
create
a
merge
request
and
at
this
point
we're
in
exactly
the
same
position
right
so
I've
got
the
release
post
item
template
I
can
fill
out.
I
can
do
the
exact
same
steps
and
at
the
end
of
that,
once
we've
submitted
our
merge
request.
Our
e/m
has
successfully
merged
it.
The
release
post
manager
will
take
over
and
merge
them
all
into
the
release
post.
A
So
that's
it.
That's
all
process
for
a
PM.
It's
a
pretty
simple
process
for
each
feature.
You'll
create
one
of
those,
mrs
you'll
get
that
merged
and
master,
and
then
you
leave
into
the
release
post
manager.
To
finish
up,
meanwhile,
you'll
have
to
get
reviews
done
based
on
what
the
feature
is.
You'll
want
to
get
your
technical
writer.
You
want
to
get
your
pmm
to
review
those
items.
You'll
want
to
work
on
making
sure
you
have
a
really
robust.
Why
statement
so
that
readers
can
understand
why
they're
reading
about
the
thing
that
they
just
read?