Hi all,
It's great to focus on nightly/snapshot publications to test.pypi.org first!
Can we change the scope of the PR [1] to just this and leave
release-candidates and SVN out?
Robert
[1] https://github.com/apache/polaris/pull/3036
On Thu, Nov 20, 2025 at 3:38 AM Honah J. wrote:
>
> Hi everyo
Hi everyone,
Thanks for all the great points and suggestions! These are key elements for
a robust release process of Python CLI. Given the number of missing pieces
and to move this forward enough parallelization, I think we could have the
following three tracks:
1. Have a formalized way to build r
Hi,
I have a proposal regarding the use of PyPI for our Python CLI publishing.
To facilitate nightly builds and staging of release candidates for
voting, I propose we utilize test.pypi.org. This platform is
specifically designed for testing and previewing packages, and several
Apache projects are
Hi all,
+1 to what JB said.
Want to emphasize that it's not only about the presence and
correctness of the LICENSE/NOTICE/DISCLAIMER files, but also quite a
few process and technical details.
Following the rules [1] is also a hard requirement [2], including the
implicit technical requirements inc
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 LIC
Hello Kevin! This sounds great!
Feel free to join the party - https://github.com/orgs/apache/projects/540
I believe Jonas is working on this part.
Regards
On 17/11/2025 16:00, Kevin Liu wrote:
Hey folks,
I have experience setting up infra for pyiceberg. Happy to help here.
Best,
Kevin Liu
On
Thanks a lot, Kevin!
Yufei
On Mon, Nov 17, 2025 at 8:00 AM Kevin Liu wrote:
> Hey folks,
>
> I have experience setting up infra for pyiceberg. Happy to help here.
>
> Best,
> Kevin Liu
>
> On Mon, Nov 10, 2025 at 2:49 AM Robert Stupp wrote:
>
> > Legally and technically correct LICENSE and NO
Hey folks,
I have experience setting up infra for pyiceberg. Happy to help here.
Best,
Kevin Liu
On Mon, Nov 10, 2025 at 2:49 AM Robert Stupp wrote:
> Legally and technically correct LICENSE and NOTICE files cannot be
> automatically generated.
> There is just no way to get the necessary infor
Legally and technically correct LICENSE and NOTICE files cannot be
automatically generated.
There is just no way to get the necessary information per published
artifact to do this, neither for Maven/Java nor for Python packages
nor for container-images.
At least not until there is an industry wide
Hi Yufei, thanks for your feedback.
I would keep focus on the current topic and make it finalized.
I believe LICENSE/NOTICE/DISCLAIMER checks can be automated but it's not
a priority.
I synced on this initiative with Honah in DM in Slack and proposed my help.
Regards,
Artur.
On 07/11/2025 1
Hi Artur,
Thanks for bringing this up again and for outlining such a clear plan.
Setting up the PyPI project and nightly Test PyPI builds sounds like a
great next move.
One thought: do you think we could automate the LICENSE, NOTICE, and
disclaimer checks as part of the build pipeline? That could
Hi everyone,
I’d like to bring this topic up again so it doesn’t get lost. I’d like
to offer my help with this initiative to speed up the package release
process.
Thanks a lot for the detailed document — from it, I can already see some
potential steps that need to be completed.
Since the pac
Hi
I'm supporting this. However, as packages on PyPi are considered as
"release artifacts", it has to be legally correct regarding The ASF
policy.
Several Apache projects already publish PyPi packages (for instance
https://superset.apache.org/docs/installation/pypi/).
As we are in the incubator,
Jonas, thanks for kicking this off! This sounds like a great direction!
Publishing the Python CLI to PyPI will definitely make installation much
smoother and improve UX. Nightly builds on Test PyPI are also nice for
faster iteration and early feedback.
I’m fully supportive of moving forward with th
+1 Thank you Jonas, for the initiative, I fully support PyPi publishing. It
is very convenient !
Best,
Prashant Singh
On Tue, Oct 14, 2025 at 9:55 AM Yufei Gu wrote:
> Jonas, thanks for kicking this off! This sounds like a great direction!
> Publishing the Python CLI to PyPI will definitely mak
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
) and to align its release and distribution process with ASF
guidelines. I’ve drafted a prop
16 matches
Mail list logo
