integration branch in plasma-mobile

[Aaron J. Seigo]

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.

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

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 :)

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/active/attachments/20121114/b48ac8b4/attachment.sig>