Add an idempotence test for pruning.
[mailshears.git] / doc / TODO
1 * There is essentially no error handling. We report errors, but we
2 don't fail when we see one. The main reason for this is that we
3 don't know when each plugin will be run. If the first plugin
4 encounters an error, we could quit right there. But what if the
5 third one fails after the first two succeed? We would need some kind
6 of rollback mechanism.
8 For "mv", a rollback is conceivable. But with "rm", there's no going
9 back. Maybe relying on the user to interpret the output and go
10 fix stuff himself is the best we can do?
12 * Add OpenDKIM support.
14 * Document everything with yard.
16 * Write a man page.
18 * Tests: Check that child tables contain what they're supposed to, too.
20 * Update the README.
22 * Make a release.