On Mon, Aug 8, 2011 at 1:35 AM, Stefan Neufeind <neufe...@php.net> wrote: > On 08/07/2011 11:37 PM, Richard Riley wrote: >> David Soria Parra <d...@php.net> writes: >> >>> On 2011-08-07, Stas Malyshev <smalys...@sugarcrm.com> wrote: > > [...] > >> Its really simple. >> >> Use git. >> >> It works, is fast and is rapidly becoming the industry standard. Do not >> sue something for "moral grounds" like the awful bzr used for emacs. >> >> Its designed as a fast, efficient DVCS. > > Hi, > > The TYPO3-folks migrated to git some while ago. And lately their > review-system "review.typo3.org" (readonly now also without a login) > went live. The review-system itself is actually another git in front > where changes for review can be pushed, can be reviewed, changed and be > mangled around, can be finally be abandoned or merged. At merge it's > pushed into the main repo. That was a huge win in terms of formal > reviews, transparency, speed and ease of reviews etc. And it even helped > bug-tracking since now there are no few lines of code hidden in the > bugtracker as some kind of "patch" or "quickfix" but that is actually a > git-change that you can checkout from review.typo3.org using your git > (the system tells you which commandline to use for that). Imho it's > dead-simple. > > I believe it would help PHP a lot to have this kind of transparency and > increase both the quality as well as the speed/ease of reviews. > > > Regards, > Stefan > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
btw. for code-review and change control there are also existing open source tools like gerrit for git. http://code.google.com/p/gerrit/ -- Ferenc Kovács @Tyr43l - http://tyrael.hu -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
