@justin oh yep I think we missed just one item? -
❌ The project description should include the incubator disclaimer. - ✅ pip install apache<project> should not install an artifact containing unapproved code. - N/A: Release candidates, nightlys or snapshots need to be clearly tagged as pre-release on *https://pypi.org/project/apache-<project>/#history <https://pypi.org/project/apache-%3Cproject%3E/#history>* - ✅ The latest version should not point to an artifact containing unapproved code e.g. to a release candidate or snapshot - ✅ The meta license field should display the ALv2 license. Or ? Otherwise: > Not all artifacts have incubating in their names. That's because there are no instructions for keeping the existing pypi library up to date. We need those artifact names to conform. If we should just post-process the source release then that's fine. But I thought this approach is clearer and more transparent. On Mon, Oct 6, 2025 at 4:21 PM Justin Mclean <[email protected]> wrote: > HI, > > Sorry, it’s -1 (binding) from me. For distribution on PyPI, please see > [1]. It appears that you are not following this, particularly in the naming > of the artifact. The vote should be only on one source artifact. However, > this is easily fixed and would probably only require a rename of the PyPI > package, and there would be no need to create another RC. > > I checked: > - Not all artifacts have incubating in their names. > - signature and hashes are fine > - DISCLAIMER exists > - LICENSE and NOTICE are good > - No unexpected binary files > - I did not compile from source > > Kind Regards, > Justin > > 1. https://incubator.apache.org/guides/distribution.html#pypi
