Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54566
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain s1998.tu-chemnitz.de from 134.109.228.11 cause and error)
Message-ID: <4E46391E.8080609@s1998.tu-chemnitz.de>
Date: Sat, 13 Aug 2011 10:43:10 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: 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> <4E462F94.6090104@lsces.co.uk>
In-Reply-To: <4E462F94.6090104@lsces.co.uk>
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: Michael.Grunert@s1998.tu-chemnitz.de (Michael Grunert)

On 08/13/2011 10:02 AM, Lester Caine wrote:
> 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?

Just to throw in some comment, you did a really good job to confuse 
people in this thread. In the beginning i really got the impression you 
were totally against dvcs and now you praise them and argue in their 
favor against people who want them too .. maybe i just misread some of 
the mails but thats my overall impression so far ..

>> 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?

So did you read the workflow document? I do have some doubt there ..
A "feature branch" does not refer to some self contained  element you 
could or even should place into a subrepo like a pecl extension or 
module. A "feature branch" is meant for a distinct unit of work, like a 
new feature or a bug fix that has to be merged with the main branch 
sometime in the future anyways. As soon as this feature or bug fix has 
been completed the feature branch dies/dries up .. which is obviously 
bad in something like svn as those branches would clutter up the 
repository but can be handled really good in dvcs as the new branches 
are only local or in some loosely coupled public forks/clones and can be 
pulled/pushed into the "main repo" as needed.

just my 2 cents before i get a headache from this

Regards,

  Michael