hi! i think the best solution is to get agavi work on 5.0.0. On the one side, most of the people using agavi have the last version of php but i have lot of clients who are using a manageged server and have only 5.0.1 because the hosting company dont update that quickly when a new version is available. i would not require 5.0.0 for ever but in this time, i would expect it to be installed. in some monthes, some of the features of the next php-version could be included.
just my 2 cents... benny On Fri, 2005-07-22 at 09:59 -0500, Mike Vincent wrote: > This topic has risen from the discussions of singleton model > implementation and I think deserves clarification. The argument is > what versions of php should we expect to be installed. > > (A) 5.0.0 - We should target php as it was released at version 5.0.0. > - Conditional checks would need to be added for any features or > changes in behavior to php which were added after the 5.0.0 release > that are to be utilized in the framework. To take the specific case > that spurred the discussion http://php.net/is_subclass_of supports > checking if a class is a subclass of a parent as of 5.0.3 where as > prior versions of the function only supported checking against a live > object. In order to utlize this change in behavior, we would need to > check if the current php version is equal or greater to 5.0.3 and if > not provide a workaround. > > (B) We should target the most current stable version of php, 5.0.4 at > this time and expect developers will be running a current release of > php. > > I dont think it is in the scope of the framework to pander to admins > that dont practice good package adminstration by keeping their > packages up to date and so I firmly believe (B) to be the best > practice we should be following. If we do not target the latest stable > release of the applications we intend to collaborate with, we need to > generate a policy to determine what factors will affect the target > platform(s). I believe the outcome of this vote should be extended to > not only php but any other application we intend to be used, ie: > Phing, Propel, SimpleTest, PhpUnit2, Creole, MySQL, et al. > > > So come one, come all, throw your 2cents in so we can establish the baseline. > > -Mike > +1 B > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
