How should we change default config values in charms?

[Mark Shuttleworth]

On 14/08/15 04:56, Stuart Bishop wrote:
> I've discussed similar things with regard to the PostgreSQL charm and
> autotuning, with the decision being that charm defaults should be set
> so things 'just work' in a development environment. 

Yes, charm defaults should be efficient for rapid iteration and development.

Iteration and development scenarios are, as Stub points out, orders of
magnitude more common than production scenarios.

In future, we might designate whole environments as dev, test or
production, so that charms could auto-tune differently.

Mark