Merge pull request #607 from carltongibson/downstream

Update Docs for new release
This commit is contained in:
Mathieu Pillard
2015-04-16 11:19:48 +02:00
2 changed files with 40 additions and 5 deletions

View File

@@ -1,6 +1,40 @@
Changelog
=========
v1.5 (03/27/2015)
-----------------
`Full Changelog <https://github.com/django-compressor/django-compressor/compare/1.4...HEAD>`_
- Fix compress command and run automated tests for Django 1.8
- Fix Django 1.8 warnings
- Handle TypeError from import_module
- Fix reading UTF-8 files which have BOM
- Fix incompatibility with Windows (shell_quote is not supported)
- Run automated tests on Django 1.7
- Ignore non-existent {{ block.super }} in offline compression instead of raising AttributeError
- Support for clean-css
- Fix link markup
- Add support for COMPRESS_CSS_HASHING_METHOD = None
- Remove compatibility with old 'staticfiles' app
- In compress command, use get_template() instead of opening template files manually, fixing compatibility issues with custom template loaders
- Fix FilterBase so that does not override self.type for subclasses if filter_type is not specified at init
- Remove unnecessary filename and existence checks in CssAbsoluteFilter
v1.4 (06/20/2014)
-----------------

View File

@@ -9,11 +9,12 @@ tidy, everybody has to follow a few rules (nothing major, I promise :) )
Community
---------
People interested in developing for the Django Compressor should head
over to #django-compressor on the `freenode`_ IRC network for help and to
discuss the development.
People interested in developing for the Django Compressor should:
1. Head over to #django-compressor on the `freenode`_ IRC network for help and to
discuss the development.
2. Open an issue on GitHub explaining your ideas.
You may also be interested in following `@jezdez`_ on Twitter.
In a nutshell
-------------
@@ -143,7 +144,7 @@ Documentation should be:
- Accessible. You should assume the reader to be moderately familiar with
Python and Django, but not anything else. Link to documentation of libraries
you use, for example, even if they are "obvious" to you. A brief
description of what it does is also welcome.
description of what it does is also welcome.
Pulling of documentation is pretty fast and painless. Usually somebody goes
over your text and merges it, since there are no "breaks" and that github