Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118228
MIME-Version: 1.0
References: <d748efe6-c2c5-f082-3ba2-eac94c5d8e47@gmx.de> <CAESVnVpsDQcWWE+GpXQpSkp8tPjYvpbyhGbgV5fybSsG26ssmw@mail.gmail.com>
 <FCEE5B5D-652C-456F-8AF1-F24EA16A620A@php.net>
In-Reply-To: <FCEE5B5D-652C-456F-8AF1-F24EA16A620A@php.net>
Date: Fri, 8 Jul 2022 14:26:04 -0500
Message-ID: <CAESVnVp=wm8N6-khc_FVUxFK7F=VhwzJrzneDuBuSJM=pAx3NQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP internals <internals@lists.php.net>, "Christoph M. Becker" <cmbecker69@gmx.de>
Content-Type: multipart/alternative; boundary="000000000000f7797d05e3502c39"
Subject: Re: [PHP-DEV] What to do with qa.php.net?
From: pollita@php.net (Sara Golemon)

--000000000000f7797d05e3502c39
Content-Type: text/plain; charset="UTF-8"

On Fri, Jul 8, 2022 at 9:48 AM Derick Rethans <derick@php.net> wrote:
> 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

--000000000000f7797d05e3502c39--