Minor documentation cleanup; Bumped version number to 1.6.0;

docs/doc/historization_with_cleanerversion.rst

@@ -745,7 +745,7 @@ will need to be ready to handle that.
 Postgresql specific
 ===================
 
-Django creates `extra indexes <https://docs.djangoproject.com/en/1.7/ref/databases/#indexes-for-varchar-and-text-columns>`_
+Django creates `extra indexes <https://docs.djangoproject.com/en/1.8/ref/databases/#indexes-for-varchar-and-text-columns>`_
 for CharFields that are used for like queries (e.g. WHERE foo like 'fish%'). Since Django 1.6 (the version CleanerVersion originally
 targeted) did not have native database UUID fields, the UUID fields that are used for the id and identity columns of Versionable models
 have these extra indexes created.  In fact, these fields will never be compared using the like operator.  Leaving these indexes would create a
@@ -779,9 +779,6 @@ at the same time, see:
 Note that this example is for Django >= 1.7; it makes use of the
 `application registry <https://docs.djangoproject.com/en/stable/ref/applications/>`_ that was introduced in Django 1.7.
 
-For Django 1.6, it is possible to do something similar.  The functions in ``versions.util.postgresql`` should be able to be used
-unchanged for Django 1.6.
-
 
 Integrating CleanerVersion versioned models with non-versioned models
 =====================================================================

setup.py

@@ -21,7 +21,7 @@
 """
 
 setup(name='CleanerVersion',
-      version='1.5.4',
+      version='1.6.0',
       description='A versioning solution for relational data models using the Django ORM',
       long_description='CleanerVersion is a solution that allows you to read and write multiple versions of an entry '
                        'to and from your relational database. It allows to keep track of modifications on an object '