Mercurial > pylearn

view doc/v2_planning/code_review.txt @ 1234:3e264967d4e3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated commity member
author Frederic Bastien <nouiz@nouiz.org>
date Thu, 23 Sep 2010 10:23:40 -0400
parents 91c285e30364
children a9b601119197
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->`
- `Review Board <http://www.reviewboard.org>`_

What we could want from our code review:

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