You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by pt...@apache.org on 2015/02/27 22:46:27 UTC
[2/4] storm git commit: update commit actions based on community
feedback
update commit actions based on community feedback
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/18a68a07
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/18a68a07
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/18a68a07
Branch: refs/heads/master
Commit: 18a68a074570db01fc6377a269feb90ecda898ab
Parents: 8b53474
Author: P. Taylor Goetz <pt...@gmail.com>
Authored: Thu Feb 12 20:51:27 2015 -0500
Committer: P. Taylor Goetz <pt...@gmail.com>
Committed: Thu Feb 12 20:51:27 2015 -0500
----------------------------------------------------------------------
BYLAWS.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/storm/blob/18a68a07/BYLAWS.md
----------------------------------------------------------------------
diff --git a/BYLAWS.md b/BYLAWS.md
index 82f26ac..fe4d846 100644
--- a/BYLAWS.md
+++ b/BYLAWS.md
@@ -82,7 +82,7 @@ This section describes the various actions which are undertaken within the proje
| Actions | Description | Approval | Binding Votes | Minimum Length | Mailing List |
|---------|-------------|----------|---------------|----------------|--------------|
-| Code Change | A change made to a source code of the project and committed by a Committer. | A minimum of one +1 from a Committer other than the one who authored the patch, and no -1s. The code can be committed after the first +1. | Active Committers | 1 day from initial patch (**Note:** Committers should consider allowing more time for review based on the complexity and/or impact of the patch in question.)|JIRA or Github pull ( with notification sent to dev@storm.apache.org) |
+| Code Change | A change made to a source code of the project and committed by a Committer. | A minimum of one +1 from a Committer other than the one who authored the patch, and no -1s. The code can be committed after the first +1. If a -1 is received to the patch within 7 days after the patch was posted, it may be reverted immediately if it was already merged. | Active Committers | 1 day from initial patch (**Note:** Committers should consider allowing more time for review based on the complexity and/or impact of the patch in question.)|JIRA or Github pull ( with notification sent to dev@storm.apache.org) |
| Non-Code Change | A change made to a repository of the project and committed by a Committer. This includes documentation, website content, etc., but not source code, unless only comments are being modified. | Lazy Consensus | Active Committers | At the discression of the Committer |JIRA or Github pull (with notification sent to dev@storm.apache.org) |
| Product Release | A vote is required to accept a proposed release as an official release of the project. Any Committer may call for a release vote at any point in time. | Majority Approval | Active PMC members | 3 days | dev@storm.apache.org |
| Adoption of New Codebase | When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue. This also covers the creation of new sub-projects and submodules within the project as well as merging of feature branches. | 2/3 Majority | Active PMC members | 6 days | dev@storm.apache.org |