From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Sun, 20 Jan 2008 08:29:55 +0530 Message-ID: References: <20071230122217.3CA84830B9A@snark.thyrsus.com> <4pd9g15e.fsf@blue.sea.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1200798016 24220 80.91.229.12 (20 Jan 2008 03:00:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 20 Jan 2008 03:00:16 +0000 (UTC) To: "Jari Aalto" , emacs-devel@gnu.org, jaalto@cante.net Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 20 04:00:34 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JGQQC-00013A-R1 for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2008 04:00:33 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGQPn-0003bF-1A for ged-emacs-devel@m.gmane.org; Sat, 19 Jan 2008 22:00:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JGQPi-0003bA-8n for emacs-devel@gnu.org; Sat, 19 Jan 2008 22:00:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JGQPg-0003ar-S9 for emacs-devel@gnu.org; Sat, 19 Jan 2008 22:00:02 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGQPg-0003ao-MN for emacs-devel@gnu.org; Sat, 19 Jan 2008 22:00:00 -0500 Original-Received: from wa-out-1112.google.com ([209.85.146.183]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JGQPg-00027P-35 for emacs-devel@gnu.org; Sat, 19 Jan 2008 22:00:00 -0500 Original-Received: by wa-out-1112.google.com with SMTP id k34so2765192wah.10 for ; Sat, 19 Jan 2008 18:59:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Uqv2o6BcgYqfwESthpDr1/Jds+pZ5K/Fe1Sat7Rnz+o=; b=afvEG/ffs8GKJRxJhzSd/u4AIAvdrEo9LAz7tmoHTkciLvYnVNZTKhp/+M5aPFYjMxmQ66f9HT/xiXLy2W8dtXgCWobU7j32sFEmyKLfJzGc6NJA40YNK7HeAXMksIvgkoN1ThOtlnSRch+wEtahiNMpP3YLl6qyX7JVH7swuLA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=V/Vl11/AJerhvcb2B53AcXabINze7jI3vd/g/7Ihjx952iePHVZ9oXGFbDxyeEaQ5gqSNP8lOM7fcmmBoPMR/dy5f3NAHtmHjd7WkC2BZJrNWtbZP7X45np2nteS8oqAHWqtgMfJeGxvuRDNlTKYhEp7fTBiuY4Dz1oG2x4VNZY= Original-Received: by 10.114.144.1 with SMTP id r1mr2424155wad.53.1200797995707; Sat, 19 Jan 2008 18:59:55 -0800 (PST) Original-Received: by 10.115.73.6 with HTTP; Sat, 19 Jan 2008 18:59:55 -0800 (PST) In-Reply-To: <4pd9g15e.fsf@blue.sea.net> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:87092 Archived-At: Hello, I request you all to consider the deployment scenerio too and please do not ignore users/dev on M$. - git needs a bunch of unix tools and the cygwin bash shell. The user will have to start getting used to the unix way - git needs perl (on top of shell) - mercurial just needs python I personally find tools with large deployment dependancies a real problem as each component will keep getting fixes/updates. -dky On 1/19/08, Jari Aalto wrote: > * Sun 2007-12-30 Eric Raymond gmane.emacs.devel > * Message-Id: 20071230122217.3CA84830B9A@snark.thyrsus.com > > > > This is a typical modern open-source project. It's not even a > > particularly large one -- no more than a dozen core devs, 58 > > developers total. Here are the collaborative tools we use every day: > > > > * Source control with Subversion > > I saw discussion that a change from CVS to distributed version control > is under consideration. To shed a little light to the DCVS scene, here > is one of my presentations: > > http://www.cante.net/~jaalto/doc/version-control-systems.pdf > > Follow the small knobs "*" and underlined words to find out more > information (URL links). > > SUMMARY > > The git seems to be overall winner. It's a clear choice for big > projects. > > - Git: phase of development is staggering and in few years > the UI/OS compatibility issues are past > * The branching and merging "in place" (no separate directories) > is thing that excells over any other VCS/DCVS. A Brilliant invention > and simple to use. > * Vibrant community: ask a question and you get instant answers to > anything. > * The weak point is UI: it is very complicated. Currently > requires very steep learning curve even from users that > have prior experience (CVS/SVN stc.) > > - Bzr seems to take second place. It has a long term progression path > and support, very strict code quality and clearly defined > development phases. > * I estimate that it will improved in two years time to meet > needs of almost any user. > * Out of the box Central / semi-central / distributed support > (much nicer than git's) > * The best is UI: it's very smooth, uniform, logical and > a CVS/SVN user is immediately at home with it. > * Weak point: performance problems with big repositories with > lot of old history. These will however be solved soon (1 year; > during 2008). > > Despite the popularity that Hg has been chosen by "Big projects" like > OpenJDK etc., I would not incline to recommended it. Reasons: Too slow > release schedule, small dev team, unclear roadmap. My observation is > based on: > > * Page 11: "DCVS Release Schedules" > * Page 12: "Pace of Development (1)" > * Page 13: "Pace of Development (2)" > > Jari > > NOTES > -------------- > > VCS = Version Control System (software) > git = Git http://git-scm.org > bzr = Bazaar http://bazaar-vcs.org > hg = Mercurial http://www.selenic.com/mercurial/ > > > > _______________________________________________ > Emacs-devel mailing list > Emacs-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-devel > -- Sent from Gmail for mobile | mobile.google.com Contents reflect my personal views only!