+1 on this as a gentle first step that can be implemented now and help us through the process in the future no matter what the time scale of the conversion to requiring 5 is. -----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Karen Stevenson Sent: Tuesday, June 26, 2007 8:20 AM To: development@drupal.org Subject: Re: [development] Go PHP 5, Go! One more thought on this subject, why not add 'minimum php version' to the .info file, and show modules that require php5 as disabled on the modules list if php5 isn't available. This would be a fairly simple thing that could still be slipped into 6.x that would allow us to start creating contrib modules that require php5 and get users thinking about the advantages of php5 so they start putting pressure on hosts to upgrade. Native timezone support didn't start working until 5.2, for instance, so the version check should test both major and minor version numbers. And add php version info to the module download page, too. Karen -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.9.9/870 - Release Date: 6/26/2007 10:07 AM