No need to start worrying yet - we ofcourse try to find a good solution for this. We would still actively recommend to use PHP 4.4.0 with eZp 3.6.1 ofcourse, as there are simply too many things that <i>can</i> go wrong with PHP 4.3.x.
Personally i'd like to see the 3.6 series untouched, changes backed out and a patch provided for those who need it. I dont like to see changes like this for a maintainence release.
I am now worried, we have production sites in 3.6 that have deployed. Now a minor release should not need an system change like this. I am concerned because this is an extra cost to deployment and basically prevent 3.6 upgrades until the systems with 4.3 can be upgraded tested etc. We could not go with 4.4 as it is still in RC.
Please ensure that 3.6 series does not require this upgrade. IMHO: This should be parked till 3.7 when we can plan for it in advance rather than finding out a week before 3.6-1 release.
I would also like to ensure that architectural changes like this are explained to us in advance so we do not get these little surprises :) I don't want to sound ratty, but this was a nasty shock to me escpecially as we just won the Olympics in London and the Software Patents Bill got canned. It was such a good day :)
Thanks
Tony
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
I've just opened a discussion about this on our public mailing list. I also want to emphasize Dericks statement: eZ publish doesn't run properly with PHP 4.3 and older (actually, no object oriented PHP program with references does). You can solve this only by upgrading to PHP 4.4. Because of this we want to provide upgrade paths to PHP 4.4 for our currently supported branches.
You must be logged in to post messages in this topic!