You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Adnan Hemani via dev <de...@polaris.apache.org> on 2026/04/16 00:39:20 UTC
Apache Polaris Release: Python CLI - PyPI Publishing
Hi all,
There was a request to publish the Python CLI for Polaris to PyPI for
v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote. How
should we proceed? I can either send a separate vote thread for the CLI or
merge it onto the existing RC2 vote thread.
Note: We currently have no verification steps for the CLI. Perhaps we can
address this in the near future?
Best,
Adnan Hemani
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Adnan Hemani via dev <de...@polaris.apache.org>.
Hi all,
Here's the PR for the automated CLI release:
https://github.com/apache/polaris/pull/4220. Please do review!
I will open a new thread for the v1.4.0 CLI, hopefully in a few hours.
Best,
Adnan Hemani
On Thu, Apr 16, 2026 at 12:15 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Awesome, thanks Adnan!
>
> Let me know if I can help on anything (PRs review, etc) and looking
> forward for the vote on the CLI release :)
>
> Regards
> JB
>
> On Thu, Apr 16, 2026 at 8:38 AM Adnan Hemani via dev <
> dev@polaris.apache.org> wrote:
>
>> Hi JB,
>>
>> Thanks for these pointers. I've almost got the changes working to automate
>> these via the PyPI Trusted Workflow, so I will open this PR soon and send
>> out a new VOTE thread for the CLI for 1.4.0. As suggested, the PR will
>> make
>> a change to include this artifact as part of all future release candidates
>> after the version 1.4.0 one.
>>
>> Best,
>> Adnan Hemani
>>
>> On Wed, Apr 15, 2026 at 11:02 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>> > Hi Kevin,
>> >
>> > Yes and no: if the source distribution MUST be included in a release
>> > (that's the only required artifact), any other artifacts published (for
>> > user convenience) should also be reviewed and covered by the vote.
>> > That's why the Maven Staging repository is included in the release vote
>> for
>> > instance.
>> >
>> > Anything we publish as part of a release (PyPI publication, for
>> instance)
>> > should be reviewed and covered by the vote.
>> >
>> > Regards
>> > JB
>> >
>> > On Thu, Apr 16, 2026 at 4:47 AM Kevin Liu <ke...@apache.org>
>> wrote:
>> >
>> > > Thanks for flagging this! I'd suggest we skip the PyPI publish for
>> 1.4.0
>> > > since the RC is already out.
>> > >
>> > > From the ASF's perspective, the source artifact is what matters most
>> for
>> > > releases; that's the "source" in open source 😄
>> > > PyPI packages are really just a convenience for users, and they can
>> > always
>> > > build the CLI locally from the 1.4.0 source. See the ASF release
>> policy
>> > for
>> > > reference:
>> > > https://www.apache.org/legal/release-policy.html#compiled-packages
>> > >
>> > > For the next release, we can properly include the PyPI publication as
>> > part
>> > > of the RC process and add the verification steps you mentioned.
>> PyIceberg
>> > > has solid release instructions we could reference:
>> > > https://py.iceberg.apache.org/how-to-release/
>> > >
>> > > Best,
>> > > Kevin Liu
>> > >
>> > > On Wed, Apr 15, 2026 at 5:39 PM Adnan Hemani via dev <
>> > > dev@polaris.apache.org>
>> > > wrote:
>> > >
>> > > > Hi all,
>> > > >
>> > > > There was a request to publish the Python CLI for Polaris to PyPI
>> for
>> > > > v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote.
>> How
>> > > > should we proceed? I can either send a separate vote thread for the
>> CLI
>> > > or
>> > > > merge it onto the existing RC2 vote thread.
>> > > >
>> > > > Note: We currently have no verification steps for the CLI. Perhaps
>> we
>> > can
>> > > > address this in the near future?
>> > > >
>> > > > Best,
>> > > > Adnan Hemani
>> > > >
>> > >
>> >
>>
>
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Awesome, thanks Adnan!
Let me know if I can help on anything (PRs review, etc) and looking forward
for the vote on the CLI release :)
Regards
JB
On Thu, Apr 16, 2026 at 8:38 AM Adnan Hemani via dev <de...@polaris.apache.org>
wrote:
> Hi JB,
>
> Thanks for these pointers. I've almost got the changes working to automate
> these via the PyPI Trusted Workflow, so I will open this PR soon and send
> out a new VOTE thread for the CLI for 1.4.0. As suggested, the PR will make
> a change to include this artifact as part of all future release candidates
> after the version 1.4.0 one.
>
> Best,
> Adnan Hemani
>
> On Wed, Apr 15, 2026 at 11:02 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi Kevin,
> >
> > Yes and no: if the source distribution MUST be included in a release
> > (that's the only required artifact), any other artifacts published (for
> > user convenience) should also be reviewed and covered by the vote.
> > That's why the Maven Staging repository is included in the release vote
> for
> > instance.
> >
> > Anything we publish as part of a release (PyPI publication, for instance)
> > should be reviewed and covered by the vote.
> >
> > Regards
> > JB
> >
> > On Thu, Apr 16, 2026 at 4:47 AM Kevin Liu <ke...@apache.org> wrote:
> >
> > > Thanks for flagging this! I'd suggest we skip the PyPI publish for
> 1.4.0
> > > since the RC is already out.
> > >
> > > From the ASF's perspective, the source artifact is what matters most
> for
> > > releases; that's the "source" in open source 😄
> > > PyPI packages are really just a convenience for users, and they can
> > always
> > > build the CLI locally from the 1.4.0 source. See the ASF release policy
> > for
> > > reference:
> > > https://www.apache.org/legal/release-policy.html#compiled-packages
> > >
> > > For the next release, we can properly include the PyPI publication as
> > part
> > > of the RC process and add the verification steps you mentioned.
> PyIceberg
> > > has solid release instructions we could reference:
> > > https://py.iceberg.apache.org/how-to-release/
> > >
> > > Best,
> > > Kevin Liu
> > >
> > > On Wed, Apr 15, 2026 at 5:39 PM Adnan Hemani via dev <
> > > dev@polaris.apache.org>
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > There was a request to publish the Python CLI for Polaris to PyPI for
> > > > v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote.
> How
> > > > should we proceed? I can either send a separate vote thread for the
> CLI
> > > or
> > > > merge it onto the existing RC2 vote thread.
> > > >
> > > > Note: We currently have no verification steps for the CLI. Perhaps we
> > can
> > > > address this in the near future?
> > > >
> > > > Best,
> > > > Adnan Hemani
> > > >
> > >
> >
>
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Adnan Hemani via dev <de...@polaris.apache.org>.
Hi JB,
Thanks for these pointers. I've almost got the changes working to automate
these via the PyPI Trusted Workflow, so I will open this PR soon and send
out a new VOTE thread for the CLI for 1.4.0. As suggested, the PR will make
a change to include this artifact as part of all future release candidates
after the version 1.4.0 one.
Best,
Adnan Hemani
On Wed, Apr 15, 2026 at 11:02 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi Kevin,
>
> Yes and no: if the source distribution MUST be included in a release
> (that's the only required artifact), any other artifacts published (for
> user convenience) should also be reviewed and covered by the vote.
> That's why the Maven Staging repository is included in the release vote for
> instance.
>
> Anything we publish as part of a release (PyPI publication, for instance)
> should be reviewed and covered by the vote.
>
> Regards
> JB
>
> On Thu, Apr 16, 2026 at 4:47 AM Kevin Liu <ke...@apache.org> wrote:
>
> > Thanks for flagging this! I'd suggest we skip the PyPI publish for 1.4.0
> > since the RC is already out.
> >
> > From the ASF's perspective, the source artifact is what matters most for
> > releases; that's the "source" in open source 😄
> > PyPI packages are really just a convenience for users, and they can
> always
> > build the CLI locally from the 1.4.0 source. See the ASF release policy
> for
> > reference:
> > https://www.apache.org/legal/release-policy.html#compiled-packages
> >
> > For the next release, we can properly include the PyPI publication as
> part
> > of the RC process and add the verification steps you mentioned. PyIceberg
> > has solid release instructions we could reference:
> > https://py.iceberg.apache.org/how-to-release/
> >
> > Best,
> > Kevin Liu
> >
> > On Wed, Apr 15, 2026 at 5:39 PM Adnan Hemani via dev <
> > dev@polaris.apache.org>
> > wrote:
> >
> > > Hi all,
> > >
> > > There was a request to publish the Python CLI for Polaris to PyPI for
> > > v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote. How
> > > should we proceed? I can either send a separate vote thread for the CLI
> > or
> > > merge it onto the existing RC2 vote thread.
> > >
> > > Note: We currently have no verification steps for the CLI. Perhaps we
> can
> > > address this in the near future?
> > >
> > > Best,
> > > Adnan Hemani
> > >
> >
>
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Kevin,
Yes and no: if the source distribution MUST be included in a release
(that's the only required artifact), any other artifacts published (for
user convenience) should also be reviewed and covered by the vote.
That's why the Maven Staging repository is included in the release vote for
instance.
Anything we publish as part of a release (PyPI publication, for instance)
should be reviewed and covered by the vote.
Regards
JB
On Thu, Apr 16, 2026 at 4:47 AM Kevin Liu <ke...@apache.org> wrote:
> Thanks for flagging this! I'd suggest we skip the PyPI publish for 1.4.0
> since the RC is already out.
>
> From the ASF's perspective, the source artifact is what matters most for
> releases; that's the "source" in open source 😄
> PyPI packages are really just a convenience for users, and they can always
> build the CLI locally from the 1.4.0 source. See the ASF release policy for
> reference:
> https://www.apache.org/legal/release-policy.html#compiled-packages
>
> For the next release, we can properly include the PyPI publication as part
> of the RC process and add the verification steps you mentioned. PyIceberg
> has solid release instructions we could reference:
> https://py.iceberg.apache.org/how-to-release/
>
> Best,
> Kevin Liu
>
> On Wed, Apr 15, 2026 at 5:39 PM Adnan Hemani via dev <
> dev@polaris.apache.org>
> wrote:
>
> > Hi all,
> >
> > There was a request to publish the Python CLI for Polaris to PyPI for
> > v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote. How
> > should we proceed? I can either send a separate vote thread for the CLI
> or
> > merge it onto the existing RC2 vote thread.
> >
> > Note: We currently have no verification steps for the CLI. Perhaps we can
> > address this in the near future?
> >
> > Best,
> > Adnan Hemani
> >
>
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Yufei Gu <fl...@gmail.com>.
We've planned the CLI publish for quite a while, and are targeting version
1.4.0 to deliver it. Many users requested it. Since we already have the
Polaris binary package, I think including this as one additional binary
package doesn't seem too much additional work. We may need to send out
another vote email (we can still call it RC2 since the source code isn't
changing at all) and add the CLI link from test.pypi.org. I understand it
requires extra voting, but it seems the most convenient way to publish the
CLI tool.
> Note: We currently have no verification steps for the CLI. Perhaps we can
address this in the near future?
We could verify it manually this time.
Yufei
On Wed, Apr 15, 2026 at 7:47 PM Kevin Liu <ke...@apache.org> wrote:
> Thanks for flagging this! I'd suggest we skip the PyPI publish for 1.4.0
> since the RC is already out.
>
> From the ASF's perspective, the source artifact is what matters most for
> releases; that's the "source" in open source 😄
> PyPI packages are really just a convenience for users, and they can always
> build the CLI locally from the 1.4.0 source. See the ASF release policy for
> reference:
> https://www.apache.org/legal/release-policy.html#compiled-packages
>
> For the next release, we can properly include the PyPI publication as part
> of the RC process and add the verification steps you mentioned. PyIceberg
> has solid release instructions we could reference:
> https://py.iceberg.apache.org/how-to-release/
>
> Best,
> Kevin Liu
>
> On Wed, Apr 15, 2026 at 5:39 PM Adnan Hemani via dev <
> dev@polaris.apache.org>
> wrote:
>
> > Hi all,
> >
> > There was a request to publish the Python CLI for Polaris to PyPI for
> > v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote. How
> > should we proceed? I can either send a separate vote thread for the CLI
> or
> > merge it onto the existing RC2 vote thread.
> >
> > Note: We currently have no verification steps for the CLI. Perhaps we can
> > address this in the near future?
> >
> > Best,
> > Adnan Hemani
> >
>
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Kevin Liu <ke...@apache.org>.
Thanks for flagging this! I'd suggest we skip the PyPI publish for 1.4.0
since the RC is already out.
From the ASF's perspective, the source artifact is what matters most for
releases; that's the "source" in open source 😄
PyPI packages are really just a convenience for users, and they can always
build the CLI locally from the 1.4.0 source. See the ASF release policy for
reference:
https://www.apache.org/legal/release-policy.html#compiled-packages
For the next release, we can properly include the PyPI publication as part
of the RC process and add the verification steps you mentioned. PyIceberg
has solid release instructions we could reference:
https://py.iceberg.apache.org/how-to-release/
Best,
Kevin Liu
On Wed, Apr 15, 2026 at 5:39 PM Adnan Hemani via dev <de...@polaris.apache.org>
wrote:
> Hi all,
>
> There was a request to publish the Python CLI for Polaris to PyPI for
> v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote. How
> should we proceed? I can either send a separate vote thread for the CLI or
> merge it onto the existing RC2 vote thread.
>
> Note: We currently have no verification steps for the CLI. Perhaps we can
> address this in the near future?
>
> Best,
> Adnan Hemani
>
Re: Apache Polaris Release: Python CLI - PyPI Publishing
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
An official Apache release is one which has been endorsed as an "act of the
Foundation" by a PMC.
Generically, a release is anything that is published beyond the group that
owns it. For an Apache project, that means any publication outside the
development community, defined as individuals actively participating in
development or following the dev list.
So, anything we published should be reviewed/votes by a release.
We can't change RC2 else it would mean cancel and vote on a RC3.
I would suggest to start a vote "[VOTE] Polaris Python CLI 1.4.0 (rc1)" for
the CLI review.
The source distribution can point to the source distribution already in
dist (as it already includes the CLI), and point to test.pypi.org for
"binary" review.
The verification is manual for this one.
I propose to work on this for the next release.
Regards
JB
On Thu, Apr 16, 2026 at 2:39 AM Adnan Hemani via dev <de...@polaris.apache.org>
wrote:
> Hi all,
>
> There was a request to publish the Python CLI for Polaris to PyPI for
> v1.4.0 earlier that I missed when sending 1.4.0 RC2 out for a vote. How
> should we proceed? I can either send a separate vote thread for the CLI or
> merge it onto the existing RC2 vote thread.
>
> Note: We currently have no verification steps for the CLI. Perhaps we can
> address this in the near future?
>
> Best,
> Adnan Hemani
>