Hi, I'm using sf1.2 with the current sfDoctrinePlugin which is using doctrine 1.0.13. We're currently facing the following bug :
http://www.doctrine-project.org/jira/browse/DC-145 which has been fixed in the future tagged version of the 1.0 branch (1.0.14) My experience with RM is limited, but I'm still wondering what's a programmer to do when doctrine has a bug which is solved but a svn up won't fix. What are our options ? - simply wait for the 1.0.14 tag --> we cannot have our project broken on the production server for a few days - update sfDoctrinePlugin to use an older tagged version, or the current checkout url of the working 1.0 branch --> what will happen when doctrine external is set to use 1.0.14 and we update the project ? an svn:external conflict ? kind of cumbersome to track / remember, isn't ? In other terms, I was just wondering if there wouldn't be RM workflow that would make svn up fix bugs that are fixed, and not require us to do steps manually. btw, I know I'm sounding like someone saying : hey, there's a bug in my software which I know was fixed in your dev team, how come doing software update doesn't fix it ? For which the obvious anwser would be : well, you have to wait for a release ... But since in this case, the bug is pretty critical, I think there should be a way for it to be fixed in a standard way (read: svn up) any comment welcome! jukea --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
