``DeprecationWarning`` (which will begin printing warning messages on
import) and in 1.0 it will be removed entirely.
Changes to registration views
:ref:`registration backend <backend-api>` to use, and so any URL
pattern for these views must supply that argument.
-The ``profile_callback`` argument of the ``register`` view has been
-removed; the functionality it provided can now be implemented easily
-via a custom backend, or by connecting listeners to :ref:`the signals
-sent during the registration process <signals>`.
+The ``profile_callback`` argument of the
+:func:`~registration.views.register` view has been removed; the
+functionality it provided can now be implemented easily via a custom
+backend, or by connecting listeners to :ref:`the signals sent during
+the registration process <signals>`.
+The :func:`~registration.views.activate` view now issues a redirect
+upon successful activation; in :ref:`the default backend
+<default-backend>` this is to the URL pattern named
+``registration_activation_complete``. On unsuccessful activation, the
+``activate()`` view still displays a template, but its context has
+changed: the context will simply consist of any keyword arguments
+captured in the URL and passed to the view.
Changes to registration forms
custom backend, or by connecting listeners to :ref:`the signals sent
during the registration process <signals>`.
Changes to the :class:`~registration.models.RegistrationProfile` model