在线代码审查工具,Review Board 2.5.1 发布

jopen 8年前

代码审查(Code Review)不但可以提高质量,而且还是一个知识共享和指导的极好的手段。不幸的是,准备工作的辛苦和工具支持的缺乏让代码审查很容易被延至“稍后再议”。Review Board的目标便是改变这一现状,它所提供的应用程序可以支持代码审查流程。

Review Board 2.5.1 发布,此版本是个 bug 修复版本:

新特性

  • The branch field of a review request is now populated when posting an existing commit for review. (Bug #3935)

    Patch by Anthony Hache.

可用性改进

  • The line numbers shown in the diff viewer no longer distract from the code. (Bug #3981)

    The line numbers are now lighter and aren’t shown as bold, helping to keep focus on the code itself.

    Patch by Edward Lau.

Bug 修复

  • Fixed the Summary column in the dashboard when using Python 2.6. (Bug #4005)

    The Summary column was being built using some logic that didn’t work on Python 2.6, resulting in broken summaries.

  • The review dialog’s footer field is no longer hidden if it has content.

    This could happen before if making some comments on a new review, adding a footer, and then deleting the comments. The footer would be invisible and thus uneditable.

  • Fixed the presentation of mode options when viewing image diffs.

    The default image diff mode wasn’t being highlighted when first viewing the image diff. They would also sometimes wrap when selected.

  • Fixed serialization of review replies for webhook payloads. (Bug #3999)

    The links in the payloads were previously incorrect for replies.

  • Fixed the standard authentication backend calling the wrong function when trying to create a user under specific circumstances.

    This wasn’t likely to cause problems in real usage, but could be an issue for anyone basing a new authentication backend off of the standard backend.

更多内容请看发行说明

在线代码审查工具,Review Board 2.5.1 发布

一些应用程序的特性包括:

  • 详细的审查请求将所有代码审查所需要的信息都集合起来,包括代码的修改和屏幕截图

  • 一个支持将评论直接写至对应的代码行的diff查看器

  • 上下文讨论

  • 一个汇总审查和被审查需求的面板

Review Board在审查补丁(Patch)方面表现完美。一个叫做“提交审查”的工具被用来和SCM系统进行连接(当前支持SVN、CVS、Perforce、 Git和Mercurial等),可以允许你请求一个将被提交的修改的审查。用户基础页面将这个过程描述如下:

  1. 你在本地检出的代码上做了些可怕的修改。

  2. 你通过公布diff、编写描述和选择一些审查者来创建一个审查请求。

  3. 你在审查请求中点击“发布”并等待你的审查者看到它。

  4. 其他人看了你的审查请求,说道“这太可怕了,除非什么东西坏掉了。”

  5. 你根据他们的评论更新了你的代码。

  6. 你公布了更新后的diff,以及对他们评论的解答以指明你修改了什么(或者你要说明为什么你不打算按照他们的建议修改代码)。

  7. 大家看了你更新后的代码,并请你继续。

  8. 你将修改提交到仓库中。

  9. 你在审查请求中点击“设置为已提交”来从其他人的面板中移除你的审查请求。

来自 InfoQ