Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118224
MIME-Version: 1.0
References: <d748efe6-c2c5-f082-3ba2-eac94c5d8e47@gmx.de>
In-Reply-To: <d748efe6-c2c5-f082-3ba2-eac94c5d8e47@gmx.de>
Date: Fri, 8 Jul 2022 09:24:13 -0500
Message-ID: <CAESVnVpsDQcWWE+GpXQpSkp8tPjYvpbyhGbgV5fybSsG26ssmw@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007ec6cb05e34bf5f2"
Subject: Re: [PHP-DEV] What to do with qa.php.net?
From: pollita@php.net (Sara Golemon)

--0000000000007ec6cb05e34bf5f2
Content-Type: text/plain; charset="UTF-8"

On Thu, Jul 7, 2022 at 11:54 AM Christoph M. Becker <cmbecker69@gmx.de>
wrote:
> I wonder what we should do with qa.php.net.
>

I too have wondered this many a time.

> The only really relevant stuff on the Website is the listing of
> available QA releases, and the information on how to write PHPT test
> cases.  In my opinion both should be moved to somewhere else (the PHPT
> docs might go into the php-src repo, and the available QA releases could
> be listed on php.net).  Afterwards I suggest to tear down the Website.
>

100% This.  PHPT can easily go in the primary manual (it's aimed at people
writing PHP code and PHPT files are PHP code!).
The QA releases as well, it would honestly save some (small) hassle during
releases to only have to touch one repo with this information.

-Sara

--0000000000007ec6cb05e34bf5f2--