> The typical approach within a development team might be to create a > branch, but I'm not sure that works within the Rails development > process either. Any thoughts?
There's two questions here, technical and process. The process side of it is harder, if you're interested in undertaking some major refactoring you should probably grab someone with commit access in irc, and talk over the changes first. 'Refactoring' is a tough sell without some kind of performance or functional improvement, especially given its tendencies to break the hell out of plugins ;) As for the technical question... My personal 'major changes' tend to happen in my git repository, then I commit them to svn when ready to go. I'm happy to take patches or proposed patches via git instead of svn diffs, but I can't promise anyone else will agree ;) git clone git://git.koziarski.com/rails http://git.koziarski.com/?p=.git;a=summary -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
