Merge branch 'release/0.2.7' into develop
Remove duplicate test.
Don't return prematurely.

It made it so that as soon as one rule matched for one user, the whole tamale
would evaluate to true for every subsequent user.  This incorrectly made it so
that users would suddenly start getting all kinds of messages not relevant to
them; messages would be directed at 40+ users simultaneously, one after
another, after another.
Merge pull request #11 from fedora-infra/feature/debug-that-crazy-last-release

Don't return prematurely.
Try to get travis tests running.
Allow individual rules to be negated.
Add alembic revision for that.
Provide an API to modify rule-negation.
Fix __repr__ logic.

As pointed out here:
https://github.com/fedora-infra/fmn.lib/pull/12/files#r16629573
Merge pull request #12 from fedora-infra/feature/rule-negation

Allow individual rules to be negated.
Add a new can_send property.
Add an `active` field to the filters table allowing to disable a filter w/o deleting it

Relates to https://github.com/fedora-infra/fmn/issues/13
Add an alembic migration script adding the `active` field to the filters table

Relates to https://github.com/fedora-infra/fmn/issues/13
Style change
Only include the filters that are active in the json representation of the preferences

Relates to https://github.com/fedora-infra/fmn/issues/13
Added a method on the Preference model to disable/enable filters
Removed session.flush from Preference.set_filter_active. It isn't needed as pointed out by @pypingou
Merge pull request #13 from rossdylan/disable_filter

Added a method on the Preference model to disable/enable filters
Make it possible to make accounts active by default.

But do so only if our caller can provide a delivery detail value.
Adjust other test cases now that providing a detail_value makes preferences active.