Update prod to PHP 5.3

Did anything break?

stagingvm and scratchvm are still on 5.2.14 and 5.2.17

re-tagging

stagingwww/git7staging/git6staging updated

I noticed that short open tags (<? instead of <?php) are not allowed on staging. While we avoid them, they do happen, and we have other software that may not be as strict as us. I think our standard PHP configuration should allow them.

Tagging for sprint 3.

@drumm, can you grep through staging to find all the short tag instances and post them here? Converting all of them to the regular tag style should be a really easy task. I am willing to help with the upgrade to 5.3 wherever I can be helpful, including converting short tags to normal tags :P

I haven't run into any other short open tags. This is hypothetical, but a big worry for me is 3rd party code. We do run other codebases, like CiviCRM and other libraries. We can't impose our coding standards on them. CiviCRM doesn't seem to use short open tags, but they do use more than 2 spaces of indentation.

It's my (possibly sole) opinion that unless we actually *have* third party code that we *know* uses short tags, there's no reason to account for the possibility within our DEV and TST environments. In this manner, we'll know quickly whether something we use has introduced short tags on purpose or by accident, and whether we want to go on using their stuff or write our own... (kidding on that last one)

This is done!

And there was much rejoicing!

Moving this back to active actually. While most things work, there are definitely warnings we need to track down.

Right now the webnodes are on 5.3 and util is on 5.2 still. I'm not going to update util to 5.3 until sam is around to help me debug any issues with the PHP git threads.

-N

Tagging for Sprint 5.

Add pift issue

More details

So, does that include the webserver where security.drupal.org runs? Because there are definite modue updates needed to get to 5.3 compliance on that site.

I appreciate the progress and don't want to slow it, but It would have been nice to get an email "this will happen on date X" before this change.

@greggles, Yes it does. My apologies for not pinging you.

This is now fully done.

even more details