-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Several years ago we neded to upgrade our management system from oracle 8 when oracle release the version 10. Our provider insists us for migrate to oracle 9 and then to 10. After a long analisys the systems engineers decide to migrate to oracle 10 because the process will be shorter. And it was fine and whe we finish the upgrade, oracle 10 was mostly very stable.
This case seems pretty equal to me. Ryan's advice is the most recommended for almost every case. What Ryan says have the most sense if you need to do a seamless upgrade for whatever other reason. Remember, just like Ryans says, a production site will not be based in development versions of framework, database, etc. But if you make re-engineering to your site, this will take time and when you finish the 2.0 framework wil be stable. Or you can wait until this happend. If you upgrade to 1.3 and then again to 2.0 when there is no need to do, it's to make the work two times. Even more, you can add new features just like in any other software version upgrade and no only migrate the framework version. I think it's no needed to do the update now, because you want to upgrade for fear to "PHP hosting can be changed to higher version" and then "the website will no work". This will not happpend in the short time, because php 5.3 it's now the "top" standard (php it's releasing yet 5.2.x versions) so your production website made with cakephp 1.2 will just work fine for several more months. Obviously, it's highly probable that there are no guide to do the upgrade from 1.2 to 2.0 Regards, Alejandro. El 18/02/2011 01:23, Ryan Schmidt escribió: > On Feb 17, 2011, at 21:41, Alejandro Gómez Fernández wrote: > >> In case you want to upgrade cake "to the most recent version" I think >> you must see cake 2.0. It's a development version, but more or less, >> when you finish your migration it will be a production version. To >> change to an 1.3.x has no sense to me. > > Upgrading a production site to the development version of CakePHP that will > become 2.0 makes no sense. The final version 2.0 is not released yet, and the > developers have provided no guidance on when it will be completed. It might > be tomorrow, it might be next year. In the mean time, you might run into > issues, the response to which will generally be "it's a development version, > it's expected to have unresolved problems, go use the stable version". > > There is a published guide explaining how to upgrade a 1.2 site to 1.3. When > 2.0 is released, I would expect there to be a guide explaining how to upgrade > a site from 1.3 to 2.0. I would not, however, expect there to be a guide on > how to upgrade from 1.2 directly to 2.0; users would be expected to have > already upgraded to 1.3. Therefore it makes a great amount of sense to > upgrade your 1.2 site to 1.3 now, verify that you've followed the existing > upgrade guide properly and that everything works, and publish your site with > 1.3, and then, whenever 2.0 does come out, you can tackle that upgrade then. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNXoELAAoJEHQn9CmeN9DJsmwH/0hKu+83Fb7FxtFNIvpYEocm R+/jrMJCmwWWZMSoLOzF+aXH2fqcJd5evtMag4ErqjjFMIPrS/7JOZIrOM/P6dPK kM672hL/WKTNvzxOPsXx/ywq9ydGHUBz3NM5i23DRP+PDCWoucIfgceZpFuTG2+H AMRHmA/QIVg/zpLP3zzcqtW+eUcDDomUjOFRCVj2NDw6ReHCYh/hkcI4LED0tAX9 PSLPGrOVH6KodySzx+Os3/ABdFUyJtSczqwAa+qOfwLMZiV5S67IoRYMnvtYUYgq 4nfy4/pK/swKOSCpfZneNp1X+/zi7pr2ueFAR0FnMt+lN+3JjrdluwXNtQQsmeU= =Tcoo -----END PGP SIGNATURE----- -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
