Hello SVN Experts,
I have the task to evaluate SVN, features, process transition from existing
project etc.
For this i need some ideas from the SVN experts.
1. Is there a baselining concept present in SVN? If not how i could achieve
in a different way?
2. SVN follows update-modify-merge model - i see this has immediate workflow
as the code is not validated by a BM. As a version control tool this is just
enough. But we have a slightly different requirement and wanted to extend
the functionality bit more.
Lets say if i wanted to implement a process where the BM checks all
checked-in versions before the revisions are visible to others?
also a process where the Deverlopers gets only the validated code from the
BM? How to ensure this with SVN?
3. Is there a way where i can specify the lifecycle for the souces??
4. Our installation includes apache, so the repos can be browsed from the
Web. Would like to know is there a possibility of doing version control
activities from the Web Client? If yes pls provide me some info.
Thanx in advance
Rgds
Thyag
Received on Fri Oct 7 12:29:27 2005