If we can get helpful release script fixes by rebasing the release branch, I think it's worth doing.... then 1.5.0 can follow after the usual (1 month) period.
However, I do not really know how important the missing workflow changes are :) Cheers, Dmitri. On Thu, Apr 9, 2026 at 1:29 PM Alexandre Dutra <[email protected]> wrote: > I also noticed that the most recent commit on the 1.4.x branch is > a69d10579 from March 16th (excluding release workflow fixes), making > it nearly a month old now. Given this gap, should we consider > recreating the 1.4.x branch completely? > > Alternatively, we could proceed with a 1.4.x release as it stands > today and aim for a 1.5.x follow-up shortly thereafter. > > What are your thoughts on this? > > Thanks, > Alex > > On Thu, Apr 9, 2026 at 12:57 PM Alexandre Dutra <[email protected]> wrote: > > > > Hi all, > > > > Indeed we have an issue with the Helm repository. The index.yaml file > > is missing, but oddly enough, the artifacthub-repo.yml is present. > > This led me to think that there is a step missing in > > release-3-build-and-publish-artifacts.yml, where only > > artifacthub-repo.yml is being properly added to SVN. I will open a PR > > shortly to fix this. > > > > This error does not invalidate the release contents per se, but makes > > it impossible to test the staged Helm chart repository. I think it's > > probably best to cancel this vote, fix the issue, and start another > > RC. > > > > What do you think? > > > > Thanks, > > Alex > > > > On Thu, Apr 9, 2026 at 5:03 AM Adnan Hemani via dev > > <[email protected]> wrote: > > > > > > Hi Dmitri, > > > > > > Thanks for the verifications. The email .txt files were generated as > part > > > of the automated release process - I'm really not sure why those are > there > > > either, but didn't change it since I didn't find it to be a big issue. > I'm > > > happy to make a change to remove them for the next release (or as part > of > > > this release if RC1 doesn't pass). > > > > > > I'm not familiar on the helm index background, but can confirm that > there > > > was not an "index.yaml" file generated as part of the GitHub Action. > > > Robert/Pierre, is this something you can confirm that we had consensus > on > > > doing and if the current release should've done this? > > > > > > Best, > > > Adnan Hemani > > > > > > On Tue, Apr 7, 2026 at 12:24 PM Dmitri Bourlatchkov <[email protected]> > > > wrote: > > > > > > > Hi All, > > > > > > > > Voting +0 for now because of the two strange .txt files and helm > index > > > > issue (below) > > > > > > > > Verified: > > > > * Checksums > > > > * Signatures > > > > * Build from source > > > > > > > > So far all clear. > > > > > > > > However: > > > > > > > > $ helm repo add polaris-rc > > > > https://dist.apache.org/repos/dist/dev/polaris/helm-chart > > > > Error: looks like " > > > > https://dist.apache.org/repos/dist/dev/polaris/helm-chart"; > > > > is not a valid chart repository or cannot be reached: failed to fetch > > > > https://dist.apache.org/repos/dist/dev/polaris/helm-chart/index.yaml > : 404 > > > > Not Found > > > > > > > > IIRC, the idea was for the RCs to host a new helm index verbatim. > The index > > > > will then replace the old index at release publication time. This > way we'd > > > > be able to validate its exact contents before making it available to > all > > > > users. > > > > > > > > WDYT? > > > > > > > > Cheers, > > > > Dmitri. > > > > > > > > > > > > > > > > On Tue, Apr 7, 2026 at 3:10 PM Dmitri Bourlatchkov <[email protected] > > > > > > wrote: > > > > > > > > > Hi Adnan, > > > > > > > > > > I see these two files in dist... Do we really need them there? > > > > > > > > > > apache-polaris-1.4.0.vote-email-body.txt > > > > > apache-polaris-1.4.0.vote-email-subject.txt > > > > > > > > > > Thanks, > > > > > Dmitri. > > > > > > > > > > On Mon, Apr 6, 2026 at 9:37 PM Adnan Hemani via dev < > > > > > [email protected]> wrote: > > > > > > > > > >> Hi everyone, > > > > >> > > > > >> I propose that we release the following RC as the official Apache > > > > Polaris > > > > >> 1.4.0 release. (Do not worry, there is no RC0 for this release :) > > > > >> > > > > >> This corresponds to the tag: apache-polaris-1.4.0-rc1 > > > > >> * > https://github.com/apache/polaris/commits/apache-polaris-1.4.0-rc1 > > > > >> * > > > > >> > > > > >> > > > > > https://github.com/apache/polaris/tree/70f7a0288412f80197fca71d5f635ca221eb6331 > > > > >> > > > > >> The release tarball, signature, and checksums are here: > > > > >> * https://dist.apache.org/repos/dist/dev/polaris/1.4.0 > > > > >> > > > > >> Helm charts are available on: > > > > >> * https://dist.apache.org/repos/dist/dev/polaris/helm-chart/1.4.0 > > > > >> > > > > >> NB: you have to build the Docker images locally in order to test > Helm > > > > >> charts. > > > > >> > > > > >> You can find the KEYS file here: > > > > >> * https://downloads.apache.org/polaris/KEYS > > > > >> > > > > >> Convenience binary artifacts are staged on Nexus. The Maven > repositories > > > > >> URLs are: > > > > >> * > > > > >> > > > > > https://repository.apache.org/content/repositories/orgapachepolaris-1063/ > > > > >> > > > > >> Please download, verify, and test according to the release > verification > > > > >> guide, which can be found at: > > > > >> * > > > > >> > > > > >> > > > > > https://polaris.apache.org/community/release-guides/release-verification-guide/ > > > > >> > > > > >> Please vote in the next 96 hours (extra time given due to Iceberg > > > > Summit). > > > > >> > > > > >> [ ] +1 Release this as Apache Polaris 1.4.0 > > > > >> [ ] +0 > > > > >> [ ] -1 Do not release this because... > > > > >> > > > > >> Only PMC members have binding votes, but other community members > are > > > > >> encouraged to cast non-binding votes. > > > > >> This vote will pass if there are 3 binding +1 votes and more > binding +1 > > > > >> votes than -1 votes. > > > > >> > > > > >> Best, > > > > >> Adnan Hemani > > > > >> > > > > > > > > > >
