integration branch in plasma-mobile

[Thomas Pfeiffer]

On Wednesday 14 November 2012 16:08:31 Aaron J. Seigo wrote:
> hello ...
> 
> so i *finally* got around to creating the integration branch in
> plasma-mobile.
> 
> from this point forward, only peer reviewed bug fixes and obvious, can't-be-
> wrong trivial fixes should be pushed into master.
> 
> ALL other activity must occur in topic branches. once the branch is ready to
> be pushed, create a review request on reviewboard.kde.org and after initial
> review, i will merge it into the integration branch.
> 
> topic branches should be started from the master branch.
> 
> all pre-release testing should be done using the integration branch.

Will there be Mer-based images which contain packages from Integration? That 
would be necessary for testing the integration branch. I'd use such an image 
on my daily-use Wetab then and test it continuously (of course knowing that it 
may break from time to time ;).

> every monday, all topic branches will be merged into master that have:
> 
> * successfully been merged in the integration branch
> * have been tested and peer reviewed with an explicit +1 from at lesat one
> other core developer and/or tester

Great! I also like that we'll be using Reviewboard. I love that tool, even as 
a non-developer :)

> at that point, i will then rebase the integration branch on master and re-
> integrate all branches under review. this will make it a messy branch in
> terms of git history since it will be rebased often; this is not a problem
> as it will never merged back into master. this means *no commits* should
> ever be made directly to the integration branch. only to topic branches.
> 
> cheers, and best of luck to us all in this new experiment :)

It's surely going to give quality a big boost!