Re: BC break in 5.4.29 and 5.5.13
| From: | Johannes Schlüter | Date: | Tue, 03 Jun 2014 16:07:04 +0000 |
| Subject: | Re: BC break in 5.4.29 and 5.5.13 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74722@lists.php.net to get a copy of this message | ||
On Tue, 2014-06-03 at 17:59 +0200, Marco Pivetta wrote:
> On 3 June 2014 17:55, Johannes Schlüter <johannes@schlueters.de>
> wrote:
>
> We send out RCs two weeks before a release, but receive barely
> any
> feedback. I'd love if external projects would verify those and
> raise a
> red flag ...
>
>
> We don't have the resources to test against RCs, and we don't have any
> CI environment on our own except for travis-ci (which is what most
> projects currently use).
>
> Maybe push a
php-nightly binary to the Travis folks instead?
> We'd
> gladly test against that, and even if people won't report immediately,
> the travis API is simple enough to allow mining on the builds to
> discover problems eagerly.
>
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.
Speaking about resources: The core PHP team is very small, way to small
to keep up with a relevant amount of projects all moving.
johannes