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.
So you did not tell the whole story then: 1. You are a contract work organization 2. Your customer has his own CVS server in which he wants to maintain the code 3. You want to use CVS also for your own development (which is good!) 4. You have different teams, presumably working with different customers 5. THere must be no leak between the customer code bases or teams 6. But you are allowed to use common library code in all projects In this case I think you should deliver a complete file set at release time to the customer(s) or if you are allowed acces put it in yourself in their CVS server. The code base you deliver should be extracted via cvs export from your own internal server and then imported into the customer server. For your internal work you can set up virtual modules definitions for the different projects where the common library code is included in all project modules but the actual project code comes from other modules where you have enforced ACL:s such that they are not possible to check out except by authorized persons. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Manjunath N.S. Sent: den 31 maj 2005 10:53 To: bo.berglund at telia.com Cc: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] Re: Sync of Local and Remote CVS Server Hi, once again thanks lot for your valuable ideas, but I have other constraints like Network Speed for Accessing CVS Server and to have complete control on the CVS Server, unfortuantely we donot have control on the Remote CVS Server,as this Server are maintained by our Client. That's why i am going for seperate Local CVS Server.. thanks Manju On 5/31/05, Bo Berglund <Bo.Berglund at system3r.se> wrote: > No need even for this... > > Just create a separate branch for each "team" and set the permissions on these > branches such that they are only accessible for that team. > Then lock down TRUNK so that only a build manager can write anything there. > > CVSNT has a big set of possibilities to set permissions very fine grained so > that you can control even branch access on single files. > > /Bo > > -----Original Message----- > From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf > Of Manjunath N.S. > Sent: den 31 maj 2005 08:00 > To: bo.berglund at telia.com > Cc: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: Re: [cvsnt] Re: Sync of Local and Remote CVS Server > > > Hi, > > what you said is right, But my requirement is I donot want share my > development code to other teams, only release source code I want to > share, for this reason I want to maintain seperate local CVS server > for my module. > > So what I will do is, on my local CVS server I will have two branches, > one branches for sycnhronizing with Remote CVS Server and other branch > for the developement purpose. So for my relase I will merge these two > branches make it well tested. Then I will add new release to Remote > CVS Server. > > But How to Sync Local CVS Branch with Remote Server. > > thanks > manju > > > > > > > On 5/31/05, Bo Berglund <bo.berglund at telia.com> wrote: > > On Tue, 31 May 2005 10:21:45 +0530, "Manjunath N.S." > > <manjunath.ns at gmail.com> wrote: > > > > >Hi, > > > > > >we have parallel development team, each works two different module, > > >each of these module has dependencies. So the main aim is if one > > >module breaks due compilation problem or some other thing, it should > > >not affect the other team. > > > > > >To acheive this what we have done is we take stable code from Main CVS > > >into our local CVS,and we start working this local CVS. If in between > > >from the Main CVS, if there is release is made, then those latest > > >changes from Main CVS we want to include into our Local CVS. > > > > > >hope this will be clear.. > > > > > >thanks > > >manju > > > > This is what branches are used for... > > Team1 works on branch Team1_FeatureX > > Team2 works on branch Team2_FeatureY > > Mainline contains only verified release code > > > > Whenever there is a verified release on any branch it gets merged to > > TRUNK and a release tag is set. > > At this time any of the teams that need to keep their code up-to-date > > with the releases merges the Release tag code back into their branch. > > So now they have a merge of their own work and the tested release > > code, which is their responsibility to verify and commit (on their > > branch). > > > > Why do you not consider this procedure??? > > It uses the functions of CVS that is there for this very purpose.... > > > > > > /Bo > > (Bo Berglund, developer in Sweden) > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 > _______________________________________________ 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