Streamline the merge request and document review process

[Robert Leach]

USE CASE: WHAT DO YOU WANT TO DO?

Use the pull request system to supplant the merge_request_form.txt and complement the document_review_form.txt.

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

Merge Request process:

1. Click "Create a pull request" on TreeView's bitbucket repository
2. Paste the merge_request_form.txt contents into the text box & fill it out

Document review process:

1. Inspect the diff panels for problems/issues
2. Hover over a line number
3. Click the plus bubble
4. Paste the contents of a document review form issue and fill it out
5. Comment on the pull request to accept/reject the issue
6. Meet if necessary

CURRENT BEHAVIOR

1. Submit the merge_request_form.txt via email.
2. Schedule meeting & distribute manually created diff files
3. Developers fill out the document_review_form.txt
4. Meet if level of effort is medium+

EXPECTED BEHAVIOR

Better tracking of the software engineering process. Less effort to create diffs. Minimized need to meet.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

Incorporate bitbucket's pull request feature into the merge request and document review process.

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

TreeViewSCMP.doc merge_request_form.txt document_review_form.txt

LEVEL OF EFFORT - developers only

trivial

COMMENTS

I'll have to think about how one would initiate a document review of unreviewed documents already in the repository.

[Robert Leach]

Changes are done. Submitted pull request. This will be automatically resolved upon approval/merge.

[Robert Leach]

Didn't automatically resolve I guess.

[Robert Leach]

Merged to master.

[Robert Leach]

Removing milestone: Software Engineering (automated comment)