Team 8 Information

Name: Jordan Burkitt
Email: [email protected]
Github ID: jdocnog
Slack ID: jburkitt

Name: Haneen Barri
Email: [email protected]
Github ID: hbarri
Slack ID: haneenbarri

Name: Matthew Burks
Email: [email protected]
Github ID: burks.20
Slack ID: burks20

Name: Jesse Liu
Email: [email protected]
Github ID: w262jxl
Slack ID: w262jxl

Name: Jason Marcum
Email: [email protected]
Github ID: jasonmarcum
Slack ID: jasonmarcum

Name: Andrew Ribar
Email: [email protected]
Github ID: ElderReebs
Slack ID: xxdrewxx

Milestones

Milestone #1

The purpose of this milestone will likely be to get everyone on the team up to speed with using eclipse and github. Getting us ready to confidently use eclipse will include getting everyone on the team to understand how to create and merge branches, update the repository on github without creating errors, and how to properly commit changes. Once all this has been accomplished, our team will then begin to work on reading through the code for issues #215, #216, and #217. Even though these issues may not be a crucial part of the project, we feel that it's best to start with these in the hopes that we may begin to better understand the program through reading and interpreting the past comments and code. In addition, we feel it's best to first start with tackling issues such as these until we get more practice on how to work with eclipse and github before we start coding.

Milestone #2

Since our last milestone included a lot of work, some of those issues bled into our second milestone. Our team will continue to work on reading through the code to fully document the project in comments and JavaDoc since we were not able to complete it all in the last milestone (issues #215, #216, and #217.) We also plan to execute the action phase of cleaning up the team1 branches through removing, merging, and editing them (issue #256).

Milestone #3

For this milestone, we plan to continue the process of cleaning up the branches of team 1. Team1RMI-dev branch was deleted and we compared the code between team1 and team1-dev to hopefully merge them in this milestone with issue #271. We decided to forget about issue #217 for now and come back to it in later milestones considering the project is still far from completion and we cannot expect to clean all of the Checkstyle and Findbugs issues with a portion of the methods and classes being empty. Lastly, we plan on expanding/adding-on to the wiki page.

Milestone #4

For this milestone, we plan to continue the process of cleaning up the branches of team 1. Team1RMI-dev branch was deleted and we successfully merged team1 and team1-dev. We now plan to work on going back through the merged code and fixing all the errors that were the result of this merge. Lastly, issue #264 (adding course specific instructions to the wiki page) included more work than was anticipated and, as a result, was carried over to this milestone as well.

Milestone #5

In our previous milestone, we had attempted to clean up the team1 branches by merging the team1 branch into the team1-dev branch in issue #271. However, because we are all new to the merging process in eclipse/git, we accidentally merged the team1-dev branch into the team1 branch. This caused us to accidentally push broken code. Because of this, this milestone will primarily be centered around fixing that failed merge in issue #298 and adding comments and JavaDoc to officially stabilize the branch with issue #297.

Milestone #6

Because of our failed attempt at a merge of the team1 and team1-dev branch, our previous milestone was centered around fixing that merge by undoing it and then finally re-merging the branches the correct way. We were able to revert the unsuccessful merge in commit f62c3ca and so we now plan on centering this milestone around re-merging the two branches but, hopefully, in the correct direction this time (in issue #311) and adding comments and JavaDoc to officially stabilize the branch with issue #297.

Milestone #7

This milestone is planned to be centered around continuing the merge process of team1 and team1-dev. In doing this, we plan to create two new branches from commits 22169e1 and a987e87, and then merging those two branches together. We then plan to merge that new commit of the merged branches with commit f62c3ca to officially stabilize the team1 branch. We were also able to complete issue #264 in adding course specific instructions to the wiki page in our last milestone, closing the issue on expanding/adding-on to the wiki page.

Milestone #8

In our previous milestone, we were able to create the two new branches from commits 22169e1 and a987e87 (calling them team1-dev2 and team1-dev3) and start the merging process. However, because the team1 and team1-dev branches have diverged so significantly, we were able to only get half way through the merge. So for this milestone, we plan to complete the merge of those two branches and then merge that new commit with commit f62c3ca to officially stabilize the team1 branch (in issue #341).

Milestone #9

After creating the two new branches from commits 22169e1 and a987e87 (calling them team1-dev2 and team1-dev3) and starting the merge process in the last milestone, we were able to finally complete the full merge of the two branches in commit 7b972d3. So for this milestone, we plan to merge that new commit with commit f62c3ca to officially stabilize the team1 branch and close issue #341.

Milestone #10

After the merge of our team1-dev3 (commit 30538e3) and team1 (commit f62c3ca) branches in commit 482741d, we expect to find issues such as errors, findbugs, and checkstyle appearing. So for our last milestone, we plan on working on issue #345 to fix these issues in the new merged branch to finally stabilize the team1 branch. We also plan to clean up the branches that we created purely for the merge and are now unnecessary in issue #370. We plan to work on issue #92, as well, to gain an understanding of the ProcessBuilder Class.