[Bug 1522422] Re: Update to php 7.0

2016-02-19 Thread Jens G.
@jstsch I'm not trying to start a specific discussion about customers or software but merely was pointing out that service providers or hosters would actually profit from both package branches staying available instead dropping one of them after freeze. And as both EOL dates are nearly the same it

[Bug 1522422] Re: Update to php 7.0

2016-02-19 Thread Jens G.
@ondrej I agree to some degree, as it would be reasonable to run xenial under the hood, not only because of the base OS but the rest of the web stack, too. And as already stated, as PHP5.6/7 are supported from PHP to almost the same EOL time now, so it's not about "please support old unmaintained

[Bug 1522422] Re: Update to php 7.0

2016-02-19 Thread Jens G.
> So I wrote a php obfuscator for myself, that I made freely available under > MIT license at https://github.com/pk-fr/yakpro-po > Perhaps you could consider using it We are a hosting and service company and only administer, consult and service our customers. Their web agencies or

[Bug 1522422] Re: Update to php 7.0

2016-02-19 Thread Jens G.
Maybe it's too late to throw my hat (and opinion) in, but from a hosting/hoster perspective, that's really a double-edged sword. Of course it would be splendid, if we could migrate all customers and applications to PHP7 as soon as possible. But with PHP itself increasing the support level of