Django-sortedm2m

-----

* `56`_: Fix bug where order is wrong after adding objects. That had to do
with using the ``count`` of the m2m objects for the next ``sort_value``
value. We now use the corret ``Max`` aggregation to make sure that newly
added objects will be in order. Thanks to Scott Kyle for the report and
patch.

.. _56: https://github.com/jazzband/django-sortedm2m/pull/56

-----

* Performance fix for sorted m2m admin widget. See `54`_ for details. Thanks
to Jonathan Liuti for fixing this.

.. _54: https://github.com/jazzband/django-sortedm2m/pull/54

-----

* Hooray, we officially declare **django-sortedm2m** to be stable and
promise to be backwards compatible to new releases (we already doing good
since since the beginning in that regard).
* Django 1.8 support for ``AlterSortedManyToManyField`` operation. Thanks to
Nicolas Trésegnie for starting the implementation.

------

* The creation of the sortedm2m intermediate model and database table is now
fully done inside of the ``SortedManyToManyField`` class. That makes it much
easier to modify the creation of this when creating a custom subclass of this
field. See `49`_ for an example usecase.
* Adding support for the custom field arguments like ``sorted`` and
``sort_value_field_name`` in Django 1.7 migrations. Thanks to Christian
Kohlstedde for the patch.

.. _49: https://github.com/jazzband/django-sortedm2m/issues/49

-----

* Fixing ``setup.py`` when run on a system that does not use UTF-8 as default
encoding. See `48`_ for details. Thanks to Richard Mitchell for the patch.

.. _48: https://github.com/jazzband/django-sortedm2m/pull/48

-----

* Fix: ``SortedMultipleChoiceField`` did not properly report changes of the
data to ``Form.changed_data``. Thanks to smcoll for the patch.