Multiple teams, same codebase

[ozrug]

A client of mine has some developers using VSS 6.0 who have never had formal training on it. They need to manage multiple teams working in the same codebase. Each team may be working on a separate version of the product: one group on a brand-new version, another on enhancements to the last-released version and so on.

How can VSS handle this requirement?

 

[TomasDill]

Hi!

Hmm, VSS is a tool to handle FILES, not a project flow, specially with different versions.

I can recommend only to put each version of product you're working on to different folders in the VSS. Than, each team will have its own folder (copy of the project). Some files could be shared using links or filder usage specification in the native VSS client (some development tools don't support this, such as VFP), so they will work only on the changable part and don't use such common parts as base class definitions, framework files etc that do not change across versions.

Hope this helps.

Vlad Grynchyshyn
vgryn@softserve.lviv.ua

http://www.softserve.lviv.ua

The professional level of programmer could be determined by level of stupidity of his/her bugs