On 9/23/13 1:15 PM, BRM wrote: > "Trunk is dirty" won't save you from bad merges, it'll just make more > conflicts in your working copy as you do updates - something that > drove a colleague of mine nuts so I started working in my own branch > for that project. You also have to more frequently be doing "svn > update" on your working copy to minimize impacts of what others are doing.
In my experience, working in a dirty trunk typically results in less checkins by developers. I don't consider this a good thing as their changes tend to remain uncommitted for very large periods of time (in the order of a week or so).