Good afternoon to all, I’ve been revisiting the subject of versioning software today, mostly because I have future plans of bring in additional developers to our project and want a central point for our collaborative efforts. I’ve been looking into TortoiseSVN, Subclipse and Git. As I’ve conducting my research I have been looking for one major feature, the ability for a lead developer to accept/deny pushes, but I simply can’t find anything that meets this need. I am hoping for something similar to the following workflow: 1) Developer X decides to make revisions of an existing project 2) Developer X pulls the most current version of the project from the SVN 3) Developer X finished his work and commits two changes to the SVN 4) Lead developer review the pushes to the SVN a. Push 1 was correct, push accepted and committed to main branch b. Push 2 was incorrect, deny the push and send it back down the pike with edit notes I’ve recently read “branches” are required for this behavior, but unfortunately I know little about SVN and branches, so I am here to hopefully tap into someone’s experience on the subject. At this point I am just information farming, but any information that would help me get the ball rolling would be greatly appreciated. I should note that our projects are private and designed with a specific community in mind, so the project and their source will not be made publicly available; this may or may not alter which SVN software we need to use. Thank you in advance to anyone who is able to offer advice on this subject.