Added select_related for user in blog_recent_posts template tag.
Added apps.in to Sites Using Mezzanine
Fix lookup of initial data in from-builder forms, and correctly handle initial values for checkbox fields.
Allow forms-builder forms to contain template code for default values.
Provide more granular export filtering for multiple-choice fields in forms-builder export, eg matches/doesn't match any/all selected choices, and also allow range filters to use only one boundary.
Fix static_proxy to work with //host STATIC_URLs

STATIC_URL = '//mybucket.s3.amazonaws.com' would break the static_proxy prefix stripper, and therefore break tinyMCE plugins. This fix adds proper handling of generic-protocol hostnames to the static_proxy view.
Added Gabe Smedresman to AUTHORS.
Reorder blog and accounts patterns in mezzanine.urls to allow for projects with a blog homepage that also have accounts enabled.
Fix handling of paths in zip imports in galleries app.
Norwegian translation string with < and > characters break page editing.
Added Kim Tore Jensen to AUTHORS.
Merge
accounts: properly reject multiple matching e-mail addresses.

Django allows multiple Users with the same e-mail address; the existing
form can throw MultipleObjectsReturned when get(email=email) is called
against such a dataset.
Added Mike Wakerly to AUTHORS.
Merge
Added default wsgi script to project template.
Only add input-xlarge on inputs without a class attribute, fixes #643
Replaced the BLOG_URLS_USE_DATE setting with a new BLOG_URLS_DATE_FORMAT setting - it can contain the string year, month, or day, which controls the date granularity in blog post URLs.
Editable settings refactor - this change is to clear up confusion around editable settings being defined in a project's settings module. Previously when this happened, the settings.py module value would only serve as a default, which would be superceded by the db editable value as soon as the settings admin form is first saved. To address this, this change means that editable settings defined in the project's settings.py module now mark the setting as not editable, so it will always be the value used. We also include some handling for the migration case so that even with this change, editable settings already in the db that have a settings.py value defined will still use the db value and provide a warning.
Revert the handling for still using db values for editable settings with settings.py values defined, since it basically defeats the purpose if a settings.py value is added once a project is live.