On 31 March 2015 at 19:03, Francis Ginther <[email protected]> wrote: > > Or if it's going to break the API, expose it as a new, versioned method >> instead. >> > > Let's be sure to document a pattern for doing this in the developer > playbook. We'll need to define some criteria for when a method is in > development mode and can be changed vs make a new one. This is probably > easy enough to define as when a service begins it's life as a production > service. >
Isn't changing the API or behaviour of a method just as much of a problem during development as it is in production? Do we even have such a line between development and production when we practice continuous deployment?
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
