datatracker/ietf/mailtrigger
Sasha Romijn 88b7b45b0e Fix #2328 - Use mailtriggers to find destinations in review app
As the review app has several conditionals that don't fit
entirely well within mailtriggers, the templates use a bit
of extra context to figure out who exactly to include. This also
extends the tests for review, to check for correct recipients.
It also adds a tiny feature to mailtrigger to entirely exclude
certain addresses, as required by the review-generated mails.

Commit ready for merge.
 - Legacy-Id: 16672
2019-08-27 15:15:13 +00:00
..
migrations Fix #2328 - Use mailtriggers to find destinations in review app 2019-08-27 15:15:13 +00:00
__init__.py mailtoken becomes mailtrigger 2015-09-17 20:03:45 +00:00
admin.py mailtoken becomes mailtrigger 2015-09-17 20:03:45 +00:00
forms.py remove some experimental cruft 2015-09-17 21:25:50 +00:00
models.py Fix #2328 - Use mailtriggers to find destinations in review app 2019-08-27 15:15:13 +00:00
resources.py Change the cache key construction to deal with query arguments containing spaces. Fixes 500 errors which would otherwise occur. 2016-09-25 13:53:22 +00:00
tests.py Added 'from __future__' imports all over the place, to bring code behaviour into closer alignment between python2 and python3 2019-07-15 15:40:51 +00:00
urls.py Fix various "RemovedInDjango20Warning" warnings. Commit ready for merge. 2017-03-25 19:16:45 +00:00
utils.py Fix #2328 - Use mailtriggers to find destinations in review app 2019-08-27 15:15:13 +00:00
views.py mailtoken becomes mailtrigger 2015-09-17 20:03:45 +00:00