[development] What about reviewing patches?

[Ryan Cross]

> Why?
> Reviewing patches would be much more fun if things would be committed
> sooner.
> Patches stay in their current mode for days/weeks and even months untill
> they got committed.

This seems like its becoming even more of an issue as the project
keeps growing. Its obviously a very major bottleneck in the developer
workflow (some could argue its a partially intentional choice) but it
does seem like its some discussion about possible ways of improving
this situation would be helpful.

Maybe speed of commitments isn't the key problem, but avoiding loosing
tester's motivations is something to consider. Or tackle the
committers speed if that is the underlying problem. Ideas?