workers using *state.State

[William Reade]

People keep writing them, in defiance of sane layering and explicit
instructions, for the most embarrassingly trivial tasks
(statushistorypruner? dblogpruner? txnpruner? *all* of those can and should
pass through a simple api facade, not just dance off to play with the
direct-db-access fairies.)

There is no justification for *any* of those things to see a *state.State,
and I'm going to start treating new workers that violate layering this way
as deliberate sabotage attempts. Leads who have overseen the introduction
of those workers, sort it out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20150908/84ce0ab6/attachment.html>