> Thanks for the advices, but I really can't take the risk to loose > other time on this trying to upgrade and test pieces of code. > > I'd take the chance if I was the one who wrote the app, but it's not > the case.
I wouldn't see it as 'taking a chance'. the differences between 1.2 beta and 1.2 aren't that big. And you can easily test this by downloading the stable release, making a copy of your existing app and dropping it in to replace the default one. woudl take 5 mins to at least find out how bad it is! 1.2 stable is leaps and bounds better than 1.2 pre-beta, has loads of useful features, is faster, and, perhaps most importantly, will not have any further API changes before 1.3 comes out! > About the docs, you can only imagine how was frustrating for me to > start learning and using Cake by modifying an app written by others > based on a version on which I couldn't find a doc perfectly matching. > I think the big mistake was for other devs to release an app based on > a pre-beta framework. I bet! I think the idea is if you're going to start building something based on a changing framework, to keep pace with the changes. j -- jon bennett w: http://www.jben.net/ iChat (AIM): jbendotnet Skype: jon-bennett --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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?hl=en -~----------~----~----~----~------~----~------~--~---
