Repository: accumulo Updated Branches: refs/heads/ACCUMULO-4647 32eaf3545 -> 9e864befc
ACCUMULO-4647: latest changes Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/9e864bef Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/9e864bef Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/9e864bef Branch: refs/heads/ACCUMULO-4647 Commit: 9e864befcd74876905697644293e21679c0e4a56 Parents: 32eaf35 Author: Dave Marion <dlmar...@apache.org> Authored: Tue Jun 6 11:45:58 2017 -0400 Committer: Dave Marion <dlmar...@apache.org> Committed: Tue Jun 6 11:45:58 2017 -0400 ---------------------------------------------------------------------- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/accumulo/blob/9e864bef/CONTRIBUTING.md ---------------------------------------------------------------------- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fd4d7e6..9f52bdb 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -27,13 +27,13 @@ limitations under the License. ## Patch Submission -- Ensure that Accumulo builds cleanly before submiting your patch using the command: `mvn clean verify` +- Ensure that Accumulo builds cleanly before submiting your patch using the command: `mvn clean verify -DskipITs` - Before submission please squash your commits using a message that starts with the JIRA issue number and a description of the changes. - Patches should be submitted in the form of Pull Requests to the Apache Accumulo GitHub [repository](https://github.com/apache/accumulo/) or to the [Review Board](https://reviews.apache.org) accumulo repository. ## Review -- While everyone is welcome to review patches, at least one committer needs to review and approve your patch. +- We welcome reviews from anyone. Any committer can approve and merge the changes. - Reviewers will be looking for things like threading issues, performance implications, API design, etc. - Reviewers will likely ask questions to better understand your change. - Reviewers will make comments about changes to your patch:
