Branching Strategy
From: Eneko Gonzalez <enekog_at_clientes.euskaltel.es>
Date: 2005-04-24 12:36:04 CEST
Hi all,
I'm a svn newbie (i've worked with CVS but never with branches) and i've
Nowadays, I have three development stages in my projects: development
The problem i have is that in this projects, some configuration files
My idea is to have three branches: trunk (development), testing and
All the development should go to trunk brach, and testing and production
-> żIs there another (and better) way to do this?
Small fixes to a testing release would be done in the testing, and
-> żIs this safe, or is it going to be a merging-hell?
If i want to test something experimental that can stop the other
-> żIs this the correct usage of a branch?
Besides, i want to know if this strategy would need a lot of free disk
If you see any problem or better solution please, let me now ...
Thanks in advance,
Keko
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.