Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105656
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
In-Reply-To: <2be9b61e-7a8b-3449-d568-c0c7a1ba0091@gmail.com>
Date: Fri, 10 May 2019 08:53:16 +0300
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD508DD5-1CA7-4D00-AB92-2E02C2516F89@gmail.com>
References: <CA+4wLCA3qR9qK065OwYzuaxWeFhK8g_GWa3gp9hhk6Nzy81=7g@mail.gmail.com> <2be9b61e-7a8b-3449-d568-c0c7a1ba0091@gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Subject: Re: [PHP-DEV] PHP Docker images
From: martins.sipenko@gmail.com (Martins Sipenko)

Hi,

I was hoping this could be somethat that would be backed by official PHP and=
 thus can be trusted. Currently there are some unofficial nightly builds, bu=
t I=E2=80=99m reluctant to use them due to trust issues.

Clearly we can build nightly images in house, but doing so does not bring an=
y benefit to the community. On the other hand, if there hasn=E2=80=99t been a=
ny demand for nightlies it probabbly means noone needs this.

I know TravisCI do maintain a next unreleased release version of PHP on thei=
r build system, but that is not really reusable in other systems.

Lastly, I think that the more real world projects grt tested against upcomin=
g PHP version, the more bugs can caught before doing a realease.

Overall, if you think this is something thats not worth the effort of writin=
g RFC I will not proceed with this further.

Martins

> On 10 May 2019, at 08:32, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>=20
> Hi!
>=20
>> I'm aware there are php images available on Docker hub, but as their docs=

>> state those are not to be confused with any official php image provided b=
y
>> php upstream.
>=20
> Generally, nothing prevents anybody from building a set of docker images
> the second after PHP tag is released. The only "official" thing is
> always that git tag, the rest are derivative anyway.
> So, if you or somebody else wants to build those images, no approval of
> any type is required. If these prove useful and consistently available,
> we could link to them in the documentation, but otherwise I don't think
> any approval is needed for doing something like this.
>=20
> --=20
> Stas Malyshev
> smalyshev@gmail.com