-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/4/2016 3:41 AM, Kristian Fiskerstrand wrote:
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>
>
>> Better late then never. Posting 72 hours from now the earliest
>> as advised by GLEP 42. Feedback welcome as usual.
>
> Do you have
On Mon, Jan 4, 2016 at 9:20 AM, Kristian Fiskerstrand wrote:
>
> And while at it, in additional to news item, this should likely follow
> a few version upgrades as elog messages before actually being
> implemented anywhere
>
I don't want to be too prescriptive with the solutions. However,
clearl
Kristian Fiskerstrand wrote:
> Maybe I'm thinking things too difficult, why not just define both -D
> PHP and -D PHP5 in the transition period and suggest this config for
> any change?
Because it mostly just defers the problem.
If the desire is to move away from PHP5 then I would suggest to force
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/04/2016 02:30 PM, Kristian Fiskerstrand wrote:
> On 01/04/2016 09:41 AM, Kristian Fiskerstrand wrote:
>> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>>> Hi!
>
>
>
>
>> Such a change should really be avoided if possible. Would it be
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/04/2016 09:41 AM, Kristian Fiskerstrand wrote:
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>
> Such a change should really be avoided if possible. Would it be
> possible to have a conditional approach where either one can be
On Mon, Jan 4, 2016 at 3:41 AM, Kristian Fiskerstrand wrote:
>
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>>
>>
>> Better late then never. Posting 72 hours from now the earliest as
>> advised by GLEP 42. Feedback welcome as usual.
>
> Do you have any timeline in place for the cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
> Hi!
>
>
> Better late then never. Posting 72 hours from now the earliest as
> advised by GLEP 42. Feedback welcome as usual.
Do you have any timeline in place for the change happening in tree (
