This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/master by this push:
new d95e5ff Clarify cool down period time CTR
d95e5ff is described below
commit d95e5ff4a4310569bea160e9b116eeaff1f9c634
Author: Stephen Mallette <[email protected]>
AuthorDate: Tue Nov 20 08:51:01 2018 -0500
Clarify cool down period time CTR
---
docs/src/dev/developer/for-committers.asciidoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/src/dev/developer/for-committers.asciidoc
b/docs/src/dev/developer/for-committers.asciidoc
index 6be1da8..0dae407 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -445,7 +445,7 @@ to the committer wanting to put code into a release branch.
** Be certain that the test suite is passing.
** If you updated documentation, be sure that the `process-docs.sh` is
building the documentation correctly.
* Before you can merge your branch into the release branch, you must have at
least 3 +1
link:http://www.apache.org/foundation/glossary.html#ConsensusApproval[consensus
votes]
-from other committers OR a single +1 from a committer and a one week review
period for objections (i.e. a "cool down
+from other committers OR a single +1 from a committer and a seven day review
period for objections (i.e. a "cool down
period") at which point we will assume a lazy consensus.
** Please see the Apache Software Foundations regulations regarding
link:http://www.apache.org/foundation/voting.html#votes-on-code-modification[Voting
on Code Modifications].
** With the "cool down" process and lazy consensus the single +1 may (should)
come from the committer who submitted
