Re: [Monotone-devel] code review in practice

[Caio Marcelo]

Hello Evan and people,

Recently (after re-reading your blog post about this subject) I wrote
down some ideas, also inspired by Mondrian talk by Guido. These ideas
are available in

http://www.students.ic.unicamp.br/~ra015599/PLAN

maybe you'll find some of these helpful. After writing this I thought
maybe the web interface could be an optional layer over the "offline
compatible" script around Monotone. Comments on that PLAN are very
welcome.


On 4/10/07, Evan Martin <address@hidden> wrote:
> 2) Submitters make a (named) branch for each new change, branch only
> merged into the main branch after it's been ok'd.
> Analysis: a new branch name for every change seems a little scary.

I choose this path, but with some "separate" namespace for the new
changes and an automatic way to assign this names. After a few commits
(and reviews), reviewer is happy and just mtn approve the head of the
'review branch' into the main branch. AFAIK, if you just use main
branch you will get access ONLY to revisions approved by someone.


(PS: thanks for the nice tech blog -- lots of good posts! evan++)

Cheers,
 Caio Marcelo