On Sat, Aug 13, 2011 at 1:51 AM, Kiall Mac Innes <ki...@managedit.ie> wrote: > On Sat, Aug 13, 2011 at 12:26 AM, Lester Caine <les...@lsces.co.uk> wrote: > >> Actually they are talking about developing Drupal ... >>
It seems to have a confusion between forks used for development by individuals and (so called) official branches. 99% of the time one does not care about the forks but when a pull request is done from it (see it as a patch being sent to the list/issue tracker). A fork is also a very good way to work on non trivial changes for a given period without having to leave the official branches in a non stable or unfinished state. And even more important, it can be done publicly with history, etc. That alone is very valuable and much more easier than having to either maintain mirrors or local repository (with all disadvantages when it gets out of sync with the main repo). 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. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
