Google Git
Sign in
apache / tooling-asf-example / refs/tags/v0.0.1-dev8
tag538b58290a380b058b5a9659caa6a394aef263f3
taggerSean B. Palmer <sean@miscoranda.com>Tue Aug 19 15:03:19 2025 +0100
object57912833c7b1b3d032f0abe4fdec0386efac7c4f 
Release 0.0.1-dev8
commit57912833c7b1b3d032f0abe4fdec0386efac7c4f[log] [tgz]
authorSean B. Palmer <sean@miscoranda.com>Tue Aug 19 15:02:53 2025 +0100
committerSean B. Palmer <sean@miscoranda.com>Tue Aug 19 15:02:53 2025 +0100
treef917cb7f955966da219aaaaf1995ac51d63c3e38
parentc400bbfd1d2bd7b10fdbbf448bb06128d9f9fdd8 [diff]
Refer to the repository explicitly when creating a release
4 files changed
tree: f917cb7f955966da219aaaaf1995ac51d63c3e38
  1. .github/
  2. bin/
  3. share/
  4. src/
  5. tests/
  6. .gitignore
  7. .pre-commit-config.yaml
  8. Makefile
  9. pyproject.toml
  10. README.md
  11. uv.lock
README.md

asf-example

This is not an official release of the Apache Software Foundation (ASF).

This is an example test package issued by Tooling at the ASF. It contains no stable user facing functionality. We do not make guarantees about any of the interfaces contained herein, nor the continued existence of this package.

The purpose of this package is to test:

  • Proposed package naming conventions and version schemes within ASF Infra and ASF Tooling
  • GHA workflows for trickle down use in other ASF Tooling projects
  • Interaction with the ATR platform presently under development by ASF Tooling

The proposed packaging conventions are:

  • Use the asf-* prefix scheme for PyPI package names to align with PEP 752
  • Use asf.* for package interfaces, utilising PEP 420 namespacing
  • Ensure that package code is in src/asf/*/ only
  • Ensure that src/asf/*/ contains an __init__.py
  • Use 0.0.N for versions, starting with 0.0.1
  • Increment N for each released version
  • Optionally use 0.0.(N+1)-devM for non-release main commits
  • Start with -dev1 if using non-release main commit versions

A package having three commits on main, then a release, then two more commits to main, then another release, will for example use the following versions if opting into -devM versions:

0.0.1-dev1
0.0.1-dev2
0.0.1-dev3
0.0.1
0.0.2-dev1
0.0.2-dev2
0.0.2

These packaging conventions are proposed only for ASF Infra and Toolings packages which will be published to PyPI. Other packages, for internal use, may use any packaging conventions. Aligning with these conventions, if adopted, would, however, make it easier to promote internal packages to PyPI.