On 17 Feb 2009, at 16:27, Robin Berjon wrote:
> On Feb 17, 2009, at 16:45 , Lee Bolding wrote: >> Why did you upgrade? >> >> If there weren't any features of the new version you desperately >> needed, *why* upgrade? it's an unnecessary project risk (as you've >> discovered). Upgrading 'for the sake of it' is pure dumb. > > People (rightfully) expect minor revisions to be compatible. I picked > up symfony with 1.2 but I am continually surprised by the BC issues > people are quoting (and which makes the plugins a real damn pain). It > should really be at v3 by now :) People should read the release notes, and follow the posted messages. Not doing so before implementing is doubly dumb. After all, it brings us back to my original question - why upgrade? if you haven't read the release notes, it's pretty obvious it's just "because it's the highest number", which is dumb. Take PHP 5.2.7 as a recent example ;) To be fair, I've always worked on the same versioning method <major>.<minor>.<revision> where any change at <minor> signifies API *incompatibility* with the previous minor release. This seems to be the method that Symfony follows too. Personally, I don't think 1.2 is ready yet - it seems to me that it was rushed to be released so that the Jobeet tutorial could begin on December 1st. Hopefully more pragmatism will be evident in the future. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
