►
From YouTube: Magento MSI Open Demo. May 25, 2018
Description
Agenda:
Regression Status
Release strategy
A
So,
let's
start
the
demo
meeting
our
product
owner
mark
today
is
from
the
PTO,
so
he
is
not
able
to
join
the
meeting
today.
So,
let's
start
without
him,
and
we
will
share
the
video
recording
to
him
afterwards.
So
let
me
share
update.
Let
me
share
my
screen
and
I
was
with
you
so
actually,
during
the
cool
this
week,
we
working
on
a
regression
of
the
project.
So
we
just
let
me
describe
our
release
process
of
the
MSI.
We
already
had
several
questions
regarding
that
in
MSI,
slack
channel
and
I
will
describe
it
now.
A
Recently
will
will
build
the
burndown
report
and
we
actualize
it
yesterday.
So
we
closed
all
the
all
the
issues
which
will
really
deliver
it,
and
we
move
to
the
milestone
to
the
issues
and
stories
which
we
are
not
going
to
release
the
scope
of
the
name,
a
viable
product.
So
you
see
currently
that
we
are
we're,
probably
on
the
ideal,
a
projectory
idea
line
for
the
release
we
supposed
to
be
done
in
the
middle
of
June.
A
So
currently
we
expected
to
make
release
on
a
June
1818-
oh
maybe
20,
and
this
is
how
we're
going
and
actually
when
we
release
the
project.
So
in
the
end
of
June,
you
know
that
magenta
to
the
tree
is
still
not
released
yet,
so
we
will
work
on
the
product
backlog
for
the
next
product
iteration.
We
will,
of
course,
pinky
you
as
a
community
will
provide
you
a
possibility
for
voting
because
have
some
features.
A
Some
feature
proposal
like
make
support
of
bundle
and
group
product
to
be
to
be
operated
on
a
multi
source
environment,
also
to
provide
the
possibility
of
this
store
pickup,
also
to
extend
the
functionality
of
the
drop
shipping,
and
there
are
a
lot
of
different
features
which
we
would
like
to
work
more
closely.
For
example,
some
of
you
I
know
that
would
like
to
provide
more
functionality
and
more
extension
for
the
b2b
so
to
make
more
feature
full
integration,
I'm
assigned
the
b2b.
So
this
also
could
be.
It
could
be
extension
point,
so
we
will
provide.
A
The
list
of
the
feature
will
provide
a
possibility
for
routing
to
this
feature
and
after
that
we'll
choose
a
pretty
strict
and
a
short
product.
Iteration
like
from
four
to
six
weeks,
and
we
will
iterate
iteratively,
make
this
iteration
and
after
each
of
this
iteration,
we
will
will
provide
you
better
version
of
MSI.
A
Iterate
him
and
heading
evaluate
a
new
functionality
to
the
MSI
until
magenta
to
the
three
would
be
released
and
when
the
magenta
to
the
three
would
be
released,
we'll
take
the
latest
version
latest,
better
version
which
is
ready
to
be
released
of
MSI
and
that
version
of
MSI
would
be
would
be
released
as
a
J
along
this
magenta
to
distri.
So
this
actually
make
us
mega.
A
A
A
Actually,
we've
tested
200,
actually
220,
and
currently
we
have
a
fail.
So
if
you'll
go
to
the
overview,
so
we
have
currently
200
test
cases,
posts,
17,
failed,
17,
failed,
so
them
so
currently,
I
wouldn't
say
that
we
have
something
something
really
critical
here.
So,
for
example,
issues
with
back
orders.
A
Actually,
mostly
about
backward
or
label
like
verifying
message
here,
so
it's
not
a
big
big
issue,
but
actually
this
is
the
labeling
issue,
and
because
of
that,
we
have
quite
a
lot
of
test
cases
which
we,
which
is
fails
currently
also.
We
have
some
issues
with
the
cache
invalidation
and
some
issue
with
law
stock
notification.
A
Also
at
the
beginning
of
the
regression
we
start
with
a
problem
of
configurable
product
configurable
product
and
what
so
that
putting
configured
configurable
product
variation
into
into
the
shopping,
cart
and
making
a
check
out
with
a
configurable
product.
That's
why?
Actually,
at
the
beginning
of
week,
I
created
several
integration
tests
and
asked
guys
from
the
community
to
to
cover
this
functionality
with
additional
integration
tests
and
actually
because
because
we
had
a
gap
in
this
integration
test
coverage
for
configurable
product
and
actually
place
an
order
with
configurable
product,
we
we've
got
this
blocker
in
the
regression.
A
A
A
The
Monday
is
a
national
holiday
in
Ukraine.
It's
a
Holy
Trinity
day,
so
I
believe
that
in
the
middle
of
the
next
week
we
will
finish
all
the
all
the
regression
and
start
fixing
bugs
so
start
fixing
these
failed
scenarios,
and
afterwards
we
will.
We
will
run
another
cycle
of
the
regression
to
make
the
stabilization
to
stabilize
all
the
products
and
to
to
fix
it.
A
So
after
that,
we
will
make
all
the
test
cases
which
we
run
on
MSI
to
be
mandatory
for,
for
the
core
development
of
magenta
to
the
tree,
to
make
sure
that
magenta
to
the
tree,
development
don't
affect
MSI
and
the
will
would
not
break
Messiah
with
the
changes
on
magenta
to
the
three
core
changes
so
regarding
the
functionality
so
I
will
show.
You
I
already
mentioned
that
we
didn't
have
a
lot
of
time
to
work
on
a
new
functionality,
but
actually
I
have
something
to
show
you.
A
So
probably,
as
you
know,
our
take.
Our
main
idea
of
MSI
is
to
provide
fully
backward-compatible
software
for
those
who
made
an
upgrade
from
2.2
or
2.1
to
magenta
2-3,
with
msi
on
board,
so
to
make
it
possible.
Actually,
we
we
make
a
mess,
I
disabled
for
all
the
magenta
upgrade
version
and
we
make
Messiah
enabled
for
those
who
make
a
fresh
installation
of
magenta.
A
So
here
we
introduce
magenta,
inventory,
composer
installer,
and
this
is
actually
the
package
which
which
is
in
charge
to
check
whether
this
is
fresh
installation
or
whether
this
is
upgrade
of
early
version
of
magenta
to
to
the
magenta
to
the
tree,
and
you
see
that
the
Installer
is
installed
about
a
whole
other
magenta
modules.
And
now
you
see
that,
like
after
that,
magenta
all
the
inventory
modules.
A
Currently
we
have
32
modulus
as
a
part
of
the
bundle
package
of
MSI,
and
you
see
that
all
the
modules
like
recognized
as
a
part
of
the
multi-source
inventor
implementation
and
no
special
rules
applied
for
magenta
and
Entering.
So
all
of
these
modules
are
installed
successfully
and
you
see
this.
Actually,
that's
all,
but
if
we
are
making
an
upgrade
of
toodle-oo
to
that
one
or
two,
the
two
version
of
magenta
to
magenta,
with
msi
on
board
to
magenta
to
decieve
is
a
mess
on
board.
A
C
A
A
Here
we
lose
the
extension
points
and
msi,
not
not
tracking
this
data
and,
as
we
know,
most
of
the
inventory
inventory
customization
happens
on
the
level
of
database
interaction
because
of
first
of
all
because
of
the
performance
aspects.
That's
why?
Actually
we
we
just
disabled
this
modules
for
a
braid,
and
but
if
immersion
would
like
to
do
it,
he
can
just
he
can
just
switch
all
these
modules.
C
A
C
A
A
A
A
A
Inventory
modules
should
be
presented
for
the
upgrade
phase,
but
I
believe
that
could
be
done.
We
are
this
way
where
the
modification
of
the
composure
composure,
inventory
composure
package,
but
I
can't
right
now
answer
precisely
as
it
could
happen,
because
the
Mirko
bliss
he
was
working
on
the
functionality.
C
A
I
did
not
have
an
ability
to
make
it
code
reviews
it
sunshine,
but
I'm
pretty
sure
that
just
keeping
this
composure
package
will
will
give
you
an
ability
to
install
all
the
packages
and
all
the
packages
which
at
the
pendant
on
inventory
packages,
so
it
should
be.
It
should
fix
the
issues
regarding
the
message.
You
are
correct
that
message
currently
reference
magenta
modules,
but
not
computer
packages,
so
the
messages
should
be
corrected.
C
B
A
A
A
C
C
A
C
A
C
A
It
I
don't
know
for
sure
how,
but
they
said
that
if
we
create
like
dedicated
package
like
computer
installer
and
make
all
all
our
inventory
inventory
modules
to
be
dependent
on
this
one-
and
here
we
can
make
some
manipulation
on
the
level
of
metadata
I.
Don't
know
just
need
to
need
to
Google
about
it,
whether
it's
possible
or
not,
but
in
any
way
we
have
s.
Currently
we
have
a
solution
which
disabled
MSI
and
maybe
it
is
also
appropriate,
but.