Integration processes in MeeGo and how they can be Improved

MeeGo development is an evolving process. To orchestrate the different components together applying "Continuous Integration" paradigm can be useful.
This session would cover the potential problems arising out of the current process followed in MeeGo and how it can be improved.
This session is mainly intended for Release/Platform/Distribution Engineers or Package Maintainers.
As an end user and as a package maintainer, I see bottlenecks and issues in the current process.
Continuous Integration aims at generating deployable software and or finding/fixing bugs at an early stage.
CI as a process should include:
1) Pre-checks - Quality, Process, Policy.
2) Integration Testing - Packages should not introduce breakage to their reverse dependencies whether by
API changes unless planned or by breaking building software images.
3) Automated Testing - Making sure it works using functional tests.
Heart of the build infrastructure in MeeGo is OBS, rich with features for distribution, building and maintenance.
Package maintainers take upstream tar balls and use OBS to build their packages. Packages once built succesfully are sent for integration
through a submit request. Currently, there is no fully automated testing facility available in MeeGo.
Release Engineers have a checklist to promote projects from devel areas or branches to Trunk.
What Release/Platform Engineers should focus on is:
1) If the package is tested on all the relevant hardware platforms.
2) Integrating new code to Trunk should not break the MeeGo images.
3) Each integration of a project should be verified by an automated build including tests and test results to detect integration errors as
quickly as possible.
4) When test results are upto a sufficient standard, package maintainer pushes his or her code towards the MeeGo Trunk project.
5) Test results should be made a mandatory step before accepting a package in Trunk.
All this can be acheived by using different tools or plugins available in open source in addition to the build infrastructure.
This session focuses on how all this can be achieved.