Hi folks, I want to reiterate the importance of ensuring legal compliance before publishing any public artifacts. As packages on PyPI are considered release artifacts, we must confirm that the Python CLI adheres to all ASF policies, especially regarding incubation status.
I have addressed the LICENSE/NOTICE requirement on the GitHub project board (https://github.com/orgs/apache/projects/540/views/1) by assigning the relevant issue. We must also confirm that the Incubator DISCLAIMER is included and that the package name and version clearly reflect the incubating status. Legal correctness is a hard requirement and a necessary blocker before we proceed with publishing any public artifacts. I will perform a complete pass and review of these details. Thanks, Jean-Baptiste Onofré On Tue, Oct 14, 2025 at 9:17 AM Honah J. <[email protected]> wrote: > > Hi everyone, > > I’d like to start a discussion about publishing the Apache Polaris Python > CLI to PyPI and providing nightly builds (test PyPi). > > The main goal is to make the CLI easier to install (pip install > <package_name>) and to align its release and distribution process with ASF > guidelines. I’ve drafted a proposal [1] that outlines the key requirements > and the high-level release process if we include the Python CLI in the next > release. The proposal also covers how we might set up nightly builds on > Test PyPI for early testing. > > While some details can be finalized later, I’d like to first gather > feedback on the overall direction — specifically, whether the community > agrees with publishing to PyPI and providing nightly builds. > > If there’s general agreement, I plan to open two separate [VOTE] threads to > formalize these decisions: > 1. Whether to the Python CLI to PyPI > 2. Whether to provide nightly build (publish to test PyPi) > > Please let me know what you think! > > [1] > https://docs.google.com/document/d/1gbKYnFftpq884GhJ59waHdfoQG6MrevVAVCspf3hbrk/edit?usp=sharing > > > Best regards, > Jonas
