Yes. symfony 1.0.X is just for bug fixes and must not introduce BC except for security fixes.
Fabien Tamcy wrote: > Well, I suddenly realized that I overlooked the "Additional > Installation Notes" part of the wiki. > So the reason not including this is purely a BC concern? > > On Jul 31, 12:28 pm, Tamcy <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I had been using trunk for development and since trunk is now facing >> big changes I changed my developing copy to use the 1.0 branch. >> >> After the switch I regenerated the Propel models and found the mixin >> calling part of the generated model changed. After some investigation >> it is the changeset 3663 (committed 23 March 2007) not brought into >> 1.0 branch (http://trac.symfony-project.com/trac/changeset/3663). >> >> The change does two things: >> 1. change the hook "addDoSelectRS" to "doSelectRS" >> 2. add hooks to some addDoSelectJoin*() methods >> >> It seems reasonable not to include this change to 1.0 as the above >> change was made after the 1.0.1 release and 1.0.x was meant to be non- >> breaking release. But the interesting part is that the plugin I'm >> using, sfPropelParanoidBehaviorPlugin, released Octobar 2006, already >> uses "doSelectRS" as the hook name. So I suspect the change from >> "addDoSelectRS" to "doSelectRS" is a kind of bugfix. >> >> If this is the case, shall [3663] be merged to the 1.0 stable (even >> the second change should not break existing things)? >> >> Thanks in advance. >> >> Tamcy > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
