Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73693
Return-Path: <julienpauli@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 4199 invoked from network); 15 Apr 2014 08:34:32 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 15 Apr 2014 08:34:32 -0000
Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.182 as permitted sender)
X-PHP-List-Original-Sender: julienpauli@gmail.com
X-Host-Fingerprint: 209.85.128.182 mail-ve0-f182.google.com  
Received: from [209.85.128.182] ([209.85.128.182:39900] helo=mail-ve0-f182.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 48/A0-27880-71FEC435 for <internals@lists.php.net>; Tue, 15 Apr 2014 04:34:31 -0400
Received: by mail-ve0-f182.google.com with SMTP id jw12so9029841veb.27
        for <internals@lists.php.net>; Tue, 15 Apr 2014 01:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type;
        bh=B34NpvSKiOk+xxj3QeI5s5OqJWxC7BkyHNKO/NpWatA=;
        b=uXefKErF1GJbl4GYGgV33f+0x2SYosdf3/OxCZChIqDASOLZhbOI1OkzzwNnc0IlnH
         pREHw+YDLDRCi7wpOChUusVsV9a+R+AaksueOpkSwr6K+Tts3GFmfweVucxvL9q5jLqA
         +JnazT6XXRJSlyv/GobOHcCizC7dP10DazioCFxZXWUoXekEn3o4x1pjLRs+Okpat2Si
         6YY6Ow4MVKeJ+54oJVUpX3LizRc611WXu9sF32gtLkqmhJOEmFO0aqBNTu+d3i768499
         ingI4YFos17gP298vdSnalSGIMGwhXTlbRXoKvHC+5esW6mYn+dfTkHrN6G6BwkWOCCm
         G68w==
X-Received: by 10.52.251.199 with SMTP id zm7mr179091vdc.21.1397550868889;
 Tue, 15 Apr 2014 01:34:28 -0700 (PDT)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
Received: by 10.220.81.68 with HTTP; Tue, 15 Apr 2014 01:33:48 -0700 (PDT)
In-Reply-To: <534C2133.8010402@sugarcrm.com>
References: <534C2133.8010402@sugarcrm.com>
Date: Tue, 15 Apr 2014 10:33:48 +0200
X-Google-Sender-Auth: MpySyKi2sSbnKvG6qjffc2vuI0k
Message-ID: <CAMUwpuQ495nqk08Se1oKC5bpsNSBBVyAyi+uNtPctbsC+sDAtA@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] keeping unit tests green
From: jpauli@php.net (Julien Pauli)

On Mon, Apr 14, 2014 at 7:56 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
> As promised, I have created an RFC on unit test policy, here:
> https://wiki.php.net/rfc/travis_ci
>
> Please discuss. Any comments/suggestions/corrections welcome.

Hi,

This looks like something we already do nowadays, except we (well, I)
don't go to watch for the CI but look after the tests in the branch
I'm as RM managing.

So I'm OK, as soon as it is simple.
For example, I dont know Travis. So when opening the Travis page about
PHP, I see many things, red or green, and feel like lost in all those
informations.
I don't know where to look to find quickly that something went wrong, and why.
So if we could have on the wiki a page explaining how to manage Travis
builds, I would be more than happy :-)

Thx.


Julien.P