Django-letsencrypt

- Breaking Changes
- Django `1.9` support has been dropped. There will be no further updates
to fix any issues that may arise from using `django-letsencrypt` with
`1.9`.
- Internal Changes
- `django-letsencrypt` now supports Django `1.11`.
- Updated builds to use the latest `1.8`, `1.10` releases.
- Bumped to the latest `pytz`, version `2017.2`.
- Updated `setup.py` marking any Django `1.9` releases as incompatible.
- Removed Python `nightly` from Travis builds and testing.
- Removed `squashed` migrations from the project. **PLEASE NOTE:** If you
are on an older `v1.x` release of this project, please make sure to
**UPGRADE** to `v1.1.1` and **migrate** your database. Failure to do so
will cause a lot of problems, since this release **only** has the single
migration file.

- Internal Changes
- Removed the need to render `ACME` responses through a template. Instead
responses are now passed through a `HttpResponse` with a `content_type` of
`text/plain`. Thanks to [Peter Curet](https://github.com/petercuret)
for providing a pull request.
- [GH-29](https://github.com/urda/django-letsencrypt/pull/29)
- [GH-30](https://github.com/urda/django-letsencrypt/pull/30)
- Corrected `Copyright` dates across the project
- Thanks to Contributors:
- [Peter Curet](https://github.com/petercuret)

- Project Changes
- Admin `ordering` for the Django admin page is now down by `challenge`
- Removed `created_ts` and `updated_ts` from model
- Switched `challenge` and `response` from `TextField` to `CharField`
- Internal Changes
- Added testing for `detail` view for `ACME` objects
- Removed `migrations.py` thanks to existing `example_project`'s manage.py

- Project Changes
- Require `pytz` for SQLite users.
- Update `travis` branch build targets.

- Project Changes
- Final "feature" release of the 1.x branch. 2.0 will support `mysql`.
This had to be done due to certain model upcoming model changes, and
will result in a new set of migrations.

- Internal Changes
- Started using `twine`
- Started uploading `bdist_wheel`