Version 1.2.0

Allow reset signal to be ignored

Stop pinning pytz

Version Bump

Unpin and inherit django version

This commit loosens the allowable version of django to anything
<1.9a0. Each of 1.8, 1.9, and 1.10 can now be tested using tox,
which will make the eventual upgrades much easier.

send created time

This data is needed for robust grades work, and is easy enough
to include in the providing signals. I've also added the freezegun
library to test-requirements.txt to test this functionality.

Serialize annotation information with scores

Add an OEP-2 compliant openedx.yaml file

Bump to version 1.1.0 in setup.py

Create new get_all_course_submission_information endpoint.

The submissions API has a get_score() method which, given a student item,
will look up the relevant ScoreSummary and return the latest Score it
contains. Our data download should do the same.

To avoid confusion, we have elected to hide scores that could not be
returned from api.get_score(). The other options are:
- include a score that may be for a different submission for the same
    student item, if using ScoreSummary.latest in all cases
- include scores that may not "count", because they'll never be the
    return value of api.get_score()

Test has been updated.

Update versioning to 1.0.0

Sibling to https://github.com/edx/edx-ora2/pull/886.
edx-submissions is rather stable, and should be bumped to a 1.0.0 release

Use the docker infrastructure for travis builds.

Add pep8 and pylint linting updates.

Version 0.1.4

Soft-delete Submissions to reset student state

Previous methods of "deleting state" for a student had just issued
reset scores, so the (unscored) submission was still hanging around.
With this change, the submission can be "deleted" for all django-
relevant purposes, while still remaining in the database in case
it turns out to be interesting to analytics later.

Includes a migration that may take some time to run, and will acquire a
table lock. This will cause an outage for any other request trying to
hit the submissions table during the migration. We've estimated the outage
to last approximately 3 minutes on a database with 700,000 rows.

Test also included.