I was tasked to create a product that would be out-of-the-box available to our users, so I added the attributes in a data migration but I had a hard time finding any resource that describes adding options via code and had to dig through Oscar's code on GitHub to figure this out. People would benefit from an addition like this, at least save time from digging through code to figure this out.

django-compressor used to trigger processing of the less files during
development. But with the browser-based compiler, an easy replacement is
available. This even lowers the barrier to altering styles, because
getting npm up and running isn't required.

Offline compilation isn't impacted.

Using the most current less version seems to not cause any trouble, so I
removed the version requirement.

This also reverses the order for the release notes overview. Makes more
sense to me that way.

And create stub release notes.

I had to manually correct the ru_RU django.po file as there were some
mismatching plurals. Not entirely sure what I did was the correct
resolution but it seemed sensible to my non-Russian eyes.

Mention bootstrap 3 dashboard and the customisation of the offer models

The TEMPLATE_DIRS and TEMPLATE_CONTEXT_PROCESSORS are no longer separate
settings thus given an example for the new TEMPLATES setting.

Also note that the user should include widget_tweaks in the
INSTALLED_APPS setting.

We got support for varying the tax rate per product in #1727. This
commit does some follow-up work.

Closes #1727.

This commit adds a bit of documention around the Elasticsearch support
introduced in #1572. It also shuffles around the handler names to be
more consistent.

I found some docs changes in my git stash that seemed useful. We removed
support for support when removing Django 1.6 support, so we can remove
mention of South.

This was an oversight that is now corrected.

This commit also switches to the more appropriate pattern_name variable
instead of reversing ourselves.

Transactions were improved with Django 1.6; the atomic decorator was
added at the same time. We could've removed this helper earlier, but
better late than never.

This fix was supplied in #1686.

Fixes #1686.

This was added with #1550.

Vagrant support was removed from release 1.0. This commit removes mentions of it from the docs.

Closes #1559.

There's no extension for it at the moment, but it seems to confuse
users. See #995.

Building upon the previous commit, we now use ordered dicts for our
search facets.

Specifying `excludes` is deprecated in Django 1.7 and not supported in
Django 1.8.

This order offers the simplest API for common needs - as evidenced by the
fact that the apply_offers crook could be removed from two test files,
saving on imports as well.

That approach is around from sometime around Oscar 0.6. With the
category refactor, it has become expensive to support. I doubt it has
any SEO impact, as e.g. Amazon has product IDs etc. all over their URLs.
@mbertheau seconded this opinion.

I also updated the handling migration section of the general upgrading
doc to use native migrations lingo instead of South's.

Previously, all views handled in Oscar's Application class were
decorated with the permissions_required decorator. That decorator would
not do anything if used with an empty set of permissions, but it
nonetheless seems cleaner to not decorate the views in the first place.

Raised in:
https://github.com/django-oscar/django-oscar-api/pull/2/files#r23832083

Unfortunately, I completely missed the host argument to is_safe_url.
Without it, the check will have always returned False (see #1557).

This change fixes this behaviour. Unfortunately, it does require
changing the notation of the safe_referrer and redirect_to_referrer
utility functions.

They are from a time when we had one stockrecord per product, and no
strategy classes. They're used for visual purposes only, and were
forgotten when the codebase was updated. They failed loudly, as reported
in #1592.

We really need to either drop them or add a helper method to the
strategy class, but to ensure backwards-compatibility, I've
re-implemented the naive approach of just sorting by price; blindly
ignoring the many shortcomings.

I also added a deprecation notice.