...
When the current chair of the PMC resigns, the PMC votes to recommend a new chair using lazy consensus, but the decision must be ratified by the Apache board.
Release Manager
A release manager takes responsibility for the mechanics of a release. Release managers take care of shepherding a release from an initial community consensus to make it to final distribution.
Release managers do the work of pushing out releases. However, release managers are not ultimately responsible. The PMC in general, and the PMC chair in particular (as an officer of the Foundation) is responsible for compliance with requirements.
Any committer may serve as the manager of a release.
A release starts when the project community agrees to make a release. However, no release manager can make a valid release unless the community has taken the necessary steps to prepare in advance. The source code and build process must comply with the legal and intellectual property requirements for a valid release, and the project must have the infrastructure in place to correctly sign the release artifacts.
Decision Making
Within the Flink project, different types of decisions require different forms of approval. For example, the previous section describes several decisions which require 'lazy consensus' approval. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval.
...
These are the types of approvals that can be sought. Different actions require different types of approvals.
Approval Type | Definition |
---|---|
Lazy Consensus | Lazy consensus Consensus requires 3 binding +1 votes and no binding vetoes. |
Lazy Majority | A lazy majority vote requires 3 binding +1 votes and more binding +1 votes than -1 votes. |
Lazy Approval | An action with lazy approval is implicitly allowed unless a -1 vote is received, at which time, depending on the type of action, either lazy majority or lazy consensus approval must be obtained. |
2/3 Majority | Some actions require a 2/3 majority of active committers or PMC members to pass. Such actions typically affect the foundation of the project (e.g. adopting a new codebase to replace an existing product). The higher threshold is designed to ensure such changes are strongly supported. To pass this vote requires at least 2/3 of binding vote holders to vote +1. |
...
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 | 0 | JIRA or Review Board Github Pull Request (with notification sent to dev@flink.apache.org) |
Release Plan | Defines the timetable and actions for a release. The plan also nominates a Release Manager. | Lazy majority | Active committers | 3 | |
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 | |
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 | 6 | |
New Committer | When a new committer is proposed for the project. | Lazy consensusConsensus | Active PMC members | 73 | |
New PMC Member | When a committer is proposed for the PMC. | Lazy consensusConsensus | Active PMC members | 3 | |
Emeritus PMC Member re-instatement | When an emeritus PMC member requests to be re-instated as an active PMC member. | Lazy consensusConsensus | Active PMC members | 3 | |
Emeritus Committer re-instatement | When an emeritus committer requests to be re-instated as an active committer. | Lazy consensusConsensus | Active PMC members | 3 | |
Committer Removal | When removal of commit privileges is sought. | Consensus | Active PMC members (excluding the committer in question if a member of the PMC). | 6 | |
PMC Member Removal | When removal of a PMC member is sought. | Consensus | Active PMC members (excluding the member in question). | 6 | |
Modifying Bylaws | Modifying this document. | 2/3 majority | Active PMC members | 6 |
...