Carl Karsten wrote: > Personally, I would think each dev should get their own branch, and use some > sort of buddy system to have changes reviewed before merged. or maybe some > unit testing... I du no. that has it's pros and cons too.
I have the ability to grant different levels of write access to different files and directories, but right now don't see the need to wield that power. I think the branch idea is great. Do it: svn copy http://svn.dabodev.com/dabo/trunk http://svn.dabodev.com/dabo/branches/carl svn copy http://svn.dabodev.com/dabodemo/trunk http://svn.dabodev.com/dabodemo/branches/carl svn copy http://svn.dabodev.com/daboide/trunk http://svn.dabodev.com/daboide/branches/carl cd ~/projects svn checkout http://svn.dabodev.com/dabo/branches/carl dabo-carl svn checkout http://svn.dabodev.com/dabodemo/branches/carl dabo-carl svn checkout http://svn.dabodev.com/daboide/branches/carl dabo-carl And then when you have some things worked out how you like them, shoot an email to dabo-dev asking us to review. That seems like a sane approach. On the other hand, when you are confident about a bugfix or a small change to something, just commit to trunk. We are all adults and can be trusted to use our brains to figure out when we may be crossing some fuzzy line. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
