On Sun, May 20, 2012 at 12:38 PM, Jeroen De Dauw jeroendedauw@gmail.com wrote:
I hope there are very few people that do not want review for their extensions. However, this is not why people need to have automatic merging. The use case is people developing extensions and not being able to wait weeks before important commits of them get reviewed and merged. Many developers in the community work for third parties that want to see results, so if you force developers to wait on review this long, they'll just go use their own repository, and then you end up with way less visibility then you have now even for things that gerrit is to dumb to show in it's list of merged changes.
Quite different motivation then not wanting changes to be reviewed ;)
Fair enough. But the end result is the same :)
Thinking about it, it would be nice to have a working post-commit review workflow like we used to have, for those projects where gated trunk does not work due to lack of quick review.
I'm open to suggestions here. We could write some custom approval/review rules in Prolog for extensions that want them (put them in rules.pl on the refs/meta/config "branch")
-Chad
PS: Here's the default review rules http://code.google.com/p/gerrit/source/browse/gerrit-server/src/main/prolog/...