►
From YouTube: PHP 7.2 support - weekly meeting, 8 Mar 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
So
I'll
start
from
my
side.
I
was
working
on
what
I
was
working
with
internal.
The
ops
team
on
making
internal
be
ready
for
HP
sounded,
and
it's
done
now
we
can
run
all
our
builds
on
PHP
72
as
well
as
there
are
no
builds
that
can
be
run
on
seven
to
zero.
So
we
won't
have
you
shouldn't
have
issues
after
after
the
symphony
for
a
great
task
is
done,
which
basically
includes
also
removal
of
PHP
seven
seven
to
zero.
So
this
is
one
thing
that
I
was
doing.
I
was
also
reviewing
the
pull
request.
A
A
Think
that's
it
about
this
poor
quest
processing
it
right
now
there
were
some
change,
the
changes
that
we
agreed
to
and
those
are
removal
of
the
changes
from
functional
tests,
because
we,
we
will
probably
be
doing
it
in
a
separate
task,
because
functional
tests
can
be
run
as
a
separate
process.
So
it's
not
really
necessary
to
to
update
their
versions
right
now,
and
it
may
also
involve
some
framework
changes,
so
it
may
make
our
task
bigger.
A
So
that's
one
thing,
then
another
thing
is
I
want
to
remind
about
the
design
document
for
removing
encrypt
and
adding
with
sodium.
So
right
now
there
was
one
round
of
review
internally
with
his
architects,
and
there
was
some
feedback
and
updates
made.
So
now
we
are
in
the
second
round
of
the
review.
I
think
we
will
be
updating
this
document
soon
and
then
one
organizational
thing
I
added
the
milestone
here,
which
is
two
three
zero.
A
I'm
cretins
and
framework
are
still
in
investigation
and
they
think
when
you
have
someone
that
is
here.
So
basically
we
have
two
more
people
joining
us
from
magenta
team,
it's
Ben
and
Jacob,
so
they
are
helping
us
all
work.
It's
all
based
from
my
side,
and
maybe
you
want
to
go
through
what
you've
been
doing.
B
Sure
so,
for
my
work,
I
was
taking
a
look
at
our
usage
of
gs1
components
as
well
as
any
usage
we
could
find
in
the
marketplace
and
so
kind
of
building
off
of
some
Volga's
previous
work.
On
doing
this
analysis,
I
was
able
to
see
their
trim.
Do
this
right,
hey
cool,
updated
spreadsheet,
with
individual,
then
modules
as
well
as
our
usages.
B
So
you
can
see
here
our
usage
in
Magento
in
a
different
pieces
and
products
within
our
or
company,
and
then
looking
at
these
intercept,
that's
in
the
marketplace
and
filtering
out
lines
that
were
comments.
Previous
versions
of
modules
or
any
modules
that
were
simply
just
not
supported,
not
had
basically
been
abandoned.
B
So
I
kind
of
operate
in
a
sauce
to
be
that
the
less
code,
the
better
so
I,
should
in
a
little
while
live
this
morning,
have
a
final
list
of
these
modules.
That
I
propose
that
we
eliminate
entirely
that
should
not
cause,
or
at
least
cause
minimal
backwards,
compatibility
issues
for
ourselves
or
our
integrators
and
maintain
make
it
easier
for
us
to
maintain
them
going
forward
and
not
worry
about
this
issue
and
7.3
comes
out.
A
Yeah,
thank
you
and
just
some
background
for
people
who
just
joined
so
why
we
have
some
framework
here
is
because
Zen
framework,
one
is
not
maintained
by
sound
anymore,
as
you
may
know,
and
magenta
has
to
maintain
it
because
we
still
use
it.
So
our
goal
and
scope
of
this
project
is
to
make
as
an
framework
one
compatible
with
speech.
P72,
and
one
of
the
approaches
that
we
have
is
just
to
clean
up
the
azan
framework.
So
I
mean
we
remove
libraries
that
are
not
used,
so
it
should
reduce
our
scope
of
work
for
72.
B
A
A
B
A
A
So
I
think
will
be
and
will
have
some
social
some
proposed
solution
soon,
we're
still
considering
whether
we
really
should
migrate
to
live
sodium
and
refactor,
or
encryption
implementation
a
little
bit
or
should
we
just
make
the
smallest
changes
possible
just
to
make
just
to
make
magenta
to
the
three
compatible
there's
a
seven
PHP
72
and
in
that
result
approach
we
might
just
use
encrypt
and
crypt
compat
library,
so
we
can
still
move
on
to
the
sound
it
to
so
yeah.
That's
that's
all
updates
any
questions.