Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21271
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43A5B727.1030107@prohost.org>
Date: Sun, 18 Dec 2005 14:23:19 -0500
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Lukas Smith <lsmith@php.net>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <43A5B487.6070405@php.net>
In-Reply-To: <43A5B487.6070405@php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] supported OS/platforms
From: ilia@prohost.org (Ilia Alshanetsky)

Lukas Smith wrote:
> As per the release check list that Derick and Ilia wrote up [1] we now
> have something called "primary testers". This is a list of projects per
> php branch that will get directly notified of php RC's. We have one for
> PHP 4.x [2], 5.x [3] and 6.x [4].

I disagree with you in that respect, I received a fair amount of input
from our test projects. One of the responses lead to a resolution of a
nasty bug affecting smarty templating system and through it the project
being tested. If we get A LOT of feedback it means our release is badly
broken ;-).

> Now as far as I know the level of success has not been all to great, but
> atleast it should push some responsibility to the given projects if we
> happen to have a release snafu. Maybe we can make this more high
> profile, by having some buttons "official php primary tester", you know
> for the warm fuzzy feeling ;-)

I think it is fine as is.

> Anyways I remember some discussions about this on internals (or maybe it
> was a PEAR meeting) about what platforms to support. Obviously this is a
> question on what the developers focus and also on what we test on.

I see no reason to add limits on the supported platforms, the bottom
line if you can compile PHP on your platform of choice it is technically
supported.

> Especially with the emergence of the gcov setup [5][6] we also have a
> nice setup to make the testing automated with pretty reports and even
> visual gadgets.

gcov shows code coverage it does not tell if you the code is working or
not. If anything it is a tool to help devise tests that would examine as
much code behavior as possible.

Ilia