...
Significant, pervasive features are often developed in a speculative branch of the repository. The While the initiative is active the PMC may grant commit rights on the branch to its consistent contributors, while the initiative is active. Branch committers are responsible for shepherding their feature into an active release and do not cast binding votes or vetoes in the project. Release candidates may not be made from speculative branches nor may they be based on child branches of speculative branches. Unless stated otherwise branch committers are required to follow the the same rules as regular committers.
Submodule Committers
Submodule committers are committers who are responsible for maintenance of a particular submodule of Hive. Committers on submodules have access to and responsibility for a specified subset of Hive's source code repository. Committers on submodules may cast binding votes on any technical discussion regarding that submodule.
...
A Release Manager (RM) is a committer who volunteers to produce a Release Candidate according to HowToRelease. The RM shall publish a Release Plan on the dev@hive list stating the branch from which they intend to make a Release Candidate, at least one week before they do so. The RM is responsible for building consensus around the content of the Release Candidate, in order to achieve a successful Product Release vote.
...
Actions | Description | Approval | Binding Votes | Minimum Length | Mailing List | ||
|---|---|---|---|---|---|---|---|
Code Change | A change made to a codebase of the project and committed by a committer. This includes source code, documentation, website content, etc. | one +1 from a committer who has not authored the patch followed by a Lazy approval (not counting the vote of the contributor), moving to lazy majority if a -1 is received | Active committers | 1 | JIRA (dev@hive.apache.org) | ||
Release Plan | Defines the timetable and actions for a release. The plan also nominates a Release Manager. | Lazy majority | Active committers | 37 | |||
Product Release | When a release of one of the project's products is ready, a vote is required to accept the release as an official release of the project. | Lazy Majority | Active PMC members | 3 | user@hive7 | ||
| New Speculative Branch | When a new speculative branch is proposed for the project. | Lazy consensus | Active PMC members | 7 | dev@hive.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. | 2/3 majority | Active PMC members | 67 | |||
New Committer | When a new committer is proposed for the project. | Lazy consensus | Active PMC members3 | 7 | |||
| New Branch Committer | When a branch committer is proposed for the project. | Lazy consensus | Active PMC members | 7 | private@hive.apache.org | ||
New PMC Member | When a committer is proposed for the PMC. | Lazy consensus | Active PMC members | 37 | |||
Committer Removal | When removal of commit privileges is sought. | Consensus | Active PMC members (excluding the committer in question if a member of the PMC). | 67 | |||
PMC Member Removal | When removal of a PMC member is sought. | Consensus | Active PMC members (excluding the member in question). | 7 | |||
| Branch Committer Removal | When removal of commit privileges is sought. Branch committer privileges will be automatically revoked when a branch is merged to mainline or the branch becomes inactive. | Lazy consensus | Active PMC members | 7 | 6private@hive.apache.org | ||
Modifying Bylaws | Modifying this document. | 2/3 majority | Active PMC members | 67 |