svn - Branches for Every Little Change? -
we have client (who has client, has client) driving mad change requests code base (in php). our first response work in main trunk in svn, client comes , requests change needs pushed live servers asap. on other hand, other changes reduced in priority suddenly, came grouped other changes (seemingly).
we thinking of using branch every change request. mad? other solutions might work?
thanks!
edit: hard question choose correct answer for. great answers.
edit: know best answer chose not particularly popular. wanted find technical solution problem. think if client wants software features can deployed in modular fashion... problem should not solved in our use of version control system. have designed software.
edit: it's month later , coworker/client has convinced me multiple branches way go. not due client's insanity, based on our need able determine if feature "ready go" or "needs more work" or whatever. don't have svn me, merge using advice svn cookbook: merge branch from revision branched head revision.
also, using system, merge branches @ point , becomes new qa , live build. branch that.
last edit (perhaps): months later, system still working out us. create branches every ticket , have problems. on other hand, try keep things separate far people working on...
two years later: use git now, , system quite reasonable.
a branch every change request sounds overkill , maybe trouble later.
try group change requests logical areas can see particular set of changes has logically related effect on application. create branches these.
i think real answer question though fix client. need make clear via contract these arbitrary change request going cost them money , might slow them down. if keeps up, svn repository least troubling aspect of project.
Comments
Post a Comment