Update notification type creation

Update notification type creation to be compatible with django-notification
1.0.  It uses a ``create`` class method instead of a function inside the
``models`` module.

Addresses #571.
Update Django and Django CMS dependencies

Update dependencies to the current stable versions of Django (1.4.3) and
Django CMS (2.3.5) and update the dependencies required by those apps.

Save the old Django 1.3.1 and Django CMS 2.2 dependencies in a new file.
I'm going to try to not break backward compatibility with Django 1.3.1/
Django CMS 2.2, but I'd like to stay synced with the more recent framework/
CMS versions moving forward.

Addresses #35
Use Pillow instead of PIL

Getting JPEG support into PIL has been a pain and my development environment
(and the production environment) is using Pillow anyway.  We should just
depend on Pillow.
Merge branch 'develop' into 35-upgrade_to_django_1.4

Conflicts:
	REQUIREMENTS
Merge branch 'develop' into 35-upgrade_to_django_1.4
Update tests to pass with Django 1.4

Updated the selectors for tests dealing with the Django admin to match the
classes used in Django 1.4.  Also, made scenarios in story_admin.feature
able to be run individually as well as all-together.

Addresses #35
Move verbatim tag library to storybase app

As it provides general functionality, it seems more appropriate in the
central storybase app.

As the verbatim tag is included in Django 1.5, I added a guard that only
loads the backport if the distribution implementation isn't included.
Add admin user fixture

The story_templates.json fixture assumes that an admin user with pk=1 has
been created and uses this value for assigning the author field of the
template stories.  However, no such user exists when loading the fixture
in the unit tests.  Django 1.3.1 didn't seem to care about this, but
Django 1.4.3 displays an error message.  I created a fixture that creates
a single admin user to suppress the error.

Addresses #35
Add docs for upgrading Django/Django CMS

Addresses #35.
Use reverse_lazy for view's success_url

Now that we're supporting Django 1.4 we can use reverse_lazy to remove
the hard-coding of AccountNotificationView's success_url.  Fall back to
get_success_url for Django 1.3

Addresses #35
Merge branch 'develop' into 35-upgrade_to_django_1.4
Merge branch 'develop' into 35-upgrade_to_django_1.4
Merge branch '35-upgrade_to_django_1.4' into develop
Merge branch 'develop' into 515-publish_cleanup
Make get_default_img_url_choices a class method

get_default_img_url_choices and get_default_img_url don't touch the
instance object, and should return the same value for all instances, so
they can be a class method.  Doing this lets me bootstrap a value into,
say, a Backbone view without having a model instance.
Upgrade Backbone and Underscore

Upgrade Backbone and Underscore libraries to most recent version.

Backbone goes to version 0.9.10 and Underscore goes to version 1.4.3.

This is mostly because I wanted to start binding to events on models and
collections, when possible, instead of the event bus.  As of Backbone 0.9.9,
there are now listenTo and stopListening methods on Events, which make
binding event callbacks a little cleaner.

Note that in this version of Backbone, the Backbone object extends
Backbone.Events so it can be used as a global event bus.  Doing this might
make the code less verbose in the future.

I had to change the Asset model validation test to reflect the way that
validation doesn't automatically happen on Model.set and that invalid data
sends the "invalid" event rather than "error".
Checkpoint commit for new featured asset views

Addresses #515