Reviews of <name of code review class/jsp page>

<See [:Code Review Process#CodeReviewPagePerPage:Code Review Page per Class/JSP-page] for description of how to name use this template.>

New reviews are added at the top

[:Code Review Process#TablesFilledPageReview:Date]:

<date when the review takes place on form YYYY/MM/DD>

[:Code Review Process#TablesFilledPageReview:Version]:

<SVN version number>

[:Code Review Process#TablesFilledPageReview:Lines/parts]:

<lines/parts reviewed>

[:Code Review Process#TablesFilledPageReview:Bugs/Feature requests]

<link to bug(s)/Feature request(s) partly or fully resolved by change>

[:Code Review Process#TablesFilledPageReview:Release test]

<excl./incl. TEST case and item and status>

[:Code Review Process#TablesFilledPageReview:Manuals]

<Manual , page(s)/chapter(s)>

BR

[:Code Review Process#TablesFilledPageReview:Line]

[:Code Review Process#TablesFilledPageReview:Description]

[:Code Review Process#TablesFilledPageReview:Severity]

[:Code Review Process#TablesFilledPageReview:Status]

||<bgcolor="#dddddd" style="text-align: center;">Release Test BR -, incl., excl. ||<bgcolor="#dddddd" style="text-align: center;">Manuals BR Quick, Deploy, Conf.,

<Line number, single, serie or interval>

<Description of review comment>

<Must be either BR Cosmetic (follow-up not necessary), BR Minor (follow-up would be nice), BR Major (follow-up must be done) or BR Showstopper (bug should be reported) >

<Must be either BR Ok (no further action), BR Postponed (must be done at a later stage – this must be noted in the "Done" column of the related [:Code_Review_Process#TableFilledReviewsOverview:Code Review Overview Table Filled for each Iteration], BR Rejected (will not be done at all) or BR Obsolete (????)>