How to use SourceSafe in my organisation?
Davy Jonet
What is the best working-method for Source Safe :
* 1 SourceSafe Database for all the departments
(administration, production,finance, ...), or 1 SS Db per
department.
With 1+ SS Db, user management must be set up for all
the databases.
* A project (v1.0) is in production, and the development
of project (v2.0) will take several months of time. Bugs of v1.0
have to be solved, without installing v2.0 with the bugfix.
This can be solved with Branching & Merging, but what's the best
method
of using branching.
* What's the use of shadow folders? When are the relevant, because
they are read-only? My guess is to use them for compilations, and
package-creation.
If anyone can give me some hints for using Source Safe in an organisation
with ca. 20 developpers for 4 departments.
Please mail me (just remove the NOSPAM_).
Thanks
Davy Jonet
---------------------------------------------
Regionale Uitgeversgroep N.V.
3500 Hasselt
Belgium
Nick
I can only speak to the first question. I would recommend the separate
databases for each department, because i have run into times when i needed
to perform maint. and had to get everyone out.. this is much easier if you
have a smaller group to contend with... and then you don't have everyone
waiting to work only a department. Performance can be an issue if the dbs
get large, keeping them broken up will of course put that day off longer...
"Davy Jonet" <NOSPAM...@rug.be> wrote in message
news:%GJy5.147$%64....@nreader1.kpnqwest.net...
Weston Morris
I agree with Nick's thinking on multiple databases. See my other comments in
the other microsoft.public.sourcesafe ng.
"Nick" <n...@iquest.net> wrote in message
news:OfYrxUM...@cppssbbsa02.microsoft.com...