| commit | 296cd898f3d635d578b6dc2762131f6202ea947e | [log] [tgz] |
|---|---|---|
| author | Logan Hanks <logan@google.com> | Wed May 03 15:14:41 2017 -0700 |
| committer | Logan Hanks <logan@google.com> | Wed Jun 14 14:13:29 2017 -0700 |
| tree | d8c9b03d2a30b8bcd7ccdfd096da779e0b242d63 | |
| parent | 1290bb0a8bdbc76efbfd53c4c6211e4e48e3f84d [diff] |
Add hasReviewStarted, pendingReviewers to Change The introduction of the WIP property on changes gives us the ability to define a new concept: whether a change has started review. A change starts review as soon as its WIP property is set to false. Starting review is permanent; hasReviewStarted remains true even if the change returns to WIP. Review also starts immediately on any change that is not WIP at creation time. This makes it possible to suppress notifications on WIP changes according to whether notifications have previously been sent. Another two properties we can add now are pendingReviewers and pendingReviewersByEmail. These are the sets of reviewer mutations that have occurred since the change entered its current WIP phase. This is necessary so we can correctly address all modified reviewers in notifications when the change leaves WIP, and so PolyGerrit can indicate to the change owner which reviewers haven't been notified yet. The hasReviewStarted property is a simple boolean column in ReviewDb, and is derived by NoteDb from Work-in-progress footers. The pendingReviewers and pendingReviewersByEmail properties are only available when changes are read from NoteDb (they reset to empty when a change is read or rebuilt from ReviewDb). They are also derived from Work-in-progress footers. Changes that are ready for review have no pending reviewers. Pending reviewers are indexed, but we do not provide any new search operators for them at this time. Change-Id: I05c7a21b078e5b1a49940d16c1196c296cd3e25c
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.