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 followed by a Lazy approval (not counting the vote of the contributor), moving to lazy majority if a -1 is received.

Note that this implies that committers can +1 their own commits and merge right away. However, the committers should use their best judgement to respect the components expertise and ongoing development plan.

Active committers

0

JIRA or Github Pull Request (with notification sent to dev@flink.apache.org)

A major change to the codebase that meets the FLIP criteria.

Release Plan

Defines the timetable and actions for a release. The plan also nominates a Release Manager.

Lazy majority

Active committers

3

dev@flink.apache.org

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

dev@flink.apache.org

Adoption of New Codebase

Adoption of large existing external codebase. This refers to contributions big enough that potentially change the shape and direction of the project with massive restructuring and future maintenance commitment.

2/3 majority

Active PMC members

6

dev@flink.apache.org

New Committer

When a new committer is proposed for the project.

Consensus

Active PMC members

3

private@flink.apache.org

New PMC Member

When a committer is proposed for the PMC.

Consensus

Active PMC members

3

private@flink.apache.org

Committer Removal

When removal of commit privileges is sought.
Note: Such actions will also be referred to the ASF board by the PMC chair.

Consensus

Active PMC members (excluding the committer in question if a member of the PMC).

6

private@flink.apache.org

PMC Member Removal

When removal of a PMC member is sought.
Note: Such actions will also be referred to the ASF board by the PMC chair. See PMC Member Change Process for details.

Consensus

Active PMC members (excluding the member in question).

6

private@flink.apache.org

Modifying Bylaws

Modifying this document.

2/3 majority

Active PMC members

6

dev@flink.apache.org