Jump to content

Connect SuperML | Leeroopedia MCP: Equip your AI agents with best practices, code verification, and debugging knowledge. Powered by Leeroo — building Organizational Superintelligence. Contact us at founders@leeroo.com.

Principle:Apache Airflow Provider Release Process

From Leeroopedia
Revision as of 18:11, 16 February 2026 by Admin (talk | contribs) (Auto-imported from principles/Apache_Airflow_Provider_Release_Process.md)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


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:

  1. Build: breeze prepares source and wheel packages
  2. Sign: GPG signing (.asc) and checksums (.sha512)
  3. Stage: Upload to Apache SVN dist/dev for community review
  4. Vote: 72-hour voting period on dev@ mailing list
  5. Publish: Upload to PyPI, tag release in Git
  6. 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
Retrieved from "https://leeroopedia.com/index.php?title=Principle:Apache_Airflow_Provider_Release_Process&oldid=25404"