In a few months, with this rate of progress, even if a stable release has not been declared, I would say there would be no question, go with 1.3. A few months ago, I would have also said there would be no question, stay with 1.2.
We are in a somewhat gray period right now, for the next little while, in my opinion. The main reasons for not adopting 1.3 just yet might be: 1. lack of 1.3 specific documentation (as mentioned) 2. less plugins/components, etc. which work with 1.3 3. less community support (most are still on 1.2) 3. perhaps a few more bugs than a stable app 4. there is always a chance in the open source world, however remote, that any project regardless of size or reputation may not make it to the finish line for any number of reasons. (eg. Mambo went from being an OpenSource award winner to a total failure and inabilty to deliver the next Mambo v5 release). I'm not saying (or even hinting) this will happen to cakePHP, and I am banking on it not happening, but I'm not sure I would want to be holding 1.3 just yet, given that the super 1.2 release is just so solid. On the other hand, the main reasons for adopting 1.3 might be: 1. you will really be helped by the new features. 2. you are comfortable enough in cake , that you can plow through the lack of documentation issue and still get things done 3. cake 1.3 is being used in many production apps already, so is practically pretty stable already. I don't think there is really a "bad" decision either way, but alot will depend on your specific situation. YMMV. On Mar 12, 4:08 am, jacmoe <[email protected]> wrote: > I am not so sure.. > Cake 1.3 is really great, and I use it myself. > But: most of - well, almost all of it, actually - the tutorials/hints/ > information/blogposts are about Cake 1.2. > I am having a really hard time finding Cake 1.3 specific stuff. > I wouldn't have stood a chance if I were to start off with Cakephp 1.3 > as a newbie right now. > That's going to change, of course, once Cake 1.3 becomes stable. > > That said, if you are not using any Ajax or fancy stuff, you can start > off with Cake 1.3 - but know that you need to translate most of your > Google results from 1.2 to 1.3 - the migration guide is actually quite > good. > > Your choice - but don't say I didn't warn you. :) > > On Mar 12, 2:50 am, nurvzy <[email protected]> wrote: > > > I recommend using 1.3 for any new project if for no other reason but > > the new and improved bake. 1.3 bake will make your life development > > easier -- I promise. I've been using it since it was in alpha. I > > have since converted all my client's sites to 1.3 and have had zero > > issues. The new features are great! > > > Hope that helps, > > Nick > > > On Mar 11, 5:00 pm, jonathan <[email protected]> wrote: > > > > Hi All, > > > > Just a general question on which version would be best to start a new > > > project with - 1.2 or jump right over to 1.3? > > > > Over the past 4 years or so, I have created some pretty large > > > enterprise systems in 1.1 and they are humming along nicely. I'll be > > > starting some new stuff soon, so I'd like to get into the new versions > > > rather than remain old school. In all honesty, 1.1 was a pleasure to > > > work with and I'm really looking forward to seeing all that I've been > > > missing. > > > > Thank you for your input and my undying gratitude to any and all who > > > help CakePHP be all that it is. > > > > Sincerely, > > > Jonathan Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. 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
