From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 41ECABB81 for ; Tue, 21 Dec 2004 23:03:38 +0100 (CET) Received: from gw.orcaware.com (bdsl.66.12.233.174.gte.net [66.12.233.174]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id iBLM3ZIK009562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Dec 2004 23:03:37 +0100 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by gw.orcaware.com (8.12.8/8.12.8) with ESMTP id iBLM3U47027425; Tue, 21 Dec 2004 14:03:31 -0800 Message-ID: <41C89DB2.4020105@orcaware.com> Date: Tue, 21 Dec 2004 14:03:30 -0800 From: Blair Zajac User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Baretta Cc: caml-list@yquem.inria.fr, Ernesto Ferrari , Paolo Donadeo Subject: Re: [Caml-list] [OT] Rant about VCS: Conclusions References: <41C3126A.3060101@barettadeit.com> <20041217213753.GA2295@pegasos> <20041218092716.18ca0ed7.ocaml-erikd@mega-nerd.com> <41C7E7EE.6030709@barettadeit.com> In-Reply-To: <41C7E7EE.6030709@barettadeit.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Miltered: at nez-perce with ID 41C89DB7.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; zajac:01 orcaware:01 caml-list:01 baretta:01 wrote:01 wrote:01 sven:01 luther:01 sven:01 luther:01 developement:01 cvs:01 merging:01 cvs:01 merging:01 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on yquem.inria.fr X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.0 X-Spam-Level: Alex Baretta wrote: > Erik de Castro Lopo wrote: > >> On Fri, 17 Dec 2004 22:37:53 +0100 >> Sven Luther wrote: >> >> >>> We have had good success with subversion, >> >> >> >> I looked at subversion before deciding on Arch. ... This allows me to >> run a couple of parallel developement branches, share those that >> need to be with other external developers and merge acorss the >> branches pretty much at will. >> I have not seen another source contol system which handles >> branches as nicely as Arch. >> >> Erik > > > Paul Snively wrote: > > It really does sound as though you're edging from "version control" > > into "configuration management." If that's the case, you may want to > > look at Arch and its surrounding tools. In particular, the > > documentation at > > > projects.html>, "Multi-tree Projects and Configuration Management," > > might be helpful to you. > > There seems to be some agreement on the fact the "Configuration > Management Tool of Choice for Discriminating Software Company" is Arch. > Our project seems complicated enough to seriously consider moving to arch. > > We have currently reimplemented our project's storage as a > non-denumerable set of darcs repositories, distributed in a > discontinuous manner over our company's network. I envision a > significant risk of complexity explosion, because darcs only supports > branches as duplicate repositories, which sounds like a nightmare. > However, darcs is about as much as would fit in before Christmas. Maybe > Santa Claus will put a working arch repository under my Christmas tree... > > Alex Alex, Coming into this thread a little late and being somebody who has commit rights to the Subversion source code, I'll try to make a couple unbiased comments on some of the statements made in this thread :) The Subversion code is stable and production ready. There were issues with the initial versions of Subversion and I had my share of locked repositories, but probably like early versions of every version control system, they have been resolved. Also, the Subversion team eats their own dog food. At this "Discriminating Software Company", we moved from CVS to Subversion one year ago and our Subversion repositories now contain 5.4 Gbytes of code, documentation, Squeak binaries, PDFs, etc. We haven't lost any data. From a company's point of view, other things you get that I don't believe the other mentioned open-source VCS' have are professional support and native Windows clients. In our team, we have people creating documentation (Word documents, PDFs) for the code we write and we use TortoiseSVN, a Windows Explorer shell integration which makes it easy for non-coders to use a VCS while keeping a familiar interface, in this case just Windows itself. Regarding merging, unlike CVS, Subversion has changesets, so merging is simply picking the changeset(s) you want from one path and applying it to another: % svn merge -r 2345:2347 branch/latest_changes branch/stable You may want to check these URLs and I'll leave the propaganda at that :) http://subversion.tigris.org/propaganda.html http://www.red-bean.com/sussman/svn-anti-fud.html http://tortoisesvn.tigris.org/ Regards, Blair -- Blair Zajac Plots of your system's performance - http://www.orcaware.com/orca/