►
From YouTube: PHP 7.2 support - weekly meeting, 15 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
A
A
A
Okay,
then,
there
is
one
more
pull
request,
which
updates
a
few
libraries
it's
from
Mohammed,
it
updates
and
the
Misses
and
view
and
credits,
libraries,
so
I
reviewed
the
pull
request
and
also
worked
on
internal
requests,
update
Enterprise
Edition
with
the
same
dependent
new
dependencies.
Everything
looks
good
right
now.
A
We
want
to
verify
that
new
credits,
library
works,
ok
on
magenta
cloud
and
Jacob
from
magenta
team
help
so
he's
working
on
trying
to
install
magenta
to
the
tree
from
our
branch
on
on
the
cloud
it's
still
on
PHP
7.1,
but
we
want
to
make
sure
that
we
don't
break
anything.
So
this
is
status
about
this
pull
request.
A
A
So
this
is
leaves
a
great
branch
and
if
you
look
into
composer
the
JSON
file,
we
updated
version
of
PHP,
so
it
doesn't
have
17
0
and
it
has
72
also
all
composer.
The
JSON
files
from
in
the
modules
are
updated,
whole
in
modules
and
all
the
components
in
framework,
and
also
it
includes
some
updates,
like
symfony
components,
to
the
latest
version
and
a
few
other
libraries
which
are
like
related
to
each
other,
which
can
not
be
updated
separately
like
HPC
s,
fixer,
I,
think
and
a
few
other
ones.
A
A
A
So
if
you
work
on
any
task
that
fixes
tests,
for
example,
after
upgrading
the
libraries
you
should
work
in
this
branch
and
I-
went
through
the
tickets
basically
and
marked
such
tickets,
not
what
I
added
a
note
here
that
this
ticket
should
be
work
should
use,
leaves
upgrade
branch
for
the
work,
so
means
that
you
should
create
your
your
feature,
branch
from
from
leaves
of
Greg
branch,
and
you
should
use
this
leaves
of
great
branches,
a
target
for
your
pull
request.
I
added
this
information
edit,
this
information
in
our
weekend.
A
So
if
you
go
to
wiki
and
open
approach
to
implementation,
there
is
a
work,
breakdown,
structure,
section
and
it
describes
the
purpose
of
leaves
a
great
branch.
So
basically
we
will
implement
all
the
fixes
and
then
we
will
also
go
and
perform
some
manual
testing
if
necessary,
and
after
that,
when
the
branch
corresponds
to
all
our
requirements.
Like
definition
of
done,
we
will
merge
it
to
to
the
tree
development.
It
will
go
to
the
mail
until
that
time
we
will
work
in
with
subgrade
branch.
A
It's
not
the
case
for
all
the
issues,
because
some
of
them
can
go
directly
to
to
the
tree
and
develop
because
they
don't
depend
on
those
libraries
that
are
updated.
For
example,
current
will
request
with
all
those
libraries
it's
independent,
so
we
can
merge
it
directly
to
two
to
three
little.
Bread
branch
is
not
of
the
updated
automatically
right
now
from
to
the
three,
so
I
think
I
will
be
updating
it
thinking.
A
So
that's
about
the
new
branch
that
we
have
and
then
one
more
update
is
about
functional
tests.
So,
as
you
may
know,
Magento
has
two
frameworks
which
is
the
older
one
is
MTF
and
the
newer
one
is
M
FTF.
We
still
use
both
kinds
of
tests
and
right
now,
our
our
team
internal
team.
That
is
responsible
for
those
frameworks.
They
are
working
on
making
them
compatible
with
hp7
do
two,
so
we
should
be
able
to
run
functional
tests
on
PHP
seven,
two,
two
and
four.
A
Now
it
like
their
estimation
is
that
it
should
be
ready
somewhere
next
week,
so
hopefully
we
will
be
able
to
run
functional
tests
as
well.
So
this
is
a
bedroom
from
my
side,
another
update
is
I
just
wanted
to
introduce
people
who
joined
the
project
from
internal
magenta
teams,
so
we
already
had
been
and
Jakob
joined,
joined
before
before
the
last
meeting
last
call.
Now
we
also
have
John
and
Daniel,
so
John
and
Daniel
are
working
mostly
on
fixing
libraries
like
a
upgrade
of
the
libraries,
so
they're
working
in
the
lives
of
great
branch.
A
Daniel
is
working
on
our
internal
tools
right
now,
so
he
is
fixing
the
tools
to
be
able.
Suite
should
be
able
to
run
to
run
all
our
bamboo
builds,
I'm
going
to
and
gentles
builds
and
yeah
burn
and
Jacob
are
focusing
on
central
corner
right
and
now
we
also
have
Ilya
who
works
on
encrypt
problem
with
speech.
P7
do
so
he's
investigating
and
right
now.
A
Okay:
okay,
what
else
update
on
Zen
framework,
one
so
Ben
was
investigating
the
usages
of
Zend
framework,
one
even
more,
and
he
searched
through
Magento
cloud
and
whether
we
have
any
essential
usages
there
like
an
additional
usages
to
what
we
found
in
marketplace
before
there
are
just
a
few
of
them.
So
it's
the
big
difference
looks
like
and
van
has
a
list
of
libraries
that
can
be
removed
from
centromere
without
impacting
anyone,
so
he
will
be
delivering
to
request
about
it
soon.
A
Okay,
so
yeah
he
worked
on
the
sunshield
usage
is
removal
in
magenta
to
code.
So,
as
I
mentioned
before
this
pull
request
and
what
we
are
processing,
this
poo
request.
Now
we
are
emerging
it
tonight.
I
saw
everything
and
also
he
worked
on
fixing
incompatibility
issues
with
HP
7
to
2
in
Zen
framework
one.
So
she
fixed
such
things
as
usage
of
each
create
function
and
introduced
edges
of
count
and
also
he
removed
the
XML
RPC
library,
because
it's
not
really
used,
and
it
has
some
records
incompatible
issues
with
HP
7.
Due
to
all.
A
This
is
nourished
right
now
in
the
master
branch
of
our
project,
repository
for
which
we
something
to
support
in
some
framework
one,
and
when
we
will
be
done,
it
is
entering
a
quandary
ownership
to
the
main
repository
and
magenta
sent
from
your
phone
and
will
release
a
new
tag
for
it.
So
we
will
start
depending
on
the
real
released
version.
But
right
now
we
are
working
just
in
this
repository.
A
Okay,
so
those
were
updates
from
been
he
couldn't
join.
Unfortunately,
he
has
another
meeting
and
he,
as
I
mentioned
before,
Jacob
doe
he's
working
on
Zen
framework,
one
and
mostly,
but
right
now
he's
helping
with
validating
or
fixes.
On
the
cloud
instance,
then
John
was
working
on
the
lips
of
great
branches
and,
as
I
mentioned
before,
so
right
now,
she's
fixing
tests
and
yeah
and
they
think
that's
all
from
my
side.