knittala

Hi All,

We have a project going into production on sunday. We are using Sourcesafe for version controlling till now.

Project contains ( TIBCO project + External Classes( at a different location))

My question is how to handle this after the production release. We need to add new services to the project, but this is due for a MAY deployment. But, if we get any
changes or defects in the UAT or PROD, we need to address them as early (seperately) as possible with out incoporating the may release changes.

How best can this be done in SourceSafe. Also, one more issue, we need to address the PROD and UAT issues/defects independently, i.e. if we get any defects only in
UAT, then we need to make changes to that code, so that it will effect only the UAT code, but not the production or the development code.

What is the best possible solution for this problem.

Please send me email if you need further information kiran.nittala@hotmail.com. Any help would be appreciated.

Thanks,

Kiran.



Re: Visual Studio Source Control and SourceSafe Best possible way to Source control TIBCO Projects in SourceSafe

Richard Berg MSFT

This is a classic example of branching. Create separate branches of your project for each deployment. You can then merge changes between the branches as needed.



Re: Visual Studio Source Control and SourceSafe Best possible way to Source control TIBCO Projects in SourceSafe

knittala

Hi Richard,

But every one I spoke tosaid that, VSS is not that goof when branching and merging a project. Is that true

Have you had any troubles in the past while branching and merging a project.

Thanks,

Kiran.





Re: Visual Studio Source Control and SourceSafe Best possible way to Source control TIBCO Projects in SourceSafe

Richard Berg MSFT

It's not as good as modern, complex systems like Team Foundation or ClearCase. But it does work fine. In terms of features it's roughly comparable to CVS, SVN, Vault, and the like (albeit with a vastly different branching model -- "path space").