You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Robert Stupp <sn...@snazy.de> on 2025/11/20 11:23:54 UTC
[DISCUSS] Release automation for polaris-tools
Hi all,
I think there is a way to have release automation for polaris-tools
similar to the release automation for the polaris repo.
UX change TL;DR: Start drafting a release with two input parameters:
1. Tool name
2. Tool version
All other steps remain the same as for the polaris repo.
The major implementation difference is that the polaris-tools
workflows become agnostic to which artifacts a specific tool builds
(Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
The effort for each tool would be pretty low, a few very simple
tool-specific shell scripts.
I will come up with a more detailed proposal soon.
Robert
[PROPOSAL] Release automation for polaris-tools
Posted by Robert Stupp <sn...@snazy.de>.
Hi all,
I've created the document [1] explaining the proposal for release
automation for polaris-tools projects. The doc is open for comments.
TL;DR is in the first message of this thread [2].
Robert
[1] https://docs.google.com/document/d/1MpovNXHFxqC1rxw_WhekQujDSj_zOAl4AN2QyFkX23k
[2] https://lists.apache.org/thread/7tlmzwpdc9m4p4dx79jrydxs3x60m875
On Fri, Nov 21, 2025 at 3:24 PM Adam Christian
<ad...@gmail.com> wrote:
>
> That would be fantastic, Robert! I know that the AppRunner, Iceberg Catalog
> Migrator, and the MCP Server would benefit from this greatly!
>
> Go community,
>
> Adam
>
> On Thu, Nov 20, 2025 at 7:07 PM Yufei Gu <fl...@gmail.com> wrote:
>
> > Hi Robert,
> >
> > Thanks so much for driving this! The direction looks great, having a
> > unified but tool-agnostic release flow will make things much smoother for
> > everyone.
> >
> > Excited to see the detailed proposal and happy to help test things out once
> > it’s ready.
> >
> > Yufei
> >
> >
> > On Thu, Nov 20, 2025 at 10:26 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi,
> > >
> > > The ability to release each tool individually is a great improvement!
> > >
> > > I agree that each tool should have its specific method for handling
> > > release resources.
> > >
> > > Thanks, and I look forward to seeing the detailed proposal.
> > >
> > > Regards,
> > > JB
> > >
> > > On Thu, Nov 20, 2025 at 3:23 AM Robert Stupp <sn...@snazy.de> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I think there is a way to have release automation for polaris-tools
> > > > similar to the release automation for the polaris repo.
> > > >
> > > > UX change TL;DR: Start drafting a release with two input parameters:
> > > > 1. Tool name
> > > > 2. Tool version
> > > > All other steps remain the same as for the polaris repo.
> > > >
> > > > The major implementation difference is that the polaris-tools
> > > > workflows become agnostic to which artifacts a specific tool builds
> > > > (Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
> > > >
> > > > The effort for each tool would be pretty low, a few very simple
> > > > tool-specific shell scripts.
> > > >
> > > > I will come up with a more detailed proposal soon.
> > > >
> > > > Robert
> > >
> >
Re: [DISCUSS] Release automation for polaris-tools
Posted by Robert Stupp <sn...@snazy.de>.
Hi all,
Thanks a lot for the positive feedback so far!
I thought I already did, but obviously I totally forgot to send out
the doc for this!
So here it is: https://docs.google.com/document/d/1MpovNXHFxqC1rxw_WhekQujDSj_zOAl4AN2QyFkX23k/
It's open for comments, I propose to keep "high level discussions" in
this thread.
Robert
On Fri, Nov 21, 2025 at 3:24 PM Adam Christian
<ad...@gmail.com> wrote:
>
> That would be fantastic, Robert! I know that the AppRunner, Iceberg Catalog
> Migrator, and the MCP Server would benefit from this greatly!
>
> Go community,
>
> Adam
>
> On Thu, Nov 20, 2025 at 7:07 PM Yufei Gu <fl...@gmail.com> wrote:
>
> > Hi Robert,
> >
> > Thanks so much for driving this! The direction looks great, having a
> > unified but tool-agnostic release flow will make things much smoother for
> > everyone.
> >
> > Excited to see the detailed proposal and happy to help test things out once
> > it’s ready.
> >
> > Yufei
> >
> >
> > On Thu, Nov 20, 2025 at 10:26 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi,
> > >
> > > The ability to release each tool individually is a great improvement!
> > >
> > > I agree that each tool should have its specific method for handling
> > > release resources.
> > >
> > > Thanks, and I look forward to seeing the detailed proposal.
> > >
> > > Regards,
> > > JB
> > >
> > > On Thu, Nov 20, 2025 at 3:23 AM Robert Stupp <sn...@snazy.de> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I think there is a way to have release automation for polaris-tools
> > > > similar to the release automation for the polaris repo.
> > > >
> > > > UX change TL;DR: Start drafting a release with two input parameters:
> > > > 1. Tool name
> > > > 2. Tool version
> > > > All other steps remain the same as for the polaris repo.
> > > >
> > > > The major implementation difference is that the polaris-tools
> > > > workflows become agnostic to which artifacts a specific tool builds
> > > > (Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
> > > >
> > > > The effort for each tool would be pretty low, a few very simple
> > > > tool-specific shell scripts.
> > > >
> > > > I will come up with a more detailed proposal soon.
> > > >
> > > > Robert
> > >
> >
Re: [DISCUSS] Release automation for polaris-tools
Posted by Adam Christian <ad...@gmail.com>.
That would be fantastic, Robert! I know that the AppRunner, Iceberg Catalog
Migrator, and the MCP Server would benefit from this greatly!
Go community,
Adam
On Thu, Nov 20, 2025 at 7:07 PM Yufei Gu <fl...@gmail.com> wrote:
> Hi Robert,
>
> Thanks so much for driving this! The direction looks great, having a
> unified but tool-agnostic release flow will make things much smoother for
> everyone.
>
> Excited to see the detailed proposal and happy to help test things out once
> it’s ready.
>
> Yufei
>
>
> On Thu, Nov 20, 2025 at 10:26 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi,
> >
> > The ability to release each tool individually is a great improvement!
> >
> > I agree that each tool should have its specific method for handling
> > release resources.
> >
> > Thanks, and I look forward to seeing the detailed proposal.
> >
> > Regards,
> > JB
> >
> > On Thu, Nov 20, 2025 at 3:23 AM Robert Stupp <sn...@snazy.de> wrote:
> > >
> > > Hi all,
> > >
> > > I think there is a way to have release automation for polaris-tools
> > > similar to the release automation for the polaris repo.
> > >
> > > UX change TL;DR: Start drafting a release with two input parameters:
> > > 1. Tool name
> > > 2. Tool version
> > > All other steps remain the same as for the polaris repo.
> > >
> > > The major implementation difference is that the polaris-tools
> > > workflows become agnostic to which artifacts a specific tool builds
> > > (Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
> > >
> > > The effort for each tool would be pretty low, a few very simple
> > > tool-specific shell scripts.
> > >
> > > I will come up with a more detailed proposal soon.
> > >
> > > Robert
> >
>
Re: [DISCUSS] Release automation for polaris-tools
Posted by Yufei Gu <fl...@gmail.com>.
Hi Robert,
Thanks so much for driving this! The direction looks great, having a
unified but tool-agnostic release flow will make things much smoother for
everyone.
Excited to see the detailed proposal and happy to help test things out once
it’s ready.
Yufei
On Thu, Nov 20, 2025 at 10:26 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi,
>
> The ability to release each tool individually is a great improvement!
>
> I agree that each tool should have its specific method for handling
> release resources.
>
> Thanks, and I look forward to seeing the detailed proposal.
>
> Regards,
> JB
>
> On Thu, Nov 20, 2025 at 3:23 AM Robert Stupp <sn...@snazy.de> wrote:
> >
> > Hi all,
> >
> > I think there is a way to have release automation for polaris-tools
> > similar to the release automation for the polaris repo.
> >
> > UX change TL;DR: Start drafting a release with two input parameters:
> > 1. Tool name
> > 2. Tool version
> > All other steps remain the same as for the polaris repo.
> >
> > The major implementation difference is that the polaris-tools
> > workflows become agnostic to which artifacts a specific tool builds
> > (Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
> >
> > The effort for each tool would be pretty low, a few very simple
> > tool-specific shell scripts.
> >
> > I will come up with a more detailed proposal soon.
> >
> > Robert
>
Re: [DISCUSS] Release automation for polaris-tools
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
The ability to release each tool individually is a great improvement!
I agree that each tool should have its specific method for handling
release resources.
Thanks, and I look forward to seeing the detailed proposal.
Regards,
JB
On Thu, Nov 20, 2025 at 3:23 AM Robert Stupp <sn...@snazy.de> wrote:
>
> Hi all,
>
> I think there is a way to have release automation for polaris-tools
> similar to the release automation for the polaris repo.
>
> UX change TL;DR: Start drafting a release with two input parameters:
> 1. Tool name
> 2. Tool version
> All other steps remain the same as for the polaris repo.
>
> The major implementation difference is that the polaris-tools
> workflows become agnostic to which artifacts a specific tool builds
> (Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
>
> The effort for each tool would be pretty low, a few very simple
> tool-specific shell scripts.
>
> I will come up with a more detailed proposal soon.
>
> Robert
Re: [DISCUSS] Release automation for polaris-tools
Posted by Ajantha Bhat <aj...@gmail.com>.
Thanks Robert.
Looking forward to using it.
Planning to have a release of `catalog-migrator` once the pening PR[1] is
merged.
I can definitely try the workflow and test it out.
[1] https://github.com/apache/polaris-tools/pull/36
- Ajantha
On Thu, Nov 20, 2025 at 4:54 PM Robert Stupp <sn...@snazy.de> wrote:
> Hi all,
>
> I think there is a way to have release automation for polaris-tools
> similar to the release automation for the polaris repo.
>
> UX change TL;DR: Start drafting a release with two input parameters:
> 1. Tool name
> 2. Tool version
> All other steps remain the same as for the polaris repo.
>
> The major implementation difference is that the polaris-tools
> workflows become agnostic to which artifacts a specific tool builds
> (Maven stuff, tarballs/zip, Python stuff, Docker images, Helm charts).
>
> The effort for each tool would be pretty low, a few very simple
> tool-specific shell scripts.
>
> I will come up with a more detailed proposal soon.
>
> Robert
>