►
From YouTube: PHP 7.2 support - weekly meeting, 22 Feb 2018
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
A
A
A
A
Also
I
created
I
added
I
added
tasks
for
updating
libraries,
like
other
libraries,
which
do
not
impact
which
piece
of
the
tool
basically
but
which
we
still
want
update,
and
they
include
investigation
results.
So
most
of
them
don't
need
any
big
changes,
so
there
are
just
small
issues
with
some
of
them
and
some
of
them
even
like
theoretically,
don't
have
any
issues.
So
we
have
several
of
these
tasks.
A
So
here
dated
the
composer
library
and
also
Symphony
console
to
the
version
that
we
want
to
update
in
the
magenta
as
well,
which
vision
it
was
updated
to
6.2,
but
I
don't
know,
maybe
we
will
want
to
update
it
to
7.0.
I
was
looking
at
draw,
not
so
big
difference
with
differences
between
version,
6
and
7.
So
if
we
are
updating,
then
we
probably
can
update
to
the
version
7
but
potential
you
can
do
it
in
a
separate
task
related
to
a
dedicated
to
PHP
unit.
A
A
Mmm-Hmm
he
removed
the
library
I
just
changed
the
target
branch,
because
I
think
we
can
like
merge.
This
change
directed
to
two
to
three
develop.
It
has
no
dependencies
on
other
libraries
and
Ramon
was
making
a
request
in
Rome
branch,
which
you
cannot
merge
to
the
main
line.
So
right
now
we
are
finishing
code
review
for
that
and
I
think
it
should
be
easy
to
merge
this
one.
A
I
bought
I'm
creeped,
so
Greg
is
working
on
the
finalizing
and
schody
and
public
18
publishing
it
to
the
community.
So
I
guess
she
still
wants
internal
architects
to
look
at
it.
I
think
it
should
happen
in
the
nearest
days
and
then
we'll
publish
it,
so
everybody
can
can
look
at
it.
So
basically
we
want
to
move
to
live
sodium,
mostly,
but
I
think
for
magenta
7.1.
We
might
for
teach
peace
under
21.
We
might
want
to
to
use
encrypt
the
library
as
well
norm
clean
crypt,
compartment,
ID
design.
B
B
So
so
we're
kind
of
safe
to
some
extent
like
if
we
are
not
on
time
with,
like
removing
everything
and
we
let's
say,
suppress
the
notices,
deprecated
notices,
we
still
have
kind
of
time,
also
7.3,
okay.
The
second
question
is:
was
anyone
able
to
just
run
if,
like
just
you
know,
disabled
notices,
duplicated
notices
run
the
full
a
built
on
seven
but
to
see
what
really
fails.
A
Yeah,
what
I
did
I
was
running,
builds
and
I
was
running.
Magento
I
was
just
like
applying
some
workarounds
to
the
items
which
which
produce
errors
or
warnings.
So
there
are
some
fatal
errors.
There
are
application,
notices
and
I
was
applying
workarounds
for
those
ones
too,
like
bypass
them
and
yeah.
So
it's
kinda
working
I've
had
issues
with
of
cache,
enabled
for
product
creation
flow
I
couldn't
create
a
product,
but
without
a
brush,
I
could
create
a
product
and
I.
Think
I
even
could
check
out
with
the
check
out.
I
need.
C
A
B
A
B
A
A
A
B
A
So
this
is
total
usage,
total
bees
marketplace
so
basically,
I
have
a
file
which
contains
all
the
marketplace
usages
and
below.
Volodymyr
whiskey
was
counting
usages
in
the
Magento
and
then
he
combined
all
those.
So
in
the
end
we
have
this
list
of
items
which
are
not
used
directly
in
marketplace
or
in
Magento
itself,
but
many
of
them
are
used
indirectly,
so
like
another,
Sion's
and
library
depends
on
them.
So
I
was
analyzing.
This
and
I
came
up
with
the
least.
A
A
A
C
B
A
A
C
Let's
looks
good
from
my
side:
I
had
a
talk
yesterday
with
Christian
from
n98
and
he
was
concerned,
but
he
was
interested
to
know
how
it's
going
to
be
kind
of
communicated
like
it's
all.
It's
fine
for
us
to
remove
the
Zen
framework,
one
stuff,
but
it
would
be
like
you
can
see
whether
things
are
used
in
marketplace
or
external
developers.
C
You
know
and
having
a
having
a
good
I,
don't
know,
release
notes
or
whatever
to
describe
what
we've
done
and
why
here
here
is
important
with
this
one
I
guess
in
terms
of
the
tasks
yeah,
it
has
look
good
I,
like
the
approach
to
upgrade
when
possible
or
replace
them,
otherwise
fixing
the
compatibility.
I
know
there
is
still
a
one
ongoing
core
request
in
the
community
engineering
teams.
C
With
these
end
feed,
I
think
it's
an
feed,
so
I
think
that
would
be
yeah
another
good
one
I
don't
know
if
that's
an
72
compatible
or
not,
but
it's
a
yeah.
It
might
be
good
I
think
that's,
probably
the
one
you
gene-
or
you
know
saying
yes
there
today,
but
that
would
be
a
good
one
as
well.
The
process
I
think
yeah.
A
A
B
C
B
C
B
C
Yeah
yeah
I
can
compression
see
see
if
we
have
any
more.
What
I
can
do
is
you
can
also
mention
it
as
part
of
with
the
team
and
see
if
you
have
those
running
projects
and
stuff
can
kind
of
mention
it
to
the
people
in
their
projects.
I
think
especially,
things
like
minecraft
there'll
be
a
lot
of
interest
in
replacing
that.
B
And
just
just
additionally,
you
know
David,
this
is
kind
of
you
know
the
uncertainty.
If
we
are
going
to
do
that
or
not
it's
also
introducing
a
lot
of
issues
like
you
know
the
DevOps
process,
we
don't
know
what
testing
environments
we
should
prepare
for
regression.
You
know
what
builds
you
should
have
seven
tours
and
run
and,
and
you
just
like,
creating
a
lot
of
confusion
in
other
places.
So
the
sooner
we
know
like,
oh,
you
know
we'll
be
able
to
do
that
on
time.