Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74722 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16906 invoked from network); 3 Jun 2014 16:07:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jun 2014 16:07:25 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.215.10 mail.experimentalworks.net Received: from [217.114.215.10] ([217.114.215.10:45350] helo=mail.experimentalworks.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 08/A9-64944-CB2FD835 for ; Tue, 03 Jun 2014 12:07:25 -0400 Received: from [192.168.2.31] (ppp-93-104-13-22.dynamic.mnet-online.de [93.104.13.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: johannes@schlueters.de) by mail.experimentalworks.net (Postfix) with ESMTPSA id 49F3F40D4C; Tue, 3 Jun 2014 18:07:23 +0200 (CEST) To: Marco Pivetta Cc: Benjamin Eberlei , Remi Collet , julien pauli , PHP In-Reply-To: References: <53886F73.70402@php.net> <1401810913.2282.81.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Date: Tue, 03 Jun 2014 18:07:04 +0200 Message-ID: <1401811624.2282.86.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] BC break in 5.4.29 and 5.5.13 From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Tue, 2014-06-03 at 17:59 +0200, Marco Pivetta wrote: > On 3 June 2014 17:55, Johannes Schlüter > 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