►
From YouTube: PHP 7.2 support - weekly meeting, 15 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
So
what
I
worked
on
so
mostly
I
was
reviewing
pull
requests
that
we
had
right
now.
We
have
still
a
few
requests.
We
need
to
decide
what
so
for
the
raddest
one.
It
looks.
Okay,
I'm,
just
not
merging
it,
because
I
want
us
to
validate
it
on
cloud
that
everything
works.
Okay
and
we
will
not
break
cloud
so
I'm
working
with
internal
teams
to
to
do
that,
and
as
soon
as
it's
done,
I
will
merge
it.
A
This
one
is
pretty
old,
so
right
now,
I
worked
it
together
with
another
pull
request
with
this
one,
which
I
preferred
where
I
combined
all
the
libraries.
So
for
this
pull
request,
update
is
but
I
basically
received
some
feedback
and
I'm
processing
it
right
now.
I
have
one
problem
is
actually
this
required.
F,
section
composer
doesn't
like
it.
A
So
in
some
cases
it
worked
right
now
it
stopped
working
so
composer
reads
on
the
HP
versions
declared
in
the
choir
section,
so
I
discussed
it
with
Putra
and
we
agreed
that
we
can
do
Anand
and
move
the
72
version
in
to
require
section,
and
the
only
limitation
would
be
is
that
we
will
have
to
keep
this
branch
in
this
separate
reap.
Until
we
are
done
with
everything
so
I
guess
we
will.
A
We
will
have
a
branch,
probably
the
sleeps,
update
branch
that
I
created,
where
we
will
combine
all
the
fixes
that
cannot
work
without
72
support,
for
example,
some
libraries
which
we
can
just
deliver
without
the
72
support,
so
I
propose
to
move
on
with
other
tasks
that
can
be
merged
separately,
like
one
by
one
into
mainline.
I
was
out
to
this
declaration
and
everything
else
will
be
done
here
and
then,
when
it's
done,
we
will
no
ships.
A
So
my
goal
would
be
to
do
before
that
and
your
as
time
is
to
clean
up
this
branch
know
everything
enough
HP
from
acquire
dev
to
require
section
and
I
know
Patrick.
You
were
working
on
that.
If
you
want,
you
can
maybe
update
your
full
request
and
I
will
just
remember:
I
will
create
my
branch
and
merge
it.
So
if
you
want
to
do
it
in
this
task,
yeah.
A
Ok,
so
then
we
can
use
your
branch
and
I
will
then
be
just
reviewing
the
library.
So
there
was
a
proposal
to
update
symphony
for
to
version
4
and,
as
I
already
mentioned
in
the
chat.
Another
goal
that
we
have
is
to
upgrade
libraries,
so
I
think
it
totally
makes
sense
to
do
that.
So
I
will
update
it
to
version
4
and
we'll
see
what
we
can
do
with
it.
A
B
A
A
B
Which
version
of
Symphony
counsel
are
we
going
with
the
latest
stuff?
Are.
A
Symphony
for
Symphony
version,
four
I
think
if
I
think
version
four
should
be
fine,
so
I
was
updating
to
the
latest
versions
internally
in
a
separate
project,
and
let
me
see
so
I
used
composer
1.6
and
symphony
4-0
and
it
was
okay,
so
I
think
it
should
be
comfortable.
So
composer
latest
is
one
point:
six
right.
A
A
Okay
and
another
update
is
that
we
are
for
the
contribution
day
and
we
went
through
the
tasks
and
marked
some
of
them
as
suitable
for
contribution
day.
Also,
potentially,
we
will
go
into
Zen
framework
project
like
related
one,
where
we
want
Queen
options
and
project,
and
maybe
some
of
the
tasks
from
that
project
will
be
also
taken
into
contribution
day.
A
Okay,
so
basically
internal
you
were
discussing
some
design
for
moving
from
encrypt
to
lip,
sodium
and
I
think
we
will
be
publishing
in
document
soon,
so
the
community
can
look
it
into
it
and
then
we'll
move
on
with
in
that
direction.
So
basically
there
are
some
some
challenges.
Definitely
like
is
especially
in
the
case
that
we
have
to
support
both
HP
sound
at
one
and
seven
to
two
and
those
versions
have
different
default
library
is
installed
so
yeah,
probably
that's
the
Update
button,
I
guess
I
hope
you
will
have
more
details
soon.