►
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).
B
Okay,
well,
thank
you,
john
for
taking
the
time.
The
purpose
of
this
is
for
you
to
well.
It
is
for
me
to
understand
how
do
you
see
the
italy
deployment
processes
and
also
the
release
processes
from
your
point
of
view,
because
I
am
familiar
with
how
we
do
it
from
the
delivery
side
and
the
process
that
we
have
now
it
works,
but
I
have
the
impression
that
it
works
better
for
us
than
it
works
for
you.
So
I
would
like
to
understand:
how
do
you
see
it
if
you
see
like
any
improvement
area?
B
B
A
A
B
B
A
A
What
happens
is
each
time
when
something
does
go
wrong
and
like
we
introduced
like
a
bug,
and
we
have
to
stop
that-
I
usually
just
come
to
you
and
nice
and
honestly,
because
you
can
stop
that
auto
exploit
then
at
some
point
we
ask
you
to
re-enable
it,
but
other
than
that
scenario.
It's
fairly
seamless
like.
I
don't
think
we
ever
really
think
about
it.
That
much.
B
Interesting,
so
is
there
any
like
an
improvement
area
that
you
would
do
to
the
current
deployment
process
for
italy,
because
we
have
talked
about
it
that
if
you
want
to
deploy
something
bold,
you
prepare
the
merge
request.
You
have
it
approved,
it
is
merged,
and
then
you
rely
on
the
merge
request
updater
to
update
the
server
file
on
gitlab
right.
So
all
of
that
process
it
seems
that
it
works.
A
A
A
B
A
A
A
B
A
B
A
B
A
B
A
B
B
Yeah,
because
when
when
a
production
incident
happens
that
is
associated
with
an
italy
error,
well,
sometimes
the
ownership
falls
into
us
delivery
and
we
don't
really
know
what
to
do,
because
none
of
us
are
like
italy
experts.
So
in
that
time,
what
we
do
is
to
go
and
put
something
on
the
italian
channel
and
to
say
like
hey:
is
there
someone
available
to
help
us
and
normally
you
either
all
are
available
or
we
need
to
wait
for
someone
to
be
available.
A
B
Okay
awesome,
so
I
have
sort
of
the
same
question
now
for
the
releases
for
the
release
process
for
italy,
like
what
are
the
steps
that
you
as
a
developer,
follow
to
go
through
a
patch
release,
because
let's
say
that
something
needs
to
be
fixed
in
a
stable
branch,
and
you
need
to
prepare
a
fix
like.
How
would
you
do
that.
B
A
Well,
we
prepare
an
mr
that
goes
into
the
master
and
if
that
gets
merged,
then
we
try
to
pick
that
into
the
stable
branch
for
that
release
and
then
once
that
happens,
I
think
I
haven't
done
this
in
a
while,
but
I
think
we
asked
the
release
managers
to
cut.
You
know
a
minor
word
yeah.
I
mean
a
patchworks
for
that.
B
A
B
A
A
B
B
B
B
So
another
question
regarding
the
deployment
process
right
now
in
our
documentation,
it
is
suggested
that
italy
and
prefect
needs
to
be
deployed
before
the
code
application
changes,
because
otherwise
something
tragic
is
going
to
happen.
I
think
that
was
at
the
beginning,
when
we
were
planning
the
auto
deploys
and
the
well
the
zero
downtime
upgrades.