That would be interesting, considering that otherwise you would have to go through the API to look for deprecated methods. A proper procedure for version upgrading on sites that are in production with Cake will definitely make Cake stand amongst the rest.
I also agree with Nate that bakers should play by the rules or then it would make cake's job quite difficult. But having a heads up on which methods will be deprecated on future versions (I understand you can't predict what will happen on Cake 11.x, but you can on Cake 2.x) definitely helps us bakers follow the rules. Bake on! -MI -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Samuel DeVore Sent: Tuesday, October 24, 2006 10:46 AM To: [email protected] Subject: Re: Re: Planning on CakePHP future versions Nate is it possible to have deprecated methods through notices in debug mode but work in deployment for deprecated methods for a release or two before the scheduled removal. Given that there are more and more sites built on CakePHP that are in production? SD -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.11/493 - Release Date: 10/23/2006 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
