►
From YouTube: CI/CD UX meeting - 2021-02-24
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
Hello,
this
is
the
cicd
ux
meeting
bi-weekly
we
meet
bi-weekly
now
right
for
february,
24
2021.,
I'm
going
to
start
with
the
some
fyi
items
you
I
think
you
all
know
friends
and
family
they
coming
up
this
friday.
We
also
have
one
scheduled
for
march
19th.
So
add
that
to
your
calendars
and
tomorrow
we
have
the
first
pilot
for
the
cicd
and
create
ux
personal
growth
day.
A
If
you
haven't
checked
yet
the
updates
for
the
other
designers
and
what
they're
going
to
be
working
on
not
suggest,
maybe
just
have
a
look,
the
fit
and
firing
if
there's
something
that
you
can
work
on
together,
but
other
than
that
anything.
Any
action,
no
action
items
required
and
I'm
gonna
jump
right
into
the
first
item,
because
I
actually
wanted
to
spend
some
time
asking
you
for
feedback
and
clarifying.
If
there
is
any
questions
left
on,
the
engagement
survey
results
for
our
team,
as
I've
seen.
A
I
created
this
issue
to
track
what
we're
going
to
be
working
on
and
in
my
suggestions,
you
see
two
issues:
focus
on
growth,
development
and
your
manager
and
action
themes,
and
so
I
just
want
to
review
quickly.
A
Let
me
share
my
screen
with
you,
because
I
updated
the
body
of
the
issue
and
added
a
couple
of
action
items.
I
apologize
for
all
all
the
mentions
on
this
issue
in
advance,
but
I
just
want
to
align
and
see
if
we
are
all
on
the
same
page
on
what
we
need
to
accomplish
for
this
quarter.
A
A
Opportunities
in
your
role
and
outside
of
gitlab,
so
just
to
recap
a
couple
of
things
if
possible.
Well,
I
put
march
5th,
but
if
possible,
continue
working
on
your
personal
development
plans
document
whatever
you
want
to
call
it
so
that
we
can
discuss
and
in
a
way
kind
of
wrap
it
up
for
q1
and
review
the
career,
development
and
engineering
development
handbook
pages
and
continue
to
identify
some
opportunities
for
your
growth.
There's
a
lot
of
documentation
in
the
handbook
around
career
development.
A
I
think
this
is
the
main.
The
most
important
ones
so
also
add
a
due
date,
but
feel
free
to
work
on
this.
When
you
have
the
time
and
another
important
thing,
I
think
that's
you
already
seen
pedro
sharing
some
content
is
to
look
into
career
and
growth
development
benefits.
Now
the
company
has.
I
think
this
is
the
tab.
Yeah
company
has
a
number.
Let
me
scroll
to
the
top
here,
a
number
of
opportunities
right
or
reimbursements.
That
gitlab
can
give
us
in
terms
of
conferences,
academic
studies
trainings.
A
So,
if
there's
anything
that
you
would
like
to
work
on
this
year,
that
would
add
would
be
beneficial
to
your
skills
on
your
personal
growth.
A
Please
have
a
look
at
this
page
and
if
you
have
anything,
if
there's
anything
interesting
for
you,
let
me
know
so
that
we
can
work
on
an
approval
for
that,
and
I
think
last
item
is
well
we're
going
to
have
to
do
that,
anyways
with
accessibility
and
the
linkedin
training
this
one.
We
all
have
to
do
this
quarter
and
it
will
adapt
to
our
our
skill
sets
or
career
development.
A
Last
one
focus
friday,
I
put
it
as
a
stretch
initially
wasn't
required,
but
I
put
a
stretch.
I
I
continued
to
encourage
you
all
to
incorporate
focus
friday
as
not
just
a
day
to
catch
up
on
things
that
you
know
kind
of
spill
over
from
the
beginning
of
the
week,
but
as
a
day,
or
at
least
a
couple
of
hours
to
focus
on
items
that
are
important
to
your
personal
development
and
make
that
it's
something
standing
in
your
agenda,
not
just
for
this
quarter.
But
if
you
can
do
it,
you
know
part
of
your.
A
Your
workflow
will
be
cool
and
then
some
tasks
for
myself.
So
communicating
continue
exercising
this
and
producing
some
content
and
clarifying
the
broad,
the
product
designer
the
designer
wrote
plan
path.
Whatever
you
want
to
call
this
with
you
all,
okay,
so
too
much
talking,
questions,
thoughts.
Next
steps.
A
Okay,
so
this
has
a
due
date
for
the
end
of
april
and
before
the
end
of
the
quarter,
or
at
least
by
the
first
week
of
q2,
I
think
it
would
be
nice
for
us
to
do
retrospective
and
then
just
talk
about
how
and
if
these
things
helped
us
in
terms
of
growth
and
development.
A
You
have
any
questions,
let
me
know
and
oh
yeah,
I
see
there's
a
couple
of
questions
here
who
wrote
this?
Who
wants
to
to
voice
the
questions
in
the
document.
B
So
unrelated
to
growth,
sorry
about
that
tim
and
I
are
kicking
off
a
new
initiative
to
kind
of
take
the
jobs
to
be
done
and
we're
talking
about
moving
it
so
that
the
jobs
to
be
done
are
also
defining
the
testing
coverage
that
we
have
for
stability,
especially
in
the
container
registry.
We've
had
some
issues
with
that.
B
C
Scorecards,
I'm
trying
to
think.
First
of
all,
I
think
it's
a
very
happy
coincidence
that
both
of
us
would
be
working
on
something
similar.
So
also
could
think
up
on
this,
because
I'm
doing
something
very
similar
for
ci,
and
I
so
one
really
good
application
of
jobs
to
be
done.
That
I
have
seen
when
put
to
practical
use
was
when
we
tried
to
divide
the
areas
within
ci
and
pipeline
authoring
like
where
the
divisions
would
be.
So.
C
If
you
look
at
I'm
trying
to
find
that
the
link
which
has
yeah
there,
you.
C
Go
okay,
I'm
putting
at
the
beginning
for
now
I'll
format
later.
So,
if
you
go
to
this
link-
and
you
look
at
that,
if
you
scroll
and
look
at
the
infographic
sort
of
thing,
which
is
there
that
it,
it
basically
is
divided
on
the
basis
of
jobs
to
be
done,
I
mean
that
hasn't
been
put
very
exclusively
anywhere.
That
has
hasn't
been
even
vocalized,
but
that's
the
basis
on
which
we
have
divided
the
areas
that
we'd
be
working
on.
C
So
it
really
gave
us
a
boundary,
and
you
just
mentioned
that
you
would
also
be
covering
the
critical
paths
which
is
otherwise
like
considered
under
testing
and
that's
fuse
template.
I
don't
know
if
you
have
looked
at
it.
I
think
you
would
have
looked
at
it,
which
is
on
the
jobs
to
be
done
page.
C
It
sort
of
it
it
has
been
so
I've
been
watching
today
morning,
yeah.
I
think
we
have
a
lot
of
to
catch
up
on.
So
if
you
look
at
the
process
which
is
defining
that
pure
template,
it
also
kind
of
triggers
you
to
consider
the
whole
process
and
I
don't
think
we
would
be
able
to
divide
things
just
connected
jobs
to
be
done
which
are
taken
care
by,
in
my
case,
pipeline
altering,
maybe
a
few
in
testing
and
release.
C
So
all
those
things
would
come
into
the
picture,
but
maybe,
while
like
arriving
at
the
final
result
of
the
whole
process,
we
have
to
be
a
little
like.
We
have
to
consider
what's
what's
more
useful
for
our
personal
stage
group
and
what
is
it
that
we
need
to
pass
on?
I
know
your
question
was
like
how
we
are
using
jobs
to
be
done.
Otherwise,
I
don't
have
a
very
good
answer
for
that,
but
I'm
very
excited
that
you're
working
on
this.
A
And
I
had
to
hear
a
link
to
a
youtube
video
where
jack,
I
think
it's
maybe
a
five,
maybe
less
than
five
minutes
video
of
jackie
going
over.
Why
we
used
the
jobs
to
do
and
framework
in
release
management
and
other
than
you
know,
validating
things
defining
that
maturity
etc.
We
use
the
jobs
to
be
done
that
were
mapped
to
create
the
maturity
plan
for
the
product
for
the
some
of
the
categories.
A
So
when
we
started
looking
to
the
scenarios,
the
jobs
to
be
done
were
really
like.
Okay,
this
is
the
scenario
and
how
this
is
how
it
translates
to,
for
example,
an
interface
or
the
three
years
vision.
So
I'm
not
sure
if
she
did
that
for
package
as
well.
Did
you
work
on
the
vision
prototypes
package
in.
B
We
started
to
do
an
investigation
of
prototypes
for
our
three-year
vision
and
we
discovered
really
quickly
a
lot
of
what
we
used
to
include
was
irrelevant
user
interface,
so
it
was
like
we
needed
to
expand
to
include
all
of
linux
packages
which,
like
we
could
make
a
ui
that
has
a
linux
package
in
it,
but
it's
not
going
to
be
different,
so
instead
we're
shifting
kind
of
our
attention
to
refactoring
the
jobs
to
be
done
and
then
finding
ways
to
better
utilize
them
across
our
entire
team
and
other
parts
of
the
organization
as
well.
B
For
example,
like
qa
testing,
has
their
own
discussion
about
how
to
prioritize
what
to
test.
What
we're,
considering
and
talking
about
now
is
the
jobs
to
be
done
should
tell
us
what
needs
to
be
tested
because
we
have
a
hierarchy
of.
We
know
this
job
to
be
done
is
the
most
important
one
and
here's
the
acceptance
criteria
to
be
able
to
perform
this
job
etc.
A
Yeah,
so
I
think
it's
it
was
similar
to
what
jackie
and
I
did
so
looking
at
the
jobs
to
be
done
and
in
terms
of
the
vision,
the
one
year
and
three
year,
vision
and
really
extrapolating
what
we
could
potentially
prototype
and
present
to
customers
to
validate
just
some
of
the
not
so
ripe
ideas,
but
also
in
terms
of
jobs
to
be
done
themselves
like
presenting
the
jobs
and
making
them
available
to
the
teams.
A
What
jackie
used
to
do
was
to
sometimes
present
the
opportunity
canvas
and
to
review
that,
together
with
the
engineering
teams,
so
with
everyone
during
the
thinkpig
sessions
or
whatever
sessions,
and
then
she
would
walk
us
through
what
she
learned
about
that
specific
job
to
be
done
and
how
that
related
to
the
next
milestone
or
the
updated
vision
or
a
specific
category.
So
in
a
way
it
was
everything
around
jobs
to
be
done
and
around
the
maturity
and
the
maturity
plan.
A
C
Yeah
and
yeah,
of
course,
I
totally
missed
I'm.
I
I
I'm
also
working
on
this
same
as
research
for
ci
and,
of
course
jobs
to
be
done
is
all
that
the
whole
thing
is
based
on
and
one
thing
that
I've
noticed,
I'm
very
sure,
other
people
who
hannah
you
have
conducted
a
cms
research.
C
You
might
have
also
noticed
that
that
the
maturity
that
we
talk
about,
even
when
we
talk
in
terms
of
jobs,
to
be
done
so
a
job
should
be
a
job
to
be
done,
is
it's
all
is
associated
with
a
certain
persona.
So
this
is
a
question
that
I
have
and
maybe
I'll
bring
it
up
in
the
I
have
more
findings
from
the
research
that
it
looks
like
that,
the
workflows
they
are
more
optimized
or
they
are
more
mature
for
a
certain
persona.
C
A
Go
ahead,
no,
you
go
ahead.
I
think
that
that's
something
that's
important
to
a
lie
that
we
don't
associate
a
job
to
be
done
to
a
persona.
We
don't
associate
job
to.
We
don't
talk
to
them
to
a
persona
or
technology
or
product,
or
anything
like
that.
So
it's
very
it's
just
a
job
that
someone
needs
to
to
complete
or
to
perform
in
their
day-to-day
jobs.
A
So
I'll
link
the
page
here
if
someone
has
the
page
so
that
we
can
see
how
to
frame
the
job
to
read-
and
I
think
that's
important
to
highlight-
and
can
you
repeat.
B
C
How
do
we
kind
of
indicate
that
there's
a
certain
persona
which
would
be
more
benefited
from
features
in
a
stage
group,
because
I
understand
so.
C
I
was
also
walking
through
this
whole
process
of
jobs
to
be
done
today,
and
I
realized
that
there
may
be
different
kinds
of
executors
for
that
jtbd,
but
we
kind
of
take
into
consideration
a
proto
persona,
that's
kind
of
an
aggregate
of
all
the
executors,
but
we
do
have
like
we
do
keep
some
someone
in
the
focus,
but
it
just
it's
very
apparent
that
when
I
talk
about
this
particular
I'll
take
an
example,
so
let's
say
optimizing
a
pipeline,
so
that's
I
mean,
even
if
I
don't
mention
it
is,
and
it
is
a
task
that's
mostly
performed
by
devops
engineers.
C
I
mean
I
I
can't
skip,
maybe
mentioning
that.
But
how
do
I
I
it
it?
It's
indicated
in
every
result
as
well
that
this
is
this
bends
more
toward
devon.
It's
pretty
apparent
from
the
results
as
well.
A
A
This
is
where
at
least
what
I'm
used
to
this
is
where
we
talk
about
the
personas
that
we
are
going
to
cover
right
on
that
specific
thing
that
we
want
to
validate.
So
the
problem
is
around.
B
A
Managers,
devon,
sasha,
delany
et
cetera,
et
cetera,
and
I'm
not
sure
how
you're
documenting
that,
maybe
that's
where
I'm
I'm
gonna
fail
on
answering
this
question
is
that
when
we,
when
I
would
document
and
propose
the
feature,
propose
the
the
enhancement
or
propose
the
functionality
around
the
job
to
be
done?
That's
when
I
talk
about
this
is
solving
a
problem
for
persona
xyz.
A
B
We
do
something
very
similar
where
a
job
is
inherently
agnostic
from
the
persona
or
user
type
and
even
the
tool
and
then
from
there
when
we're
talking
about
either
a
specific
task
that
has
to
be
performed
related
to
that
child
or
a
person
who
has
to
manage
that
job.
That's
when
the
conversation
comes
in
of
most
of
the
time.
The
person
impacted
by
this
task
is
the
engineer
is
devon,
and
so
we
tailored
this
part
of
the
experience
to
be
devon
in
mind,
and
we
based
that
choice
on
this
survey.
B
That
said,
everyone
that
cared
was
blah
blah,
and
so
we
bring
the
persona
into
the
solution.
But
the
job
is
still,
anybody
could
have
performed
the
job
and
technically
it
should
still
work.
We
just
focus
on
the
personas.
We
have
data
or
believe
to
be
most
impacted
by
this
and
then
sometimes
you'll
have
a
job
to
be
done
where
a
persona
performs
the
first
half
of
the
task
and
then
a
totally
different
persona
has
to
perform
another
part
related
to
the
same
job.
So
that's
how
it's
still
agnostic
from
the
persona.
A
C
That
really
helps
so
in
terms
of
documentation.
Yes,
we
have
absolutely
kept
it
personal
agnostic,
but
what
he
just
said
like
how
do
we
have
to
consider
those
and
connect
the
jtv?
This
is
the
personal
like
at
under
what
circumstances
and
in
what
kind
of
applications
that
it
really
helped
me.
D
C
So
when
I
mean
I'll
just
sum
it
up
that
there
are
certain
parts
like
certain
jtvds
that
scored
higher
in
the
cms.
That
just
means
that
those
jobs
to
be
done
were
easier
to
perform.
Maybe
they
have
a
higher
maturity
level,
but
we
wouldn't
focus
on
the
part
that
this
is
like
more
under
the
area
of
devops
engineer
or
whatever.
The
person
is.
C
A
Because
our
product
is
so
complex
and
there's
like
so
many
personas,
interacting
with
the
interfaith
interacting
with
a
certain
part
of
the
workflow,
I
had
a
similar
challenge
challenging
release
management.
Where
I
think
I
mentioned
this
before
we
had
a
very
technical
release,
manager
or
just
a
devops
engineer
responsible
for
release
management
tasks,
and
we
had
someone
that
was
the
release
manager
that
wrote
a
blog
post.
That
created
you,
know
the
marketing
content
etc
and
was
not
technical
at
all.
A
So
I
think
that's
where
the
point
we
get
where
my
experience
is
that
you're,
just
gonna
have
to
break
the
scenarios
and
in
a
way,
work
with
this
micro
job,
the
micro
tasks
dedicated
to
personas
and
that
those
might
become
separate
features
right
and
from
going
back
to
the
point
where
we
use
the
jobs
to
be
done
to
build
the
maturity
or
like
the
vision
for
the
feature
is
like
what
do
we
want
to
build?
First,
we
want
to
build
first,
the
a
right
or
the
api.
A
So
that's
where
the
those
those
this
division
map
for
the
jobs
reading
can
enter
to
help.
You
give
the
more
confidence
on
what
you
are
prioritizing
in
terms
of
a
roadmap.
C
You
got
it
so
personas
they
play
a
part
when
it
comes
to
when
it
comes
down
to
execution.
To
I
mean
better,
understand
the
requirements
and
like
keep
in
mind
the
kind
of
person
who
would
be
using
the
feature
to
make
it
like
more
usable
for
them.
B
B
One
thing
that
we
also
do
with
the
persona
the
jobs
to
be
done
is
that
things
mature,
so
the
package
registry
itself
is
actually
doing
pretty
well.
We
will
note
that
for
devon,
like
a
developer
role,
it
was
really
easy,
but
when
we
introduced
someone
who
was
less
technical
but
like
a
cis
admin
who
had
to
deal
with
like
billing
and
consumption
and
those
kinds
of
things
it
was
challenging
and
we
can
use
that
data
to
say
the
same
job
to
be
done
is
being
performed,
but
because
they're,
two
different
people
there's
two
different
experiences.
B
We've
got
this
one
going
really
well
now,
let's
look
at
that
second
one
and
that's
how
you
can
also
use
persona
to
expand
on
something
that's
already
there,
so
you
hit
it
with
the
primary
person
didn't
test
well
with
a
secondary
person.
Now
we
can
get
attention
in
that
area
too,
make
the
ui
more
friendly,
for
example,.
A
I
have
that
I
think
all
these
information
is
in
the
handbook.
I
know
that
it's
a
lot.
I
know
it
a
lot.
A
Whenever
I
have
a
question,
I
go
there
because
the
research
team
they
put
a
lot
of
effort
in
documenting
all
these
scenarios
and
all
these
questions
so
have
a
have
a
look
see
if
there's
a
video
see
if
there
is
a
way
that
you
can
consume
this
information
a
bit
more
easily,
but
there
is
guidance
around
why
how
to
validate
what
happens
in
scenario
a
b
c
d
and
how
jobs
should
be
done,
deferred,
forex
and
perform
user
stories.
A
I
think
it's
also
important
for
us
to
be
empowered
to
answer
those
questions
when
pms
or
the
counterparts
kind
of
get
stuck
in
the
whole
jobs
to
be
done
framework
universe,
and
if
you
have,
of
course,
any
questions
or
if
you
have
any
learning
to
share.
Please
do
so.
I
think
we're
we're
all
learning
here
on.
B
A
Information
awesome-
and
I'm
just
gonna-
add
this
here-
also
to
the
link
to
the
doc
there's
a
there's,
some
information
of
what
is
in
a
job
to
be
done
and
some
examples.
So
gotta
look
it's
a
hot
topic
for.
C
Oh
okay,
so
I
would
quickly
share
my
screen,
so
I
was
exploring
this
particular
template
when
I
actually
started
off
with
finding
out
or
documenting
the
jobs
to
be
done
for
ci.
I
did
not
use
this
template,
but
I
thought
that
since
I
have
enough
data
enough
information
at
hand
now
from
different
researches
and
even
the
previous
researches,
I
would
give
it
a
go.
I
mean
I
would
follow
the
difference.
C
When
it's
I
mean
it
says
your
domain.
But
if
you
talk
about
ci
ci
is
not
something
that's
I
mean,
of
course,
it's
fans
right.
I
mean
the
different
area
of
expertise
which
are
kind
of
contained
within
ci,
for
example,
testing
deployment
and
even
some
release
stuff.
So
I
just
wanted
to
share
that
what
I
have.
C
Is
I
include
all
those
steps
which
are
kind
of
contained
within
ci
without
discrimination
is
and
is
not
very
extremely
relevant
to
the
features
that
I
work
with,
but
towards
the
end,
when
it
would
come
to
privatization,
maybe
I
would
focus
only
on
the
ones
that
ci
could
act
upon.
A
Me
be
honest:
I
never
used
this
template
before.
I
don't
even
think
I've
seen
this
one
before,
because
when
I
work
with
the
jobs
to
be
done
with
jackie,
we
were
the
first
one
of
the
first
team
doing
that
in
the
maturity
scorecard
as
well.
So
I'm
not
familiar
with
this
side
of
the
process
and
you.
B
C
Problem
so
I
mean
I
would
share
my
experience
as
I
progress
with
this,
but
yeah,
so
maybe
in
the
in
the
next
meeting
that
we
have,
I
would
give
a
run
through
because
my
agenda
is
to
use
this
next
week.
D
C
So
this
is
from
the
handbook,
and
I
mean
I
I
saw
this
before
as
well,
but
because
it
looks
so
complex,
I
kind
of
skipped
it
when
I
was
doing
the
documenting
the
jobs
to
be
done
for
ci.
But
now
I
I
think
this
is
going
to
be
very
handy,
especially
when
I
want
to
make
sure
that
there's
nothing
missed,
especially
when
we
have
some
assistance
with
the
information.
A
Yeah
I
used
a
sheet
with
together
with
jackie,
so
I'm
trying
to
find
that
jobs
to
be
done.
Is
it
this
one
yeah
this
one
jack
and
I
used
to
track?
Maybe
that's
what
this
spreadsheet
is
replacing.
I'm
just
gonna
add
here
in
the
chat
because
it's
faster,
oh,
he
lost
ian,
oh
no,
he
dropped.
A
B
A
Is
how
jack
and
I
used
to
track
so
you
see
that's
very
complete,
but
at
that
point
we
were
doing
the
environments.
So
if
you
look
at
the
third
tab,
third
tab
yeah.
So
these
are
all
the
jobs
that
we
mapped
out
and
I
think
that's
what
the
this
mural
template,
because
we
talk
about
priority.
If
you
look
at
the
the
second
tab
oops,
I
should
probably
be
sharing
my
screen,
so
others
see
later
on
yeah.
So
here
you
have
the
category.
A
C
Yeah
and
that's
a
step,
I
think
that
I
would
also
be
taking
tao's
help
on,
especially
with
the
private
privatization
part.
So
I
want
something
that
we
can
quickly
collaborate
on
like
a
platform
that
it's
easier.
B
A
Try
it
out
and
see
if
it
works
for
you,
I
think
also
what's
in
the
handbook,
it's
something
that
it's
prescribed,
but
it
needs
to
work
right
and
if
it
works
differently
for
you
and
if
you
think
there
is
any
feedback
or
changes
that
could
be
applied,
that's
you
know
were
beneficial
during
a
process
open
a
merge
request
update
because
these
are
yeah
guidelines
to
help
you
figure
out
this
process
together
and
to
facilitate.
C
A
And
I
know
we
are
a
time,
but
I
just
want
to
kind
of
give
this
heads
up,
so
it
stays
recorded
pedro
shared.
I
think
yesterday,
in
in
the
ux
slack
channel
a
thread
about
upcoming
waxing
conference
events,
so
I
I
mention
you
in
that
that
one,
but
for
the
others
or
people
who
are
going
to
watch
this
later
on.
A
Please
review
the
growth
and
benefit
page
that
I
mentioned
earlier
in
this
call
that
talks
about
what
type
of
benefits,
what
type
of
events
and
how
much
you
can
ask
for
a
refund
if
you're
interested
in
yeah
attending
a
conference
or
doing
a
course
yeah.
C
C
Thank
you
so
much
anything
else,
viticulture,
nothing
else.
Just
for
an
fyi.
I
have
put
a
link
to
a
tweet
which
is
about
pipeline,
so
I
I
I
felt
that
this
tweet
was
framed
in
a
very
interesting
way,
so
it
would
anticipate
some
interesting.
I
mean
replies
which
is
imagine
we
never
invented
this
icd
pipeline.
How
would
you
improve
quality.
B
C
Just
been
following,
and
people
have
so
far
been
giving
very
nice
feedback
yeah,
and
I
I
of
course
don't
have
any
great
insight
from
this,
but
for
fun
and
for
like
looking
at
things
for
a
different
lens.
I
found
this
useful.
A
That's
fun
telemetry
from
production,
thanks
for
sharing
awesome,
you're
welcome,
enjoy
the
rest
of
your
day.
I
see
you
if
not
tomorrow,
I
see
one
monday.