Re: [RFC] php-community: a faster-moving, community-driven PHP.

On 3/19/26 11:19, Larry Garfield wrote:

A much, much more useful approach would be to devise some way to automatically build docker images out of PRs against php-src. So if you download the php-dev-aviz-2024-03-10 docker image, it's easy to run it and see what the code "feels like," but no one is going to mistake it for a stable, production-usable image they can build a business on. (Well, almost no one; I'm sure someone will try, but it's a lot easier then to say "it's your own damned fault for running some rando PR in production".) That would allow devs to more easily "try out" a feature and report back manually. That potentially improves the quality of feedback from "I read the syntax in the RFC and I don't like X" to "I tried writing a class with this syntax and I kept mistyping it because it's fugly". Or perhaps not, but at least it is vastly lower effort to do. The Async people are already doing this, which is very good! All we need is make that easier and more automated to do for any RFC.

I believe the "official"[^1] Docker PHP images provide builds of every RC version of PHP. It might be interesting for them to provide php-unstable variants that are builds of specific feature branches, much like 3v4l does. Doing so would be up to that community,[^2] though—not this one. Cheers, Ben [^1]: They are officially maintained and supported by the Docker Community, not by Docker or the PHP project. [^2]: https://github.com/docker-library/php