Re: 5.3 final release

bump. On Tue, Jul 8, 2014 at 5:48 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote: > > > > On Sat, Jun 14, 2014 at 2:45 PM, Johannes Schlüter <johannes@schlueters.de > > wrote: > >> Hi, >> >> On Fri, 2014-06-13 at 16:38 -0700, Stas Malyshev wrote: >> > As decided in https://wiki.php.net/rfc/php53eol, 5.3 >> > EOL is 1 year >> after >> > the 5.5.0 release, which is on June 20th. Do we want to make one last >> > release before EOL with latest security patches (probably in sync with >> > 5.4/5.5 releases planned for June 29)? If so, I can scan the logs and >> > backport the recent security-relevant patches. Last 5.3 was half a year >> > ago so we probably have some, even with remote exploit potential. >> >> The last time this was discussed on security@ I intended for "having one >> release in July to send 5.3 to eternal sleep" I still plan to do that. >> >> I won't directly sync with 5.4/5.5, though (unless there is a critical >> issue requiring this) to have different news. I expect this final EOL to >> receive more media echo which shouldn't hide other releases. >> >> If there are specific changes you want to see in there please send a >> note to me (cc security@), I'll check myself, too. >> >> johannes >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > Hi Johannes, > > I would like to cherry-pick > > http://git.php.net/?p=php-src.git;a=commit;h=4d804aa52d8c74ddcbdb07694b75b38c5eba8004 > into PHP-5.3 so that > REPORT_EXIT_STATUS=1 make test > can be used on every php version provided by travis. > currently one has to either manually execute run-tests.php or grepping the > make test output for failures. > Would that be ok with you? > > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu > -- Ferenc Kovács @Tyr43l - http://tyrael.hu