Improve document review efficiency

[Robert Leach]

USE CASE: WHAT DO YOU WANT TO DO?

Have a shorter, more productive document review meeting

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

1. Have a way to easily advance to issues.
2. Have a way to easily skip minor- issues which have been dealt with via comments.
3. have a way to skip issues unrelated or unchanged (like when code has moved to a new file).

CURRENT BEHAVIOR

Time is spent finding issues & on issues that are already resolved.

EXPECTED BEHAVIOR

Only address issues that are pressing & easily advance to a specific issue.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

1. Have a case for handling issues brought up on old code that were mistakenly highlighted by the diff
2. Implement a way to refer to issues in a pull request (bring back the ID/number)
3. If minor- issues are addressed by comments before the meeting, skip them

FILES AFFECTED (where the changes will be implemented) - developers only

1. document_review_form.txt
2. SCMP_TreeView3.doc
3. document_review_meeting_guidelines.txt

LEVEL OF EFFORT - developers only

medium

COMMENTS

[Robert Leach]

Resolved on branch "issue302...".

[Robert Leach]

Merged to master.

[Robert Leach]

Removing milestone: Software Engineering (automated comment)