Review Board 2.0.10 发布,代码评审工具

来源: 投稿
作者: donghui2020
2014-10-24

Review Board 2.0.10 发布,此版本包括  reviews_reviewrequest 和 reviews_reviewrequestdraft 表的数据库模式修改,此改进只是简单的添加一个索引到 summary field。

更新内容:

性能提升

  • Sped up the Dashboard when using the People, Groups, or To Me columns.

    These columns have been optimized to reduce the number of SQL queries, greatly speeding up the dashboard when used.

  • Sped up searching of summaries in the search field. (Bug #3619)

    There were performance issues with the search field when looking up summaries. We were looking up text anywhere in the summary, but this resulted in too much load on the database.

    For now, we are limiting search to the beginning of the summary text.

    In future versions, we plan to rework this search to allow for looking up text anywhere in the summary.

Bug 修复:

Diff Viewer

  • Fixed selection of text within a single line. (Bug #3631)

    This broke with the improved column-based text selection support in 2.0.9.

  • Fixed navigating between comment flags through key bindings. (Bug #3626)

Administration

  • Fixed problems loading and saving empty passwords.

    This broke with the hardened password storage in 2.0.9.

  • Fixed warnings in the log about naive timestamps.

  • Fixed searching for comment text for file attachment comments and screenshot comments in the database viewer. (Bug #3616)

Git

  • Fixed filename parsing when referenced files in Git diffs contained spaces. (Bug #3558)

    While it doesn’t cover every possible case, the Git diff parsing does do a much better job now of dealing with filenames that contain spaces.

    Patch by Pierre Wilmot.

贡献者

  • Christian Hammond

  • David Trowbridge

  • Pierre Wilmot

Review Board起源于VMware的一些开发者。它基于Django,你可以把它安装在自己的服务器上,工作流和Rietveld极为类似。令人高兴的是它提 供了在diffs里进行语法彩色编码,使得代码阅读变得简便。此外,它还实现了基于Lucene的搜索来帮助管理较大的diffs组。

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

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

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

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

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

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

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

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

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

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


展开阅读全文
18 收藏
分享
加载中
更多评论
2 评论
18 收藏
分享
返回顶部
顶部