Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54905
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 24 Aug 2011 19:03:55 -0400
To: internals@lists.php.net
References: <slrnj5appg.6vi.dsp@experimentalworks.net>
 <4E556A0B.4010406@sugarcrm.com> <4E556AC0.5070706@gmx.net>
 <4E557F52.2040008@lsces.co.uk>
User-Agent: slrn/0.9.9p1 (SunOS)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <slrnj5b0qp.6vi.dsp@experimentalworks.net>
Subject: Re: [PHP-DEV] [VOTE] Choosing a distributed version control system
 for PHP
From: dsp@php.net (David Soria Parra)

On 2011-08-24, Lester Caine <lester@lsces.co.uk> wrote:
> 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.
Those wanting to use git and git workflows have a disadvantage when we stay with SVN.
Choosing a VCS happens from time to time and sometimes your favorit is not the winner.
I personally would love to see PHP moving to hg, but if more people like git more, the
hg people have to deal with it.

> 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?
The RFC points out that there will be modules. We will _not_ copy the current SVN
history into one big repo. In fact having everything, pecl, php-src and co in one
repository does not make sense.