►
From YouTube: Slippers Release Process
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everybody-
this
is
javier
from
the
digital
experience
team
and
I'm
just
going
to
be
updating
the
npm
package
for
slippers
slippers
ui.
So
I'm
going
to
start
sharing
my
screen
in
just
a
second,
and
I
have
my
one
one-on-one
with
my
manager
in
like
two
seconds,
so
this
will
probably
be
just
a
brief
video
yeah.
Let
me
just
share
my
screen
really
quickly.
A
So
lauren
from
our
team
had
pushed
up
changes,
and
so
then
I
just
briefly
pulled
them
down
and
I'm
just
going
to
be
walking
through
the
process
of
actually
like
updating
this,
and
this
is
all
something
that,
with
time
will
be
automated,
but
for
right
now
you
know
with
the
value
of
iteration
we're
just
like
doing
this
manually,
but
essentially
what
we
do
is
we
bump
the
patch
number
of
the
version
in
the
package.json,
because
every
two
weeks
right,
we
bump
the
minor
version
up
a
number
so
right
now
because
we're
in
the
middle
of
an
iteration
we're
bumping
this.
A
So
we'll
do
that
next
thing:
we're
going
to
do
is
if
we
go
to
the
build
command
here,
we
actually
have
to
build
the
view
and
css
that's
created
with
this
so
and
this
is
just
to
make
sure
that
all
the
stuff
is
like
in
there
and
working
it
may
be
possible
that
some
of
the
components-
I
don't
know
if
lauren
added
components
to
it,
might
need
to
be
added
to
main.js,
but
I
think
that's
something
that
we
can
do
later
again.
A
I
don't
have
a
ton
of
time
right
now,
just
because
I
have
my
one-on-one
literally
like
right
now
but
yeah,
so
I'm
gonna
do
that
really
quickly.
I'm
gonna
hit
git
status.
A
A
Seven
point
eight,
I
believe,
all
right,
so
I'm
going
to
do
that
really
quickly
and
the
reason
why
I'm
like
being
super
on
it
is
that
I
don't
want
super
on
it
in
terms
of
like
wanting
to
make
the
changes
is
because
lauren
merged
the
change
already
so
like.
I
don't
want
someone
else
to
merge
another
thing
and
then
like
have
there
be
a
conflict
in
versioning
and
all
that
stuff.
So
that's
why
I'm
being
really
particular
about
doing
this
like
right
away,
so
I'm
just
going
to
push
this
really
quickly.
A
Whenever
my
computer
decides
to
like
that,
I'm
going
to
do
that
sweet,
and
so
then
I
push
directly
to
master,
which
is
not
like
an
amazing
practice,
but
it's
the
way
that
I've
been
doing
it
and
I've
seen
other
people
do
it.
You
can
also
do
it
in
the
merge
requests,
and
I
don't
know
if
we
have
a
strong
opinion
within
our
team,
whether
to
do
it
that
way
or
not,
but
something
to
consider
so
have
that
set
up
now.
A
What
I'm
going
to
do
briefly
is
run
the
npm
publish
command
and
because
I
have
right
authorization
for
the
package
should
just
let
me
do
that
really
quickly
and
I
can
show
you
like
what
ends
up
getting
updated
in
one
second
stop
share,
so
let
me
go
to
npm
js
on
another
screen
and
then
share
my
screen
really
quickly,
and
you
see
that
this
has
been
published
a
few
seconds
ago
and
so
now,
whenever
you're
working
within
a
package.json,
if
you
are
looking
to
like
use
the
dependency
that
you
know
the
version
of
slippers
that
we
just
updated,
you
would
use
this
number
instead.
A
So,
that's
all
you
do
pretty
simple:
straightforward:
we're
gonna
automate
it
in
the
future
yeah
all
right
thanks
and
I
just
need
to
know
how
to
end
my
thing.
All
right
see
ya.