Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50680 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68215 invoked from network); 29 Nov 2010 06:31:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Nov 2010 06:31:38 -0000 Authentication-Results: pb1.pair.com header.from=clint@ubuntu.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=clint@ubuntu.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain ubuntu.com from 65.98.207.160 cause and error) X-PHP-List-Original-Sender: clint@ubuntu.com X-Host-Fingerprint: 65.98.207.160 xenclint.srihosting.com Received: from [65.98.207.160] ([65.98.207.160:57949] helo=xen.spamaps.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/50-64483-8C843FC4 for ; Mon, 29 Nov 2010 01:31:37 -0500 Received: from [192.168.1.102] (76-216-240-245.lightspeed.irvnca.sbcglobal.net [76.216.240.245]) by xen.spamaps.org (Postfix) with ESMTP id B4CDE16019D; Sun, 28 Nov 2010 22:31:32 -0800 (PST) To: Lester Caine Cc: PHP internals In-Reply-To: <4CF1311F.9070802@lsces.co.uk> References: <4CEE0ADA.5010705@lsces.co.uk> <4CEE1327.7050405@lsces.co.uk> <9A.53.20008.2113EEC4@pb1.pair.com> <4CF1311F.9070802@lsces.co.uk> Content-Type: text/plain; charset="UTF-8" Date: Sun, 28 Nov 2010 22:31:32 -0800 Message-ID: <1291012292.2879.13.camel@clint-MacBookPro> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] git anyone? From: clint@ubuntu.com (Clint Byrum) On Sat, 2010-11-27 at 16:26 +0000, Lester Caine wrote: > At the end of the day however it probably has nothing to do with which DVCS is > used for master copies. The interoperability now available does mean that we can > safely ignore any 'choice' and simply use our own preference locally :) It will > be the management of processes which are the main problem, something that is > still outstanding anyway currently ... Agreed that most of them are pretty interoperable at this point. ** DISCLAIMER: I am an employee of Canonical, owners of Launchpad ** May I suggest bzr+launchpad as another alternative. MySQL has successfully migrated, and it would offer some real benefits to the process management. * Release and Milestone Management for bugs and specs (Blueprints) * Blueprints tied to milestones/releases (Blueprints == RFC's) * Powerful web based merge proposal management. * Branch aware bug management (bzr commit --fixes lp:1234567 && bzr push automatically attaches the branch to the bug) I've not used git or hg much at all, but bzr has always satisfied my needs for DVCS, and has recently gotten much faster and more space efficient than it was in the past.