Principle:Apache Airflow Community Voting
| Knowledge Sources | |
|---|---|
| Domains | Release_Engineering, Governance |
| Last Updated | 2026-02-08 00:00 GMT |
Overview
An Apache Software Foundation governance process for community approval of release candidates through email-based voting.
Description
Community Voting is the formal approval mechanism for Apache releases. A release manager sends a vote email to dev@airflow.apache.org describing the release candidate and linking to artifacts. PMC members cast binding votes (+1, 0, -1) during a 72-hour voting period. A release requires at least three +1 binding votes and no -1 votes. After the vote, a result email summarizes the outcome.
Usage
Initiate community voting after RC verification passes. Send vote emails using send_email.py. Wait 72 hours for the voting period. Send result email summarizing votes.
Theoretical Basis
ASF Voting Rules:
- Binding votes: Only PMC members cast binding votes
- Approval threshold: 3+ binding +1 votes required
- Veto power: Any -1 binding vote blocks the release
- 72-hour window: Minimum voting period
- Lazy consensus: No response is implicitly neutral
Related Pages
Implemented By
Page Connections
Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment