Merge branch 'release/0.2.1' into develop
Include requirements in the next release.
How did that get in there?
Make BadgeRules accept the actual issuer_id.
Pass the whole badge dict along with the fedmsg message.
Link to the ansible repo.
Merge pull request #9 from fedora-infra/feature/link-to-badge-repo

Link to the ansible repo.
Merge pull request #7 from fedora-infra/feature/issuer-ambiguity

Make BadgeRules accept the actual issuer_id.
Merge pull request #8 from fedora-infra/feature/more-info-in-messages

Pass the whole badge dict along with the fedmsg message.
Allow topic and otherwise comparisons to use "endswith".

This will be convenient especially for topics.  Instead of having
to define:

    trigger:
        topic: org.fedoraproject.stg.bodhi.update.request.testing

In one badge, and then *redefine* in another:

    trigger:
        topic: org.fedoraproject.prod.bodhi.update.request.testing

With this we can just define one badge rule with:

    trigger:
        topic: bodhi.update.request.testing
Initialize fedmsg early.
Pass along the tahrir user_id so we can construct URLs from it elsewhere.
Merge pull request #10 from fedora-infra/feature/endswith-comparisons

Allow topic and otherwise comparisons to use "endswith".
Merge pull request #11 from fedora-infra/feature/init-fedmsg-early

Feature/init fedmsg early
Merge pull request #12 from fedora-infra/feature/still-more-fedmsg-info

Feature/still more fedmsg info
This is the right way to do this.
Patch out fedmsg.init so tests are idempotent.
Add failing test for dotted substitutions.
Clarify that it is "recipient" not "recipient_key".
Enforce possible arguments to BadgeRule.