Comment 13 for bug 1198465

I have not tested the code to confirm any difference in output in the face of settings that should preserve the current behavior, but Dan's (2) in comment #7 strikes home hard with me.

That said, I think I disagree with the current push toward less settings. If this goes in soon, I would rather see it go in with the full set of 6 settings. My reasoning is that if this feature set is attractive for a broad set of libraries, but there is no consensus on whether exactly one setting or all six are needed (IOW, different combinations of settings are common), then it stands to reason that the functionality will likely want to grow and extend to other billing types and situations. In that case, the precedent of a "all in" setting, and one per situation or billing type for more granular control, will have already been set. I look at it as one extra knob now so that we can add more knobs in the future without breaking folks' mental models.

It also means less churn before commit.

... my 0$.02