Re: com web/php: Mentioned that code must work with PHP 5.3: README.md

On Thu, Dec 28, 2017 at 7:54 PM, Philip Olson <philip@roshambo.org> wrote: > >> On Dec 22, 2017, at 7:21 AM, Levi Morrison <morrison.levi@gmail.com> wrote: >> >> On Thu, Dec 21, 2017 at 8:21 PM, Philip Olson <philip@php.net> wrote: >>> Commit: 9eb060965d4bbd1ca401f0adace36c0616b96b3e >>> Author: Philip Olson <philip@roshambo.org> Thu, 21 Dec 2017 19:21:55 >>> -0800 >>> Parents: 86580c9a4be551588ae77de1e51a81c247bfebca >>> Branches: master >>> >>> Link: >>> http://git.php.net/?p=web/php.git;a=commitdiff;h=9eb060965d4bbd1ca401f0adace36c0616b96b3e >>> >>> Log: >>> Mentioned that code must work with PHP 5.3 >>> >>> Changed paths: >>> M README.md >>> >>> >>> Diff: >>> diff --git a/README.md b/README.md >>> index add3938..113c89a 100644 >>> --- a/README.md >>> +++ b/README.md >>> @@ -22,4 +22,7 @@ operation of this website, such as >>> >>> To install a full official mirror please see [the mirroring >>> guidelines](http://php.net/mirroring). >>> >>> +## Code requirements >>> >>> +Code must function on a vanilla PHP 5.3 installation as some php.net mirrors still run >>> PHP 5.3. >>> +Please keep this in mind before filing a pull request. >> >> I'd propose we move all infrastructure to version 5.5 or newer - with >> PHP 5.5 and 7.0 being allowed only if the distribution they run is >> supporting it - within the next few months. This is not just a "let's >> modernize!" push; I suspect these out-of-date versions of PHP are not >> being updated with security patches. For instance >> 5.3.10 is used by a few mirrors but I'm not aware of any OS's >> maintaining that version. > > Hi Levi, > > That sounds good although I'm an old timer that's not around much these days but the > php.net infrastructure feels fragile on several levels. > > As for your proposed and fully understandable requirement, that'd immediately eliminate > about half of the mirrors. Worse yet, master.php.net itself is running 5.4.11-dev which must be a > security risk. That said, I also think it'd be worth requiring 5.5 or newer. Or maybe finding a > single company to sponsor/manage/host _all_ of this is another option? > > Regards, > Philip > > We should probably make an application container and move to a container orchestration toolchain. Then we can update all mirrors ourselves. I am allocating my time elsewhere right now, though, so it's definitely a wishlist. Using a single company seems unlikely. Can they provide the same world-wide reliability we generally provide now? And if they can that can't be cheap, so I doubt they would donate so much. Levi Morrison