On Thu, Nov 11, 2010 at 4:26 AM, Jonathan dos Santos < jonat...@prioriti.com.br> wrote:
> Hello, first of all if I’m infringing any rule on the mailing list I’m > really sorry. I’ve tryied searching but couldn’t find a good phrase to > describe my problem. > > > > I’m pretty new to svn and version control so this question may be very > elementary: > > > > In our company we use SVN to manage the source code of our Delphi > applications, generally we use trunks tomake changes to the source code and > we only generate tags when we need to deploy the implemented features, still > bugs happen and since the software is used in critical processes (at least > for our clients they are critical…) , we need to fix bugs and deploy the > corrections quickly sometimes, > > generally we need to develop both in the trunk and the tag and sometimes > that’s really frustrating – mainly because some processes are huge and after > each minimal change we need to test it over and over in a dozen ways, I try > my best to use patches or to convince the deployer to make a new tag. Still > It happens more often the I wish it too, is there a way to prevent this > through SVN or its more of a company problem unrelated to svn usage? Or > maybe its just me ? > > > > Thanks for your help in advance > It sounds like a little of both. 1) Tags are usually read-only, so you could prevent modification via pre-commit hooks or path-based authorization of some sort. 2) The 'standard' process for using trunk/branches/tags structure is: develop on trunk, merge to a release branch, and system-test there. Once ready, tag the branch. If a change needs to be made (ie urgent fix), then make it on trunk, merge to the release branch, and re-tag. Cheers, Daniel B.
