canonical-ci-engineering team mailing list archive

[Thomi Richards <thomi.richards@xxxxxxxxxxxxx>]

Hi,

On Wed, Apr 1, 2015 at 1:56 AM, Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>
wrote:

>
>
> On 31 March 2015 at 00:27, Thomi Richards <thomi.richards@xxxxxxxxxxxxx>
> 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.
>
>
Indeed.



>
>> 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.
>

For sure - I want proper releases, at least to launchpad, if not to pypi as
well. Apart from anything else, I want to avoid the "oh, we're using some
random release I built on my laptop" problem. Releases get versions,
version numbers indicate API compatibility.

Cheers,
-- 
Thomi Richards
thomi.richards@xxxxxxxxxxxxx