From owner-freebsd-questions@FreeBSD.ORG Thu Dec 22 05:21:21 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 928C5106566B for ; Thu, 22 Dec 2011 05:21:21 +0000 (UTC) (envelope-from rbyrnes@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 23FEC8FC0C for ; Thu, 22 Dec 2011 05:21:20 +0000 (UTC) Received: by eaaf13 with SMTP id f13so10254058eaa.13 for ; Wed, 21 Dec 2011 21:21:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=9aOyAo3L5feoWk1Su8KV3pD7m137IJvm+SKRA93T6iw=; b=gbSirVzQykivJN1/ND7x+dYAV/9ytI8jfp+QSqD6FoyaBglzZE7o67hZwlKtcEK8gg X6pe1m/vXpPIQxUc6JT3ON0ob4LUxBOsLUUUnDxH5OQGhFkb3ERjt/bBskjuQyD/EGK7 CBeNlye4NeQgHmaGDKS15JanfraWGwKUktciI= Received: by 10.204.130.85 with SMTP id r21mr2732944bks.38.1324529623499; Wed, 21 Dec 2011 20:53:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.100.144 with HTTP; Wed, 21 Dec 2011 20:53:22 -0800 (PST) In-Reply-To: References: <4EF29AD7.5040807@herveybayaustralia.com.au> From: Rob Byrnes Date: Thu, 22 Dec 2011 15:53:22 +1100 Message-ID: To: Outback Dingo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ss griffon , freebsd-questions@freebsd.org Subject: Re: Revision control advice X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2011 05:21:21 -0000 On 22 December 2011 15:07, Outback Dingo wrote: > On Wed, Dec 21, 2011 at 10:24 PM, ss griffon wr= ote: >> On Wed, Dec 21, 2011 at 7:49 PM, Da Rock >> wrote: >>> On 12/22/11 11:37, Chris Hill wrote: >>>> >>>> Hello list, >>>> >>>> I apologize for this posting being not-much-on-topic, but my other >>>> resources have come to naught and I think you folks may have some expe= rience >>>> in this area. >>>> >>>> I'm looking to set up some sort of revision control system at work. Si= mple >>>> enough, except that our situation is approximately the reverse of what= most >>>> revision control systems are designed for. >>>> >>>> Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds o= f >>>> small, rapid-fire projects that are created at the rate of 3 to 20 per >>>> month. They last a few days or a few months and are (usually) not deve= loped >>>> afterward. Each project has one to three developers working on it, som= etimes >>>> simultaneously. Usually it's one guy per project. >>>> >>>> Since my programmers are not necessarily UNIX-savvy, I'd like to deplo= y a >>>> web interface for them which will allow them to create new repositorie= s >>>> (projects) as well as the normal checkin, checkout, etc. I want to set= this >>>> up once, and from there on have the programmers deal with managing the= ir own >>>> repos. And heaven forfend exposing them to the horrors of the shell. >>>> >>>> I've built a test server (9.0-RC3, amd64) for experimenting with this >>>> stuff. So far I've installed and played with: >>>> =A0- fossil. I like the simplicity and light weight, but it doesn't se= em to >>>> allow creation of new repos at all (let alone multiple ones) from the = web >>>> interface, and the documentation is meager. I've pretty much given up = on it. >>>> =A0- subversion, which looks like the heavy hitter of RCSs, but it's n= ot at >>>> all clear to me how to handle the multiple-project scenario. Still wor= king >>>> on it. >>>> =A0- git looks promising, but I have not installed it yet. >>>> >>>> If anyone can point me to a tool that might be suitable, I would be mo= st >>>> grateful. >>> >>> I'd suggest subversion. It allows individual files to be versioned, you= can >>> setup a webdav interface, and there are other tools that can help maint= ain >>> it. >>> >>> Forget the individual repositories. Setup a single repository and have >>> directories for each project. in each directory you can then setup trun= k, >>> branches, whatever, as per best practices in the Book. >>> >>> Designate a person or two to administer, and use directory level auth, = or >>> another alternative I haven't thought of. >>> >>> My 2c's anyway. HTH >>> >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd= .org" >> >> Yeah I would second what Mr Rock says. =A0Set up a single repo where >> folders can be used for projects. =A0Since svn lets you checkout sub >> folders of a repo, each developer can check out the folder that >> corresponds to their project. =A0Also, Tortoise svn is a very nice >> graphical utility that will allow your developers to manage there svn >> folders without even needing a web interface (most non unix people >> that I know like tortoise), so there is less maintenance for you :) >> Finally, kudos to moving towards using version control, its an >> important step for a software company. > > git or mercurial - best choices For what reasons? Rob --=20 Idiot : =A0 =A0 A member of a large and powerful tribe whose influence in human affairs has always been dominant and controlling. (Ambrose Bierce - The Devils Dictionary)