Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29983
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.180 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=AuBh5JJSeOlXsQDJruXozqyLf2F1GlqI5BdPRxusp6+WSt82kigeTfa3UEIBva4aCWOyOQgIREx7c/bD+PZEG7Coj03Q/d/sJpaRv9m6yYKCnHepf72wGXMi4rStFCHC6ToJnT2OrkR54RaVJ1mN4zWsP7AxMjgCL7ZKCRETel0=
Message-ID: <fe05d1540705310117y1e1c6bcbn3ceb4ff49c91fa5f@mail.gmail.com>
Date: Thu, 31 May 2007 10:17:48 +0200
To: "Andi Gutmans" <andi@zend.com>
Cc: "Rasmus Lerdorf" <rasmus@lerdorf.com>, sniper@iki.fi, 
	"PHP Internals List" <internals@lists.php.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CE418708@us-ex1.zend.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com>
	 <001d01c7a27f$6d12bf80$39dc2f52@foxbox> <465D13E4.9050201@lerdorf.com>
	 <1237063851.20070530094541@marcus-boerger.de>
	 <465D2FB0.5060308@lerdorf.com> <014601c7a293$3e047440$39dc2f52@foxbox>
	 <465D35D2.4050001@lerdorf.com>
	 <1180530241.3496.13.camel@localhost.localdomain>
	 <465D90D3.1090601@lerdorf.com>
	 <698DE66518E7CA45812BD18E807866CE418708@us-ex1.zend.net>
Subject: Re: [PHP-DEV] better changeset tracking
From: pierre.php@gmail.com (Pierre)

Hi,

On 5/31/07, Andi Gutmans <andi@zend.com> wrote:

> As we expect many more years for PHP we should make sure that the train
> we're riding has momentum and can help us continue to scale our dev
> process. I think SVN is the right train to hop onto.

I would like to propose Git. I think it is more appropriate for large
projects like PHP. I do not have the time to provide a full list of
its advantages or features but here are some of its huge advantages:
- user tree
- its ability to push patches from a tree to another
- CVS bridge (non developers can still checkout/provide patches using cvs)

For example, it is possible to have (only examples! :): Dmitry working
on a complete rewrite of the engine,  Stan is fixing TSRM and the QA
fixing the stable/dev trees. The RMs can still prepare releases in the
main tree.

The release manager can then safely choose which patches should be
pushed. The developers do not have to take care about the release
process in their trees. Experiments can be done safely in a tree and
merged (even partially) when they are ready.

freedesktop has moved to GIT some time ago and for what I heard from
the developers, it is a huge improvement in their development process.
The only bad point (which exists with any other migratrion) is the
time required to learn the new tool.


--Pierre