Update release notes for changes made when dropping support for Django < 1.11
@@ -19,9 +19,8 @@ Table of contents:
Compatibility
-------------
-Oscar 1.6 is compatible with Django 1.11 and 2.0 as well as Python 2.7, 3.4,
-3.5 and 3.6. Django 1.8 is no longer supported, in line with the Django
-project recommendation.
+Oscar 1.6 is compatible with Django 1.11 as well as Python 2.7, 3.4,
+3.5 and 3.6. Django 1.8, 1.9 and 1.10 are no longer supported.
.. _new_in_1.6:
@@ -32,11 +31,8 @@ What's new in Oscar 1.6?
Removal of deprecated features
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- - Removed ``OSCAR_PROMOTION_MERCHANDISING_BLOCK_TYPES`` setting since
- merchandising block promotions, which used it, already removed for a while.
-Minor changes
-~~~~~~~~~~~~~
+ - Removed the redundant ``OSCAR_PROMOTION_MERCHANDISING_BLOCK_TYPES`` setting.
- Majority of the Oscar imports now using dynamic loading, instead of
direct importing for better extensibility and customizability, except
signals.
@@ -62,6 +58,7 @@ Minor changes
- Product attribute value save now handled by separate methods, similar to
validation which allows to override save logic for file, multi-option or
generic attribute values.
+<<<<<<< HEAD
- Address hash generation is now separated from the summary in order to
preserve same behavior when summary property customized (see :issue:`1537`).
They can use different field names, listed out in `base_fields` and
@@ -69,6 +66,20 @@ Minor changes
platform-independent and generates the same for Python 2 and 3.
Corresponding data migration will update hashes automatically. Take it into
account that it will take time to run if you have large user base.
+=======
+ - ``oscar.core.validators.validate_password`` was removed.
+ Use ``django.contrib.auth.password_validation.validate_password`` instead.
+ - ``oscar.core.validators.CommonPasswordValidator`` was removed. Use ``django.contrib.auth.password_validation.CommonPasswordValidator`` instead.
+
+
+Minor changes
+~~~~~~~~~~~~~
+
+ - The majority of the Oscar imports now use dynamic loading, instead of
+ direct importing, for better extensibility and customisability.
+
+ - Customer transaction emails now use a basic HTML template.
+>>>>>>> 96172f0... Update release notes for changes made when dropping support for Django < 1.11
.. _incompatible_in_1.6:
@@ -78,6 +89,12 @@ Backwards incompatible changes in Oscar 1.6
- ``oscar.apps.customer.auth_backends.EmailBackend`` now rejects inactive users
(where ``User.is_active`` is ``False``).
+ - ``EmailBackend`` no longer enforces its own password strength validation,
+ and relies instead on the ``AUTH_PASSWORD_VALIDATORS`` setting used by Django.
+
+ - ``oscar.apps.basket.middleware.BasketMiddleware`` was rewritten as new-style
+ middleware for Django 1.11.
+
- ``oscar.apps.offer.models.ConditionalOffer`` now has a new flag
``exclusive`` to denote that the offer involved can not be combined on the
same item on the same basket line with another offer.
@@ -96,7 +113,7 @@ Backwards incompatible changes in Oscar 1.6
The offending menu item will be skipped during menu rendering.
In Oscar 1.8 the exception will be raised without being intercepted.
- - All signals are now loaded directly.
+ - All signals are now loaded directly rather than using the dynamic importer.
Dependency changes
------------------
