Mercurial > pylearn

view doc/v2_planning/code_review.txt @ 1224:f68b857eb11b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
reply to comments on architecture document
author Ian Goodfellow
date Wed, 22 Sep 2010 15:44:14 -0400
parents 5ff1d375fc33
children 91c285e30364
line wrap: on
line source


Code Review
===========

Some system that we should check:

- `rietveld <http://code.google.com/p/rietveld/>` Made by Guido van Rossum
- `Gerrit <http://code.google.com/p/gerrit/>`
- `track PeerReviewPlugin <http://trac-hacks.org/wiki/PeerReviewPlugin>` Could be integrated with the current ticket system?

- `feature request at assembla <http://feedback.assembla.com/forums/5433-feature-requests/suggestions/253297-add-a-code-review-tool-e-g-reviewboard->`

What we could want from our code review:

- integrate with our ticket system?
    - Should we keep our current ticket system?