Version 0.2.2

Author: Kevin Renskers

CHANGELOG

@@ -27,6 +27,6 @@
 0.2.1: December 7, 2011
 - New model DisabledNotificationsTypeBackend: instead of saving what backend a user wants to use, we save what he does not want to use instead
 
-NEXT
+0.2.2: February 5, 2012
 - New timed queue, send notifications after a certain time
-- The default types and backends are no longer registered by default, the developer needs to do this explicitly
+- The default types and backends are no longer registered by default, the developer needs to do this explicitly

README.rst

@@ -29,15 +29,15 @@ There are multiple output backends. Some possible examples are:
 - iPhone push notification
 - notification center
 
-At this moment only two email backends are provided, one of which is turned on by default.
+At this moment only two email backends are provided.
 
 Notification types
 ==================
 A notification type is the glue between a message (input) and one or more possible backends (output). For example, you
 might want to send all account related messages to email only, but notifications about new private messages could go to
 email, iPhone push messages, Django's own messages app, you name it.
 
-Each notification type can specify its allowed backend, and each user can specify his preferred output backend(s).
+Each notification type can specify its allowed backend(s), and each user can specify his preferred output backend(s).
 Each notification will then figure out what backend to use based on this information.
 
 Settings

notifications/__init__.py

@@ -1 +1 @@
-__version__ = '0.2.1'
+__version__ = '0.2.2'