s/simplejson/json/ (#1060234)
Allow editing bugs/notes during a push, but not builds. (#739)
Update our test_remove_build_and_add_different_release_to_update unit test
Test editing updates that are headed to stable and testing
Link to the update feedback guidelines on each update (#713)
Whitespace
Avoid count()ing multiple times
Clean up some unused imports
Increase the bodhi client request timeout to 300 seconds.

This is currently being applied as a hotfix in fedora infrastructure.
https://fedorahosted.org/fedora-infrastructure/ticket/3755
More prevention of duplicate builds across multiple updates (#682)
Add a unit test to ensure that we disallow adding duplicate builds when editing updates
Don't try and set the request of an update if it's already in that state.

This can occur when editing updates, and causes certain tests to fail. Since
PackageUpdate.set_request throws an exception if it is already in the requested
state, we want to avoid this because at this point we've already made changes
to the update/builds.
Merge pull request #30 from fedora-infra/feature/ticket-682

Disallow the same build in two different updates
Bump version to 0.9.8
Merge branch 'release/0.9.8' into develop
Fix the year
Require python-tgcaptcha, not python-tgcaptcha2
Fix an edge case when someone logs in right after failing the captcha
Reset karma to 0 on edit

When testers submit karma to an update, it shouldn't be kept if the
update is edited and its builds are changed.

However, we keep the history of comments added, because that is
important.

Also, if no builds are changed (e.g just the update notes were
modified), then there's no point in resetting the karma to 0.

https://fedorahosted.org/bodhi/ticket/388
https://fedorahosted.org/fesco/ticket/1238