#2 would be great; I know a lot of people have requested the ability to have
some indication that the patch submitted will (a) apply cleanly and (b)
build (maybe even including automated testing).
#1 is often requested, but it's something which we've been wary of because
of the complexities of user authentication, audit chains, and the abilities
it would introduce to break things. It would be a cool feature, but I think
we'd need to approach it carefully.
On Thu, Apr 14, 2011 at 10:19 AM, Jan Koprowski <jan.koprow...@gmail.com>wrote:
> Recently i look at Gerrit - review tool dedicated for git guys. Two things
> bring my attention:
> 1) Gerrit try to merge code automatically after review. This is great
> ability. As far I'm aware when merge won't end with success developer get
> message to rebase their code and send to review again. It will be cool to
> get something similar at reviewboard. I think this approach will for for Git
> and probably for Mercurial too.
> 2) Build system integration. I saw Hudson & Gerrit integration which assume
> additional field for build system which check is project build with new
> versions or not. It is well exposed at
> http://source.android.com/source/life-of-a-patch.html. Will be something
> nice to make accessible some by API "checkbox field" for build system and
> approach such workflow in reviewboard - optional ofcourse.
> What do You think?
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at