Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54560
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.185 cause and error)
Message-ID: <4E45B6A9.9080607@lsces.co.uk>
Date: Sat, 13 Aug 2011 00:26:33 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-2.2 SeaMonkey/2.0.14
MIME-Version: 1.0
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: PHP internals <internals@lists.php.net>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net> <CAKUjMCUirzSjVs7GvaZmWmhx2W=h6OGyOX0YKPnUHztRkZc5xQ@mail.gmail.com> <4E3F02E8.2050402@sugarcrm.com>	<alpine.DEB.2.02.1108121119420.4043@whisky> <CAH-PCH4YO1e-+=+38DrhwUe-nR9akJ+c=64vk0ar3GZGM5YOmw@mail.gmail.com> <4E450EB1.6090502@lsces.co.uk> <4E456F2F.7030809@sugarcrm.com> <4E45755F.3020005@lsces.co.uk> <4E4578B6.6050708@sugarcrm.com> <4E45A2BD.7060506@lsces.co.uk> <4E45AFDF.9000001@sugarcrm.com>
In-Reply-To: <4E45AFDF.9000001@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system
 for PHP (or not). Call for Participation.
From: lester@lsces.co.uk (Lester Caine)

Stas Malyshev wrote:
>>> Branches are different things than github forks, for different purposes.
>>> Branch is a project, fork is a workspace. You can have multiple people
>>> work on a project, using multiple workspaces.
>>
>> That is not how Drupal seems to be using git ...
>> http://drupal.org/node/803746#clone - See 'Creating a Working Branch'
>
> I think they're describing local modifications for the Drupal site
> there, not developing Drupal. Think about it: suppose we have Drupal
> versions 7.0, 7.1, 7.2. Those will be branches. But if you want to do
> something into each of them, it won't do for each developer to create a
> private branch for each of them - the amount of branches will quickly
> get out of control. That's when you'd need forks.

Actually they are talking about developing Drupal ... "Once you have finished 
working on your fix or feature, you’ll need to bring those changes from your 
topic branch back into the main fooproject branch."
Bare in mind that this is more like PEAR code than compiled C code, so the end 
target is different but the process is what matters. I'm not sure that is the 
right way to be doing this process, but if it's what is documented?

As Herman says ... "Moving svn to a dvcs is less of a technical change and more 
of a paradigm shift in the fundamental way a user interacts with version control."
There are many ways that DVCS can be abused, so managing things in an agreed 
manner is more what needs to be agreed than the simple - switch to DVCS?

-- 
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