Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59158
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
Date: Mon, 26 Mar 2012 01:44:40 +0500
Message-ID: <CAAAa2shEWhNfUzah8zSY379doK0qG7mWnLgs8Did9Wh12n_5rg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Adopt GitFlow process
From: confik@gmail.com (Alexey Shein)

Hi, internals!

There was a discussion recently on IRC that our current git working
process is not perfect (especially about keeping one branch-only
bugfixes) so that's a
suggestion to use (and modify to better suit our needs) nvie's gitflow
process and git-flow tool he developed to ease the process.
If you're not yet familiar what is that, please read
his wonderful article   http://nvie.com/posts/a-successful-git-branching-model/
another wonderful article about the gitflow tool
http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/

go to git-flow project on github: https://github.com/nvie/gitflow

watch video tutorials about gitflow
http://buildamodule.com/video/change-management-and-version-control-deploying-releases-features-and-fixes-with-git-how-to-use-a-scalable-git-branching-model-called-gitflow
http://vimeo.com/16018419
http://codesherpas.com/screencasts/on_the_path_gitflow.mov

Personally, I see migration from current setup that way so each
release branch (PHP-5.3, PHP-5.4 and master) becomes a separate
repository with adopted gitflow model (although it should be thought
through more carefully).
What do you think about that?
-- 
Regards,
Shein Alexey