Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54565
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: <4E462F94.6090104@lsces.co.uk>
Date: Sat, 13 Aug 2011 09:02:28 +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: 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>	<4E45B6A9.9080607@lsces.co.uk>	<CAGSj+QtJ-XdNWhpKMR44WLjS5eNh_EiwuOcM7=aR=JugWHZz2A@mail.gmail.com> <CAEZPtU45hGm4STEU8xQvjA8NkjUCaQ8ex8vWKFrWrLzMcrH7tg@mail.gmail.com>
In-Reply-To: <CAEZPtU45hGm4STEU8xQvjA8NkjUCaQ8ex8vWKFrWrLzMcrH7tg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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)

Pierre Joye wrote:
> It seems to have a confusion between forks used for development by
> individuals and (so called) official branches.
Looking back, the point that I was not explaining very well was the fact that 
people seem to think that they need to create a fork into their on-line account 
before cloning to the local copy. On the whole these are not needed, and the 
'sandbox' approach for sharing tangential work seems better? Similarly 
extensions like apt have their own subrepo which can be worked on independent to 
the bulk of the code base?

> About branching, tagging or developing using a DVCS, I can only
> recommend to read the doc linked in this rfc:
>
> http://nvie.com/posts/a-successful-git-branching-model/
>
> It explains one model which has been proven to work pretty well.
This model is ideal for a main trunk. The major advantage to DVCS is being able 
to work on things like PECL modules and even core extensions in parallel to the 
main core. It is only recently that git and hg have finally supported 'subrepo' 
and I see this as the ideal model for my own work. I can create a superproject 
which just combines the extensions (php and third party!) that I am using and 
almost manage them nicely. There are still a few rough edges to this since 
neither git nor hg have been convinced that it is an important requirement ... 
they don't use it themselves which seems strange when their own code base has 
many third party elements? I don't see 'feature branches' as the correct way to 
handle what are essentially self contained elements?

-- 
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