Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109170 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47892 invoked from network); 20 Mar 2020 19:20:06 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Mar 2020 19:20:06 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 063CC1804F8 for ; Fri, 20 Mar 2020 10:43:32 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-qv1-f42.google.com (mail-qv1-f42.google.com [209.85.219.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 20 Mar 2020 10:43:31 -0700 (PDT) Received: by mail-qv1-f42.google.com with SMTP id h20so3399159qvr.12 for ; Fri, 20 Mar 2020 10:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/rgjXyNWKvNGN0T0cB/JHklZVIWZe845KaT5sXfrnp4=; b=Anl7MAa6968JNE1Kg4kf08idPmayIP/6zaaUbXkSUD9diLfJiLCJVrg4tMjcTp/i4q PBiS4Uc13BBEWBxn1FNl9p2EU/In45j1g8O///rXhcrvG7NH8g8iwdnyPyFqymqsT21Z eSnKV06Dcd1rzihL2Yn5CmIV8Z/0UGZbZ2SrM7eGXqNhv0H+VXvxZMiYJBPRqWQSB+py tU8ig2Kpu5zWZ2iEITxNAgV9bLD29TFJsCiU7nBarqRapb6dV/YnLmAnGv4UrbrSpLKz AyN8ffFTpw6v8FKeG4IkamyQ/vy6qPD+TROm3tgzhHId3SLlBtl0hSc1WnoFxAg2MOJr aI+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/rgjXyNWKvNGN0T0cB/JHklZVIWZe845KaT5sXfrnp4=; b=tCJgipvqnu+ug0kk1y1ZNrT6kGrMEBysLQcQMzF3WpQcNcsW/2qyJWhSl9ESAlaCuT 1S/lilYbHpl2eQg1pe7Pyo7D+jzluYe29WVB7wrea5Eelfb2WWkAt+Gyy7pjLuIBoTxi GRLCpPYutPt2GTKwNp1+A/ZPQI1Uljj8ANf1tNpNxydjLGv3bQ8bpg0TByNkSKmgWoEJ Mjs3Q9qrhCC2jUZxEHvFZCxAEzk7yfPAafvEKVodx8yCkmrWP+wUpSo2/ECxdIF6C7On bfqbW+jwTkqd+1xC02jusiAB96kNGZ8db+LP26Z0lfqNdsK76BB8pJ8YvffSP3R/pr9g sq7w== X-Gm-Message-State: ANhLgQ3rAT77QcQTbPEbFkL000STkfW4FnvYLp5at67kY09WiKvPCx2W xRe/kGVJSu61baclxtutUgUoVA== X-Google-Smtp-Source: ADFU+vs2LPqd2AgqTwTGcSDRTPh9NCgNjYjMSI0d6oqQ4JNAXUrEUn3FQVTQLo72vdHDhad6PXISig== X-Received: by 2002:ad4:5994:: with SMTP id ek20mr9360162qvb.93.1584726210627; Fri, 20 Mar 2020 10:43:30 -0700 (PDT) Received: from ?IPv6:2601:c0:c680:5cc0:a554:e98e:ee7d:a65? ([2601:c0:c680:5cc0:a554:e98e:ee7d:a65]) by smtp.gmail.com with ESMTPSA id k4sm4703420qkc.18.2020.03.20.10.43.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Mar 2020 10:43:29 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) In-Reply-To: <1485816E-75F5-4C95-8D39-73D8F859888A@benramsey.com> Date: Fri, 20 Mar 2020 13:43:28 -0400 Cc: Rowan Tommins , PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <99CC3F40-5F75-4D71-B4C4-DB6831D38A0D@newclarity.net> References: <5e74db3f.1c69fb81.8f943.ad24SMTPIN_ADDED_MISSING@mx.google.com> <606B9434-7765-4509-93FA-5DEA523C76A0@benramsey.com> <1485816E-75F5-4C95-8D39-73D8F859888A@benramsey.com> To: Ben Ramsey X-Mailer: Apple Mail (2.3445.104.11) Subject: Re: [PHP-DEV] An incubation period for RFCs? [repost as own thread] From: mike@newclarity.net (Mike Schinkel) > On Mar 20, 2020, at 1:09 PM, Ben Ramsey wrote: >=20 >> On Mar 20, 2020, at 11:30, Rowan Tommins = wrote: >>=20 >> On Fri, 20 Mar 2020 at 15:48, Ben Ramsey wrote: >>=20 >>>=20 >>> To encourage userland testing of RC versions, I think it would be = helpful >>> to maintain Docker images of RCs. >>>=20 >>> I=E2=80=99m not suggesting the internals group take this on = themselves. IMO, this >>> is something that the community can take on and offer >>>=20 >>=20 >>=20 >> Just to be clear, other than a few permissions and a very small = number of >> legal roles, I don't think there is any difference between "the = internals >> group" and "the community". >>=20 >> If someone were to maintain these, I doubt anyone would object to = seeing >> them linked on php.net somewhere, with a suitable disclaimer that = they >> weren't supported builds. >>=20 >> Incidentally, I suggested something related for PHP 8 specifically, = so that >> people could test the JIT (I talked about distributing pre-alpha = milestone >> builds in general, rather than Docker in particular), but I'm not = sure >> anyone got around to doing it. >=20 >=20 > At the risk of getting off-topic in this thread, here is a Dockerfile = where someone is doing this for PHP 8, but it could probably use some = help to keep it up-to-date. >=20 > https://github.com/KEINOS/Dockerfile_of_PHP8-JIT My team has been working on a project called Gearbox which is a local = development solution the uses Docker containers within a VM. Gearbox in = its entirety is pre-alpha, but many components of it are already solid, = including the Docker containers as they have been use for several years = on a sister project. I won't in this thread delve into the details of Gearbox or go into a = sale pitch since I don't think that is appropriate, but we would be = happy to implement and then maintain whatever containers are needed for = PHP 8.x. - https://github.com/gearboxworks/docker-php - https://hub.docker.com/search?q=3Dgearboxworks/php Note that we have not updated to PHP 7.4 yet because it has not been on = our critical development path, but if the PHP community wants us to = offer support PHP 8.x we'd be happy to add staying on the bleeding edge = of PHP to our critical path. We would of course welcome collaboration with PRs and possibly even = commit rights for others to help us maintain the containers so we are = never a bottleneck. Our container generation infrastructure always would let up create many = different versions to allow for having proof-of-concept versions of PHP = for different RFCs, especially if the RFC authors provide PRs for their = work. We wil also very soon have a `gb-launch` tool that will simplify using = containers so it won't require experience using Docker to be able to = load and run them. So we should be able to do something like this = within a week or maybe two: gb_launch php --version=3D8.0.0-alpha-rfc-123 The above command will pull the container down if you don't already have = it locally. What do people here think about this as a solution for what Ben and = Rowan were discussing? -Mike P.S. The Gearbox project is open-source. We are currently envisioning a = SaaS as a future revenue model, but we are not exactly sure what that = will look like. First, we want to bulld Gearbox because we want it to = exist.=