I'll add that, with the changes that have occurred *within* the 1.2 branch itself, it seems odd that we're not looking at a 2.0 release. IMO, 1.2 should have been released long ago with many of the current changes moved into a 2.0 target branch.
And, yes, I realise that development is never as tidy as all that. I'm sure it couldn't be helped without releasing a dodgy 1.2. That is, I'm confident the devs had very good reasons to go ahead with all the changes within 1.2. I'm not complaining, just commenting on the very significant changes since the first 1.2beta became available. In any case, I don't really care what no. release it is--it's all tasty stuff :-p On Fri, Apr 25, 2008 at 1:06 PM, seb <[EMAIL PROTECTED]> wrote: > > > And looking at the bug list in trac, I wouldn't say there are any > > major changes in the pipeline either. Going from 1.1 to 1.2 isn't > > totally trivial, so the sooner you get started on such a transition > > the better. If you are waiting for a "final" release before making > > that change, I would re-think the strategy, and instead just go with > > the current build. > > Well, I've been working with 1.2 beta since a while now. Since the very > beginning in fact. Changes from 1.1 to 1.2 were so important that after > 2 days learning 1.1, I switched to 1.2 even there was no "official" doc > yet. New Cookbook is nice and a good way to start learning :D > > I've got a website working with 1.2 beta nicely and I'm currently > working on a total recode of my good old (and rather badly coded) PHP4 > webstore > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
