Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118225
Return-Path: <derick@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 80745 invoked from network); 8 Jul 2022 12:55:15 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 8 Jul 2022 12:55:15 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 6ED271804B5
	for <internals@lists.php.net>; Fri,  8 Jul 2022 07:48:44 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_05,SPF_HELO_PASS,
	SPF_NEUTRAL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no
	version=3.4.2
X-Spam-ASN: AS30827 82.113.144.0/20
X-Spam-Virus: No
X-Envelope-From: <derick@php.net>
Received: from xdebug.org (xdebug.org [82.113.146.227])
	by php-smtp4.php.net (Postfix) with ESMTP
	for <internals@lists.php.net>; Fri,  8 Jul 2022 07:48:43 -0700 (PDT)
Received: from [127.0.0.1] (unknown [85.255.237.185])
	by xdebug.org (Postfix) with ESMTPSA id D005410C035;
	Fri,  8 Jul 2022 15:48:42 +0100 (BST)
Date: Fri, 08 Jul 2022 16:48:41 +0200
To: internals@lists.php.net, Sara Golemon <pollita@php.net>,
 "Christoph M. Becker" <cmbecker69@gmx.de>
CC: PHP internals <internals@lists.php.net>
User-Agent: K-9 Mail for Android
In-Reply-To: <CAESVnVpsDQcWWE+GpXQpSkp8tPjYvpbyhGbgV5fybSsG26ssmw@mail.gmail.com>
References: <d748efe6-c2c5-f082-3ba2-eac94c5d8e47@gmx.de> <CAESVnVpsDQcWWE+GpXQpSkp8tPjYvpbyhGbgV5fybSsG26ssmw@mail.gmail.com>
Message-ID: <FCEE5B5D-652C-456F-8AF1-F24EA16A620A@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] What to do with qa.php.net?
From: derick@php.net (Derick Rethans)

On 8 July 2022 16:24:13 CEST, Sara Golemon <pollita@php=2Enet> wrote:
>On Thu, Jul 7, 2022 at 11:54 AM Christoph M=2E Becker <cmbecker69@gmx=2Ed=
e>
>wrote:
>> I wonder what we should do with qa=2Ephp=2Enet=2E
>>
>
>I too have wondered this many a time=2E
>
>> 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=2E  In my opinion both should be moved to somewhere else (the PHP=
T
>> docs might go into the php-src repo, and the available QA releases coul=
d
>> be listed on php=2Enet)=2E  Afterwards I suggest to tear down the Websi=
te=2E
>>
>
>100% This=2E  PHPT can easily go in the primary manual (it's aimed at peo=
ple
>writing PHP code and PHPT files are PHP code!)=2E
>The QA releases as well, it would honestly save some (small) hassle durin=
g
>releases to only have to touch one repo with this information=2E

I don't however think we should stick these QA builds in the web-downloads=
 Git Repository though=2E It is growing big enough already and there was so=
me earlier talk about moving them to Git LFS instead=2E I don't know how fe=
asible or proprietary that is though=2E=20

cheers=20
Derick=20