  
      from django.utils import timezone
      param = timezone.make_naive(param, timezone.utc)
  
  If you fail to do so, Django 1.9 and 2.0 will perform the conversion like
  earlier versions but emit a deprecation warning. Django 2.0 won't perform any
  conversion, which may result in data corruption.
  
  If you're reading :class:`~datetime.datetime` values from the results, they
  will be naive instead of aware. You can compensate as follows::
  
 
</s> remove     :doc:`deprecation timeline </internals/deprecation>` for any features that
    have been removed. If you haven't updated your code within the
    deprecation timeline for a given feature, its removal may appear as a
    backwards incompatible change.
 </s> add     :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore been removed. If you haven't updated
    your code within the deprecation timeline for a given feature, its removal
    may appear as a backwards incompatible change. </s> remove :ref:`Direct assignment <direct-assignment>`) used to perform a ``clear()``
followed by a call to ``add()``. This caused needlessly large data changes
and prevented using the :data:`~django.db.models.signals.m2m_changed` signal
to track individual changes in many-to-many relations.
 </s> add :ref:`Direct assignment <direct-assignment>` of related objects in the ORM used
to perform a ``clear()`` followed by a call to ``add()``. This caused
needlessly large data changes and prevented using the
:data:`~django.db.models.signals.m2m_changed` signal to track individual
changes in many-to-many relations. </s> remove   including ``django.contrib.auth`` in :setting:`INSTALLED_APPS` (this raised
  a deprecation warning in older versions and is no longer supported in
 </s> add   including ``django.contrib.auth`` in :setting:`INSTALLED_APPS` (doing so
  raised a deprecation warning in older versions and is no longer supported in </s> remove 1.8 or older versions. We've :ref:`dropped some features
<deprecation-removed-in-1.9>` that have reached the end of their deprecation
cycle, and we've `begun the deprecation process for some features`_.
 </s> add 1.8 or older versions. We've :ref:`dropped some features<removed-features-1.9>`
that have reached the end of their deprecation cycle, and we've `begun the
deprecation process for some features`_. </s> remove .. removed-features-1.9:
 </s> add .. _removed-features-1.9:
If you fail to do so, the conversion will be performed as in earlier versions
(with a deprecation warning) up until Django 1.11. Django 2.0 won't perform any
  
      from django.utils import timezone
      param = timezone.make_naive(param, timezone.utc)
  
If you fail to do so, the conversion will be performed as in earlier versions
(with a deprecation warning) up until Django 1.11. Django 2.0 won't perform any
If you fail to do so, the conversion will be performed as in earlier versions
(with a deprecation warning) up until Django 1.11. Django 2.0 won't perform any
  conversion, which may result in data corruption.
  
  If you're reading :class:`~datetime.datetime` values from the results, they
  will be naive instead of aware. You can compensate as follows::
  
keep keep keep keep replace replace keep keep keep keep keep
 Alphabetized a few sections in the 1.9 release notes + made a few tweaks. 
docs/releases/1.9.txt