Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54564
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGSj+QtJ-XdNWhpKMR44WLjS5eNh_EiwuOcM7=aR=JugWHZz2A@mail.gmail.com>
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>
Date: Sat, 13 Aug 2011 09:36:51 +0200
Message-ID: <CAEZPtU45hGm4STEU8xQvjA8NkjUCaQ8ex8vWKFrWrLzMcrH7tg@mail.gmail.com>
To: Kiall Mac Innes <kiall@managedit.ie>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system for
 PHP (or not). Call for Participation.
From: pierre.php@gmail.com (Pierre Joye)

On Sat, Aug 13, 2011 at 1:51 AM, Kiall Mac Innes <kiall@managedit.ie> wrote:
> On Sat, Aug 13, 2011 at 12:26 AM, Lester Caine <lester@lsces.co.uk> wrote:
>
>> Actually they are talking about developing Drupal ...
>>

It seems to have a confusion between forks used for development by
individuals and (so called) official branches.

99% of the time one does not care about the forks but when a pull
request is done from it (see it as a patch being sent to the
list/issue tracker).

A fork is also a very good way to work on non trivial changes for a
given period without having to leave the official branches in a non
stable or unfinished state. And even more important, it can be done
publicly with history, etc. That alone is very valuable and much more
easier than having to either maintain mirrors or local repository
(with all disadvantages when it gets out of sync with the main repo).

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.

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org