title: Best way to prevent changes on a branch with Subversion
body: <p>The way we use Subversion is to work on the trunk, feature branches for significant features (> 1 days work) and release branches.</p>
  
  <p>We delete feature branches once they are happily merged but we want to keep release branches around in case they are needed for bug fixes and so on.</p>
  
  <p>Each of us checks out the root of the project as a minimum so we all have a copy of whole directory structure (trunk, branches, releases). As much as I can educate people to check they are working against the trunk, they could end up working against a release branch by accident.</p>
  
  <p>What is the best way to prevent this from happening? I'm thinking of locking all the files in the release branch, would this help? What other options are there?</p>