Principle:Apache Airflow Provider Release Process
| Knowledge Sources | |
|---|---|
| Domains | Release_Engineering, Package_Management |
| Last Updated | 2026-02-08 00:00 GMT |
Overview
A standardized release process for building, signing, testing, and publishing Airflow provider distribution packages.
Description
The Provider Release Process follows Apache Software Foundation guidelines: build packages using the breeze development tool, sign artifacts with GPG keys, publish to Apache SVN for voting, then release to PyPI after community approval. The process supports batch release of multiple providers simultaneously with automated version bumping and changelog generation.
Usage
Follow the Provider Release Process when releasing new versions of provider packages. Use breeze for package building, sign.sh for artifact signing, and twine for PyPI publication.
Theoretical Basis
Release Pipeline:
- Build: breeze prepares source and wheel packages
- Sign: GPG signing (.asc) and checksums (.sha512)
- Stage: Upload to Apache SVN dist/dev for community review
- Vote: 72-hour voting period on dev@ mailing list
- Publish: Upload to PyPI, tag release in Git
- Announce: Send announcement to mailing lists
Related Pages
Implemented By
Page Connections
Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment