Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Glen,
Some follow up if you don't mind.
> If you share modules between customers, then you should have them all in the
> same repository.
>
Would this still be true if the code that was shared was common in general and changed over time and when working on a project 2 years old the developer would need to work with the same version of the common code that was used 2 years ago? I.E. the common code is more like common knowledge code. Things like how to fill a list box with an API call. It basically stays the same but is probably tweaked over time as further improvements are made.
> You can restore individual modules if there is some sort of disaster, but
> I'm not aware of anyone losing information to CVS. You should consider the
> administration and module sharing aspects more than disaster recovery, since
> those have a higher impact.
>
Ok. I agree 100% here. I doubt the building will burn down overnight but my biggest concern is an end user doing something to the repository that they didn't intend to do but they didn't know better and thus we might have to spend hours getting back to a point where normal development can continue. Basically limiting down time during the learning of CVS phase. Would this type of disaster alter your answer?
> I have a handful of repositories set up. We have several developers split
> into a number of teams that have little interaction and virtually no file
> sharing. I elected to set up one repository per independent group so that
> they could administer their own repositories and control read/write access
> conveniently for each (via the CVSROOT writers file).
>
> Take some time and think about what you want to do with your
> repositories--what scripting, access control, etc. That should lead you to
> a logical ordering of the repositories.
>
> Regards,
>
> Glen Starrett
>
> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
> Of David Williamson
> Sent: Thursday, July 03, 2003 12:18 PM
> To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> Subject: [cvsnt] One Repository or Multiple Repositories
>
> To anyone who has an opinion,
>
> Our custom software shop is new to CVSNT and CVS in general. We are
> debating the best approach to setting up our repository. Should we setup a
> repository for each customer that we have and put each of their projects in
> a separate module or should we have one large software repository that has a
> module for each customer?
>
> The administrators thought was to create a repository for each customer and
> place their projects within it. Reason: If something happened to a
> repository then our down time would be limited to one customer and backup
> recovery would be easier by replacing the entire repository from last
> night's backup.
>
> The users thought was to create a single "Software" repository and create a
> module for each customer and place their projects within it. Reason: It
> would be easier to just go to the same repository and list the modules.
>
> --
>
> ****************************************
> Name: David Williamson
> Company: Integrated Visual Systems, Inc.
> ****************************************
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs
--
****************************************
Name: David Williamson
Company: Integrated Visual Systems, Inc.
Address: 1207-E Crews Road
Matthews, NC 28105
email: dwilliamson at ivsi.com
phone: 704-847-3379
fax: 704-847-4655
****************************************