As a web hosting company, I think this is a great idea. One of the impediments to updating all hosting accounts is the cost/benefit of making such an invasive change. The biggest cost is convincing customers that it's necessary to incur additional testing and modification costs on sites that were working just fine with PHP4. We're driven by the market. With only minor demand and little justification to rock our customers' boats, we're as stuck as everyone else, and PHP5 instances are relegated to special configurations or separate applications. Consequently, big projects must support PHP4 to play to our least common denominator - it's a vicious circle! Such a "deadline" would provide enough justification to make the switch without worrying that PHP4 customers will feel jerked around on a whim and go elsewhere ( to that "stable" PHP4 host ). Long story short: +1 -----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org]On Behalf Of Larry Garfield Sent: Tuesday, May 22, 2007 9:00 PM To: development@drupal.org Subject: Re: [development] PHP5 going forward Well, the idea is to make the ISPs aware when/if we actually agree to something. "We're thinking about dropping PHP 5 eventually" isn't as quite persuasive as "We're dropping PHP 5 on X date, just so you know..." :-)