From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 12:22:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F46B16A4E3 for ; Sat, 6 Nov 2004 12:22:41 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94E3343D1F for ; Sat, 6 Nov 2004 12:22:40 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CQPaZ-00034M-00 for ; Sat, 06 Nov 2004 13:22:39 +0100 Received: from anyanka.rfc1149.net ([81.56.47.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Nov 2004 13:22:39 +0100 Received: from sam by anyanka.rfc1149.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Nov 2004 13:22:39 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Samuel Tardieu Date: 06 Nov 2004 13:22:28 +0100 Organization: Avian Carrier & Friends Lines: 52 Message-ID: <87oeibnp4r.fsf@beeblebrox.rfc1149.net> References: <418C0EED.1060301@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: anyanka.rfc1149.net User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Leafnode-NNTP-Posting-Host: 2001:660:330f:f810:200:39ff:fe25:3aa2 Sender: news Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 12:22:41 -0000 >>>>> "Scott" == Scott Long writes: Scott> Second, it means that development efforts for major features Scott> will continue to shift out of CVS and into Perforce. This Scott> already happens quite a bit, so it's not as radical of a change Scott> as it seems. Wouldn't it also be a good time to reevaluate the development system? New free software revision control systems such as GNU Arch are now mature and could be used precisely for this kind of things. For those not knowing it, let me introduce GNU Arch by small examples of what you can do with it: - Anyone with read access to a branch can create a new branch (tag a branch in GNU Arch vocabulary) on its own system and develop in it; this doesn't involve the originating system any more and doesn't consume any resource. - Merges between branches take in account the whole history of those branches and can be done at any point; if a developper wants one of its branch to be reviewed by others or merged into the main branch, she only has to publish its branch read-only. - A developper may base her own work on a branch published by another one; this allows development of dependent features even if the original feature has not been merged in yet. For example, if phk had done his GEOM development in a publicly readable GNU Arch branch, anyone could have tested it and develop new GEOM module even before it has been merged in the main branch. - Anyone could work on fixing bugs in their own branches and then request a merge to the main one. Also, even before the bug fixes are merged, other developpers can pick them up and integrate them in their own branches and test them in different configurations (to reuse my previous example, phk would be able to pull candidate bug fixes into his GEOM branch and test whether it would break something or not). - GNU Arch doesn't use a server -- files are published using HTTP, FTP, WebDav, SCP, ... I have used Perforce for a long time before, and I can say that GNU Arch outperforms it by a huge factor in my opinion. Moreover, there are no user limits, no accounts to create on a server I don't intend to open a can of worms, but I think now would be a good time to start small experiments wrt new RCS software. Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam