Is there any word or ideas/plans on what Magento plans to do with the core of 1.x when PHP 5.6 and 7.0 are EOL in December 2018?
I did some searching but I haven't seen anything about it.
For example, will Magento 1.x still be officially supported for security fixes but only official supported to run on unsupported version of PHP?
The Inchoo compatibility extension will apparently correct issues to run on PHP 7.1 -- I understand third-party extensions will have their own issues. Will that be the published recommendation by Magento?
Or, is there a plan to release a Magento 1.10 that will officially incorporate the those compatibility fixes?
I'll try to find out about this for you as there's no official communication about this so far.
Personally I wouldn't be surprised to see them releasing a patch (like the PHP 5.4 patch in the past) but this is just speculation on my part.
Thanks. I'm looking forward to any info you can squeeze out ahead of time so we have more info to prep our clients with expectations and possible options.
I don't think it will procide patch for that.
Magento is now focus on magento2 more compare to Magento 1.
Inchoo already provide solution for that, you can use that . For custom module you need to ask to that module provider for same.
I think it's up in the air. I could see it going either way since there's a lot of established M1.x stores still running strong.
Inchoo does have modifications (pointed out in my original post) but it doesn't have Magento's official blessing, so I'm trying to get an official answer from Magento.
As you know there isn't an official solution yet but the informal answer is that there will be.
The main reason should be (I guess) that the latest version of Magento Commerce 1.13 and 1.14 (Enterprise) will have oficial support until June 2020. (But requires a renewal of the Magento license through the stated date.)
Those dates are official and you'll find it into the Subscription Agreement of Magento Commerce/Enterprise.
Since the EOL of PHP versions will happen before that we should believe that there will be an official patch/solution for this.