[Toaster] Toaster master breakages

[Damian, Alexandru]

Hello all,

I've posted a patchset, on Friday 26, that broke the Toaster master in a
number of ways. As usual in these situations, the breakage was not caused
by a single fault, but by a chain of mis-happenings that show policy
failures in our processes.


Paul was kind enough to help analyze the situation, and we've identified
some of the gaps:
- I've posted upstream a patch that I didn't actually intend to upstream in
this release, and which wasn't properly reviewed. Probably happened because
I hurried on manually submitting.
- While, thanks to latest efforts, we've got better in terms of unit
testing, we still have a significant gap in functional and integration
tests, especially automated tests.​


​Michael was very proactive and helpful in fixing the master, and I want to
thank him for that - but we shouldn't continue on this path. While we
continue to have the policy of not breaking master, we should take steps to
set out proper policies in place enforce correct submissions, and to
prevent us from chasing fires all the time.


​This is a call for ​proposals and suggestions. Please help me figure out
solutions to have better policies around submission and testing, and proper
automation against these tasks.

Please reply to this thread with:
- observations on any process/policy gaps that you might notice, and
proposals for fixing them
- suggestions around automating the patch review process
- suggestions around possibly changing the review requirements
- suggestions around automating the patch upstreaming process
- suggestions on improving the functional and integration testing coverage


Thank you !

Cheers,
Alex

-- 
Alex Damian
Yocto Project
SSG / OTC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20150706/9f3dd0fd/attachment.html>