Re: BC break in 5.4.29 and 5.5.13
| From: | Marco Pivetta | Date: | Tue, 03 Jun 2014 16:17:20 +0000 |
| Subject: | Re: BC break in 5.4.29 and 5.5.13 | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74723@lists.php.net to get a copy of this message | ||
On 3 June 2014 18:07, Johannes Schlüter <johannes@schlueters.de> wrote:
> Nightly testing (or push testing) I see on our side. The issue with
> testing applications is that we need the time from the individual
> project maintainers. Not knowing the application it often is quite hard
> to dig down what in the underlying systems broke. Project maintainers
> typically an pinpoint this faster.
>
Pushing a "nightly" package to Travis would solve this issue almost
entirely.
> Speaking about resources: The core PHP team is very small, way to small
> to keep up with a relevant amount of projects all moving.
>
There's an already working test suite by the HHVM folks at
https://github.com/facebook/hhvm/blob/1ecb4443d95c2e2659028f148083dd5c85f2099b/hphp/test/frameworks/frameworks.yaml
In the eventuality in which PHP-SRC retains control over the CI environment
that runs the framework tests, this suite could be reused. The problem is
that it actually takes days to run all those tests, and I don't know if the
hardware is available.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/