On 2012-03-25, Alexey Shein <con...@gmail.com> wrote: > 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/
One thing I'll point out is that git-flow is a set of extensions and aliases for the git CLI. The problem with this is if you are not using the git CLI tooling (e.g, if you're using an IDE), or if you're on a system where installing the tooling may not work (Windows). As such, developers on those systems end up having to do a lot of manual work that git-flow normally automates -- and ends up in those same developers taking shortcuts. In short: while I like the idea of git flow, I think it's more sane for OSS projects to adopt processes that do not depend on it. -- Matthew Weier O'Phinney Project Lead | matt...@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
