Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up, so this
is just a heads-up: if you think that there is some fix, which should make
into the 5.6.0 final (which isn't in RC4) or if you think that there is
some blocker issue which should be solved before the 5.6.0 final release,
please drop me an email just to be sure.
Thanks!
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up, so
this is just a heads-up: if you think that there is some fix, which should
make into the 5.6.0 final (which isn't in RC4) or if you think that there
is some blocker issue which should be solved before the 5.6.0 final
release, please drop me an email just to be sure.Thanks!
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi,
just to clarify:
if no blocker issue is reported from php-5.6.0RC4, then we won't have
another RC, but php-5.6.0 (final) will be tagged using PHP-5.6.0RC4 as it
base, and maybe some commits cherry-picked (security fixes for example, or
changes with low impact like NEWS/UPGRADING/test fixes) on top of it.
so commits in the PHP-5.6 branch after the RC4 tagging won't be in the
final by default, only if you can convince me that we need that.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Please make sure these security fixes are included:
fileinfo:
Fixed bug #67716 (Segfault in cdf.c). (CVE-2014-3587)
gd:
Fixed bug #67730 (Null byte injection possible with imagexxx functions).
(CVE-2014-5120)
Thanks,
Kaplan
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up, so
this is just a heads-up: if you think that there is some fix, which
should
make into the 5.6.0 final (which isn't in RC4) or if you think that there
is some blocker issue which should be solved before the 5.6.0 final
release, please drop me an email just to be sure.Thanks!
--
Ferenc Kovács
@Tyr43l - http://tyrael.huHi,
just to clarify:
if no blocker issue is reported from php-5.6.0RC4, then we won't have
another RC, but php-5.6.0 (final) will be tagged using PHP-5.6.0RC4 as it
base, and maybe some commits cherry-picked (security fixes for example, or
changes with low impact like NEWS/UPGRADING/test fixes) on top of it.
so commits in the PHP-5.6 branch after the RC4 tagging won't be in the
final by default, only if you can convince me that we need that.--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up, so
this is just a heads-up: if you think that there is some fix, which should
make into the 5.6.0 final (which isn't in RC4) or if you think that there
is some blocker issue which should be solved before the 5.6.0 final
release, please drop me an email just to be sure.Thanks!
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi,
it seems that we have a blocker:
https://bugs.php.net/bug.php?id=67694
ps: thanks to Florian for pinging me about it, I missed this one :(
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up, so
this is just a heads-up: if you think that there is some fix, which should
make into the 5.6.0 final (which isn't in RC4) or if you think that there
is some blocker issue which should be solved before the 5.6.0 final
release, please drop me an email just to be sure.Thanks!
--
Ferenc Kovács
@Tyr43l - http://tyrael.huHi,
it seems that we have a blocker:
https://bugs.php.net/bug.php?id=67694ps: thanks to Florian for pinging me about it, I missed this one :(
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Kudos for Tjerk for the quick fix, which seems a rather small one-liner
fix, so I'm not sure to release another RC based on RC4 plus the security
fixes, the proper fix for https://bugs.php.net/bug.php?id=67865 and with
the fix for https://bugs.php.net/bug.php?id=67694, or to release the final
version based on RC4 + reverting
http://git.php.net/?p=php-src.git;a=commit;h=e4ff7f2ee346d641715694209e61704c9e815483
(which introduced https://bugs.php.net/bug.php?id=67865) and with the fix
for https://bugs.php.net/bug.php?id=67694.
Julien what do you think?
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up, so
this is just a heads-up: if you think that there is some fix, which should
make into the 5.6.0 final (which isn't in RC4) or if you think that there is
some blocker issue which should be solved before the 5.6.0 final release,
please drop me an email just to be sure.Thanks!
--
Ferenc Kovács
@Tyr43l - http://tyrael.huHi,
it seems that we have a blocker:
https://bugs.php.net/bug.php?id=67694ps: thanks to Florian for pinging me about it, I missed this one :(
--
Ferenc Kovács
@Tyr43l - http://tyrael.huKudos for Tjerk for the quick fix, which seems a rather small one-liner fix,
so I'm not sure to release another RC based on RC4 plus the security fixes,
the proper fix for https://bugs.php.net/bug.php?id=67865 and with the fix
for https://bugs.php.net/bug.php?id=67694, or to release the final version
based on RC4 + reverting
http://git.php.net/?p=php-src.git;a=commit;h=e4ff7f2ee346d641715694209e61704c9e815483
(which introduced https://bugs.php.net/bug.php?id=67865) and with the fix
for https://bugs.php.net/bug.php?id=67694.
Julien what do you think?
I'm more in favour of releasing a GA.
So, RC4 + sec fixes (that's OK) + revert of
e4ff7f2ee346d641715694209e61704c9e815483 (done in last 5.4 and 5.5
releases) + fix for #67694.
That's the safest path to have a GA soon (we are late) and on a stable
code basis.
Then we'll start our classical support plan, and have a 5.6.1RC1 in two weeks.
Julien.Pauli
Le 17/08/2014 11:25, Ferenc Kovacs a écrit :
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up,
so this is just a heads-up: if you think that there is some fix,
which should make into the 5.6.0 final (which isn't in RC4) or if
you think that there is some blocker issue which should be solved
before the 5.6.0 final release, please drop me an email just to be
sure.
Any plan to drop the -dev from some extensions version ?
Zend 2.6.0-dev
OPcache v7.0.4-dev,
mysqlnd 5.0.11-dev
sqlite3 0.7-dev
Remi.
Le 17/08/2014 11:25, Ferenc Kovacs a écrit :
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up,
so this is just a heads-up: if you think that there is some fix,
which should make into the 5.6.0 final (which isn't in RC4) or if
you think that there is some blocker issue which should be solved
before the 5.6.0 final release, please drop me an email just to be
sure.Any plan to drop the -dev from some extensions version ?
Zend 2.6.0-dev OPcache v7.0.4-dev, mysqlnd 5.0.11-dev sqlite3 0.7-devRemi.
--
Hi Remi,
I've planned to do it for Zend, but didn't think about the others.
I see no harm in removing those, so if nobody objects I think it would be
fine.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
On Mon, Aug 25, 2014 at 2:38 PM, Remi Collet remi@fedoraproject.org
wrote:Le 17/08/2014 11:25, Ferenc Kovacs a écrit :
Hi,
I'm planning to release 5.6.0 from RC4 if nothing serious comes up,
so this is just a heads-up: if you think that there is some fix,
which should make into the 5.6.0 final (which isn't in RC4) or if
you think that there is some blocker issue which should be solved
before the 5.6.0 final release, please drop me an email just to be
sure.Any plan to drop the -dev from some extensions version ?
Zend 2.6.0-dev OPcache v7.0.4-dev, mysqlnd 5.0.11-dev sqlite3 0.7-devRemi.
--
Hi Remi,
I've planned to do it for Zend, but didn't think about the others.
I see no harm in removing those, so if nobody objects I think it would be
fine.
in the end, I only removed the -dev suffix from the Zend version, because
all of the others have the same version number in 5.4 and 5.5, so was a bit
afraid that changing it would introduce last-minute problems.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu