Hi It's not a problem for me to release "part" of Polaris like Helm chart.
However, the release has to be "ASF valid", meaning that the release needs to include source distribution. Today, we don't have source distribution only for Helm chart (it's global source distribution including Helm sources). So, I propose to include a source tar gradle task in Helm chart (with signing and checksum). If we do that, no problem. I can take a crack on this :) Regards JB On Sat, Jul 12, 2025 at 1:30 AM Yufei Gu <flyrain...@gmail.com> wrote: > > Hi everyone, > > While testing the freshly-minted 1.0.0-incubating release, we noticed > something odd: the Polaris release has relational-jdbc persistence, yet the > Helm chart only understands the legacy eclipselink. Here is the issue: > https://github.com/apache/polaris/issues/2030. > > We previously made the decision to publish Helm Chart with Polaris src and > bin, check the ML thread: > https://lists.apache.org/thread/d1vf7xpn6nkzp8gbh417m8qb58tkpcqz. We may > revisit the approach. I think it makes more sense to release the Helm chart > on its own cadence. Not all Polaris users need Helm charts, plus Helm chart > tweaking happens commonly between Polaris server releases. WDYT? > > Meanwhile, we can start to release the nightly Helm Chart as a quick > solution for any users trying the new release with JDBC backend. Thoughts > and volunteers for this one? > > Yufei
