Hi all,
I wonder what we should do with qa.php.net. While that site probably
was useful in the past (at least the possibility to merge Github PRs),
it seems that it is mostly abandoned nowadays. Besides some (partially)
out-dated information, and apparently some TODO lists[1] which were
never really addressed, it supports uploading and display of user
submitted test results. Especially the latter seems to be totally
useless, or is there anybody having a look at these reports? Ah, yes,
there are also PFTT test results, although there have not been any
updates for several years, and the PFTT2 project[2] has (fortunately)
been abandoned.
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.
Thoughts?
[1] http://qa.php.net/projects.php
[2] https://github.com/php/pftt2
--
Christoph M. Becker
Hi all,
I wonder what we should do with qa.php.net. While that site probably
was useful in the past (at least the possibility to merge Github PRs),
it seems that it is mostly abandoned nowadays. Besides some (partially)
out-dated information, and apparently some TODO lists[1] which were
never really addressed, it supports uploading and display of user
submitted test results. Especially the latter seems to be totally
useless, or is there anybody having a look at these reports? Ah, yes,
there are also PFTT test results, although there have not been any
updates for several years, and the PFTT2 project[2] has (fortunately)
been abandoned.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.Thoughts?
[1] http://qa.php.net/projects.php
[2] https://github.com/php/pftt2--
Christoph M. Becker
I agree with moving the QA release listings to php.net. The PHPT
documentation could move into the manual or to phpinternalsbook.com.
--
Cheers,
Ben
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.
+1
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
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.
I don't however think we should stick these QA builds in the web-downloads Git Repository though. It is growing big enough already and there was some earlier talk about moving them to Git LFS instead. I don't know how feasible or proprietary that is though.
cheers
Derick
I don't however think we should stick these QA builds in the
web-downloads Git Repository though. It is growing big enough already and
there was some earlier talk about moving them to Git LFS instead. I don't
know how feasible or proprietary that is though.
Oh sure, no. We'll keep the bit of the QA version struct that points at
the downloads path (maybe making all by the userpath portion hardcoded
because the rest never changes) and construct from there.
Something like:
<?php // includes/qa.inc
$QA = [
'8.2' => [
'version' => '8.2.0beta3',
'date' => '18 Aug 2022',
'download_path' => 'https://downloads.php.net/~ramsey',
'sha256' => [
'tar.gz' => 'deadbeefcafe',
'tar.bz2' => '...',
'tar.xz' => '...',
],
// 8.1, 8.0, etc...
];
Then on php.net/downloads/testing we list the active alpha/beta/RC builds
like we have on php.net/downloads (and which we link from there). Probably
make a nice JSON endpoint as well, because why not?
-Sara
It's useful to me, as I've always been able to merge PRs on the QA site,
because I've not been added to any php-web/php-src github repos since we
migrated over there.
However, if it's not too useful to the majority of people, then I'll still
vote to delete it/move stuff.
One less site for us all to maintain, the better IMO, :-)
Hi all,
I wonder what we should do with qa.php.net. While that site probably
was useful in the past (at least the possibility to merge Github PRs),
it seems that it is mostly abandoned nowadays. Besides some (partially)
out-dated information, and apparently some TODO lists[1] which were
never really addressed, it supports uploading and display of user
submitted test results. Especially the latter seems to be totally
useless, or is there anybody having a look at these reports? Ah, yes,
there are also PFTT test results, although there have not been any
updates for several years, and the PFTT2 project[2] has (fortunately)
been abandoned.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.Thoughts?
[1] http://qa.php.net/projects.php
[2] https://github.com/php/pftt2--
Christoph M. Becker--
To unsubscribe, visit: https://www.php.net/unsub.php