[MeeGo-touch-dev] INFO: Speeding up merge requests

[Jörgen Scheibengruber]

A public service announcement:

There have been some hints here and there, that many people are not
happy with how quickly their merge-requests are being handled. We are
aware of the situation, and the libmeegotouch maintainers[1] are working
hard on keeping up with all contributions.

Here is what you can do to speed up things.

1) Please get in touch with one or two other _non-maintainers_ that you
think qualify as reviewers for the piece of code that you want to see
changed. Ask them to review your code, and update the code with their
comments and suggestions, or convince them that you're code is already
perfect.
2) Test the code on actual hardware (if you have access to it). Make
sure nothing breaks, that the performance is ok, that all unit tests
still pass (on the target hardware!), etc. Say that you have done so in
the merge request, and that you are willing to bet your first-born child
on that your change does not break anything.
3) Merge requests that are already "Go ahead and merge" by someone who
knows the code-base in question well are usually processes very
quickly. 

Thanks for listening,
Jörgen

[1] http://gitorious.org/+meegotouch-maintainers