Thanks for the correction, trunk development sounds like a lot of pain imho. Is it really that hard to use branches in svn, and merge later on to trunk? What happens if you have 3 people working on different things working straight on the trunk?
People working on different branches and changing the same files (in those different branches) is a really really bad thing. And this is something svn only handles with manual merge conflict handling.
Key to successful development with a lot of people on a shared code base is continuous integration. Trunk based development is also an essential part of proper CI.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the correction, trunk development sounds like a lot of pain imho. Is it really that hard to use branches in svn, and merge later on to trunk? What happens if you have 3 people working on different things working straight on the trunk?
People working on different branches and changing the same files (in those different branches) is a really really bad thing. And this is something svn only handles with manual merge conflict handling.
Key to successful development with a lot of people on a shared code base is continuous integration. Trunk based development is also an essential part of proper CI.