Code Reviews in Iteration <XX>
<See Code Review Overview per Iteration for description of how to name use this template.>
Review of code should happen immediately after coding for a task or bug is done, so as little as possible is based on unreviewed code.
If the reviewer for some reason cannot be contacted within a reasonable timeframe, another reviewer should be chosen.
We don't register review time as separate from coding time.
For details on how to do a review, see Code Review Process.
<Link to code review page for class/JSP-page named with java path name, f.ex. dk.netarkivet.harvestdefinition.JobDAO> |
<SVN version of code being reviewed> |
<Lines/parts to review> |
<Reference to task caused the code changes that are being reviewed as for example a bugs, a feature request or an assignment> |
<Initials of author of changes in code> |
<Initials of reviewer in code review> |
<Date that review was held on form YYYY/MM/DD> |
<Initials of person to do follow-up on code review> |
<Must be either |