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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
