Ideas for improving the release process

[Cemil Azizoglu]

>
>
>>>  3. Downstreams' build/sanity testing could be done as part of MP
>>>     autolanding to identify breaks.
>>>
>>
> where exactly - autolanding on devel?
>

​
Yes
​


>
>
>>  4. Downstreams' release testing. How useful are AP tests for U8
>>>     and Browser? General opinion is 'not very'. Should we look into
>>>     doing away with them? Or at least identify the subset of them that
>>>     is relevant to Mir, and run them during every release as part of
>>>     autolanding as a 'nonblocking' test.
>>>
>>>
> I am not opposed to pruning down the list because it is a time killer.
> however, one reason we are running these AP tests is due to the fact we've
> broken them before with Mir releases. I would suggest if we want to prune
> the tests, to engage with unity8 & web browser team to work up a list of
> the individual AP tests we should run.
>

It's good to learn that they did at some point fail as part of the release.
​
That means there are some tests that are relevant.
Yes we will go through them and identify those and still use them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20160216/9ceab2ed/attachment.html>