►
From YouTube: Import/Export Weekly Call 28th March 2018
Description
Recording of the import/export weekly call from the 28th of March 2018.
This project focuses on the https://github.com/magento-engcom/import-export-improvements repository with the aim to provide some key bug fixes in the 2.3 release of Magento 2.
If you would like to get involved in the project please see the github issues or contact the Magento Community Engineering team for more information.
A
All
right,
this
is
the
import/export
weekly
meeting
for
the
28th
of
March,
which
is
means
the
year
is
going
quite
quickly.
We
update
from
my
side.
We
had
the
distributor
contribution
day
last
week
and
unfortunately,
I
didn't
have
time
to
go
through
the
import/export
as
it
was,
but
we
did
get
to
other
poor
request
for
import/export
during
that
day,
not
specific
tasks
we
picked
up
but
specific
to
they
were
just
generic
tasks
as
part
of
import
export
and
they
were
in
the
project.
A
A
Look
through
the
code
code,
looks
fine,
it
works
products
and
for
customers,
and
but
what
I'm
gonna
do
is
get
an
enterprise
set
up,
yeah,
an
enterprise
testing
environment
just
to
double-check
that
it
was
how
the
attribute
was
created
rather
than
any
of
the
code
after
that,
we'll
be
happy
to
merge
this
one.
So
that's
good.
A
The
empty
value
support
rows.
I've
tried
to
contact
Peter,
but
he
has
not
got
back
to
me,
which
is
a
bit
of
a
shame.
We
got
some
response
from
QA,
but
what
I
would
suggest
we
do?
Is
we
wait
until
we're
finished
with
our
current
tasks?
If
he
hasn't
got
back
to
us
by
then,
then
we
one
of
us
can
just
take
it
up
at
that
point,
yeah
and
next
week
next
week,
yeah
on
the
fifth
so
the
first
thing.
A
Next
week
there
was
a
contribution
day
in
Milan
which
I
will
be
at
and
with
Andrew
as
well.
She
unfortunately
can
make
this
cause
she's
quite
busy
with
that
event,
because
it's
part
of
a
conference,
and
but
during
that
the
plan
is
for
me
and
her
to
work
through
import
exports.
So
I
should
have
a
good
full
full
day
with
her
working
through
probably
her
tasks
and
maybe
a
couple
of
other
tasks
at
that
point
yeah.
That
is
basically
my
update
at
the
moment.
B
Continued
working
on
101
I
also
participated
in
the
contribution
day
in
Argentina
last
Saturday
so
use
some
of
that
time
to
make
some
progress
in
this
one,
I
already
identified
quite
a
few
integration
tests
that
I
need
to
work
on
I
already
started
working
on
those
I
didn't
finish
yet,
but
I
guess
I
will
get
that
done
today
or
tomorrow.
Perhaps
also
there
is
a
question
in
that
ticket
from
our
guru,
which
says
what
happens
when
the
user
doesn't
feel
the
SKU
field,
and
he
says
that
we
should
consider
that
use
case
for
this
issue.
B
A
Yeah
so
like
a
certain
next
week,
we
have
the
contribution
during
so
hopefully
we
can
progress,
issue
61,
which
is
the
translation
issues
of
Lee
yeah.
We
can
sit
down
and
get
get
through
on
that
other
those
issues
yeah
there
isn't
actually
that
much
left
to
pick
up
so
I
think
we're
pretty
pretty
good
on
time
for
the
April
release.
The
only
issue
I
can
see
they
might
hold
it
up
would
be
the
anti-roll
value
so
yeah,
like
I,
said
once
once
we
finished
with
our
current
tasks.
A
One
of
us,
I
guess,
can
work
on
to
that
next,
one,
my
focus
will
be
the
test
that's
assigned
to
me
at
the
moment,
the
filtering
and
then
next
week
to
do
the
one
with
Andrew
during
the
contribution
day.
So
after
those
two
and
after
your
two,
then
we
could
and
figure
out
what
the
best
steps
are
next
and
we
did
have
a
few
pull
requests
from
Adam,
but
Adam
is
in
and
out
of
the
project
when
he
has
time
basically
which
I
knew
from
the
start.
A
So
that's
okay
and
he
does
have
a
few
things
assigned
to
him.
So
I'm
gonna
reach
out
to
him
as
well,
just
to
just
to
double
check
if,
if
he's
still
interested
in
working
on
them
and
if
he
would
be
able
to
do
it
in
the
next
month
or
so,
I
think
is
pretty
much
how
much
time
we've
got
at
the
moment
again.
A
lot
of
the
changes
will
be
doing
won't
be
breaking
changes,
so
if
they
come
in
in
future
releases,
that's
not
a
problem.
I
think.
A
As
far
as
I
understand
all
of
our
changes
aren't
breaking
now
or
are
backwards
compatible,
and
so
we
should
be
okay
with
regards
to
getting
them
in
2.3
and
then
keeping
providing
changes
after
2.3
yeah
all
right
fabulous.
Thank
you
very
much.
Man
and
I
will
see
you
yeah
see
you
soon.
If
you
need
anything.
Just
let
me
know,
of
course,
all
right.
Thanks.