I use SVN to manage source code in a classic ASP application that I develop / maintain. I support several versions of the application, as required by my company:
- Discovery / playground version - where I do all the work. My working copy
- Dev / Test (without access to these sites / servers)
- Live version (without access to these sites / servers)
That's when I came across difficulties:
- Work on project A is ongoing and ongoing.
- Project A Advances in Dev / Test Using Log Export
- There is a problem with Project A, and it stalled in Dev / Test
- Project B is being implemented, prepared and completed.
- Project B is now based on Project A, but there are parts of Project A that are not ready for prime time.
Just “be careful not to screw anything” is not enough, is there anything I can do to make sure that parts of projects can stop in the development process without lifting everything?
The need for a web server in this process seems to be causing me problems. I know that I can fork out Project A when it goes to Dev / Test, and then merge it back into the trunk when it lives. Also in this way I can return my playground from the branch and execute Project B without any action from Project A, which could accidentally go on the air. However, then I can not play Project A on my playground. Should I create a new playground site for each branch?
, , , , , - .
!
EDIT:
: - , - WC . , , . , , . , . , .
, ?