Django-datafreezer

Added
- Added non-admin-specific login & logout pages for users.
- Added more blocks to the base template, including one to populate the `{{ title }}` tag.

Changed
- Implemented more accurate semantic versioning.
- Modified URL structure for dataset creating/editing/detail pages:
* `/datasets/create/` now enables users to create a new dataset.
* `/datasets/FOO/` now shows the dataset's detail page.
* `/datasets/FOO/change-dataset/` now enables users to edit a dataset's metadata.
* `/datasets/FOO/change-dictionary/` now enables users to edit a dataset's data dictionary.
- Restricted upload and editing views to authenticated users.
- Tailored options in sitewide title bar depending on whether users are authenticated.

Changed
- Storage class no longer refers to boto (or django-storages) directly. Users can create such a storage class on their own implementations if desired.
- As a result of this change, Datafreezer now uses only one optional storage-related setting, `DATAFREEZER_CUSTOM_STORAGE_CLASS`. In the previous version there were four optional storage-related settings to decide between.

Added
- First version of this changelog.

- Custom storages setting (with multiple fallbacks) for all FileFields in app:
* Datafreezer will first look for custom S3 settings, applying a django-storages `S3BotoStorage` subclass if S3 credentials are available.
* If no custom S3 settings are provided, Datafreezer will look for and apply a custom storage class, as defined in `settings.py`.
* Failing both these options, Datafreezer will default to the project-wide file storage class.

Added
- Files for favicon and touch icon.
- HTML for favicon.

Changed
- Removed unnecessary dependencies from `requirements.in` (and `requirements.txt`).

Changed
- `setup.py` file will now read in dependencies rendered to `requirements.txt` and install them accordingly.