- Team uses DVCS
- IDE supports comments parsing (like TODO and etc.)
- Tools like CodeCollaborator are expensive for budget
- Tools like gerrit are too complex for install or not usable
- Author publishes somewhere on central repo feature branch
- Reviewer fetch it and start review
In case of some question/issue reviewer create comment with special label, like "REV". Such label MUST not be in production code -- only on review stage:
$somevar = 123; // REV Why do echo this here? echo $somevar;
When reviewer finish post comments -- it just commits with stupid message "comments" and pushes back
- Author pulls feature branch back and answer comments in similar way or improve code and push it back
- When "REV" comments have gone we can think, that review has successfully finished.
- Author interactively rebases feature branch, squashes it to remove those "comment" commits and now is ready to merge feature to develop or make any action that usualy could be after successful internal review
I know, that custom comment tags are possible in eclipse & netbeans. Sure it also should be in blablaStorm family.
- Do you think this methodology is viable?
- Do you know something similar?
- What can be improved in it?