Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73698
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <534C2133.8010402@sugarcrm.com>
References: <534C2133.8010402@sugarcrm.com>
Date: Tue, 15 Apr 2014 13:49:28 +0200
Message-ID: <CAEZPtU4qYezOBrHtp2QNo93PBHL_zCHpDyryZ02ERn1hXGk5AQ@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: pierre.php@gmail.com (Pierre Joye)

Hi Stas,

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.


I very much like this idea, a must do.

I also like to extend it more:

- for stable branches, I would like a staging branche where all of us
can commit, RM can then cherry pick stable patches for a given branche

- add static analyzers to the staging branch (gcc, clang, VC and PVS,
that will covers much issues including vicious 64bit issues
   . it could be possible to do it per commit

- try as much as possible to get warning free commits, linux and
partially windows. Windows may have false positive while it will be
drastically reduced once we have the int64 patch in

Doing so we will always be able to do security releases very
efficiently and safely

I do not care much about the wording, unit tests vs whatever the name is :)

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org