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.

Closes #1482

Part of #1569

Closes #1571.

They got shifted by accident in 1023401c

Backport of 58e91e6 from master.

A simple typo lead to star imports not working as expected. As it's
easily worked around, we won't issue a release right away.

Closes #1553.

(cherry picked from commit 80babf2c19)

Conflicts:
	docs/source/releases/index.rst

A simple typo lead to star imports not working as expected. As it's
easily worked around, we won't issue a release right away.

Closes #1553.

South 1.0.1 doesn't break with Python 3 any more, so we can remove any
special logic for that case. Lovely.

Oscar is becoming a more community-owned project. This commit reflects a
few organisational changes taking place.

This reflects the change in the repo URL.

Oscar is in production at major companies, and has proven itself in all
kinds of scenarios. It's time the version number acknowledges that.

This means there never will be a 0.8 final release; only betas were
released as 0.8 version.

* Add note for __all__ imports to release notes
* Add note on likelihood of Django 1.6 support being removed sooner than
  later

This commit removes a few long deprecated bits in the docs and in
code. It also updates the
release notes to include those removals, and highlights what has been
deprecated in 0.8. And it fixes a Sphinx warning when building the docs.

Changes include:

- New section on organisation
- General moving round of sections, especially around backwards
  incompatibilities
- Various copy changes

Have tested on sandobx site seems all working,
not sure if you need more testing on it.

Fixes #1541.

This changeset adjusts `build_submission` to include the billing address.
This also requires changes to a few method signatures to handle the
billing address explicitly.

This only works when the billing address is stored in the session (as
that's where it is looked up from when building the submission data in
`build_submission`). In many cases (such as Oscar's demo site), we don't
store the billing address in the session - instead, it is captured via
the payment-details forms. Hence, the billing address will still need to
be explicitly set within the submission data.

Fixes #1508

It's necessary to add South before running migrate to successfully
create the database.

Cherry-picked by @maikhoepfel from #1545.