Update requirements files (#1934) and first working .travis.yml (bug 914808)
bug 914808: Stop updating product details at test time; tweak usage of constance in demos forms
bug 914808: Notify mdndev in IRC and mailing list on travis status
Migration fixes for starting from a fresh DB
Remove and redirect obsolete and unused templates
Upgrade django-badger
fix bug 967500 - Add alternate lang link tags
Merge pull request #1957 from darkwing/alt-lang-967500

fix bug 967500 - Add alternate lang link tags
Issue #1934: No longer installing PIL, so drop the insecure exception
Issue #1934: Update repo location for django-debug-toolbar
Merge pull request #1945 from lmorchard/death-to-kuma-lib

Update requirements to match kuma-lib; initial working Travis-CI tests
Bump django-constance to v0.6
Merge pull request #1960 from lmorchard/bump-django-constance-v0.6

Bump django-constance to v0.6
Merge pull request #1938 from openjck/remove-and-redirect-pages

Remove and redirect obsolete and unused templates
Do not override "clear" property with custom mixin

Until now, we used a mixin named clear() to apply clear-fixes to
elements.

When Stylus encounters a property that shares a name with a mixin, it
assumes the property is a transparent call to the mixin [1]. Thus,
whenever we used the real CSS property "clear", Stylus assumed we were
calling the mixin of the same name, and we ended up applying clear-fixes
to elements accidentally.

To test this, inspect a Zone landing page title. Without this change,
the title should be incorrectly clear-fixed. With the change, the title
should correctly not be clear-fixed.

[1] http://pages.citebite.com/e2t7l2p4m9dig
Merge pull request #1968 from openjck/clearfix-fix

Do not override "clear" property with custom mixin
Added an index for the deleted field for faster filtering.