Yesterday I was visiting a company with performance issues. I bumped into some corporate trouble.
As I only recently joined the company, decisions were made before my time. We are making a drupal 6 site. There are many reasons for this.
It was planned like that a long time ago We need modules that aren’t/weren’t ported yet The client agreed to that.
There is no way of moving to drupal 7 (yet).
According to the drupal requirements page http://drupal.org/requirements#php
Note that some contributed modules may not be compatible with PHP 5.3, …
Because we did not intend to fix all 5.3 uncompliant modules we decided to stick to php 5.2.(imagecache was not 5.3 compliant at that time).
It seems now PHP 5.2 is not supported by Red hat corporate support contracts. This feels as an very unconfortable posisition knowing that the php crashes from time to time. PHP.net community does not support php 5.2 neither. That’s probably why Red Hat does not want to support it either.
So it seems they are now forced to move to php 5.3 and we are forced to retest the entrire cms. This is gonna cost me and the client.
Is it possible to please have a php version compatibility indication on the module page? (Or did I miss this?)
I might have calculated the porting of some modules from 5.2 to 5.3. into the budget. Actually, i would have loved to do that, that’s good fun. Now we are just both unhappy.
For the bigger companies where compatibility (and support) is of importance, this will really make a difference. It also could have spared me a hole lot of head-aches.
What do you guys think of this?