Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39328 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11545 invoked from network); 25 Jul 2008 17:20:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2008 17:20:07 -0000 Authentication-Results: pb1.pair.com header.from=parasane@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=parasane@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.229 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: parasane@gmail.com X-Host-Fingerprint: 66.249.82.229 wx-out-0506.google.com Received: from [66.249.82.229] ([66.249.82.229:53208] helo=wx-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/3E-22699-64B0A884 for ; Fri, 25 Jul 2008 13:20:07 -0400 Received: by wx-out-0506.google.com with SMTP id s12so1093312wxc.26 for ; Fri, 25 Jul 2008 10:20:03 -0700 (PDT) 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=6yAE2vA31rpiUricc6pG3kmNP+KyRMqiAjjTGzpqncc=; b=G4FkA3Jq80bkgEqOl3C2P2IDv+rSkcR+THW+h82IxXgCUjdXSc7MbMM+TulIJRZXPO mU19xcjlVbFoKJzXEl/nOiyzmxmbGGfktXT5X866AunyOiZCcMU0CKuKHhSNXbYBG/JK rgihWcMVNiX3M4Kaw654LALF6TwSQ29pprmJI= 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=g7//tadH0X5fYfKXF78fITRYadP9Y7ty/ahtaaVuEt5ixAoekbrssUKjxkRQYMlQuu t0j/qBHhy5v55eIjTHoYiMZXaVDLrn5UhLm43L0Nepxj/cZTukjpnJMMMFTZyxOAt5Yi 9LM9epb575oaTIJZc5mnrUMWn15oHichLSf74= Received: by 10.100.227.20 with SMTP id z20mr3357998ang.62.1217006403770; Fri, 25 Jul 2008 10:20:03 -0700 (PDT) Received: by 10.151.85.13 with HTTP; Fri, 25 Jul 2008 10:20:03 -0700 (PDT) Message-ID: Date: Fri, 25 Jul 2008 13:20:03 -0400 To: RQuadling@googlemail.com, "PHP Developers Mailing List" , "SVN Migration List" In-Reply-To: <10845a340807250215o26b80e88waae03f5429615a07@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40FEB6C9-9B66-4761-8B9C-0E70158D9962@wanderingknights.org> <10845a340807250215o26b80e88waae03f5429615a07@mail.gmail.com> Subject: Re: [PHP-DEV] CVS to SVN Migration From: parasane@gmail.com ("Daniel Brown") On Fri, Jul 25, 2008 at 5:15 AM, Richard Quadling wrote: > > As a windows user my observations/opinions are ... .... taken with a grain of salt. ;-P Isn't discussion about how to add on to SVN and which tools will be better-suited for development a decade from now counterproductive to the idea at hand? SVN and CVS are the industry standard right now, with SVN being the better-supported and, in many ways, more economical and prudent approach. I'd be afraid that requiring existing and future developers to learn newer technologies would stall several aspects of the project, introduce many new problems, and hinder the advancement of the language as a whole. There's no reason other things couldn't be introduced at a later point, but my personal preference would be to approach the migration one step at a time. Making small bits of progress over time (while simultaneously being able to focus on PHP) seems to be more sensible than trying to radically change everything at once, negating a proven system in favor of "what might work better." -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.