Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74721
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1401810913.2282.81.camel@guybrush>
References: <53886F73.70402@php.net> <CAEPJdunEaCHaBvzQ+AJiO5tLGW2NhW53fot1hztNXkV+sUDNSQ@mail.gmail.com>
 <1401810913.2282.81.camel@guybrush>
Date: Tue, 3 Jun 2014 17:59:26 +0200
Message-ID: <CADyq6sKfUU_v+vSaCTFijxcu3PW4HGD7sU5SQS+fdaERhtn3rA@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Benjamin Eberlei <kontakt@beberlei.de>, Remi Collet <remi@php.net>, julien pauli <jpauli@php.net>, 
	PHP <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2ba7cd305ea04faf0993f
Subject: Re: [PHP-DEV] BC break in 5.4.29 and 5.5.13
From: ocramius@gmail.com (Marco Pivetta)

--001a11c2ba7cd305ea04faf0993f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 3 June 2014 17:55, Johannes Schl=C3=BCter <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.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--001a11c2ba7cd305ea04faf0993f--