Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54904
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.132 cause and error)
Message-ID: <4E557F52.2040008@lsces.co.uk>
Date: Wed, 24 Aug 2011 23:46:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110815 Firefox/6.0 SeaMonkey/2.3
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
References: <slrnj5appg.6vi.dsp@experimentalworks.net> <4E556A0B.4010406@sugarcrm.com> <4E556AC0.5070706@gmx.net>
In-Reply-To: <4E556AC0.5070706@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Choosing a distributed version control system
 for PHP
From: lester@lsces.co.uk (Lester Caine)

David Soria Parra wrote:
>> I'm not sure choosing DCVS by vote is actually a good way to go here.
>> >  I think we need much more input from people that maintain all the
>> >  infrastructure we're using now and would be doing the move. If we
>> >  don't have people committed to making it happen majority-based vote
>> >  is useless IMHO.
> Sure. I wrote the RFC because I plan to implement it. I will make it
> possible for either Git or Mercurial, but as stated, I prefer doing it
> with Mercurial.
>
> The vote is not a 100% we do it, but rather a: we would like to have it
> that way. So if people choose Bazaar, someone has to come up with a
> solution.

I think the problem here is that _if_ the majority are already committed to git 
anyway, those of use who are using hg or something else are going to be at a 
disadvantage since it is now obvious that cross working will not work especially 
if everything is rolled into the one super repo.

Even the 'decision' to roll everything into single repo copying the current SVN 
history _should_ be something that is put to a vote. The problems of testing 
_sections_ of this vast code base and tracking bugs against them should be a 
perfect reason for a much more modular approach so we can test each module as a 
separate package. And the process is something that _does_ change depending on 
the different DVCS's. So simply voting on the current rfc seems a little 
pointless at the moment?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php