BB clean up

[Christopher Keil]

USE CASE: WHAT DO YOU WANT TO DO?

NA

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

NA

CURRENT BEHAVIOR

Many old redundant JARs in the downloads section. Many old abandoned branches in the repo.

EXPECTED BEHAVIOR

No excess files or branches / no dead weight

DEVELOPERS ONLY SECTION SUGGESTED CHANGE (Pseudocode optional)

Remove non-important JARs from downloads section, clean up the abandoned remote branches.

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

Repository

LEVEL OF EFFORT - developers only

medium

COMMENTS

Can be done during a Skype session to discuss which files/ branches should remain and which should be deleted.

[Robert Leach]

I've found the old jars useful... See if some new bug was previously fixed...

I'm fine with eliminating branches though.

[Lance Parsons]

@abarysh Collect all test data, README.txt that describes the "test" for each dataset, upload zip file of test datasets, remove old test datasets.

[Robert Leach]

I have removed my orphaned and merged branches. I kept 1 merged branch because I think it could be useful. There are a few branches of Chris's that could probably be deleted, but I wasn't sure.

Since it was revealed in our last meeting that numerous links from issues to the downloads page would be broken if we were to delete old things from the downloads page, I believe we decided to not delete old downloads. So once @TreeView3Dev has deleted his old branches, I think we can resolve this issue.

[Christopher Keil]

Deleted my merged branches which weren't closed during the PR. Resolving since I suppose the clean up is done now.