Nothing is forcing you to upgrade. When 3.x lands, you don't need to take your legacy site and make it 3.x compatible. Just run a legacy site on a legacy version of cake. I really hope that the Cake devs don't hold back on cool new stuff in the name of backwards compatibility - that would be a shame.
On Tue, May 14, 2013 at 10:36 AM, Advantage+ <movepix...@gmail.com> wrote: > Its always easier said than done….**** > > ** ** > > Dry it you just baked a cake site but all sites are unique. Not just add > edit save and delete you have custom functions pulling out data from the > models contain all that stuff. Migration will not touch that! **** > > ** ** > > *From:* cake-php@googlegroups.com [mailto:cake-php@googlegroups.com] *On > Behalf Of *euromark > *Sent:* Monday, May 13, 2013 8:27 PM > > *To:* cake-php@googlegroups.com > *Subject:* Re: Cake 3.0**** > > ** ** > > Upgrading from 1.x to any 2.x is doable and really not that big of a deal. > **** > > Mostly preg_replacing which can be automated, and some other stuff like > renaming/folderstructure which also can also be automated.**** > > I use an extended upgrade shell for this - and it takes me less than 10% > of the time it needed otherwise.**** > > Only some things need to be adjusted manually. But the migration guides > help you here.**** > > So I dont really see the issue if you got a few days (for larger projects) > - they will be worth it (think about all the improvements).**** > > You just can't expect it to work within 1 hour.**** > > ** ** > > Upgrading to 3.x might be a little bit more difficult.**** > > Most upgrades will also be doable with the same approaches above.**** > > Some might not. But 3.x will be a complete rewrite of model layer for > example. So what would one expect?**** > > Lets just wait until it becomes clearer - and less theoretical**** > > ** ** > > Also, keeping in mind what will be deprecated, and what features will > persist and be improved helps to code apps future-proof**** > > One aspect that came up in the past: query strings instead of named > params. I wrote about it a few days back.**** > > If you - like me - start writing new apps with the 3.x way of how its done > - the potential upgrade will be far less complicated.**** > > And there is usually a good reason why some things change over time and > will be more important/correct in future versions.**** > > No need to cling to stuff that will not be supported or is already clear > to be dropped.**** > > ** ** > > So you can write clean and DRY code. You can also stay up to date and use > best practice approaches and switch from deprecated to new ways of doing it. > **** > > Then, upgrading will be kinda quick, easy and fun. Having to recode a > whole mess of code at once isn't, though.**** > > > > Am Montag, 13. Mai 2013 19:11:35 UTC+2 schrieb Jamie:**** > > I personally didn't bother to upgrade any production sites from 1.3 to 2 - > I just started over. I found that it took just as long to convert my > existing custom code than just to do it over again. I will likely do the > same when 3 comes out: develop future projects in 3, maintain current ones > with the current version. > > On Sunday, May 12, 2013 12:44:48 PM UTC-7, advantage+ wrote:**** > > Yes I would have to agree with you. Rather harsh but ohh well.**** > > **** > > It will be fun upgrading to 3.**** > > **** > > All I wanted to know was if they have 3.x in development maybe there was a > way to get a jump on the change over. **** > > Something that might be backwards compatible. Still works in 2.x but in > 3.x it will be this way just to get a jump start rather than waiting till > the release and saying ohh wow now I need to re-do everything again.**** > > **** > > *From:* cake...@googlegroups.com [mailto:cake...@googlegroups.com] *On > Behalf Of *Jamie > *Sent:* Sunday, May 12, 2013 3:33 AM > *To:* cake...@googlegroups.com > *Subject:* Re: Cake 3.0**** > > **** > > "If not it's your code that sucks" - that's a little harsh, don't you > think? Sure doesn't reflect well on the professionalism of CakeDC.**** > > **** > > Upgrading from 1.3 to 2.0 is time consuming and tedious, especially for > large projects. The upgrade shell helps but by no means does all the work. > Going from 2 to 3 will likely be difficult as well given that the model > layer is being re-written. > > > On Saturday, May 11, 2013 5:10:30 AM UTC-7, Florian Krämer wrote:**** > > Write clean code, follow the CakePHP coding standards and use the API > correcty and upgrading will be easy as it ever was in the past. CakePHP was > always easy to upgrade, if not it's your code that sucks and needs a > refactor anyways. > > On Saturday, May 11, 2013 5:37:02 AM UTC+2, advantage+ wrote:**** > > Is there any date set / expected?**** > > **** > > Is there anything we can do to current sites to anticipate the new release > to get ahead of the changes?**** > > **** > > Thanks,**** > > **** > > Dave**** > > **** > > This email may contain material that is confidential, privileged and/or > work product for the sole use of the intended recipient. Any review, > reliance or distribution by others or forwarding without express permission > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies.**** > > **** > > Cake Development Corporation.**** > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to cake-php+u...@googlegroups.com. > To post to this group, send email to cake...@googlegroups.com. > Visit this group at http://groups.google.com/group/cake-php?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to cake-php+unsubscr...@googlegroups.com. > To post to this group, send email to cake-php@googlegroups.com. > Visit this group at http://groups.google.com/group/cake-php?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to cake-php+unsubscr...@googlegroups.com. > To post to this group, send email to cake-php@googlegroups.com. > Visit this group at http://groups.google.com/group/cake-php?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
