Quoting Dries Buytaert <dries.buytaert@gmail.com>:
I'm slightly worried that 'reviewed and tested by the community' will have lower quality submissions than 'ready to be committed'. The problem with 'reviewed and tested by the community' is that people will set it to 'reviewed and tested by the community' after one review, whereas with 'ready to be committed', we typically had different people looking at a patch.
As was stated in the issue at least two reviewers and testers should comment before setting to this status. As for the control of the setting, it operates the same as Ready To Be Committed.
Read: I think 'ready to committed' was perfectly fine and I don't understand why this was changed without my approval. After all, I'm the one reviewing and committing these patches.
It is a user perception thing. Ready To Be Committed not committed inflames developers. Reviewed and Tested is implies that some role level greater than the patch creator can now take his precious time to look at this lowly patch.
Also, why the 'by the community' part? Why not just 'reviewed and tested'? Please rename at least to 'reviewed and tested'. Everything we do is community-driven so 'by the community' is completely redundant. It seems to suggest that there is a non-community body as well.
Agreed. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/