On 31 March 2015 at 00:27, Thomi Richards <[email protected]> wrote: > > What makes it into the library (acceptance criteria): > > * Must be backwards compatible. Our services are depending on this, so > breaking changes won't be allowed. >
Or if it's going to break the API, expose it as a new, versioned method instead. We'll have to be super careful to watch out for not just API breakage in MPs, but changes in behaviour. Anything that so alters a method should really be a separate one. * Must be reasonably well tested. > +1 > * Must not contain ci-specific logic. This is *not* where we store common > data payloads between services (that's a separate library that exists on a > per-sprint basis). > A big +1. Let's take a really small slice to try as a library. > > How do we publish & use this? > > I propose that we include it in our pip cache for each service. Whether we > actually publish it to pypi or not is open for debate (I don't really mind, > I guess I'm leaning slightly towards publishing it, since it may be useful > for others). > I honestly don't care, but I don't think we should make a big effort around creating a proper project with releases.
-- 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
