Fix: fields from the shared model should not be validated on the Translation formset
Fix: all where nodes do not have children. In some circumstances, Django ORM generates Constraint nodes that have their 'field' attribute set to None. It looks like it is related to custom through model in m2m relationships.
Clarify logic in TranslationFormset intent. Fixes #195 as a side effect.
Update tested Django versions.
Update release notes, add deprecation warning (and matching tests), get ready for v0.5.
Get ready for work on v0.6.0: update version, make new release entry.
Implement TranslationQueryset.fallbacks for Django 1.6+.