Hi,
I've mostly been concentrating on getting 1.5 ready to ship, so I haven't been reviewing much code lately.
I love the idea of integration like this, but let me quickly tell you where we stand on it. We're trying to keep the core of Review Board nice and simple, without features that are specific to one setup or another. Hudson support is something I want, but it can't be done today, or we'll just get hammered with questions about Tinderbox, Buildbot, etc. If something like this went into the codebase, it would have to be designed in such a way where it supported a variety of systems cleanly, and we'd have to be comfortable enough with it to support it as part of the product.
What we are doing, though, is building in mechanisms for third parties to easily extend Review Board. There are three efforts:
1) The web API, which has been revamped in RB 1.5, and is useful more for when you want other tools to talk to Review Board.
2) WebHooks support, which will be landing in 1.6. This allows Review Board to notify another service (such as some bridge service between Review Board and something else) when something on the server has changed (a review request was posted, updated, etc.)
3) Extension support. This is the big one. This will allow people to write loadable extensions for Review Board that introduce new features, new UI, new settings, etc. This will probably be coming in 2.0, but that's hopefully not *too* far off, at least for people to start testing. The extension framework lives on a couple branches and is pretty far along.
Christian
--
Christian Hammond -
chi...@chipx86.comReview Board -
http://www.reviewboard.orgVMware, Inc. -
http://www.vmware.com