►
From YouTube: SNS Nav Release Livestream
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
A
This
is
digital
experience,
team's
first
live
stream
and
today
we're
gonna
walk
through
how
we're
gonna
do
a
nap,
so
we're
gonna
walk
through
and
actually
push
a
minor
release
to
the
marketing
site.
So
I
will
pass
it
on
over
to
TMA
after
hobby
turns
out
music
down
there
we
go
there,
we
go
nice,
nice,
so
TMO
just
pass
a
review,
and
how
about
you
talk
about
what
we're
releasing
today.
C
Okay,
so
hi
everyone,
we
are
going
to
show
how
our
lab
release
Works.
So
we
have
basically
three
steps.
The
first
one
is
publishing
the
npm
package,
I'll
be
showing
this
one.
Some
minutes,
second
steps
updating
fire
experience
in
www
Rebel,
with
our
new
version,
this
John
and
gel
will
show
to
you
and
the
last
parts
of
the
our
navigation
package
Json
file.
So
what
we
are
releasing
today
I
will
share
my
screen
with
you.
C
D
C
Yeah,
okay,
so
first
those
first
shows
are
from
Megan
she's,
not
here,
but
basically
what
she
did
was
replace
the
mat
base
with
success,
and
then
she
made
the
last
spot
faster,
the
second
one
and
that
you
are
related.
These
other
two
are
also
related
one
in
this
was
made
by
John
and
the
other
one
by
Javi
and
Detroit
related,
because
now
right
now
we
have
the
now
our
language
selector
in
our
footer
and
navbar.
C
If
we
try
to
like
navigate
from,
for
example,
French
page
to
German
page
just
by
like
typing
the
URL,
we
couldn't
because
we
had
like
a
token
made,
making
the
red
drag
so
right.
Now,
it's
not
going
to
happen
more,
but
we'll
show
this
happening
in
the
end
of
the
call,
and
also
we
removed
the
the
button
of
contact,
an
expert
because
this
button
shouldn't
appear
in
our
home
page,
but
it
was
appearing
in
the
other
language
homepage.
C
Now
it's
not
happening
anymore,
and
also
we
had
a
horizontal
scroll
book
that
was
happening
because
of
this
button.
In
all
the
pages
that
head
is
button,
we
had
like
horizontal
scoreboard
in
a
specific
window
size
and
it's
also
not
happening
anymore,
so
yeah,
those
are
the
links
for
our
related
Mrs
and
yeah.
I.
Think
that's
it
right
now,
I
will
be
starting.
C
E
C
Right
yeah
it's
here,
but
I
didn't
create
this
package
yet
because
we
were
using
like
an
alpha
version
to
test
it,
so
I
can
create
it
right
now
and
you
can
see
it
in
action
super
amazing.
So
let's
do
this
yeah,
okay,
yeah
I'm,
the
right
Rebel.
So
what
we
have
to
do
is
things
I
am
I'm
just
checking
from
the
correct
Branch.
I
am
okay,
so
we
need
to
publish
a
new
actually
first,
we
have
to
run
this
command
here,
because
this
one
will
create.
Are
our
this
folder.
C
Yeah
yeah,
that's
it
and
now
we
can
publish
so.
C
Cool
so
now
we
had
it
and
everyone
can
use
it
and
actually
I
will
just
commit
these
updates
to
our
navigation
release,
because
we
have
the
MRI
right
now,
I'll
just
update
and
then
John.
We
show
the
next
steps
Okay,
so
I
just
need
to
push
it.
Let
me
check,
if
I
mean
maybe
I
already
pushed
it.
I
think
I
think
we
just
need
to
approve
it.
C
I
think
that
one
yeah
yeah
so
as
you
can
see
yeah
we
have
the
update
here.
I
think
we
can
merge
it
right
now,
learning
or
do
you
think
we
can.
C
F
Thank
you
very
much.
Well,
I'm
going
to
walk
through
all
the
processes
on
the
buyer.
Experience
repo,
as,
as
you
may
know,
we
have
two
repos
one
is
and
the
other
one
is
a
buyer
experience
and,
in
this
case,
I'm
going
to
update
the
navigation,
the
new
navigation
version
in
by
experience.
So
let
me
please
share
my
screen
real
quick.
F
F
Yes,
yarn
is
our
dependency
configuration
or
or
it
is
a
command
that
we
can
run
in
order
to
install
all
the
dependencies
that
we
have
in
our
project.
So
in
this
case
we
are
updating
and
our
B
navigation
dependency
on
buyers
experience
to
a
new
version.
F
So
every
time
we
update
a
new
version,
we
we
should
run
this
yarn
installed
common
after
that
the
analog
file
will
be
updated,
and
this
Dragon
lock
file
has
all
the
configuration
that
the
server
needs
to
know,
which
versions
to
the
load
when
installing
the
dependencies.
So
right
now
we
are
updated.
Our
navigation
project
to
the
new
final
version
and
I
should
push
these
changes.
E
E
F
No
sorry,
it's
not
updated.
Let
me
oh
I'm,
not
on
the
correct.
F
F
Yes,
we
have
a
pipeline
building
right
now.
It
takes
some
time
so
I
believe
we
can
pass
it
over
to
Miguel
to
do
the
same
thing
and
while
the
pylon
finish,
I
can
continue
with
with
the
demo.
A
F
Of
course,
of
course,
yes,
so,
right
now
we
have
a
pipeline.
That
is
the
one
that
builds
configures
and
creates
our
server
where
our
buyers
experience
project
is
located
so
right
now
we
have
these
five
steps
in
in
buyer.
Experience
pipeline
in
this
case
is
to
install
the
dependencies
that
I
mentioned
before
then
check
the
code
to
verify
if
everything
is
correct,
I'm
following
our
standards,
the
next
step
is
to
build
their
the
whole
package
that
will
be
served
to
the
user
seed
in
in
the
production
environment.
F
Then
we
are
going
to
run
some
tests
in
order
to
verify
that
everything
is
working
correctly
and
finally,
the
review
app
is
deployed
to
the
Internet.
So
after
this
last
last
step
is
deployed,
we
can
check
the
review
up.
We
have
a
review
up
already
deployed
previous
to
this
meeting.
This
review
app
has
some
of
the
changes
that
we
that
tme
mentioned
before,
like,
for
example,
we
have
our
language
selector
here
in
English.
You
can
see
the
URL
here
also
in
English.
F
But
if
we
check
the
language
that
I
selected
before
opening
this
URL
I
selected
French
what
was
happening
before
right
now
in
production,
if
we
go
to
the
home
page,
but
my
selected
language
is
French
like
I'm
showing
you
in
this
example,
the
page
automatically
goes
to
the
French
homepage.
In
this
case,
we
keep
the
user
in
the
English
page,
even
though
the
user
has
selected
the
French
language.
So
you
can
see
like
this.
For
example,
if
we
go
to
the
German
version.
F
We
also
did
a
fix
in
the
English
version
of
the
homepage.
Let
me
go
to
that
version
of
the
homepage
that
we
had
between
sorry
in
this
size
of
the
sorry.
This
one
okay.
F
Thank
you
so
much
yes,
so
we
have
the
talk
to
other
button.
Previously
in
this
size
of
the
of
the
page,
we
have
one
scroll,
an
original
scroll,
as
you
may
see
right
now,
we
have,
we
do
not
have
horizontal
scroll,
so
that
speaks
also
for
this
release.
F
We
also
have
the
thing
Sixth,
Sense
change,.
F
That
we
can
test
like
this
or
the
ends
because
SMB
so
right
now
we
we
are
checking
out
all
these
with
a
tool
called
six
six
heads
and
with
these
two
we
can
verify
what
is
our
user
type
if
it's
a
small
business
or
Enterprise,
and
depending
on
that,
we
show
a
different
image
and
customers
to
say
success
story
here
in
the
resources
attack.
F
And
finally,
we
have
we
had
Dynamic
regulations
in
our
links
in
the
navigation,
so
we
change
it
to
static
links.
So
right
now,
if
I
step
here
on
demopes,
we
see
that
we
are
going
to
be
redirected
to
the
team
of
English
version
of
the
page.
But
if
we
go
to.
F
Another
language
we
should
statically
see
that
we
are
going
to
be
redirected
to
the
German
version
of
the
timos.
If
you,
if
you
see
at
the
left
down
of
the
page,
you
can
see
that
the
next
URL
is
Teamworks
but
General
version.
So
we
have.
We
have
now
static
links
on
the
navigation
and
that's
it
the
last
one,
but
is
right
now,
building
in
the
timeline
is
we
are.
F
We
want
to
hide
this
button
from
from
the
home
page
in
localized
versions,
for
example
in
the
German
page,
but
after
this
pipeline
finish,
we
can
see
that
change,
but
this
button
here
should
not
appear
on
the
home
page,
but
if
we
go
to
the
English
version,
the
button
is
not
there.
After
the
pipeline
success
success,
we
can
see
that
that
bottle
won't
appear
in
any
localized
version
of
the
homepage.
F
A
Yeah,
let's
wait
for
this
pipeline
to
finish
and
when
it's
ready,
let's
smash
that
merge
button,
so
we
can
release
it
to
production
and
yay
yeah.
That's
yeah!
That's
what
we're
doing
so.
Let's
get
that!
Let's
wait
for
that.
F
F
F
Oh
I'm,
based
in
in
Colombia
or
you
see
here
they
both
have
disappeared.
So
yes,
I'm,
based
in
Colombia
I'm,
doing
localization
for
every
language,
except
for
mine,
but
maybe
in
the
future
we
can
add
Spanish.
Okay,
so
everything
worked
as
expected.
We
have
our
all
our
checklist
complete.
So
this
checklist
means
that
the
default
behavior
of
the
navigation
has
been
thoroughly
tested
before
this
meeting.
So
all
minor
things
and
all
links
and
buttons
have.
E
F
A
A
A
F
So
that
that's
it
for
me,
we
are
now
deploying
our
navigation
4.1.0
into
production.
Right
now
we
have
another
pipeline
running
right
now,
let's
see
the
Pipelines,
let's
see
pipelines
where
I
can
see,
deploy
here
releases.
No,
with
this
new
GitHub
I
I
I
lost.
Where
are
the
pipelines?
Could
you
help
me?
Please
yeah.
A
Yeah
I
think
if
you
go
to
buyer
experience
like
the
project
root
like
the
the
project
Repository,
we
yep
there
we
go.
We
see
here.
F
F
D
Yeah
thanks
John
I
think
I'm
a
bit
delayed.
Maybe
my
internet
connection
is,
is
not
the
the
best.
D
Can
you
hear
me
well,
can
you
hear
me
good,
okay,
awesome,
so
I
will
share
my
screen
and
we
will
do
the
updating
their
inversion
in
the
dot
repo.
So
we
can
have
the
latest
navigation
version
that
tme
published
to
to
npm
and
yeah.
D
Sorry,
my
my
computer
is
a
bit
slow,
yeah.
So
right
now
we
have
this
Mr,
which
has
the
the
latest
changes
to
to
the
navigation.
So
now
we
want
to
update
this
version
to
be
just
4.1
the
zero,
and
so
we
will
go
to
RVs
code.
We
don't
have
Webster
here,
but
vs
code.
D
And
since
this
repo
is
huge,
it
takes
a
little
bit
so
every
everything
it's
a
little
bit
delayed
yeah.
So
we
will
have
to
go
to
our
package.json
file
here
we,
we
are
right
now
at
the
branch
for
that
Mr
and
we
will
look
for
the
navigation
package.
D
D
A
D
Yeah,
so
this
is
kind
of
like
the
Legacy
repo
that
we
have
for
the
marketing
page
and
there
we
have
like
holds
of
different
things
combined
like,
for
example,
internal
Pages,
like
the
handbook
or
the
blog,
which
is
like
a
big
module
of
the
page
and
so
having
all
those
things.
Besides
the
marketing
stuff,
the
the
the
normal
pages
of
marketing
that
makes
like
everything
is
like
multiplied.
So
that
includes
includes
the
pipelines
times
and
also
for
local
development.
It's
a
lot
download
slower!
D
Then
you
will
be
used
to
so.
The
idea
is
to
break
down
this
whole.
This
big
site
and
bring
software
belongs,
and
so
that's,
for
example,
we
will.
We
will
see
in
the
in
the
review
app
that
the
language
selector
is
not
implemented
in.
They
have
book
pages,
because
that
effort
is
is
being
focused
on
the
marketing
pages,
so
those
kind
of
stuff
where
we
need
to
change.
D
D
D
We
have
the
log
files,
and
now
we
want
to
push
these
changes
to
the
Mr,
should
I
do
this.
E
D
A
A
I
was
I
like
Sublime,
you
know,
I
mean
I've
been
on
Sublime
for
about
15
years
and
I.
I
didn't
know
that.
C
A
D
A
Yeah
and
then
and
then
once
you
can
see
the
Mr
pipeline
building
with
those
changes
since
the
dub
takes
so
long,
we'll
have
to
wait
for
the
changes
to
change
in
the
Mr
20-ish
minutes
and
then
it's
a
whole
nother
20
minutes
to
actually
deploy
to
production
so
we'll
at
that
time,
we'll
just
pass
it
on
and
pass
it
over.
For
the
next
thing.
D
Not
really,
we
can
debug
live
if
you
want
to
yeah.
D
Yeah
so
I
I
try
to
to
add
my
SSH
okay,
which
I
usually
do,
and
it's
still
asks
for
username
and
password
and
HTTP
Authentication.
D
A
D
This
is,
this
is
handy
when
you
are
dealing
with
environments
issues
in
the
dark
people,
so
this.
E
D
Yeah,
a
container
that
runs
yeah,
it
runs
containers
workspace
in
in
the
cloud,
so
you
can
select
the
repo
that
you
want
to
use.
So
here
we
want
to
use
the
deductible.
D
And
since
I
I
don't
do
this
recently,
it
could,
it
could
have
like
a
fresh
research.
D
Copy
the
the
branch
name
make
all
this
stop
because
automatically
we'll
try
to
build
everything,
but
we
don't
want
to
do
that.
D
Takes
a
long
time
so
here
we
will,
we
will
just
switch.
D
A
Here,
how
about
heading
back
to
the
Mr
in
the
changes
Tab
and
like
let's
see
if
we
can
actually
use
the
the
single
file
or
the
web
ID
to
make
this
change?
So
if
you
go
to
the
changes,
tab.
A
Okay,
well
I
think
because
this
this
repo
is
very,
very
large.
It's
going
to
take,
take
some
time
to
to
get
get
pod
and
that
environment
up
to
date,
so,
let's
let's
hand
it
over
to
Javi,
so
he
could
show
since
our
buyer
experience
navigation
released,
it's
probably
six.
It's
probably
all
prod.
Now
did
that
pipeline
finish
and
then
we
can
demo.
The
things
live
on
aboutgitlab.com.
B
B
Oh
no
you're
good
yeah
looks
like
it
finished
right
yeah.
So
if
I
check
it
yeah,
so
let
me
share
my
screen
real
quickly
with
the
folks.
B
A
B
A
B
A
I,
like
that,
the
Enterprise
page
is
a
really
good
one,
because
that
does
have
languages.
But
the
whole
point
is
that
once
you're
on
the
French
home
page
yeah.
B
B
C
B
Couple
things
I
did
want
to
talk
about,
especially
as
we're
waiting
for
some
of
the
get
pod
stuff
figured
out
is
why
we
chose
to
have
the
buyer
experience.
Navigation
be
separate
from
this
Repository,
as
you
kind
of
saw,
we
were
switching
between
the
buyer,
experience,
site
and
www
really
like
our
decision
to
have
that
be
a
separate
package
came
down
to.
We
wanted
to
Value
having
those
two
repository
stay
in
sync
with
each
other.
B
When
we
first
moved
over
to
the
bar
experience
site,
there
was
for
one
less
stuff
on
it,
and
so
then
the
decision
of
keeping
those
two
in
sync
came
with
the
essentially
like.
We
want
the
handbook
to
stay
in
sync.
We
want
the
blog
and
everything
else
that
doesn't
live
in
it
by
experience
to
have
the
same
navigation.
This
is
existing
Behavior
as
we
had
before.
B
So
essentially,
that's
our
reason
why
there's
probably
a
future
where
we
don't
necessarily
need
to
do
that
anymore,
especially
as
the
handbook
migration
is
happening,
there's
stuff
with
the
blog
that's
moving
along,
we
will
assess
that
at
a
future
date.
I,
don't
really
think
we're
in
a
position
to
really
say
like
what
we
will
do
in
that
future
going
forward,
but
just
in
the
reality
that
we
live
today.
B
This
is
the
process
that
we
have
I
think
there's
probably
a
desire
to
simplify
our
process
if
it
makes
sense
for
us
but
we'll
you
know
we'll
get
there
when
we
get
there
kind
of
thing.
One
thing
to
note
is
that
when
we're
using
the
npm,
they
use
semantic
versioning,
and
so
we,
as
a
consequence,
are
also
using
semantic
versioning
for
that
package.
I
just
wanted
to
quickly
like
talk
over
that
real
quick.
B
B
These
are
corresponding
semantic
versioning
numbers
for
all
of
these
different
dependencies.
If
we
go
to
d
e
right
here,
you'll
see
that
we
have
4.1.0,
which
is
the
package
version
that
we've
published
right
now.
The
first
number
is
corresponding
to
a
major
version,
and
the
this
is
talking
about
like
essentially
changes
that
are
non-compatible
or
slash
breaking.
B
The
second
number
is
just
like
minor
changes
that
we
will
want
to
do,
and
then
the
smallest
number
is
just
bug
fixes,
and
so
that
helps
keep
the
keep
us
organized
in
terms
of
what
packages
get
pushed
out
where
it's
really
easy
to
switch
between
different
versions.
So
if
something
breaks
in
one,
we
can
go
back
to
the
other.
We've
ran
into
that
in
the
past
with
our
workflow,
especially
with
updates
having
to
fly,
you
know
pretty
quickly.
B
So
in
our
workflow
now
really
like
what
we
have
is
that
decision
comes
down
to
the
like
the
person
who's
directly
responsible
for
the
nav
release.
From
what
it
looks
like
to
me
is
that
this
was
adding
functionality
that
well
it
was
undoing
functionality,
I,
wouldn't
say
it's
adding
it's
undoing
functionality
that
we
were
trying
to
get
smart
with
once
we
realized
that
some
of
this,
like
automatic,
like
route
detection
thing
for
the
most
part,
is
not
great.
B
For
SEO,
we
decided
as
a
team
that
it
would
probably
be
best
to
move
away
from
that
that
I
think
Falls,
at
least
for
me
personally
also
falls
into
the
minor
release
category.
So
whoever
did
that
good
job
for
following
that
in
the
right
bucket?
But
it's
a
it's
a
it's.
It's
a
kind
of
a
gray,
Zone,
sometimes
and
I
think
it
comes
down
almost
a
little
bit
to
like
what
we're
doing.
B
I
think
we
could
it's
a
little
bit
of
a
convention
thing
as
well,
where
it's
like.
We
could
just
make
everything
a
major
release
if
we
wanted
to,
and
some
people
operate
by
more
loose
interpretations
of
the
guidelines,
but
I
think
we're
the
way
that
we've
done
it
works
for
us
and
that's
how
we've
been
doing
it
thus
far.
D
The
gate
for
container
actually
I
think
that
the
fetch
finished
all
right,
but
also
Tammy,
updated
diversion
already
so
I
guess
the
pipeline
is
running.
Oh.
D
We
also
have
the
linking
process.
The
unit
testing,
the
secret
detection.
All
awesome
features
that
I
can
offer
gitlab
with
their
CI
CD
the
images
and.
A
Yeah
well
go
ahead
and
go
to
Hobby
to
Jam
us
out
with
some
sweet
sweet
Tunes,
because
now
we
get
to
celebrate
I
think
you
gotta,
stop
sharing
your
screen
Miguel
when
you
get
a
chance
and
we
could
celebrate
this
minor
NAB
release,
as
as
you
can
see,
it's
quite
involved.
It's
not
it's!
Not
just
one
Mr
and
one
merge,
it's
three
repositories
and
npm
and
takes
it,
takes
everyone
and
there's
all
kinds
of
testing
like
with
the
nav
release.
There
was
five
Mrs
that
were
also
getting
released
so.
A
I
know
and
we've
caught
some
really
big
things.
That's
why
we
have
that
checklist.
While
it
is
large
and
it's
a
lot
of
work
because
you
have
to
do
it
for
eats,
you
know:
buyer
experience
and
the
dub
we
caught
some
pretty
big
bugs
by
that
checklist,
so
it's
great
to
check
catch
them
in
the
Mr
and
not
see
them
on
production.